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...

Discussion posts and replies are publicly visible

Parents

0 Aleksi White
Appian Employee
over 10 years ago

Could you explain the use case for having the task wait 2 minutes to start? What is the reasoning behind that?
What's likely happening is that the rule node is going ahead and evaluating. Since there is not active task yet, it's evaluating to false, and not continuing the flow. Once the task starts and you restart the rule node, it evaluates to true and the flow continues.
I would recommend one of two things:

1) If the 2 minute delay isn't necessary, then remove it so the rule node can execute properly and continue the flow

2) If you do need to the 2 minute timer, then I would add another similar timer in front of the rule node. This way the rule node will only execute (and be able to continue the flow) once the task node has started and been assigned
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Aleksi White
Appian Employee
over 10 years ago

Could you explain the use case for having the task wait 2 minutes to start? What is the reasoning behind that?
What's likely happening is that the rule node is going ahead and evaluating. Since there is not active task yet, it's evaluating to false, and not continuing the flow. Once the task starts and you restart the rule node, it evaluates to true and the flow continues.
I would recommend one of two things:

1) If the 2 minute delay isn't necessary, then remove it so the rule node can execute properly and continue the flow

2) If you do need to the 2 minute timer, then I would add another similar timer in front of the rule node. This way the rule node will only execute (and be able to continue the flow) once the task node has started and been assigned
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data