Posted: 8 Aug 2019 7:08 EDT Last activity: 30 Sep 2019 2:16 EDT
Problem with operator instance saving
I am changing the email address of an operator in production level but the email address goes back to it's old value some time later. This situation repeat many times. I changed the email address of the operator like 8-10 times but still when I open the operator's profile some time later, I see the old email address. This is so awkward. What could cause this situation ?
I have an agent activity and I am using that agent for the integration with another DB. Another job in the other products writes an email address to a table. Then my agent browses the table periodically. If a new record is found a data page then is executed in order to find matching operator in Pega (pxGetOperatosByEmailAddress). But it does not update anything for an operator. I just use it to know if an operator exists in Pega or not.
In history tab, there are only the record saving rows which are updated by me.
Point 1: If you by mistake used any activity to update an operator (Obj-Open > Property-Set > Obj-Save), it won't leave an audit trail. So, just make sure that none of your functionality is updating the application profile by mistake (SSO?)
Point 2: If you believe that profile is corrupted, try to revalidate and save it once.
Point 3: If issue persists, check the log for any exception/error as soon as you update the profile and save it.