Constraints on allowable values are set on the Type. Conditions can be set in terms of field values, and in the case of IBPL the values of the target. One condition which doesn't appear is the user's group membership. We would like our automated system users to be exempt from constraints. As it is now, we have to add the user into a field in order to make constraints not apply to them. This would be much less trouble if the whole group of automated users could be designated at the Type itself. Better yet would be to disable constraint checking for all triggers.
This request is a simpler option in lieu of https://community.ptc.com/t5/Integrity-Ideas/Soft-Constraints-non-blocking-filters/idi-p/458629 , which is the more preferred solution to the problems we face. If this would be easier to have included in a future version of Integrity then that would be okay.