Slots Not Seen as Blocked When Using VPD to See Other User's Appointments
(Doc ID 2740931.1)
Last updated on AUGUST 12, 2022
Applies to:
Oracle Transportation Management Cloud Service - Version 20.2 and laterInformation in this document applies to any platform.
Symptoms
When having two users with the same user role that has the following VPD predicate:
Table name: APPOINTMENT
Predicate: insert_user=(SYS_CONTEXT('gl_user_ctx','GL_USER_GID'))
in order for one user not to be able to see the appointments the other user has, when trying to create an appointment, the slots that are already blocked cannot be seen as blocked. They seem to be available.
You can see the expected behavior when performing the action to schedule an appointment or move an appointment to a slot that is already blocked by another user - the slot is already blocked and the appointment cannot be moved to that slot as expected. Message seen as expected:
What is wanted is for the user to see from the beginning that that particular slot is blocked.
The issue can be reproduced at will with the following steps:
1. Go to Dock and Yard Managers
2. Search for the Location
3. Select it and go to Actions, Manage Appointments
4. Select the date
5. Try to move the appointment (the slot looks free even though there is an appointment done by another user)
6. Press on Save
The above error appears.
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 |
Cause |
Solution |
References |