Write records is refreshing record type only after enabling the activity chain. Is there any other option to refresh record type other than enabling the activity chain.
Discussion posts and replies are publicly visible
No. You somehow need to tell the user interface when to refresh the data from the backend. This can be a single node or multiple nodes down into the process.
Do you have a specific reason to look for an alternative option?
Hi Stefan, Thanks for your reply.
Based on my understanding enable activity will reduce the application performance.
Chaining make the Appian process execution engines execute the nodes in the chain be executed with the highest priority. That's all. Now when you enable chaining on all nodes in all processes, you will end up with a confused process scheduler.
So, does chaining reduce app performance? No, but using it too much will have negative effects on the system.
In the end, it is pretty simple. Do not enable chaining except for the following use cases:
- Control refresh behaviour of an interface
- Control return timing of a process started by a!startProcess
- Guide a user seamlessly through multiple user input tasks in a process
And keep these chains as short as possible!
Thanks Stefan
I have below question: -
1) True
2) Parallel flows do not define any kind of priority. When chained, Appian will just try to execute the chained nodes as fast as possible. Non-chained nodes are delayed.
Gotcha. Thanks
This is relatively new: https://community.appian.com/b/appmarket/posts/sail-events-field
You can use it (judiciously) to refresh aspects of a SAIL interface rather than having to wait for the whole Interface to load if you know certain aspects would unnecessarily delay the interface in loading.