You are here: Security > Application Security > Transaction Security

Oracle® Insurance Rules Palette 9.4.0.0 E18894_01

# Transaction Security

After Company and Plan security have been defined, the transactions associated with the company and plans are displayed under the Transaction Security folder. Plan folders are listed inside the associated company folder.

Security can be added to all transactions in a plan by right-clicking on the plan name. Security can also be assigned to individual transactions by opening the Plan folder and selecting a specific transaction.

Transaction Security Right-Click Options

Note: Security is applied from the top down. Once Primary Company security is defined in the Company file and the Company pages, then the Plan Security folder will populate with available plans. Once Plan security is defined, then the Transaction Security folder will populate with available transactions.

## Explanation of Transaction Security

To open a Transaction Security editor, right-click on the transaction and select Check-out. There are four sections that display in the Configuration Area.

1. Transaction level security: grants access to all buttons and fields associated with the transaction by clicking the checkbox at the top of the Configuration Area to the right of the transaction's name.

2. Button security: grant access to individual buttons and actions for the transaction by clicking the checkbox to the right of a button. Buttons that are unchecked will not be visible to the user in OIPA. Override buttons receive security from this section. These override buttons are related to the TransactionTimes business rule .

3. Transaction Comments Button Security: this section will be enabled for transactions that were configured with Allow Comments=Yes. Specific levels of access to activity comments and the buttons in OIPA are set here.

- Add: options are Yes, user can add comments or No, user cannot add comments. This may be used in combination with either View security access.

- View: options are

- ViewAllComments: This provides access to the comment icon regardless of who added an entry to the activity. This is the default selection.

- ViewUserCommentsOnly: This provides access to the comment icon only when the comment entries added or last modified by the user exist.

- Update: options are

- UpdateAllComments: This allows the user to save modifications to any non-shadowed comment entry. This can only be used when View All access is granted in the View drop down box. This is the default selection.

- UpdateUserCommentsOnly: This allows the user to save modifications to comment entries. Comment entries are limited to those created by or last modified by the user. This may be used in combination with either View security access.

- Delete: options are

  - DeleteAllComments: This allows the user to delete comment entries, regardless of who added the entry. This can only be used in combination with View All access. This is the default selection.
  - DeleteUserCommentsOnly: This allows the user to delete comment entries. Comment entries are limited to those created by or last modified by the user. This may be used in combination with either View security access.

- View History: options are

- ViewAllCommentsHistory: This provides access to all history records regardless of who executed the action. This is the default selection. This selection should only be available when View All access is granted in the View drop down.

- ViewUserCommentsOnly: This provides access to the history records on which the user has executed an action. This may be used in combination with either View security access.

4. Field security: grant access to individual fields. There are three options for field security:

- Visible and Editiable: the field is both enabled and the value held in the field is visible. This is the default setting and when selected no database entry will be made.

- Hide field value: the field is disabled, but the value held in the field is hidden.

- Disable field value: the field is disabled and any values are visible.

5. Requirement Fields: this section will be enabled for transactions that were configured with requirements. Specific levels of access to requirement fields in OIPA are set here.

6. Masking: Add security to the mask applied to a text field. Security levels are defined in AsCodeMaskSecurityLevel and AsMaskDetail.

Transaction Security Folder Structure

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents