...
...
...
...
...
...
...
...
| Excerpt |
|---|
New features, improvements and bug fixes done for version 5.0.0 |
...
The styles are predefined and cannot be adjusted for now. Those are:
dot,
dash,
dash-dot,
dash-dot-dot.
Change Requests related changes
...
All - sync all objects on the list, respecting current filters and status selected.
Selected - sync only explicitly selected objects
Subtree - sync selected objects with subtree. Subtree is resolved according to pre-set perspective.
Sub sync option:
Sync - sync all or selected objects now. Below is a strategy to use in this sync operation.
FMA Wins - Objects from FMA will be sent to Asset.
Asset Wins - Objects from Asset are pulled to HDC
Do Not Sync - set “do not sync” status for that objects(s)
| Note |
|---|
FMA or Asset Wins strategy will exclusively be applied to objects that have not been synced previously! This encompasses objects currently labeled as "not present in Asset" or other items lacking external (Asset) date information. For objects that have already been synced, a comparison will take place, and the syncing of objects will occur in the appropriate direction. The chosen strategy does not impact these objects. In cases where objects have been modified on both sides, they will be designated with a "conflict" status. |
Full Sync (Initial Sync - select strategy
system Sync)
Now system sync can be initialized with selected strategy:
...
| Note |
|---|
Full Sync should only be run when the sync was not initialized before or when a configuration (e.g. domain mappings) have been altered. If new fields are added to the domain, standard sync will not pick up this change. A Full Sync is needed. |
New Data Export Capabilities
...