@SakhibHussain you can use reopenworkobject ootb activity to reopen a resolved work object. 

HI @SakhibHussain: What is the business need? Is it to reopen the process? Or do you wish to do only a backend update for some reason. If it is a business process for reopening, you need to follow the reopen way (reopenworkobject). If it is a backend update, you can still use obj methods. Please note that the update in the work object will update other properties like update date time etc. Do take note of this for your impact assessment.

Thanks.

Hi @SakhibHussain,

Here are a couple of things you need to understand: If you are given the chance to update some property values on the UI for business users, you can reopen the object. Otherwise, it is not required to re-open the work object.

OOTB Activity Names: These two are available in Work Class.

1. Reopen

2.reopenWorkObject

If you are updating the values from The Develoer Studio, why do you need to open the work object? You can directly update the values by creating a temporary activity and doing Property-Set. If you are updating the OOTB properties, you can use Property-Set-Special.

Note: If you are updating some property value, keep in mind and do set audit note mention Incdient number into the audit note as well. Later, sometime, maybe somebody will come and ask you why you updated like that.

If you have a huge number of work objects to be updated, then you can use RDB methods like RDB-List to include all the work objects pyid/pzInskey in the Connect SQL Rule in the browse tab.

I hope this will help you,

Thanks,

Ashok

@SakhibHussain

Use this in activity:4

Pages and class: History= History-ABC-DEF-Work-XYZ

Step1: Page-New- History

Step 2: Property-Set-History

.pxHistoryForReference= ABC-DEF-Work-XYZ Case-123

.pxTimeCreated=@CurrentDateTime()

.pyMemo=""Your Audit"

.pyMessageKey= "your audit"

Step 3: Obj-Save- History

Write Now -true

withErrors -true

Step 4: Page remove- History