Skip to main content
Contact a Moderator

Discussion

3
Replies
261
Views
 shivakumar Hugar (shivakumarH)
Virtusa

Virtusa
IN
shivakumarH Member since 2015 4 posts
Virtusa
Posted: September 10, 2015
Last activity: September 15, 2015
Posted: 10 Sep 2015 10:00 EDT
Last activity: 15 Sep 2015 13:45 EDT
Closed

Obj-Refresh-And-Lock chaning the status from Resolved completed to NEW

Hi ,

 

We upgraded from 6.2 to p7.1.8

In one of the flow there is one subcase status changing from resolved completed to NEW in Obj-Refresh-And-Lock method .

After tracing we found that there is one resumeOnboarding activity laststep Obj-Refresh-And-Lock method status changing from resolved-completed to New.

 

Is any body come accross such situation?

 

Thanks

Shiva
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
Posted: 6 years ago
Posted: 14 Sep 2015 1:31 EDT
shivakumar Hugar (shivakumarH)
Virtusa

Virtusa
IN

No . we dont have other steps .


I noticed that in same activity if removed obj-Save write now and next step using commit then status is chaning to resolved completed.


 


Still want to know same code working in pega 6 why not working in pega 7?


 


Regards


Shiva
Posted: 6 years ago
Posted: 15 Sep 2015 13:45 EDT
Jessica Haider (Jessica_H)
Pegasystems
Product Manager
Pegasystems
US

If you do an Obj-Refresh-And-Lock on a page before saving and comitting that page, any changes on the page will be lost and be replaced with what was in the database (based on last save and commit) for that object.  

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice