Configuration Packages Import Rules
The following explains import rules for the configuration packages.
Manually, a design object such as a business process can be set up in a Shell template, Single Instance Shell, Company Workspace only if the design object has an Active Configuration, which is set in the Configuration node.
Because the system does not perform checks for the existence of an Active status configuration at the time of import, the configuration setup is imported irrespective of configuration status (Active or Inactive). As a result, the user must tag the configuration of the corresponding design, in the Development/Test environment, so that it is a part of the Configuration Package.
This rule applies to the following components:
- Business Process
- Asset Manager
- Planning Manager
- Portfolio Manager
- Resource Manager
- Shell Manager
- Space Manager
- Configurable Manager
The system imports all content included in the Configuration Package.
The system aborts the import process if there is an error.
For a successful import, you must load all necessary modules, for each component, in the destination server. For example, if the configuration package includes Cash Flow Curves, then the Cash Flow module must be loaded in the Production environment, or destination server.
If the following objects do not exist in the Production environment, or destination server, the system creates these objects in the Production environment, or destination server, automatically:
- Design
- Data structure setup components
- Shell templates
If a report does not exist in the Production environment, or destination server, the system creates the report after a successful import.
If the configuration package components exist in the Production environment, or destination server, the system performs an update upon a successful import.
System updates result in complete replacement. For example, if the Auto Creation setup has changed in the BP setup, the system applies the updates to all the tabs in the BP setup.
If you include BIP reports in your configuration package, ensure that:
- The application modules have been deployed in the imported environment, prior to import.
- The BIP reports are at application level.
If the application modules have not been deployed in the imported environment prior to import, then the import process will fail.
Unifier module options that have associated files are based on the Configuration Package, always.
The components for the following objects in the Configuration Package overwrite the components of the corresponding objects in the Production environment, or destination server, after a successful import:
- Shell templates
- Templates
- Company Workspace
- Single Instance Shells
If the components of the objects do not exist in the Production environment, or destination server, then the system adds the components of the objects in the Production environment, or destination server, after a successful import.
If the components of the objects exist in the Production environment, or destination server, the system updates the components of the corresponding objects in the Production environment, or destination server, after a successful import.
When the User Mode Navigator setup is included in the Configuration Package, the system deploys the setup after a successful import.
If external Custom Reports are used in the User Mode Navigator, ensure that the external Custom Reports names and locations in the Configuration Package match those existing in the Production environment, or destination server; otherwise, the import process will fail.
If the names of the following components of Cost Manager sheets (Funding), in a Template, do not match, then the import process will fail:
- Funding Sheets
- Commitment Funding Sheets
The registry name of Data Views that are imported into the Production environment, or destination server, must match those in the Configuration Package. Data Views can only be imported between two servers belonging to the same registry. This condition also applies to the following components, which use Data Views:
- Data Cubes
- UDRs
- BIP reports
Last Published Saturday, July 13, 2024