Inquiry Regarding Unexpected Metadata in Data Type Records
Dear Pega Support Team,
I am writing to seek assistance regarding an issue I have encountered with one of our data types in the production environment. Specifically, I have noticed that the first record of the data type includes my user ID and the operation date as fields. I do not recall making any updates or modifications to this data type that would result in this metadata being added.
Could you please provide guidance on the following points:
- Why might my user ID and operation date be automatically included in the first record of the data type?
- What steps can I take to investigate this issue further? For example, should I review the Operator Log or any other specific logs to trace the actions that led to this metadata being recorded? ※I checked all the access log on the same day but nothing found.
Your assistance in resolving this matter would be greatly appreciated.
Thank you for your support.
Best regards,
Yihan
***Edited by Moderator Rupashree S. to add Capability tags***
Accepted Solution
Updated: 2 Dec 2024 0:12 EST
Pegasystems Inc.
IN
@YihanL17 This issue may be due to the system automatically capturing metadata for auditing purposes. This is common in many applications to track changes and actions performed by users. To investigate this issue further, you may have to review the history table and the operator table in the database to see if there are any entries related to the creation or modification of that data type. Additionally, checking the logs for any custom activities or processes that might have been triggered during the time the record was created could provide insights. If no relevant information is found in the access logs, consider looking into the pr_history_data and pr4_history_rule tables for any changes made during that period.
CTC
JP
Hi Thulasi
Thanks for your help.
I have checked pr_history_data and pr4_history_rule tables for any changes made during that period but nothing found.
(I filtered by my operatorID)
So I think this issue may be due to the system automatically capturing metadata for auditing purposes.
I will ingore it this time.
Best,
Yihan
CTC
JP