Hi, We are on Appian Cloud 7.6. I have following requirement:

aksharc over 9 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...

Discussion posts and replies are publicly visible

Parents

0 aksharc over 9 years ago

Thanks Aleksi!

What I did was, I added Complex Gateway, and had a condition there that if =gettaskacceptedtimestamp(pv!TaskIDFromRule3) is true, then go and call the API. If that condition is not true, I am sending it to an empty script task (No input, output expressions defined). And again, from the same script task I am flowing to that complex gateway (In a way creating a repeating loop). Also, I have checked the "Delete previously completed/cancelled instances" from the Other tab in the script task.

This kind of served my purpose. But now concern is, how it will be impacted performance-wise? (We have instances of tasks which are not accepted for as long as 6-7 months.)

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 aksharc over 9 years ago

Thanks Aleksi!

What I did was, I added Complex Gateway, and had a condition there that if =gettaskacceptedtimestamp(pv!TaskIDFromRule3) is true, then go and call the API. If that condition is not true, I am sending it to an empty script task (No input, output expressions defined). And again, from the same script task I am flowing to that complex gateway (In a way creating a repeating loop). Also, I have checked the "Delete previously completed/cancelled instances" from the Other tab in the script task.

This kind of served my purpose. But now concern is, how it will be impacted performance-wise? (We have instances of tasks which are not accepted for as long as 6-7 months.)

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data