Deffered instance outdated causes insert on commit
Hello,
I just resolved a bug on my application but I don't understand the error Pega gave to me, that caused the resolution of the bug to be much harder.
I did an Obj-Open-By-Handle on an object. I modified the corresponding clipboard page, saved it one time.
At this stage, I understand that there is the creation of a defferend instance that will be commited at the next move in a flow for example.
Then I modified the clipboard page another time and forgot to save it.
So at the next commit, I should have a pyCommitError like : "A commit cannot be performed because a deferred save of instance ..." : am I wrong ?
Instead Pega does an insert (instead of a merge) in the database causing the following error : "** ORA-00001: unique constraint (ORACLE.XXXXX violated".
I don't understand this behaviour. Why the insert ? Why not the other pyCommitError ?
Thanks for your help,
Pegasystems Inc.
US
Hi,
To my understanding, if you forgot to save the page, the page will remain in the clipboard and will not get committed to DB until unless the page is present in the pyWorkPage that gets automatically committed after the flow moves forward.
Neither it should throw pycommiterror nor ORA error.
I confirmed this by opening an object from a data class using obj-open-by-handle and saving it. Please find the screenshot attached and let me know if my scenario is any different from yours.
--Ravi
Sopra Steria
FR
Thanks for your response, it helped me. But I saw both this error while coding so, in your understanding, how and when could I encounter these errors ?
Maybe with several different threads ?
Thanks,
