After you completed collecting record versions, you need to export the changes for further import to other instances. For this, please complete the steps below:
at the top of the form, click Export Local Pack. OR
in the hamburger menu , select Export → As a New Application.
Use this option cautiously. In case the local pack contains updated vendor records, it may cause collisions while updating the system.
We recommend using the Export Local Pack option.
The downloaded .SOP file will be named automatically as this: Local Pack name_2021-12-31 18:00:00
Datetime format is YYYY-MM-DD.
The timestamp indicates the datetime when the local pack was transferred to the Complete state.
The time is displayed according to the locale of the user who exported the file. That is, if the local pack was transferred to the Complete state at 12:00:00 UTC, then for a user from UTC+3 the file will have the 15:00:00 timestamp.
If the local pack name contains the symbols listed below, they will be replaced by the underscore symbol ( _ ):
\, /, :, *, ?, ", <, >, |
.SOP file export comparison
Export Local Pack
Export → As a New Application
Protection Policy
Does not change.
The policy will be changed to Protected or Open depending on the protected.essences property:
if the table defined in the Table Name field is included in the property, the policy will change from Changed to Protected
if such a table is not included in the property, the policy will change from Changed to Open
Description
Use this export for minor record version changes.
Use this export for a local pack containing a huge number of record versions.
Do not use the option Export → As a New Application for local packs containing vendor records. It may cause collisions while updating the system. Instead, use the Export Local Pack option.
It is a good practice to download your local pack straight away after the job is done; otherwise, the versions stored in it may go out of date.