Differences

This shows you the differences between two versions of the page.

--- devel:documentation:adm:export_import [2020/09/30 12:54]
svandav [Export descriptors]
+++ devel:documentation:adm:export_import [2021/05/26 08:21]
127.0.0.1 external edit
@@ Line 58: / Line 58: @@
 Version **10.2.0** implements export of **roles**, **systems**, **application configurations**, and some related objects (such as form definitions or catalogs ...).
-<note important>Passwords (stored in confidentila storage) are **never exported**. When you first import an object that contained a password (for example, a connector configuration (EAV attributes) or password in remote connector server), the password will not be filled in the target IdM. If it is an update of an existing object, then the password in the target IdM will **not be modified** in any way.</note>
+<note important>Passwords (stored in confidential storage) are **never exported**. When you first import an object that contained a password (for example, a connector configuration (EAV attributes) or password in remote connector server), the password will not be filled in the target IdM. If it is an update of an existing object, then the password in the target IdM will **not be modified** in any way.</note>
 ==== Roles ====
@@ Line 88: / Line 88: @@
 * **Attributes mapping** (authoritative mode = **on**) - If a particular attribute maps an EAV attribute to an entity (such as identity), then **the attribute definition is also added to the export**.
 * **Role assigns account in systems** (authoritative mode = **on**, optional = **on**) - Relations between system and roles are exports as optional. It means if some of a role isn't found on target IdM, then is that relation skipped (import will be continue). Within exporting of this relations are role-defined attributes also exported (authoritative mode = **on**, optional = **on**).
-* **Sync configuration** (authoritative mode = **on**)
+* **Sync configuration** (authoritative mode = **on**, optional=**on**) - Sync contract/slice configuration contains relation on a tree-type and tree-node object. If this objects will be not found (by ID or code), then whole configuration of the sync will be skipped (not updated, not created, not deleted).
+<note important>Since **10.6.0**: **Sync contract/slice configuration** contains relation on a organization structure and organization node. If this objects will be not found (by ID or code), then whole **configuration of the sync will be skipped** (not updated, not created, not deleted)</note>
+<note tip>Virtual systems may be imported with some limitations, see the section **Limitations**.</note>
 ==== Application configuration ====
@@ Line 151: / Line 155: @@
 ==== No skip implemented  ====
 <note important>Omitting for recalculation of business roles, incompatible roles or provisioning is not implemented in version 10.2.0!</note>
+==== Virtual systems  ====
+<note tip > Full support of the virtual system export and import has been available since version 11.1. Following workaround should not be necessary anymore. </note>
+When importing a virtual system, you must make some further adjustments so the imported system behaves in the same way as the exported system. Especially if you use the "rights" attribute or if you changed or [[tutorial:adm:virtual_system_-_adding_or_deleting_managed_extended_attributes#deleting_attributes_on_virtual_systems|removed some of the default attributes]]. After you import the system:
+  * Go to **Settings -> Form definitions**, search for the definition of type *VsAccount* and name containing the name of your system.
+  * Go to **Form attributes**, remove the attributes that are superfluous. For the attribute "rights", switch the checkbox "multivalued".
+More info [[https://redmine.czechidm.com/issues/2550|here]].
-==== Future improvements ====
-<note tip >**Modularity** - Allow to export a single batch across multiple modules.</note>