Translations:Glossar/4/en: Unterschied zwischen den Versionen
Aus HITGuard User Guide
Weitere Optionen
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
==== ID in third party system ==== | ==== ID in third party system ==== | ||
In HITGuard, it is possible to import existing data, e.g. | In HITGuard, it is possible to import existing data, e.g. risks or organizational units, from other sources (e.g. SAP). The ID makes it possible to keep data consistent across applications. If an import is performed and the ID of the import data set matches an existing ID, then a new data set is not imported, but the existing data set is updated with the import data set. | ||
<u>Example</u>: You use SAP to manage organizational units and import them monthly to HITGuard to bring all changes from SAP into HITGuard.<p>For more information, see [[Special:MyLanguage/Datenimport| Data import]]. | <u>Example</u>: You use SAP to manage organizational units and import them monthly to HITGuard to bring all changes from SAP into HITGuard.<p>For more information, see [[Special:MyLanguage/Datenimport| Data import]]. | ||
Aktuelle Version vom 24. Oktober 2023, 07:03 Uhr
ID in third party system
In HITGuard, it is possible to import existing data, e.g. risks or organizational units, from other sources (e.g. SAP). The ID makes it possible to keep data consistent across applications. If an import is performed and the ID of the import data set matches an existing ID, then a new data set is not imported, but the existing data set is updated with the import data set.
Example: You use SAP to manage organizational units and import them monthly to HITGuard to bring all changes from SAP into HITGuard.
For more information, see Data import.