Below is the description of issue. Hope it will help now.
Actually, according to requirement i cannot do the changes on screen for resolved-completed work object because then it will distort the report's data for original work-object.
So i am having another flow to create new work object under same cover (as for original work object) to make changes, becasue i need to show changed information in reports along with original work-object.
Problem is that already created work-object does have cover records in PC_WORK table, and so i am facing problem to create another work-object under the cover.
Once a Case (Work Object or Work Item) is "Resolved" it is essentially locked and can not be modified unless it is reopened. You will need to Re-Open the Case first before you can make it a subcase. You can write a custom activity to do this. In the Custom Activity you create use the Obj-Open method to open the case and then Call the Work- pxMove Activity (Call pxMove) to make the Case a SubCase of another Case. The pxMove Activity takes several parameters:
WorkObjectID : Id of the work object to move(can be pyId or pzInsKey)
NewCoverID : Id of the cover to move to (can be pyId or pzInsKey)
AuditNote : Audit note to be added (to the case history)
Commit : When outside of flow processing,choose to manually perform commit of all changes
UpdateHistory : Should the history be updated
PXCOVERINSKEY is a read only property that can only be updated by PRPC so you must use the Pega provided (OOTB) pxMove Activity or the Pega provided (OOTB) pyMoveToAnotherCase Flow Action to change PXCOVERINSKEY.