My Oracle Support Banner

E-SEC: RUNNING DYNAMIC ROLE RULES DOES NOT UPDATE OPRID VERSION ON PSOPRDEFN TABLE (Doc ID 2626467.1)

Last updated on JANUARY 06, 2020

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Information in this document applies to any platform.

Symptoms

Clicking the Execute Rule(s) button on the Dynamic Members page of the Roles component adds (or removes) that role from user profiles based on criteria in a role query or in PeopleCode. It initiates a process that successfully inserts (and deletes) rows from PSROLEUSER, but that process does not update PSOPRDEFN.VERSION for the affected user profiles. This means that those user profiles which have already been cached cannot access components granted to them by the inserted role until such time as cache is cleared or some other process updates their user profile. Clicking the Execute Rules(s) button on the User Profiles component does not have this issue - it does update PSOPRDEFN.VERSION. Likewise, executing all dynamic role rules via the Execute Role Rules component also updates PSOPRDEFN.VERSION. Application Package PeopleCode program ROLESYNCHEXT_MSG.Write_RoleUser_to_Database has logic to update PSOPRDEFN.VERSION, but it does not work when the process was initiated from the Roles component (run control ID = DYN_ROLES_ONE_ROLE).

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.