E-AD: Change Control Locking Functionality Does not Work As Expected With SQL Objects within 'Find In' in Application Designer
(Doc ID 2944947.1)
Last updated on APRIL 28, 2023
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
Information in this document applies to any platform.
Change Control Locking functionality is not working as expected with SQL Objects when the object is opened from Edit > "Find In" menu in Application Designer.
When it is opened normally via File-Open then there is no problem.
With system wide Lock enabled, if an object is locked by one user, it should not allow another user to edit the object without first unlocking.
However, when the object is opened using Edit > "Find In", it allows the second user to edit and lock the object without first unlocking it.
In order to replicate the issue, follow the below steps:
1. Log into Application Designer as VP1 and Create a SQL Definition and Save it.
2. Log out of Application Designer
3: Log in as another UserID (e.g. VP2)
4. Use 'Find In' to open the SQL Definition. Observe that user VP2 can lock it again without unlocking it, and also update it.
5. Edit the SQL definition, and save it.
6. Log out from Application Designer
7. Log into Application Designer again as VP1
8. Open the SQL Object, observe the new updated text, and that the object is still locked by user VP1.
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