After all the necessary record versions are added to the local pack, you need to complete it. Then you can export the changes to other instances. To do so, complete the steps below:
Export the local pack. A SOP file will be downloaded on your computer:
at the top of the form, click Export local pack. OR
in the hamburger menu , select Export → As a new application.
Use the second option cautiously. If a local pack contains records updated by vendor, collisions may occur while updating the system.
Use the Export local pack option instead.
The name of the downloaded SOP file is generated in the following format: Local Pack name_2021-12-31 18:00:00
The date and time format is YYYY-MM-DD.
The timestamp indicates the date and time when the local pack state was set toComplete.
The time is displayed according to the locale of the user who exported the file. That is, if the local pack was moved to the Complete state at 12:00:00 UTC, then for a user from UTC+3 the file will have the timestamp of 15:00:00.
If a local pack name contains the symbols listed below, they will be replaced with an underscore symbol ( _ ):
\, /, :, *, ?, ", <, >, |
SOP file export comparison
Export Local Pack
Export → As a new application
Protection Policy
Does not change
The policy is 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 changes from Changed to Protected.
if such a table is not included in the property, the policy changes from Changed to Open.
Description
Use this export for minor changes of record versions.
Use this export for a local pack that contains a large number of record versions.
Do not use the option Export → As a new application for the local packs that contain 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 work is done; otherwise, the versions stored in it may go out of date.