Oracle® Insurance Rules Palette
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.
- 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.
- <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.
- 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'.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices