Activity Requirement Screen Prototype
This prototype was configured to demonstrate the recently renamed ActivityRequirementScreen (formerly RequirementScreen) business rule.
Prototype Prerequisites
- OIPA user credentials for the Functional Prototype Plan
Prototype Configuration
-
The ContractRenew transaction was created to demonstrate that the ActivityRequirementScreen business rule functions exactly as it did before it was renamed. In the Main Explorer window, navigate to Companies | Prototype |Products (if Products are enabled) | Individual Prototype Product (if Products are enabled) | Plans | Functional Prototype Plan | Transactions | Policy Transaction | ContractRenew to view the transaction configuration.
- The DeliveryRequirements business rule has been attached to the ContractRenew transaction to facilitate requirement processing, as is typical for transaction requirement configuration. In the Main Explorer window, navigate to Companies | Prototype |Products (if Products are enabled) | Individual Prototype Product (if Products are enabled) | Plans | Functional Prototype Plan | Transactions | Policy Transaction | ContractRenew | Attached Rules | DeliveryRequirements to view the business rule configuration. The key configuration for this business rule is explained below. This is previously existing functionality.
- The OpenDate and CloseDate fields of the ContractRenew activity are both required to have values for the activity to process
- The GeneratePendingRequirements business rule has been attached to the ContractRenew transaction to facilitate requirement processing, as is typical for transaction requirement configuration. In the Main Explorer window, navigate to Companies | Prototype |Products (if Products are enabled) | Individual Prototype Product (if Products are enabled) | Plans | Functional Prototype Plan | Transactions | Policy Transaction | ContractRenew | Attached Rules | GeneratePendingRequirements to view the business rule configuration. The key configuration for this business rule is explained below. This is previously existing functionality.
- The PlanGUID of the plan to which the transaction belongs must match that defined in the AsRequirementDefinition database table
- The values of the RenewalDate and DueDate fields will be copied from the RenewalDateMV and DueDateMV MathVariables, respectively.
View Prototype in OIPA
- Log in to a Rules Palette environment.
- In the Global Rules Explorer window, navigate to Business Rules | Screen | ActivityRequirementScreen.
- Open the ActivityRequirementScreen XML file.
- Note that the parent tag of the rule has been changed from <RequirementScreen> to <ActivityRequirementScreen>.
- Log in to OIPA using credentials for a user belonging to the Functional Prototype Plan.
- Open a policy or create a shell policy.
- Add the ContractRenew activity.
- Process the ContractRenew activity.
- On the Activity screen, click the icon to the left of the activity name to open the Activity Requirement screen.
- Enter a date in the Close Date field. Doing so will satisfy the requirement specified in the DeliveryRequirements business rule attached to the activity.
- Click OK.
- Process the activity. It should process as is expected.