Oracle® Rules Palette Release 9.1.0.0.0 E15811-01

# Create and Configure Transactions

There are two important points to keep in mind when configuring or creating transactions. First, new transactions must be assigned security or they will not be available in the OIPA application.

Also, transactions will not be displayed in the Activity drop down list in OIPA unless they have been added to the EligibleTransactionsByPolicyStatus plan rule. This rule allows you to determine what status a policy must be in before the transaction can be applied to the policy.

Note: If you are configuring a transaction that runs valuation, refer to the valuation section.

Steps to Configure a Transaction

1. Open the Transaction folder.

2. Right-click on the transaction’s XML file.

3. Select Check-out.

4. Refer to General, Allocations, Fields, Events, Math, Assignment, Spawn, XML Source or Debug for information on how to configure.

5. Check-In when finished.

6. Open the application and test your configuration.

Note: You can control when a transaction is available for use as an activity in OIPA by adding it to the EligibleTransactionsByPolicyStatus plan rule.

Steps to Create a New Transaction

Expand the appropriate company folder in the Main Explorer window. Expand the appropriate plan folder. Right-click the Transaction folder. Select New Transaction and the wizard will open. Enter a name for the transaction. The transaction name should never include spaces. Note: Transaction names are not case sensitive and the name can only be used one time. The application will not let you reuse a transaction name even if the case is altered. |
Enter the following items: (Please see the Transaction Type and Processing Order section for further information.) Select the transaction type. Enter the processing order for the transaction. Note: If you want to add a new Client-Import transaction, you need to create a new transaction from the Client Plan folder. All Client related transactions must be created on the Client level. |
Select the configuration sections you need to create the transaction. You can use an entire CopyBook or you can select only the configuration sections you need to create the transaction. A sample configuration of the sections you select will be given as a starting point when you open the transaction’s XML file. All panes are available for configuration regardless of whether the pane is checked or not. Not checking a pane simply means that the pane will be a blank slate. If an entire Copybook is selected, a Copybook Lookup window will appear. Select the Copybook you want to use. If you don't want to use an entire Copybook, select No. You can then select the individual tags from the list. The tags that are selected will be added to the transaction’s general pane. If sections are selected a sample of the configuration will be given as a starting point. All panes are available for configuration regardless of whether the pane is checked. Not checking a pane simply means that the pane will be a blank slate. Click Finish. The new transaction is created and displayed in blue (not checked-in). Check-in the transaction. A translation window will appear. Enter the correct translation for each language and click OK. If you leave one of the locale values empty, then this window will appear every time you check-in the transaction. Note: Let the Security Manager know that you have created a new transaction. The Security Manager will have to add security to the transaction so that the appropriate users will be able to see it in OIPA. |

Every new transaction automatically overrides and attaches the TransactionCosmetics and TransactionBusinessRulePacket business rule. You do not need to manually override and attach these business rules. These two rules are copied from the existing global rules. They are mandatory for the transaction to process and cannot be deleted from the transaction; however, the information may be edited.

Note: You can control when a transaction is available for use as an activity in OIPA by adding it to the EligibleTransactionsByPolicyStatus plan rule.