You are here: Admin Explorer > Requirements > Requirements Overview

Requirements Overview

Requirements can be defined in the Rules Palette and then attached to specific transactions. When those transactions process as activities in OIPA, the requirement conditions must be met in order for the activity to process. If the requirement conditions are not met, then a requirement icon is generated next to the activity and the activity will remain in a pending status. Once the requirement is met, the activity can be processed.

The Prototype Company provides an example of requirement processing. View the prototype example for additional information.

Set-up Requirements

There are two steps involved in setting up requirements:

Create a requirement definition. The AsRequirementDefinition table holds the information entered while creating a new requirement definition.
Configure the requirement. There are two additional requirement tables that hold requirement information entered when configuring the requirement. They are AsRequirementCriteria and AsRequirementGroup.

Attach Requirement to a Transaction

After requirements are created and configured, they can be associated with transactions. The requirements will prevent the transaction from processing as an activity in OIPA until all criteria are met.

Requirements are associated with transactions through the GeneratePendingRequirements and DeliveryRequirements business rules. Attach these two rules to the transaction. Then open the attached rules and configure them as needed.

When adding the requirement business rules to a transaction, GeneratePendingRequirements MUST ALWAYS appear in the rule list before DeliveryRequirements.