Search the Community
Showing results for tags 'substatus'.
Found 3 results
Currently the 'Wait for Status Change' node only completes when the primary 'Status' changes i.e. from 'OnHold' to 'Open'. It does not trigger is the SubStatus is changed within the same parent 'Status', i.e. changes from 'Open->Pending with AM' to 'Open->Pending with Analyst'. Can the node be extended to have the option to trigger on a change to the SubStatus or can a new Suspend Node be for this. i.e. 'Wait for SubStatus Change'? Cheers Martyn
I'm having a moment, does anyone know where the setting is that allows a request to be automatically taken off hold if a customer updates the request from the Portal? I'm also hoping that I can reference this in the BPM to check to see if a customer has updated the request by email or portal and then progress based on this?
Hello, One of my colleague raised this interesting request few days ago. He asking for the reason box when use substatus of the request to be remove, because the substatus should be clear of what it means without need to add reason on it. Also he mentioned that if necessary to add information then he would use comment box instead of reason box for update. (Please see example below). I wonder if there is possible to add new ability to turn on or off for each individually of substatus if need to keep reason box. Thanks, Aaron cc: @samwoo