Dynamic HUD checkpoint titles?

[Guest Paul Alexander]

Just an idea...

But would it be possible to have Stage Checkpoints titles which could be dynamic, and which could be changed in the BPM? For instance, if we need to get a request approved, we currently have 2 options - Call Approved, and Call Rejected.

 

I think it would look nice if, while the Approval process is happening (which is triggered in the BPM), we could have just one of these Checkpoints saying something like 'Approval Pending' and then, once the approval is returned, we could change this (so remove 'Approval Pending' and replace it with 'Request Approved' or 'Request Rejected'). At the moment the whole HUD is shown for the lifetime of the request, and I think it's possibly more useful for the customer to see what IS happening with the request, and not necessarily what REMAINS to happen. Also, having the checkpoint list showing what possibly MIGHT have happened in the lifetime of the request (in this case 'Request Approved' OR 'Request Rejected') is a little messy.

I understand that other people won't necessarily use the same wording or update their requests in the same way as we do, but is the idea of 'dynamic Checkpoints' of interest to anyone else?

 

[Jeremy]

We do something similar with some of our requests where we don't show the checkpoints to the customer but add a notice that can be displayed in the portal and these can be dynamic and reflect the changing statuses etc.

[Kevin Kennedy]

+1 We would definitely use this!

[HGrigsby]

+1 for me too please 

[George Warren]

Appreciate its been a few years but yes something like this would be great, or even just being able to set Stage checkpoint icons to a cross or some sort of N/A icon would be useful, I was hoping in the workflow that having it set the checkpoint to false would put a cross but that just seems to set it to blank. 

[Berto2002]

You could simplify this requirement with it as a request to have an "Only show TRUE" switch in the workflow like this:

Or perhaps similar in the node config for stage check lists:

[Steve Giller]

That's basically reversing the purpose of the display.

This is intended to give the Customer visibility of what steps have been completed, but more importantly what steps are yet to complete.

I can see the value in having checkpoints like "Approved" and "Rejected" merged, however as true/false is a binary value this is not straightforward, but having only those that are true - especially on a stage where all are optional - display would frequently leave the Customer with no indication of where the process is, rendering the whole display pointless.

[Peter Clough]

Would an alternative option be, perhaps, to consider grouping specific checkpoints.

For example, you could have pending, then approved/rejected.

Pending runs before-hand, then can unset afterwards.

You have approved/rejected as paired checkpoints, where one is mandatory, and then once that node pairing is complete, it only shows the completed ones from that group. Wouldn't have to be a pair, of course, could have more than one, approved/rejected/expired perhaps, to stick with this example.

I realise this would be non-trivial to implement and will probably not happen, at least not in this form, but would in principle cover all the described needs.