Packaging Single Instance Shells
You can package Single Instance Shells that exist in the Development/Test environment in order to transfer the Configuration Package to the Production environment.
The Configuration Package that you create will include:
- The Shell details data (data from all tabs in the Shell).
- The currency defined in the Currency tab and if the selected currency does not exist in the destination environment, the system will create it.
Note: The Currency attributes such as Code, Name, Symbol, and so forth are not updated when you import the Configuration Package, and after you create the shell, the Currency tab content will not be updated upon subsequent imports.
- The calendar from the Calendar tab and if the selected calendar does not exist in the destination environment, the system will create it.
The following Shell details are included in the Single Instance Shell:
Note: The following Shell details are exported and imported to the destination environment only on the first import. No subsequent updates of Shell details data can be performed in the destination environment.
- Shell data that exists in the form for the following fields: Shell Name, Shell Number, Administrator, and Shell Status.
The Shell log is a user-defined log, and the user-defined columns appear next to the system-defined columns.
When you create a Single Instance Shell Configuration Package successfully, the system stamps the Shell with the Last Packaged Date.
Shells cannot be created if they are not activated in the Configuration module, so the configuration of the Shell will be included in the Shell Configuration Package at the time of transfer between environments.
Note: The contents of the Organize tab, which defines the Shell hierarchy, will be included.
Last Published Thursday, December 14, 2023