We are using UpdateStatus OOTB activity to update(in fact it should be called set) pyStatusWork. However this activity doesn't capture pxUpdateDateTime, pxUpdateOperator...etc like how RecalculateAndSave does. It doesn't save the instance also, read another article where it said, we have to use obj-save explicitly in the application activities.
What's weird is that, history/documentation of the UpdateStatus activity says, it calls RecalculateAndSave to update pxUpdate* properties....
Fixed in my application by adding an additional step to capture pxUpdate* properties as well, since it's available for extension...problem solved.
Shouldn't pega update this OOTB activity to capture pxUpdate* properties as well ?
We call UpdateStatus activity for multiple purposes. One of it is to set a status: The WO goes thru multiple statuses...New, Pending-Employee, Pending-Customer etc... each time it changes the status we need to have the right pxUpdateDateTime. The problem is that unless we set pxUpdateDateTime and pxUpdateOperator etc. explicitly, it doesn't happen. I was asking should Pega do it in OOTB activity along with setting the new status ?
Resolve - as I understand it's called only if the new status is Resolved-*, so for my use case Resolve shouldn't be called and it's not calling.