Share this page

# Validations and Execution Type Relationships

There is a correlation between the validation and the execution type. For data-dependent transitions (token, SQL, PL/SQL), the validation must contain all possible values of the query or token resolution. Otherwise, the execution step could result in a value that is not defined for the process, and the request or package line could become stuck in a workflow step.

For most built-in workflow events and executions that run commands, the validation often includes the standard workflow results (Success or Failure). If the commands or event run without error, the result of Success is returned. Otherwise, Failure is returned.

Table 3-5. Relationship between validation and execution types summarizes this relationship.

Table 3-5. Relationship between validation and execution types
Execution Types | Validation Notes
--- | ---
Built-in workflow event and workflow step commands | Typically use a variation of the WF - Standard Execution Results validation (Succeeded or Failed). A few of the workflow events have specific validation requirements: wf_return wf_jump wf_receive
PL/SQL function | Validation must contain all possible values returned by the function.
Token | Validation must contain all possible values for the token.
SQL statement | Validation must contain all possible values for the SQL query. You can use the same SQL in the validation (drop-down or auto-complete list) minus the WHERE clause.

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: