EOS MDI Background Manager: what is it?
EOS MDI Background Manager manages the processes (creates or destroys them if necessary) that will take care of the synchronization. Clears the log if the "Delete processed entries" setup flag is enabled and based on the "Log retention" values.
When should it be set?
Always in the master company. If the companies have the "Local" synchronization type (therefore not Oauth or WebService) it must also be set and enabled in the slave companies. Regarding frequency, we recommend "always". The more times it runs, the better, otherwise the records will struggle to update in the slaves.
When to use Local asynchronous sync?
If you see heavy slowdowns, you can try using Asynchronous synchronization (which will be performed not immediately, but based on the job queue). It is advisable to activate it even when the standard feature is active.
|
Feature Update: Auto-save with every field change |
How do "Manual records synchronized” and "Automatic” work?
The record synchronization mode depends on the value set in the “Records Synchronization” field in the synchronization profile. If the synchronization is manual, then it is not automatic. In the first, the records that the users (if the synchronization type is "User Defined" or "Setup Defined") have chosen will be synchronized. If it is automatic, all records that will be inside the table filter will be synchronized.
Is it better to use the Local or Auth2 type?
In general, the webservice implementation with Oauth2 is always preferable. Despite a higher initial effort for the Azure setup, it guarantees more fluid and punctual operation as it is based on push communication that requires only one Job Queue instead of two. The OAuth implementation then becomes mandatory and necessary in a series of contexts:
o Companies that are not on the same database
o Synch of hybrid systems (OnPrem / Saas)
o Synch of different tables on the same company (e.g. Master GL account on GL account)
See also:
