Requirements

Open

Fields:

• ID - This is a unique ID that will be used in the ABAP user exit to determine if the Requirement is true or false.

• Description - This is the friendly name that is shown in the workflow designer when configuring the requirements in Tasks and Task Outcomes. 

Requirements are used to control two sets of behavior:

1. Tasks
   
   Tasks have associated Requirements that will inform the workflow engine whether that task should be executed or not.
   
   

2. Task Outcomes
   
   Task actions have Outcomes.  Each outcome can also be configured based on a Requirement.  This is an alternative to the above method.
   
   

Determining whether a Requirement is True or False

To determine if a requirement is met or not, the ABAP user exit "Evaluate Task/Outcome Requirements" should be implemented.

Open

An example of how to implement the Value Greater than $1,000 example is shown below.  The code checks the Data Model for a Field called TotalAmount and will set the e_required field true of false accordingly.  This example is working with the Requirement with ID of VALUEGT1000 but as many requirements as needed can be placed in the CASE block. 

Open