Pre and Post Process Triggers on State or Transition Changes in Work Item Workflows

The Pre and Post Process fields can be found in the Processes tab of both the Workflow State Edit and Transition Edit dialog boxes of Work Item Workflows allowing you to leverage the power of database stored procedures to execute various functions. The primary purpose of these fields is to empower you with the capability to define and implement your own custom business rules that will be executed either before or after a Transition or a State in the workflow process.

You can seamlessly integrate your unique business logic into the workflow management system, streamlining your operations and maximizing efficiency. The utilization of database stored procedures ensures that the business rules defined in the Pre and Post Process fields are executed with precision and reliability, contributing to a seamless and efficient workflow process. As a result, you can stay in control of your business operations, ensuring that each step in the workflow is optimized to meet your specific needs and requirements.

When transitioning from the source State to the target State, the execution sequence of the custom Stored Procedure is as follows:

1. Post process Stored Procedure for the source State is called (can be a validating Stored Procedure)
2. Pre process Stored Procedure for the Transition is called (can be a validating Stored Procedure)
3. Post process Stored Procedure for the Transition is called (called after Transition is committed to the database, ideally with no validation)
4. Post process Stored Procedure for the target State SP is called (called after transition is committed to the database, ideally with no validation)

Note: To create the stored procedures, contact your PSA Project Manager or Customer Success Manager to discuss your needs further.