Discussion3Replies247Views shivakumarH Member since 2015 4 posts Virtusa Posted: 5 years agoLast activity: 5 years 1 month ago Closed Obj-Refresh-And-Lock chaning the status from Resolved completed to NEWHi , We upgraded from 6.2 to p7.1.8In 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? ThanksShiva×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! 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: 5 years agoSreeRamK5970 American Express replied to shivakumarHDo you have any other steps after Obj-Refresh and lock? Posted: 5 years agoshivakumarH Virtusa replied to shivakumarHNo . 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: 5 years agoJessica_H Pegasystems replied to shivakumarHIf 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.