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 aksharc over 10 years ago

Thanks all for the response.

Aleksi,
What I tried in the process model that, I have added a rule node which will flow if, not(isnull(gettaskacceptedtimestamp(pv!TaskIDFromRule3))) is true. Where pv!TaskIDFromRule3 = getactivetaskidsforprocess(pp!id). But, somehow the flow is not moving ahead even after I accept a task. (Note: The flow the task resides on, and the rule's flow is different, but they are in the same process model.

Do I need to put the timestamp value in the process variable in order to use the not(isnull()) duo?

Or am I implementing it in a wrong way?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 aksharc over 10 years ago

Thanks all for the response.

Aleksi,
What I tried in the process model that, I have added a rule node which will flow if, not(isnull(gettaskacceptedtimestamp(pv!TaskIDFromRule3))) is true. Where pv!TaskIDFromRule3 = getactivetaskidsforprocess(pp!id). But, somehow the flow is not moving ahead even after I accept a task. (Note: The flow the task resides on, and the rule's flow is different, but they are in the same process model.

Do I need to put the timestamp value in the process variable in order to use the not(isnull()) duo?

Or am I implementing it in a wrong way?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data