Obj-Save with deferred write, check if success
We have an activity of type Utility that creates a new page (TargetPage) and does obj-save. 'WriteNow' is unchecked (the Help doc recommends to leave this unchecked for activities of type utility)
psuedo-code:
1. Page-New -> TargetPage
2. Apply DT on TargetPage
3. Obj-Save -> TargetPage
(WriteNow, withErrors, OnlyIfNew are all Unchecked)
If stepStatusFail then go to LogError else PageRemove step
4. LogSuccess (and go to PageRemove step) -> hardcoded 'Success' message, for debugging
5. LogError -> hardcoded 'Failure' message, for debugging
6. Page-Remove -> TargetPage
Now, we have cases where the obj-save didn't throw any StepStatusFail but no data was committed to the target table. It logged success (step4) and removed the target page. This 'false success' happens only in few instances.
For deferred write operations, does the StepStatusFail in the obj-save step hold any value to check if the write succeed? I mean, it's deferred write and if the write isn't committed yet the StepStatusFail in this step will not have any info on how the write happened.
In the last step we are doing Page-Remove, what happens if the deferred write is not yet commited by this time? If the page is removed the deferred write can still succeed later?
How to check status if the deferred write has committed successfully (whenever it happens eventually)?
Accepted Solution
Pegasystems Inc.
IN
Hi Sri,
Your logic seems to be absolutely fine. If no StepStatusFail is thrown that means it is saved succesfully to deferred list.
And since you are calling this activity using utility shape, you need not do any explicit commit. Flow processing should have taken care.
Only thing to not here is since it is in flow processing, even if there are errors in next shapes (until assignment shape is reached), it will rollback everything.
Page-Remove will not impact anything to deferred list.
For checking the status of deferred write, you can trace SQL using tracer and it will show exactly when it commits. Else looking in DB directly is also fine.
Areteans Technologies
AU
Deferred save purpose is to commit when the pega does a normal transaction like completing a step or moving from one assignment to other. If you want to commit you can use Work-.commitwithErrorHandling activity.
Accepted Solution
Pegasystems Inc.
IN
Hi Sri,
Your logic seems to be absolutely fine. If no StepStatusFail is thrown that means it is saved succesfully to deferred list.
And since you are calling this activity using utility shape, you need not do any explicit commit. Flow processing should have taken care.
Only thing to not here is since it is in flow processing, even if there are errors in next shapes (until assignment shape is reached), it will rollback everything.
Page-Remove will not impact anything to deferred list.
For checking the status of deferred write, you can trace SQL using tracer and it will show exactly when it commits. Else looking in DB directly is also fine.
Pegasystems Inc.
US
Thanks Pankaj and Dharan. Few more related questions
(a) Another scenario:
1. Page-New -> TargetPage
2. Obj-open-by-handle -> TargetPage
3. Apply DT on TargetPage
4. Obj-Save -> TargetPage
(WriteNow, withErrors, OnlyIfNew are all Unchecked)
5. Call commitWithErrorHandling -> TargetPage
6. Page-Remove -> TargetPage
Does step 5, commitWithErrorHandling wait for any defferred writes (obj-save) to be committed/rollback?
Should this step 5 have the same step page (TargetPage) or can it be empty (primary)?
If either obj-open or obj-save stepstatusfails, then is it still okay to call commitWithErrorHandling (because there's nothing to write possibly anyway)?
(b) When deferred obj-save write fails, we got details in the error log, but it doesn't say from which activity this obj-save call was issued. We have couple of activities which save work objects and it's difficult to identify the culprit ! How to log the source activity of obj-save?
(c) Obj-Open-By-Handle has method parameter 'LockInfoPage'. If we use this option what should be the page type of the page we provide here?
Is it possible to write the entire clipboard page to the log file (just like we view clipboard page in the tracer)?
Thanks Pankaj and Dharan. Few more related questions
(a) Another scenario:
1. Page-New -> TargetPage
2. Obj-open-by-handle -> TargetPage
3. Apply DT on TargetPage
4. Obj-Save -> TargetPage
(WriteNow, withErrors, OnlyIfNew are all Unchecked)
5. Call commitWithErrorHandling -> TargetPage
6. Page-Remove -> TargetPage
Does step 5, commitWithErrorHandling wait for any defferred writes (obj-save) to be committed/rollback?
Should this step 5 have the same step page (TargetPage) or can it be empty (primary)?
If either obj-open or obj-save stepstatusfails, then is it still okay to call commitWithErrorHandling (because there's nothing to write possibly anyway)?
(b) When deferred obj-save write fails, we got details in the error log, but it doesn't say from which activity this obj-save call was issued. We have couple of activities which save work objects and it's difficult to identify the culprit ! How to log the source activity of obj-save?
(c) Obj-Open-By-Handle has method parameter 'LockInfoPage'. If we use this option what should be the page type of the page we provide here?
Is it possible to write the entire clipboard page to the log file (just like we view clipboard page in the tracer)?
(d) In a report defn that gets instances of a class, I want to show if any lock (and if yes then by whom) is held for that particular instance. Which fields should I use in the columns to get this info?
.pzInsKey, .pxUpdateDateTime, <is locked?>, <locked by>
Thanks
Pegasystems Inc.
IN
If either obj-open or obj-save stepstatusfails, then is it still okay to call commitWithErrorHandling (because there's nothing to write possibly anyway)? No, There might be some other deferred operations (beyond this activity). You have to skip commit in this case
When deferred obj-save write fails, we got details in the error log, but it doesn't say from which activity this obj-save call was issued. We have couple of activities which save work objects and it's difficult to identify the culprit ! How to log the source activity of obj-save? Only way is to look at the entire stack trace.
In a report defn that gets instances of a class, I want to show if any lock (and if yes then by whom) is held for that particular instance. Which fields should I use in the columns to get this info? You need a join between work and pr_sys_locks table.(This will change in future)
Obj-Open-By-Handle has method parameter 'LockInfoPage'. If we use this option what should be the page type of the page we provide here? Page should be clipboard page of class System-Locks. It will tell you you who have the lock and expiry time of lock and few other properties
Should this step 5 have the same step page (TargetPage) or can it be empty (primary)? Have to be TargetPage
Cognizant Technology Solutions
US
Hi Pankaj,
I have a query here, lets say there are two deferred obj-save in an activity followed by one commit method in the later steps. Lets say one of the obj-save fails, and so commit fails. Does another one also fails or rolled back. How does it behave in such scenario.