Localization has become a complex business need for organizations that operate in several countries, sites or subsidiaries and that have different machinery, departments, software products and much more.
But, too much time and effort is spent tracking new information: adding, editing, deleting from “source” to “local” processes without any mistakes, making it difficult to have correct and up-to-date data.
With the new Synchronization of Changes from Global to Local feature, propagation of data from a source process to some or all local processes is automatic. On the other hand, data that does not need localization remains intact, allowing efficiency and above all, control.
This new functionality will allow you to:
- Propagate selected data from Global to Local in a click of a button.
- Pick and choose which Local flow objects will be synched with the Source flow objects.
- Apply changes from Source tasks to Local tasks using a matrix for changes and synchronizations at the attribute level.
Rules of Localization Sync:
Deletion of objects:
1. When a task is deleted from local but still available in source, it will not be created again when users sync again.
2. If a flow object with transitions is deleted in source, the flow object and transitions will be deleted in local on the synch too.
Creation of objects:
1. When a new task is created in the source process the sync is on by default
2. Created tasks will appear in the local graph only when users click on “Sync to local”
3. If a task is created (with synch on) next (connected by a transition) to a flow object that is not synched (in the source). When I click on synch to local The newly created task will be added but it will not be attached to any flow object. It will be floating
4. The newly added task will keep the same location as the source location, if the local positioning is different – user will adjust manually the newly added task
Hinterlasse einen Kommentar.