You are here: Security > Application Security > Transaction Security in Admin Explorer

 

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 secuirty right-click options

Transaction Security Right-Click Options

 

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.  

 

If the underlying rule has a context that allows state overrides, the Rules Palette will prompt the user to select a state value from a Context pop-up window.This state value is used to resolve potential copybooks for their field information.

  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. Error Overridability Security: Specifies whether users belonging to the security group have the ability to override individual errors displayed during activity processing. The exact errors that can have their overridability configured on this pane are specified in the ValidateExpressions or PostAssignmentValidateExpressions business rule attached to the transaction. Each error on this pane has a Security drop-down box used for designating whether the error should be overridable by users belonging to the security group.The options available for selection in the Security drop-down box are as follows:
  4. Field security: grant access to individual fields. There are three options for field security:  

  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

Transaction Security Folder Structure

 

 

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