Workflow Configuration and Performance

Table 2-1. What not to include in PPM Center workflow lists the practices that We recommend you avoid as you configure the workflows for the requests, packages and deployments, in PPM.

Table 2-1. What not to include in PPM Center workflow



Tight loops

Tight loops of execution steps can be run faster than backend processing occurs. For example, if the loop depends on a backend update, the backend update may not have occurred before the loop is running again.

Transitions back to the workflow step itself, resulting in infinite loops

For example, "Failed" results are often used as a transition to loop back to the execution itself. Such a loop can cause indefinite processing, thereby slowing the entire system.

Unnecessary execution steps

Unless step-by-step commits are required, combine execution steps into one database function or procedure. Too many execution steps can degrade workflow performance.

If you require custom functions or procedures, use autonomous transactions, or use built-in special commands in an execution step.