Multifield Events
This prototype demonstrates event functionality within the MultiFields section of a transaction. You will see how transaction field and math is used to trigger changes to multifields and also how action/events are configured within a MultiField business rule to trigger changes to a specific multifield section.
The Multifield action and event processing in screen business rules ensures that the functionality is extended to all other screens BR such as client, role etc.
Configuration Requirements
- There are two pieces of configuration required to demonstrate this prototype. First, a Multifield rule must be configured to define the characteristics of the multifield. Then a transaction must be configured to display the multifields and allow user selections.
- User should have access to "Functional Prototype Plan".
Prototype Configuration
- The Mulitfields business rule called MultiField-MultiFieldEvents demonstrates the ability to use Events within a MultiField section. Navigate to Global Explorer | Business Rules | System | MultiField-MultiFieldEvents to view the prototype configuration. The following event functionality is included in the prototype:
- In the <Actions> section, OnLoad, OnChange and OnSubmit are configured.
- In the <ActionSets> section, Assign, Hide, Disable, Enable and Show are configured. These actions are applied in three scenarios. First, to impact an entire multifield, second, to impact an index from a multifield. Third, to impact a single field in a single row of the multifield.
- In the ComboTestMF multifield, the <Actions> section has a QuerySet that uses the action types OPTIONS and SQLQUERY.
- In the TextTestMF multifield, the <ActionSet> TestTextActionOnChange uses MultiValueFieldIndex in Conditions.
- In the TextTestMF multifield, the <ActionSet> TestTextActionOnChange uses $$$MultiValueFieldIndex$$$ substitution in an error message.
- The MultiFieldEvents transaction demonstrates the ability for transaction configuration to trigger events on multifields. Navigate to Global Explorer | Transactions | MultiFieldEvents (Functional Prototype Plan) to view the prototype configuration. The following event functionality is included in the prototype:
- <MultifFields> element identifies the multifield rule that should be called.
- In the <Actions> section, OnLoad, OnChange and OnSubmit are configured.
- In the <ActionSets> section, Assign, Hide, Disable, Enable and Show are configured. These actions are applied in three scenarios. First, to impact an entire multifield, second, to impact an index from a multifield. Third, to impact a single field in a single row of the multifield.
- In the <ActionSet> TestTextActionOnLoad, ScreenMath from the transaction is pulled into a multifield.
- In the <ActionSet> TestTextActionOnChange, a transaction field value is assigned to a multifield.
- A set of actions and event is added to AddressScreen, PolicyScreen, ClientScreen, MultiFields-Phones, MultiFields-PrototypePolicyScreen and MultiFields-AccountNumber which is present at the 'PrototypeCompany' level and a new field 'Some Integer' field is added to 'MultiFields-PrototypePolicyScreen' business rule.
- AddressScreen: This business rule is modified by adding 'CallExternalEvent' and 'CalledEvent'. When the user does not add a value to 'PhoneNumber' field which is present in 'MultiFields-Phones' business rule, user will be prompted with a warning 'PhoneNumber is a required field'.
- PolicyScreen: This business rule is modified by adding 'CallExternalEvent' and 'CalledEvent'. When the user does not add a value to 'Some Integer' field which is present in 'MultiFields-PrototypePolicyScreen' business rule, user will be prompted with a warning 'Some Integer' is a required field'.
- ClientScreen: This business rule is modified by adding 'CallExternalEvent' and 'CalledEvent'. When the user does not add a value to 'BankAccountNumber' field which is present in 'MultiFields-AccountNumber' business rule, user will be prompted with a warning 'BankAccountNumber is a required field'.
View Prototype in OIPA
- Log in OIPA using the Prototype Company user ID and password.
- Click Policy | New from the Main menu.
- Add a shell policy to test the prototype.
- Click Add Activity on the Secondary menu.
- Select the MultifieldEvents activity from the Activity drop down box.
- Make changes to the various fields to view the action event functionality.