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
3 replies
Subscribers
4 subscribers
Views
1254 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Greetings, We have a use-case where we need to send, by e-mail, the l
samartzisg
over 8 years ago
Greetings,
We have a use-case where we need to send, by e-mail, the link of a new task to a user (or list of users) so they can click the link from inside the e-mail and be directed to the Tempo Task. We use an Escalation as soon as a User Task is activated to send the e-mail to the Task's Assignees and we build the link using the TaskID (tp!id) parameter. However, we see the task id we receive in the email is aggregated by 2, e.g. the taskid is 33773 and at the email is 33775.
Any ideas on how we can implement this?
OriginalPostID-168755
OriginalPostID-168755
Discussion posts and replies are publicly visible
Parents
0
ryanh
over 8 years ago
We had a consultant working on an application and wanted to create a link (I believe for an email) to point to a task. However, because the task id wasn't available until the task was created (and normally not available as a pv variable until the task is submitted and the ac!taskid saved as a pv) and the need for the link was immediate there was an issue with retrieving the task id. I don't recall the details, but it sounded like a race condition issue (create task, grab id, use elsewhere, but the id isn't available normally until after task is completed).
The solution was to create the task and have a process report smart service query the system to get the task id. To compensate for the risk the task wouldn't be found (system hadn't generated it or made the new task id available yet to the other engines) a loop was added into the processes to keep checking for the newly created task. I wasn't part of the project and didn't fully agree with the repeated execution of a process report to compensate for a race condition or weird business logic, but it seemed to work in the end. The app has been in production for months and I haven't heard of issues around this part of the logic.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
ryanh
over 8 years ago
We had a consultant working on an application and wanted to create a link (I believe for an email) to point to a task. However, because the task id wasn't available until the task was created (and normally not available as a pv variable until the task is submitted and the ac!taskid saved as a pv) and the need for the link was immediate there was an issue with retrieving the task id. I don't recall the details, but it sounded like a race condition issue (create task, grab id, use elsewhere, but the id isn't available normally until after task is completed).
The solution was to create the task and have a process report smart service query the system to get the task id. To compensate for the risk the task wouldn't be found (system hadn't generated it or made the new task id available yet to the other engines) a loop was added into the processes to keep checking for the newly created task. I wasn't part of the project and didn't fully agree with the repeated execution of a process report to compensate for a race condition or weird business logic, but it seemed to work in the end. The app has been in production for months and I haven't heard of issues around this part of the logic.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data