Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
4 subscribers
Views
1851 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
I recently came across an unexpected behavior with task escalations. When attem
bradc
over 9 years ago
I recently came across an unexpected behavior with task escalations. When attempting to send tp!id or tp!starttime via an alert or message event from a task escalation, the values sent are not that of the task associated with the escalation. Instead, it appears that the escalation has a tp!id and tp!starttime associated with itself, and not the task I'm attempting to escalate.
Has anyone else experienced this behavior and come up with a solution? I would like to send the tp!id and tp!starttime directly from the escalation to an alert and/or message event.
As a side note, the tp!display and tp!name does send the task values. I have not testing any other tp! values.
OriginalPostID-149062
OriginalPostID-149062
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Just to add more information to this, you're correct. Escalations, as part of the design of the product, have their own properties. Using tp!id will return the escalation ID not the task id. This is how the product was designed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Just to add more information to this, you're correct. Escalations, as part of the design of the product, have their own properties. Using tp!id will return the escalation ID not the task id. This is how the product was designed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data