I have a user input task with 3 reminders being sent by escalations. The input task is stored in our database and indicates if it was completed and the reminder dates (basically writing a near empty object). I'm trying to figure out how to move passed the input task after the last escalation and still write the record before ending the process.
I've found older posts where users discussed the "send message request" item within the escalation, but they would do that to kill their entire process. I still need my process to complete.
An alternative approach I'm testing out is splitting the flow with an AND gateway:
If pv!taskComplete = true, Path 2 resolves to an end node and everything is fine.
If pv!taskComplete = false, but pv!counter = 4, Path 2 also resolves to an end node. However, the user input task is still active in the process monitor. How can I end this? The tp!id doesn't exist since the task isn't submitted
Discussion posts and replies are publicly visible
Did you try to add an exception to that task? Your use case would fit perfectly.It is not directly "after x amount of escalations", but it should be pretty easy to calculate that point in time when to skip the task and go the alternative way.
Hi do you have a link to exception flow guides for Appian 21.2? I added an exception for the User Input task, however, I receive a message when validating/testing: "Node [node_name] has exception triggers and does not have an exception flow". I'm not sure what that is supposed to look like.
Information about configuring exceptions is available here: https://docs.appian.com/suite/help/latest/Process_Node_and_Smart_Service_Properties.html#exceptions-tab
In general the key is that you must make sure you connect a flow from the exception itself to an alternate path. It's easy to accidentally connect from the node, but it actually needs to be from the exception icon itself. If you've done it correctly, your exception flow should show up as red.
Thank you. This was able to address my error