|
Oracle® Rules Palette Release 9.1.0.0.0 E15811-01 |
The EligibleTransactionsByPolicyStatus rule is a plan rule that enhances and supports the processing of events in the system. This type of rule can be configured using XML or it can be configured using visual editing tools.
The EligibleTransactionsByPolicyStatus business rule controls the transactions that are available to the OIPA user depending on the status of the policy and whether in that status the transaction will be initiated by the user or by the system. For example, the Issue activity that issues a policy is available only when the policy is in pending status. If the policy was already in active status, there would be no reason to have the Issue activity available, as the policy has already been issued.
Using XML elements, attributes and values you can configure these processing rules according to business needs. You can configure the rule using the XML Source pane, which displays color coded XML for optimal reading and buttons for finding and formatting code. For a list of XML editing features, please see the XML Source Editing section.
The General Pane displays the rule properties. The fields on the general pane include:
Version - the version of the rule.
Type - the type of rule. In this case it is a system rule.
Long name - the complete name for the rule.
Keywords - any words that might be helpful for locating the rule during a search.
Comments - any comments that might explain the function of the rule.
Error message - any pertinent error messages.
The Eligible Txns Pane allows for the visual editing of this rule. You can drag and drop from the Components listed in the Palette window to the Transactions section of the Configuration Area.
PolicyStatus can be dragged onto the Transaction section to create a new policy status. You can either enter the code value and name of the policy status manually or you can use the Lookup link to select one from records in AsCodeStatus. If you enter a new policy status code it is important to make sure it exists in AsCodeStatus.
Transactions can be dragged onto any PolicyStatus in the Transactions section. You must identify the transaction that should be available in the associated policy status either by entering the name manually or using the Lookup link to select the transaction from the AsTransaction table.
Note: System transactions are added to the Activity screen in OIPA only by spawns and will not be available from a drop-down list. User transactions can be added manually (through drop-down list selection) or through spawns.
Test should be used in conjunction with the TestTransaction component. Test is available if you want to validate a screen field against a value in a transaction. Write the validation in the Test field. There may be multiple Test validations per TestTransaction.
TestTransaction is used in conjunction with Test and identifies the transaction that will be available if the test condition result is true.
Navigate to the Main Explorer tab and open the Company and Plan folders where your new transaction resides.
Open Business Rules | Plan Rules and double-click on the EligibleTransactionByPolicyStatus folder. Right-click on the XML file and select Check-out.
Click the Eligible Txns tab. This will open the window in the Configuration Area and allow you to add your new transaction using drag and drop features.
Click Transaction from the right-side window and drag it under the appropriate policy status heading.
From the bottom of the Configuration Area, click the Lookup link to find the name of your new transaction. When the Lookup window appears, highlight the new transaction name and click OK.
Click the radio button for user to identify your new transaction as user generated or click the radio button for system to identify your new transaction as system generated.
Check-in the EligibleTransactionByPolicyStatus business rule to save your changes to the database.
Configure Using XML Source Pane
In the EligibleTransactionsByPolicyStatus example below, you can see how to add, edit or delete a transaction’s availably by status. The transaction’s name must be the value between the <Transaction> start and end tags. All <Transaction> tags must be sub-elements of the <PolicyStatus> tag. You can also define whether the transaction is system generated or user generated with the TYPE attribute. The <PolicyStatus> element has an attribute called NAME that lists the name of the policy status that the policy must be in for the transaction to be available. The NAME attribute is only used for readability. The CODE attribute controls what policy status the transaction will be available in. CODE values are available in AsCodeStatus, which you can view in the Codes Name folder.
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 Business Rules | Plan Rules | EligibleTransactionsByPolicyStatus.
