Oracle® Rules Palette Release 9.1.0.0.0 E15811-01

# Events Pane

Action Events provide the ability to perform actions on a field when an event occurs on the screen. Configuration is done by establishing user events and linking them to Action Sets via ID attributes. So when the user selects something in OIPA an event invokes a set of Action Sets that change fields or displays messages.

There are various types of Action Events that you can configure.

- create custom error and warning messages that appear to the end user after the system validates what was entered.

- change whether fields are enabled or disabled when an event occurs.

- change whether fields are hidden or displayed.

- change a field’s data according to the value in a trigger field.

Configuration is performed through the Events pane located on the menu bar across the top of the Configuration Area.

IMPORTANT: Please see the V9 XML Configuration topic in this help system for a list of all elements, attributes and values needed for configuration. View Transaction Rules | Transaction Elements | ActionEvents.

######

High Level Steps to Configure Action Events

1. Configure the fields that the actions can be applied to.

2. Configure the event that needs to occur to invoke the actions. This is done using XML.

3. Identify the set of actions, ScreenMath, QuerySets and/or ActionSet, that are configured in the event.

- If needed, configure ScreenMath to define the math that is available for use when an event is invoked. You can configure global or local math for use by fields.

- If changing field data, configure a QuerySet that defines the data used to populate combo boxes according to a trigger field’s value.

- If creating errors, warnings or controlling a field, configure an ActionSet that defines the action to be performed on a field.

#### Configure an Event

The events section identifies the type of event that needs to occur to invoke a set of actions. It also identifies the field that is connected to the event.

The available event TYPEs that can invoke an action are:

- ONLOAD - runs the event on the initial load of the screen.

- ONCHANGE - runs the event when a trigger field is changed.

- ONSUBMIT - processes the event when the final submission on the screen is selected.

Steps to Configure an Event

1. Check-out the transaction, segment or business rule's XML file.

2. Click the Events tab. The Event Navigator window will open.

3. Double-click the Events node. The XML data will open on the Configuration Area.

4. Configure the event. You need to identify the event TYPE and, if applicable, the FIELD that the event applies to.

5. Configure any combination of Math, ActionSets and/or QuerySets. Each action ID attribute must having a matching action.

6. Check-in the file to save the changes to the database.

######

#### Define Action

There are three types of actions that you can configure: (You may use any combination of the options listed below.)

- Math identifies a set of math configuration to be used for the event called ScreenMath.

- ActionSets identifies a set of action configuration to be used for the event.

- QuerySets identifies a set of query configuration to be used for the event.

#### ScreenMath

In order to perform field math to support actions you must configure the <ScreenMath> section. In <ScreenMath> you will configure <Math> sub-elements that are each identified with an ID so that events may locate it for use. This is different from the <Math> section, because it provides the ability to perform calculations for the Fields section. ScreenMath is not available for use in the main transaction <Math> section.

The <ScreenMath> is identified through a configurable ID and can include two types of <Math>:

- Global ScreenMath: All fields can use math in this section. It is only loaded on the initial load of the screen and cannot use field values.

- Local ScreenMath: This is invoked when indicated by an action. Fields may be used; however, the configuror must be aware that the ScreenMath logic must be configured in such a way as to ensure that all fields being used take into consideration all of the calls to the use of the ScreenMath for that ID.

There can only be one GLOBAL ScreenMath section. The GLOBAL attribute with a value of Yes indicates to the system that the math is global. Without the GLOBAL attribute the system identities the <Math> as local. The global ScreenMath is available in the local ScreenMath section. Local ScreenMath is not available in global ScreenMath. When naming ScreenMath you cannot name global and local math the same. If you do then the local math will take precedence.

Steps to Configure Screen Math

1. Check-out the transaction, segment or business rule's XML file.

2. Click the Events tab. The Event Navigator window will open.

3. Right-click the Screen Math node and select New Math Section.

4. Enter the Section ID, which is the name of your ScreenMath.

5. Check the Global box if the math you are configuring is global math.

6. Select Finish.

7. Configure the math section by dragging and dropping math variables from the Palette window.

8. Check-in the XML file to save your changes to the database.

Note: You can view the ScreenMath XML from the XML Source pane. See image below.

######

#### QuerySets

QuerySets allow you to load combo boxes with a SQL statement, as well as define a set of hard coded combo box options. <QuerySet> is a sub-element of <Actions> and each <QuerySet> is identified with an ID attribute that the <Event> section uses to locate the correct configuration.

When configuring the change of combo box data, make sure to use the FIELD attribute in the corresponding <Event> section for the trigger field. In the <QuerySet> sub-element use the FIELD attribute for the field that will have its data changed.

You can also write conditional logic in this section.

- Compare single values by writing expressions. Please see the V9 XML Configuration topic in this help system for a list of all elements, attributes and values needed for configuration. View Common Elements | Operations Available for Expression Writing.

- Use available functions.

- Use Global and Local math (Must use MathID prefix).

- Compare dates.

######

Steps to Configure Action with QuerySets

1. Check-out the transaction, segment or business rule's XML file.

2. Click the Events tab. The Event Navigator window will open.

3. Double-click the Actions node. The XML data will open on the Configuration Area.

4. Configure the action by defining the QuerySets needed for the event. A sample is shown above.

5. Check-in the file to save the changes to the database.

#### ActionSets

ActionSets allow for the configuration of errors and warnings, enabling fields, disabling fields, hiding fields, displaying fields and assigning a value to a field. <ActionSet> is a sub-element of the <Actions> and each <ActionSet> is identified with an ID attribute that the <Event> section uses to locate the correct configuration.

There is also the ability to write conditional logic in the section. Available logic includes:

- Compare single values by writing expressions.

- Use available functions.

- Use global and local math (must use MathID prefix).

- Compare dates.

Available actions are:

- Error: Provides an error message to the user. The user will not be able to proceed until all errors are fixed.

- Warning: Provides a warning message to the user. The user will be able to proceed even with warnings on the screen.

- Enable: The user can key in a field value.

- Disable: The user cannot key in a field value and the fields background color changes.

- ReadOnly: The user cannot key in a field value but the fields background color does not change.

- Show: The user will see the field.

- Hide: The user will not see the field.

- Assign: Allows a value to be set based on the change of a different field. Assign does not have an option to set a value and then re-execute the OnLoad or OnChange of the field being set.

Steps to Configure Action with ActionSet

1. Check-out the transaction, segment or business rule's XML file.

2. Click the Events tab. The Event Navigator window will open.

3. Double-click the Actions node. The XML data will open on the Configuration Area.

4. Configure the action by defining the ActionSets needed for the event.

5. Check-in the file to save the changes to the database.