Hi,

There is a Scenario where a data is not saving into the DataTable. So on the use of "Commit" in an activity I am able to retrieve the data(pyWorkPage).

Now, problem arising with the releasing locks, By using this method operation by one requestor acquires a lock on an instance needed by the current requestor this should not happen, and I tired using Obj-Save but it did not work, So is there any possibility using "commit and with no release lock issues" can I get back data from DB. please share scenario so it can help me.

To prevent inadvertent loss of locks Using Commit

Hi Sangamesh,

It sounds like you have a fairly complicated scenario, and locking strategy is often dependent on the details.  Can you elaborate a bit more on your particulars?

Do you have both a data table and a work object (pyWrokPage)  involved, (since you can in Pega use DataTable as a specific non work object class) or were you using DataTable in a more generic sense.

To keep things most portable, you will want to avoid the commit if possible, and leave that to the flow processing/ system to figure out.

Also I think this thread may be helpful to review

https://collaborate.pega.com/question/how-have-persistent-data-db-without-using-commit-activity-called-flow

If you search the Product Support Community for "using commit" you can find a lot of ways you can get into trouble, so lets fill in some details of your specific situation.