Hi All,
There is requirement for implementing workflows having Approve and Reject functionality for people belonging to various groups. We have implemented it using Appian Task based feature where in person belonging to specific group can see the list of task that person needs to Approve Or Reject and based on Approve and Reject it moves to next persons bucket.
But the issue we are facing is that the task are user input based and the process remains in Active state for long time until and unless the person acts on it. So keeping multiple process Active for long time is causing load on the performance of APPIAN as huge amount of Active task gets piled up.
So my query, is this the recommended way for implementing workflows using APPIAN Task based approach.
Regards
Bihitak
Discussion posts and replies are publicly visible
The best way is using the record centric approach. Record-centric design is about eliminating long running processes which is don't have active instances and many people can interact with records and finish the tasks based on the requirement.
We need to implement workflows, is it possible using records
Yes, We can create process models with a start form separately and provide a start process link to open the task. The task status will be saved with respective to the button approved or rejected. Then all the task data will be saved in the database table.
The main difference will be if we use User Input Task it will query data from process report using a!queryProcessAnalytics(). If we go with record centric approach we get the task data from Database using a!queryEntity() or a!queryRecordType(). From there the process is same.