I am trying to escalate a task when it is idle for 90 days
During escalation i use
I didnt provide any values in DestinationProcessID since i dont know the runtime process ID of the escalation process model.
somehow my escalation is not triggering the escalation workflow
Discussion posts and replies are publicly visible
It's actually not the Process Id but the Process Model Id which needs to be mapped. You can easily get that from the Process Model properties.
Why do you not use the in-built escalations on the Task node itself?
This is not correct - you should provide both the process model (by selecting the appropriate model) and the process ID to identify which process model to send to. If you do not define a process ID, Appian will assume you want to send the message to all active processes for that model, which can have a negative impact on performance.
Like Stewart said though, I would also recommend using escalations directly on the node rather than configuring a process-to-process message.
I think the in-built escalation feature will not be a good fit for customised alert template.
Also from the above explanation. The processDestinationId needs a process model id instead of a process id since the process will trigger on receiving message and we will not have a process id.
This is where a little lateral thinking can help.
In the Task that you want monitored you can add an escalation that sends a message. In the very same process you can have a Receive Message "listener" node that can be triggered by the Send Message form the escalation. This can then transition to, say, a Send Email node where you can then generate a customised alert. In short: your process can send a message to itself!
© 2023 Appian. All rights reserved.