Setting Up Security for a Custom Object Created in Application Composer

Steps:

1. Hello, my name is John, and today we are discussing security for custom objects in Application Composer.

   Step 1

2. In this demo, I will show you how to set up security for a custom object in Application Composer.

   Step 2

3. Oracle Fusion Applications come secured using the industry standard called role-based access control (RBAC).

    

   Step 3

4. Oracle provides you with job roles corresponding to the common jobs in your organization., such as the Sales Representative job role.

   Step 4

5. Each job role is a hierarchy of  duty roles.

   These duty roles provide users with the permissions to carry out various duties of their jobs.

    

    

   Step 5

6. When you set up security for a custom object, you specify what  permissions you want to give to not to the job  role but to the duty role at the top of the  hierarchy. This duty role has the same name as the corresponding job role.

    

   So, if I want to permit users with the sales representative job role to update the object, I grant the permissions to the sales representative duty role.

    

   Step 6

7. The application automatically creates all the required policies and privileges for me.

   Step 7

8. In Application Composer you begin by navigating to the custom object, in this case the trouble ticket.

   Step 8

9. Click the Security link.

   Step 9

10. For each duty role, you can specify user actions and data access.

    Step 10

11. These options control what UI actions are available to users.

    Step 11

12. You use these two options to permit users to view and update data.

    You must select both View All and Update All to permit users to Create, Update, and Delete. Update All doesn't do the job on its own.

     

    Step 12

13. The Grant Access column is not used.

    Step 13

14. Let's provide  sales representatives with full access to our custom object.

     

    We'll start by providing the view and update data access first.

    Click the View All option.

    Step 14

15. Now let's provide update access to all data.

     

    Click the Update All option.

    Step 15

16. Notice that the application made both the View and Update actions available automatically.

    Step 16

17. Now let's add the Create and Delete actions.

    Click the Create option.

    Step 17

18. Click the Delete option.

    Step 18

19. We are done.

    Click the Save and Close button.

    Step 19

20. There's an alternate way of setting up security for multiple custom objects.

     

     Instead of specifying security object by object,  you can set security for all your custom objects by role.

     

    It's a common setup called Role Security. Let me show you.

    Step 20

21. Click the Show next panels button.

    Step 21

22. Click the Common Setup link.

    Step 22

23. Click the Role Security link.

    Step 23

24. In Role Security, you select a duty and then click the Define Policies button.

     

    Click the Sales Manager Duty cell.

    Step 24

25. Click the Define Policies button.

    Step 25

26. Defining security by role works the same way as by object. The only difference is the related roles column.

     

    If you see a related role name in this column, this means that the role you are setting up inherits its access from the related role. You can drill down

    into the related role to view its security policies.

    Step 26

27. In this demo you learned about setting up security for an object in Application Composer.

    You can find additional learning resources in your Oracle Fusion Help application, as well as in the Oracle Learning Library, and at Oracle University. Thank you.

    Step 27

Table of Contents  Start Topic