Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
We have a requirement to integrate our appian workflow to cafexUI where that UI will get the active taskitems in the form of report and when they open and action any record the relevant taskitem in appian should be closed and the process model should be progressed to next nodes successfully and complete. We need approach and Error handling.
We created an API which will call a!Completetask smart service which will complete the task however we have activity chaining in the process model of the task which will reopen the taskitem based on the integration node failure or it will complete when success. we need to know how to handle this?
Discussion posts and replies are publicly visible
a!completeTask( taskId: tointeger(a!fromJson(http!request.body).taskId), taskInputs: rule!PM_ICC_GetTaskInputs(http!request.body), onSuccess: a!httpResponse( statusCode: 200, body: "Task completed successfully." ), onError: a!httpResponse( statusCode: 500, body: "Failed to complete task." ) )
Run the integration first, and only call a!completeTask() if it succeeds else return an error.Or decouple it by triggering a child process post-task for integration with independent error handling and retries.
Are you sure this is a good way? Do you need these user input tasks? I this CafexUI the only way to complete a task?
We are using completetask smartservice only but we need error handling technique when task is actioned but later got reopened because there was an error in next integrationnode.
This is not a good pattern to follow.
I suggest to go with a process based approach where a process sends the required "task" information to that other system. The other system then makes an API call to Appian to start the next phase in the process.
I need the example for this to understand. Please share any working example.
Any properly example to understand the flow or elaborated explanation will be really helpful.