Question
Bluerose Technology
IN
Last activity: 15 May 2024 4:20 EDT
Savable Data Page in JS
Hi Team,
We have a requirement to save the record after queuing to a QP. We are using Savable Data page.We need to write the changes immedietly so enabled write-now option. Which gives me a severe warning and reduces the guardrail score!
Do we have any approach to save it without write now option?
I see CommitWithErrorHandling, which can commit the changes, but is it the right scenario to use Savable Data Page?
We are using plain Pega, 8.8 Version.
Infosys Limited
IN
You can make use of commitwitherrorhandling in this situation.
Pegasystems Inc.
CA
Yes, CommitWithErrorHandling works for your scenario.
Job schedulers decide whether a record requires a lock and whether it needs to commit records that use Obj-Save to update. If a job scheduler creates a case or opens a case with a lock and causes it to move to a new assignment or complete its life cycle, the job scheduler does not have to issue a commit.
https://academy.pega.com/topic/queue-processors-and-job-schedulers/v1
Bluerose Technology
IN
@RameshSangili , CommitWithErrorHandling, calls commit which will commit all deferred saves or we can say high level commit. When we see Obj-Save/Save-DataPage with write now option, which saves that transaction. Do we have any such option.
My use case is just to save one record, is that okay If I use the Commit method for saving one record?