Sub Status - transition BPM on Hold Node to set default sub status

[Martyn Houghton]

We have now rolled out the use of Sub Statuses on our services, but now have the transition period where we have global sub statuses applying to all requests, but a mixture of workflows, i.e. request logged prior to rolling this out still have workflow which are not sub status aware so only set the primary parent status values.

This causes a problem as we have request being put On-Hold via the BPM, but have a sub-status of Pending, which is a sub status of Open not On-Hold. In order to then be able to 'resume' the request via the user app, we have change the sub status another sub-status value and then back to our standard Open Sub-Status of 'Pending'. Also the incorrect sub-status value causes confusion when being displayed in the Request List and in the Customer Portal.

It would help with the transition if the BPM Status Update node had the ability to set a default 'On-Hold' and 'Open' sub-status when one is not specified in the BPM node.

Cheers

Martyn 

[Martyn Houghton]

Just wondering if this is being considered and how other sites are getting around the sub-status not being set when updating existing requests.

Cheers

Martyn

[Victor]

@Martyn Houghton hmm... seems we missed a reply on this one, sorry .... you still need assistance with this?

[Martyn Houghton]

@Victor

It would still be useful to have a default value for the sub status to be set, as we still have active requests which were created with workflows prior to the setup of our sub-statuses. 

This will also be the case for any other sites who migrate to using sub-statuses with open requests using non sub-status aware workflows.

Cheers

Martyn

[Victor]

@Martyn Houghton it depends on what @James Ainsworth thinks about it...