RR Generic Synch Pattern is a forge component that creates a standard for your data synchronisation processes.
This component uses a set of generic actions that provides out-of-the-box features for all your different types of synchronisations while following best practices.
Raphael created this component because he noticed that almost every project he participated in had the same synchronisation requirements. Eventually, he decided to build a forge component to deal with it.
The main features and benefits of using this component are;
• Keeping track of all steps, logs, and errors in your synchs.
• Managing different synch types’ status, periodicity and other properties in a central place
• Manually starting a synch if needed.
• Keeping the history of synch runs if you want. Also, delete them after a specific time if you don’t need them anymore.
• Defining default behaviour and who has access to change the synch properties using roles.
• No longer having to worry about very long processes; the synch will run in the background on timers that have control to end and restart if the session is reaching the timeout. In other words, it will stop, and on the next run, start where it ended on the previous run.
For more detail about how to use the component, please refer to Raphael’s Medium article Speed up development with OutSystems by standardising External Syncs Behaviours.
Raphael Ranieri, Tech Lead and OutSystems MVP, has detailed and demoed this forge component and how to use it. Watch this 12-minute video.
Raphael shared this Dev Tip as part of an OutSystems Community event in February 2022. Please see below the associated slide deck. If you want to watch the entire event, including 5 Dev Tips, you can watch it here.
Sign up for our newsletter and stay tuned for more Dev Tips.