Automatically Refreshing a Creatio Freedom UI Page or List After Updating a Record in a Process (With No Code)

Typically, when you launch a process from a page in Creatio, you want to refresh the page after the process completes so you see any data that was changed by the process. This has always been done by sending a message from a script task in the process to the UI to tell it to refresh. Starting in Creatio 8.0.7 there is now a no-code approach to do this automatically.

In Creatio 8.0.7 and higher, you can now set a property on an entity Object that indicates if it should automatically refresh itself on a page or list if it is updated by something on the server. This could mean it is updated in a process, or in C#, or from a Web Service, or import. Best of all, this will refresh the record in any:

• Pages
• Lists (section or a list on a page)
• Timeline
• Even when displayed as related data on a page (for example, if this option is turned on for the Account and you’re on a Contact page that also displays Account data, the Account data on this contact page would auto refresh)

To turn this on for any object, simply open the object in the configuration and check the “Enable live data update” option in the object behaviors area.

That is it. Once you save/publish the change, anytime a record in this object is updated on the server, the UI will refresh where ever this record is currently displayed. You can see this in action on the Case page (Freedom UI version) in Creatio 8.0.8. When you click the “Assign to me” button, it simply launches the process Set case assignee, which only does a Modify data, nothing more. The UI automatically refreshes to show this updated value using this new feature.

Just to make this clear, this new feature set on the object only applies to Freedom UI pages and lists. If you’re using classic pages/sections/details, it won’t work there. Also, you do want to be careful where you turn this on based on how an object is used. Each update triggers a websocket from the server to the client. If a particular object is very volatile and is changed often from back end processes, you don’t want to cause an unreasonable amount of sockets from the server to the client.

It’s a fantastic and welcome addition to Creatio. Tedious tasks like this in previous versions won’t be missed.