Sync and resync are inherent features of any integration platform…
But what if we say for sync and resync, you don’t need an additional implementation cycle? What if you don’t need to put in additional efforts? What if you don’t need to maintain a separate repository? What if you can configure the lapse between two individual data to retry? What if those features are natively available just by defining the normal integration flow?
Yes, the APPSeCONNECT integration platform provides that, so that you don’t have to worry about any failed data sync.
Sync Info and Automatic Re-sync Triggers
In APPSeCONNECT, any data that passes through the platform is tracked using their respective primary key field, which enables us to keep the IDs of the data. Any sync operation goes through various branches and orchestration rules to transform itself into an object consumable to the destination system. During this period, the integration platform automatically tracks the IDs and statuses. These IDs and statuses of any execution are presented inside the platform using the ‘Sync Info’ window.
Here the ProcessFlow keeps track of the Source and Destination IDs and the respective statuses of each record such that you can easily identify the data which has been passed through the platform.
If you have multiple systems running in your business, connect all of them under one single platform to automate the business process and improve your productivity and efficiency!
Automated Resync Operation
Now, for an integration platform, it is important to do an automated re-sync operation too, to ensure that the data integration for a failed item gets fixed automatically without manually coming to the platform again. For that, APPSeCONNECT offers you a scheduler that you can use to schedule the auto fix, such that when it encounters a problem, it tries to automatically fix it over time.
Here you can set up the frequency of the scheduler, based on which the scheduler will automatically go to your sync info window and trigger the retry. It acts as an invisible hand that works continuously behind your attention.
The optimization of resources is very important to run a business. To ensure the automatic resync of a failed item works optimally, we have also provided an option for Time Lapse, which will ensure that the same data sync is not to be retried successively and you have a time buffer to fix the issue on that data. The batch size will ensure that the actual failed items are broken into batches before executing the re-sync automatically.
In order to get more transparency on the data synchronized through the platform, you can click on the ID, which will give you a complete overview of the synchronization steps.
The Snapshot is an immutable data entry that keeps track of all the nodes present in the ProcessFlow and shows the Activity Log, Data Log and Transaction File.
The Data Log
The data log gives you a reference of all the data passed through a node at a particular point of time. The data tracked through “Get Node” will be propagated to every node and their statuses will be modified. Here the same data is getting propagated between the nodes to identify the status of each record. Once the final record is generated, it will be recorded into the Sync Info. The Data Log is the intermediate state of the data during the execution.
The Activity Log
An activity log provides information about the logs generated during the execution of individual nodes. Here you will find the detailed step-by-step resource, where each log entry could be opened again to see more details about a particular step. The steps generated here give you major technical insight into the process it has performed from a particular node.
The Transaction File
Each node in the ProcessFlow takes an input file, processes it and sends it to the next node. Now the output after processing the file is shown in the Transaction File. Here you can check what files it has produced or what files have been passed through the ProcessFlow transaction.
Benefits of Sync Info
1. This feature is inherently supported and hence does not require any major implementation cycle for Failed items. It saves a huge amount of time and effort.
2. Resync will execute the same ProcessFlow but restrict itself to the branches associated with that data. This works automatically and you don’t have to worry about the process.
3. APPSeCONNECT also provides an advanced scheduler tailored for Resync only, which can be scheduled to ensure that the failed items could be automatically fixed over time.
4. Sync info gives you an option to track custom properties of an item, which can be added directly in the sync info panel. This gives you more insights about a record, rather than only the source and destination IDs.
5. The entire life cycle of an individual record could be retrieved using the snapshot link, such that it produces only the snapshots which has executed that record.
Conclusion
As integration is a communication between two disparate applications, it is often a case fact some item fails to sync. These failures could be caused by defective data in the source application or even it could be an issue with the implementation of integration. If you do not have track of all your data, it will be hard to sync these failed items again.
APPSeCONNECT provides the Sync Info panel to give you a clear visualization of your data and shows the failed items which provide a way to automatically (or manually) fix these issues.
This feature comes in very handy and saves a lot of human effort to fix business-critical data.
We will be back with another article on the features of the APPSeCONNECT integration platform and how it helps digital commerce organizations automate their business processes efficiently.
Connect all your business applications under one single platform to automate the business process and improve your productivity and efficiency. Schedule a personalized demo of APPSeCONNECT or request a free trial and explore the platform for yourself! Get Started Now!!
