You are here: Security > Security for New Companies, Plans and Transactions

Oracle® Insurance Rules Palette 9.4.0.0 E18894_01

# Security for New Companies, Plans and Transactions

When a new transaction, plan or company is created, it must have security applied to it or it will not be visible in OIPA. Configurors will be able to see the new item in the Rules Palette and can edit it if necessary. OIPA users will not be able to view the new item until the Security Manager assigns security to it.

Warning Message to Update Security

IMPORTANT: The Security Manager must be notified each time a new item is created so that security can be added.

## Steps to Assign Security to a New Item

1. Open the Admin Explorer tab in the Rules Palette.

2. Open Security | Application Security | Security Groups.

3. Right-click on Security Groups node and select Refresh. This will update the folders with the new item that was added. Make sure any security changes you previously made are saved before performing refresh.

4. Open the folder for the security group that should receive access to the new item.

5. Open the folder that corresponds to the type of item you are adding. If it is a new company, open the Company Security folder. If it is a new plan, open the Plan Security folder. If it is a new transaction, open the Transaction Security folder.

6. Locate the new item in the folder structure. When you see the new item in the list of Company Pages, Plan Pages or Transactions, double-click on the name to open it in the Configuration Area.

7. Click the check box at the top to grant security to all pages, buttons and fields or expand the individual sections to add security to individual buttons or fields.

8. If masking was added to a text field in the transaction, expand the Masks section and select a security level for the mask.

9. Repeat steps three through seven for all security groups that need access to the new item.

10. Check-in all security group files to make sure the changes are saved to the database.

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

Open table of contents