Unifier_dm_file_content.Upload_by & Unifier_dm_file.Create_by Do Not Capture The User_id Who Revised Document File
(Doc ID 2974241.1)
Last updated on SEPTEMBER 29, 2023
Applies to:Primavera Unifier Cloud Service - Version 23.6 to 23.8 [Release 23.6 to 23.8]
Information in this document applies to any platform.
On : 23.6 version, Unifier Application
When user is trying to revise document in Business Process (BP) workflow process, Unifier_dm_file_content.Upload_by & Unifier_dm_file.Create_by cannot capture the user_id who revises the document file.
Upload_by column should be update based on which user login and same user_id should be update in corresponding table, currently it is updating earlier user_id.
Expect the 'Created_by' & 'upload_by' show the revised user id instead of showing the initial upload user_id
The issue can be reproduced at will with the following steps:
- In version 21.12.11 , User1 log into Unifier and create one bp record with attachment file1 and send to next step.
- User2 log into Unifier and access to the same bp record with attachment file1 and click gear icon->Revise->select another file to upload->Send to next step.
- When view the data in table unifier_dm_file&unifier_dm_file_content, the reviser user2's user_id has been captured.
- But in 23.6 version unifier, do the same actions, user2 is not being captured in above table.column after doing the same revise actions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!