This type of export makes a copy of the selected objects that is as complete as possible. It can for instance be used to archive some projects from a ITP/MDK Repository before deleting them, or to send a troublesome model to the helpdesk. It is the only kind of export that maintains authorization information, which would be senseless for other applications of export. Because everything is exported in an Archival export it is less complicated than the other exports. Still, it is a good idea to check the objects to be exported to see if they are in a state that can be archived.
If the export is used to send a troublesome section of the ITP/MDK Repository to the Helpdesk you must do the opposite. Do not change anything, export as is.
Note
Users added since the export of the archive might not have any role with regard to the imported objects and so might not be allowed to do anything.
Note
For security reasons, the global authorization of users (i.e., authorization granted to a user directly, not for a particular project) will not be exported.
Note
When ITP/MDK Repository data is archived, make sure to also store a copy of the current version of the ITP/MDK Repository installers. Newer versions of the ITP/MDK Repository will evolve and, although it is tried to avoid it when possible, they may have a sufficiently different storage structure to make it impossible to load old archives. If the version with which the archive was written is still present, it is always possible to install that version, load the archive and then upgrade to the new version of the ITP/MDK Repository.
Note
This export also exports the [in development] revision of objects.