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
16 replies
Subscribers
6 subscribers
Views
3702 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi, We are on Appian Cloud 7.6. I have following requirement:
aksharc
over 10 years ago
Hi,
We are on Appian Cloud 7.6.
I have following requirement:
In our current portal version of task form, we have set up a hidden field, which will send an API call to our database with the task information as soon as user accepts the task. That was possible because task form in portal wasn't refreshing on moving between the components.
Now, we are on process of migrating to Tempo, and we want to create the same scenario in the Tempo. So, whenever user accepts the task, then and only in that case API call should be made. I tried following things:
(1) Having the API call in the load(). But that call will be made as soon as the form will be load, not after user accepts the task.
(2) Had a dummy task before the actual task, both of them are activity chained. So, whenever the actual task loads that API call is made. But, this is actually not preferred by our users and conflicts with our business need.
So, is there a way I can achieve the above mentioned...
OriginalPostID-125111
OriginalPostID-125111
Discussion posts and replies are publicly visible
Parents
0
Aleksi White
Appian Employee
over 10 years ago
getactivetaskidsforprocess() will return an integer array, but gettaskacceptedtimestamp() accepts a single integer. This might be the issue. Try using the index() function to get the first index from getactivetaskidsforprocess(pp!id), and then pass that into gettaskacceptedtimestamp()
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Aleksi White
Appian Employee
over 10 years ago
getactivetaskidsforprocess() will return an integer array, but gettaskacceptedtimestamp() accepts a single integer. This might be the issue. Try using the index() function to get the first index from getactivetaskidsforprocess(pp!id), and then pass that into gettaskacceptedtimestamp()
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data