Areas of Responsibility UIs Trigger Role Provisioning for Individual Workers

The Areas of Responsibility user interfaces will trigger an individual worker's role provisioning. As a result of role provisioning, users may have roles added or removed in a timely manner. As you create, update , or delete Areas of Responsibility (AORs), role autoprovisioning will now be automatically triggered. Depending on the action performed, a user’s role may be created, updated, or deleted. All role changes are reflected in the Account Management UI.

When an active role mapping is defined with a responsibility type corresponding to a person-level AOR, then that person will be evaluated for role autoprovisioning. Changes can occur from Redwood and Responsive AOR UI pages in the following task flows:

• Areas of Responsibility 
  • Create a responsibility (without a template)
  • Create a responsibility from a responsibility template
  • Update of responsibility attributes (except only a status change)
  • Delete a responsibility
• Responsibility Template 
  • Directly assigned people (add or remove people) 
• Reassigning AOR from Maintain Areas of Responsibility

Role autoprovisioning occurs when active role mappings with associated roles have enabled the corresponding autoprovision option, as shown here:

Role Mapping UI’s Associated Roles Section Reflecting Autoprovisioned Role is Enabled

Reassigning an Area of Responsibility

When an AOR is reassigned from one person to another, the AOR for both users will trigger role provisioning. Role autoprovisioning occurs when the responsibility type matches the role mapping’s responsibility type. For example, if the original user no longer has the AOR that previously caused a role to be assigned, that role will be removed. Likewise, the newly assigned representative now has the AOR with the relevant responsibility type, so their user account will reflect the addition of the new role.

Note: Another role is not added if the user is already assigned that role.

The business benefit is that you may not need to run the Role Provisioning ESS job, Autoprovision Roles for All Users. This feature reduces delays in role assignment that may result from changes to Areas of Responsibility.

Steps to Enable and Configure

Area of Responsibility (AOR) changes trigger role provisioning for role mappings that are active as of the current date, provided the associated roles have the corresponding autoprovision option enabled.

Tips And Considerations

• This feature impacts both Redwood and Responsive UI.
• Users must have an assigned user account.
• Only role mappings that are active as of the current date, have a defined responsibility type, and include autoprovisioned roles are considered.
• Bulk creation or update of responsibilities—such as responsibility autoprovisioning or HDL loads—does not trigger user role provisioning.
• If approvals are enabled, role provisioning is triggered once all AOR approvals are complete.
• Future-dated responsibility will result in a user role-assignment on that future date.
  • You need to run the Send Pending LDAP Requests job to process future-dated role requests. 

Key Resources

For more information, refer to these topics on the Oracle Help Center: 

• Chapter 14, Provisioning Roles to Application Users 
• Chapter 8 Areas of Responsibility

Access Requirements

To use this feature, you need the following job roles: 

• Human Resource Specialist for access to Areas of Responsibility 
• Human Capital Management Application Administrator for access to responsibility templates (direct assignment)