Processing Constraints

Processing Constraints

Processing constraints are rules that control who can change what and when they can change it. Processing constraints can prevent certain changes, but can also be set up to perform actions based on those changes. They can define actions that can result from these changes, such as requiring a reason for the change, triggering an action in Audit Trail or Versioning, or raising an Integration Event.

In this example, we’ll create a processing constraint where a user is not able to change the PO number once the order is booked

Navigate to Setup > Rules > Security > Processing Constraints & give details as shown below

Save the record & create a sales order to check it

Book the order & try to change the PO number & you’ll get the following error

Now create a new processing constraint where if we are changing the order line details once the order is booked, the system will ask for a reason & will generate the next version

Navigate to Setup > Rules > Security > Processing Constraints & give details as shown below

User action value is : ‘Generate Version & Require Reason’

Save the record & book the order. Once booked, change the order quantity

Now change the quantity & save the record

Change once again & version 2 will be generated

In order to see the versions, navigate to Actions à Version History & we can see the different versions