Hi All,We have an application which will receive various details from an external system including primary keys for documents which are used for retrieving documents from another system. We receive these details via an API and a task is created for the user to process the same. When the task is being processed by the user, the external system might update the data again which includes adding or removing documents. Since the task is opened by the user, he will never know whether some update has happened to the task or not. We thought of using some refresh variable but it does not seem to be a viable solution. Also it might lead to performance issues since the number of users and number of tasks will be high. Is there any way to handle real time updates and show them in UI?? Any suggestions would be helpful
Discussion posts and replies are publicly visible
Hi Sarathkumar R ,I don't think you can make an realtime updates in an interface without using a refresh variable.As you said it might cause performance issues, if refresh always true, I suggest you to use a button that triggers refreshing of the data from external system, It's not possible with any other method except using a!refreshVariable().Please let me know if you still had something to know....
I think you are suggesting Appian to call external system instead of them calling/updating Appian. Is there any other way to handle this because users dont want this extra clicks to be done.We are suggesting to create new case/task by cancelling existing one so that we dont have any performance issue or anything unknown to us as of now.
Sarathkumar R said:number of users and number of tasks will be high
What does this mean? The number of users and tasks does not matter on its own, the number of users looking at such a task at the same time matters.
The number of users working on open tasks can be huge number at the same time and its expected to increase in upcoming months.
OK. Then I suggest to discuss this with Appian.
BTW, what happens when there is a new document for a case after the task is completed? Can you give us a more insight into the nature of this task?
If new document comes after a task is closed, we will create a new case. This is what we are currently discussing into and the purpose of task is for the user to process the details present in the task in some external system.
OK, then why even care about new documents while working on a task?
Business want both systems to be in sync and they dont want duplicate cases/tasks to be created. New documents might serve a purpose for the in progress task which they dont want to redo again in another task.
Sure, but as you never know when a new document arrives, there is no guarantee. It could arrive a split second after I complete my task.
I have the feeling that the answer to this issue is more a business answer, than a technical answer.
We are also thinking the same. Just wanted to know if there is something we might be missing, so wanted to double check. Thanks for the input Stefan