I’m working on a large and complex process where we do not use User Input Tasks. Instead, we implemented a pool-based approach, where each group has its own pool of requests.
Hi everyone,
I’m working on a large and complex process where we are not using User Input Tasks. Instead, we implemented a pool-based approach, where each group has its own pool of requests.
All request data is stored in the database. We also have an Admin Configuration interface that allows the admin to enable or disable certain tasks for specific groups.
For example, in the database we store a boolean flag:
-
true → the request/task should appear in the pool
-
false → the request/task should no longer appear
On the interface side, we are using a grid that queries the database and filters the tasks based on this flag to display the pool for each group.
The issue we are facing is the following:
When the admin disables a task (changing the flag from true to false), the request still appears in the pool grid. It only disappears after performing a hard browser refresh. The standard refresh mechanisms in the interface do not update the grid immediately.
My questions are:
-
Is there a recommended way to force the grid/pool to refresh immediately when the admin disables the task?
-
Are there any best practices for implementing pool-based task management like this in Appian?
-
Is there a better architectural approach for handling this scenario?
Any suggestions or best practices would be greatly appreciated.
Thanks!