Oracle Recruiting Cloud (ORC) provides an extensive set of functionalities within the Actions menu, enabling users to manage requisitions effectively. However, when organizations require restricting specific actions—such as Reopen Job Requisition, Fill Job Requisition, or Send Message to Team—granular privilege control is unavailable. This limitation creates challenges for ensuring appropriate role-based access.

In this guide, we provide detailed, step-by-step instructions that even users with minimal experience in Oracle Fusion or Oracle Recruiting Cloud can follow. By the end of this document, you will have the knowledge to successfully restrict specific actions in the Actions menu using Page Composer and EL Expressions.

The Challenge

The Actions menu in ORC combines several functionalities under grouped privileges like Duty Roles or Aggregate Privileges. This setup prevents administrators from selectively restricting individual actions. For example, you cannot allow one user to access ‘Reopen Job Requisition’ while hiding it from another without applying the same restriction to the entire menu. This challenge becomes more apparent when organizations need role-based access control for specific users like Hiring Managers or Recruiters.

Examples of actions in the menu include:

• Fill Job Requisition
• Preview Job Requisition
• Translate Job Requisition
• Send Message to Team
• Suspend Job Requisition
• Cancel Job Requisition
• Reopen Job Requisition
  

Step-by-Step Solution

1. Create a Sandbox

1.1 Navigate to Configuration > Sandboxes in Oracle Fusion.
1.2 Click on Create Sandbox and provide a name (e.g., ‘Restrict_Action_Menu’).
1.3 Enable the ‘Page Composer’ tool in the sandbox settings and activate the sandbox.
Note: Using a sandbox ensures all changes are made in a safe, testable environment and do not impact live users.

2. Locate the Requisition

2.1 Navigate to Hiring > Requisitions in Oracle Recruiting Cloud.
2.2 To include inactive requisitions in your view, click on Filters and select ‘Include Inactive Requisitions.’
2.3 Use the ‘State’ filter to select ‘Cancelled.’ This narrows down the list to requisitions that have been cancelled.
2.4 Click on one of the cancelled requisitions to open its details page.

Tip: Ensure you select a requisition with sufficient test data to validate changes later.

3. Enable Page Composer

3.1 Once the sandbox is active, click on ‘Page Composer’ in the top-right corner of the Oracle Fusion UI.
3.2 Select the ‘Structure’ option to enable editing of page components.

Important: Always use the ‘Edit’ mode specific to the component you intend to modify.

4. Edit the Actions Menu Component

4.1 Navigate to the Actions menu on the requisition details page.
4.2 Hover over the menu and click to inspect its structure.
4.3 Locate the specific action you wish to restrict (e.g., ‘Reopen Job Requisition’).
4.4 Click on the ‘commandMenuItem: Reopen Job Requisition’ component and select ‘Properties.’

Note: Ensure you correctly identify the component, as the Actions menu may have multiple items grouped together.

5. Apply an EL Expression for Restriction

5.1 In the ‘Show Component’ field, enter the following EL Expression:

#{(action.label=='Reopen Job Requisition' and securityContext.userInRole['FPF_RECRUITER_JOB_GSE'])==true?true:(action.label!='Reopen Job Requisition'?true:false)} 

5.2 Click ‘Test’ to verify the logic. The output should return ‘True’ for users with the required role.

5.3 Save the changes by clicking ‘OK’ and ‘Apply.’

5.4 Repeat the same action for the 2^nd Group as well

Tip: Modify the expression to suit other actions by replacing ‘Reopen Job Requisition’ with the respective action label.

6. Test the Changes for Role-Specific Visibility

6.1 Switch the sandbox to ‘Preview as if Published’ mode.
6.2 Log in as a user with the required role (e.g., FPF Recruiter) and verify that the restricted action is visible.
6.3 Navigate to the Security Console and remove the required role from a test user’s account.
6.4 Log back in as the test user and confirm that the action is no longer visible.

Common Troubleshooting Tips:
– Ensure the EL Expression syntax is correct.
– Verify that the role mappings in the Security Console are accurate.
– Check for sandbox-related issues if the changes do not reflect as expected.

7. Repeat for Other Actions

7.1 Identify additional actions in the Actions menu, such as ‘Cancel Job Requisition’ or ‘Fill Job Requisition.’
7.2 Apply similar EL Expressions to restrict each action based on the required role.

Note: Test each action independently to avoid conflicts or unintended behavior.

8. Publish the Sandbox

8.1 Once all changes are verified and functioning as intended, return to the Sandbox management screen.
8.2 Click on ‘Publish Sandbox’ to make the customizations live for all users.

Reminder: Communicate with your team about the changes to ensure a smooth transition.

Extending to Redwood Pages

For customers transitioning to Redwood pages, similar customizations are required. Redwood pages may have a different component structure, and the following considerations apply:

• Component Identification: Use Visual Builder for Oracle’s Redwood-specific Page Composer to locate the relevant components for the Actions menu.
• EL Expression Adjustments: Ensure the EL Expressions align with the Redwood component architecture.
• Testing: Test thoroughly in a sandbox environment to verify the behavior across both Responsive and Redwood pages.

Key Takeaways

The approach described works on Responsive pages and can be adapted for Redwood pages. EL Expressions can be tailored to restrict other actions like Fill Job Requisition, Preview Job Requisition, or Suspend Job Requisition. Regular testing is crucial, especially during upgrades or UI transitions.

Conclusion

While Oracle Recruiting Cloud lacks built-in privileges for restricting specific actions within the Actions menu, customizations using Page Composer and EL Expressions provide a reliable workaround. By leveraging these techniques, organizations can enforce stricter role-based access and minimize risks.

As Oracle continues to enhance Redwood UX, we hope to see more granular privilege options in future updates. Until then, these customizations remain an effective solution for managing requisition actions.