PostAssignmentValidateExpressions Enhancements Prototype
New functionality has been added to allow values from the PostAssignmentValidateExpressions business rule to be accessible on the Verification screen, Activity Summary and Transaction Cosmetics.
Prototype Prerequisites
- NUVs must exist for the funds that are selected for allocation for the processing of the transaction. Otherwise, the transaction will go into NUVPending status upon processing.
- The error number DCM666 must exist in the AsErrorCatalog database table.
Prototype Explanation
The following transactions and business rules were configured in the Model Prototype Plan in the Prototype Company to demonstrate this new functionality.
Transactions
- PremiumWithAllocation: This transaction is configured to allow the user to enter a premium amount and then to select the funds to which this amount should be allocated. To view the prototype configuration, navigate in the Main Explorer to Companies | Prototype Company | Plans | Model Prototype Plan | Transactions | PremiumWithAllocation. The key configuration for this transaction is explained below.
- The <Field> section is configured for the Premium Amount field, which allows the user to enter the amount of the policy's premium.
Business Rules
-
PostAssignmentValidateExpressions: This business rule is attached to the PremiumWithAllocation transaction. It contains configuration to calculate the policy's existing cash value using a math variable, as well as to generate error or warning messages in certain situations. To view the prototype configuration, navigate in the Main Explorer to Companies | Prototype Company | Plans | Model Prototype Plan | Business Rules |Attached Rules | PostAssignmentValidateExpressions. The key configuration for this business rule is explained below.
- The <MathVariables> section contains configuration for a math variable called CurrentCashValue, which is calculated by adding the policy's existing cash value to the premium amount entered by the user.
- The <ValidateExpressions> section contains configuration for two validations:
- The first expression throws an error if the policy has no existing cash value. The OVERRIDABLE attribute is set to "Auto", meaning that the error will be automatically overridden. The client number of the user who views the error window and presses "OK" will be recorded against the overriding user in the activity XML.
- The second expression displays a warning message if the premium amount entered by the user is greater than 5000. This expression includes an error number, on which the error message and Error Fix Tip shown on the Verification screen are based.
Note | Note: The following business rules have been configured to show the accessibility of the PostAssignmentValidateExpressions math variable across these business rules. |
- VerificationScreen: This business rule is attached to the PremiumWithAllocation transaction To view the prototype configuration, navigate in the Main Explorer to Companies | Prototype Company | Plans | Model Prototype Plan | Business Rules |Attached Rules | VerificationScreen. The key configuration for this business rule is explained below.
- A field is configured to access the math variable CurrentCashValue, which is configured in the PostAssignmentValidateExpressions attached rule.
- ActivitySummary: This business rule is attached to the PremiumWithAllocation transaction To view the prototype configuration, navigate in the Main Explorer to Companies | Prototype Company | Plans | Model Prototype Plan | Business Rules |Attached Rules | ActivitySummary. The key configuration for this business rule is explained below.
- A field is configured in the <MathandFields> section to access the math variable CurrentCashValue, which is configured in the PostAssignmentValidateExpressions attached rule.
- TransactionCosmetics: This business rule is attached to the PremiumWithAllocation transaction To view the prototype configuration, navigate in the Main Explorer to Companies | Prototype Company | Plans | Model Prototype Plan | Business Rules |Attached Rules | TransactionCosmetics. The key configuration for this business rule is explained below.
- A field is configured in the <AmountField> section to access the math variable CurrentCashValue, which is configured in the PostAssignmentValidateExpressions attached rule.
View Prototype in OIPA
- Log in to OIPA using the Prototype Company user ID and password.
- Open a policy or create a shell policy.
- Add the PremiumWithAllocation activity and enter a premium amount over 5000.
- Process the activity. Note that a warning appears alerting the user to the amount of the premium.
- View the Verification screen, Activity Summary and/or Transaction Cosmetics for the activity and note that the value from the CurrentCashValue math variable in the ValidateExpressions rule is utilized.