Importing Configuration Packages
When a configuration package is imported into the destination environment, the items in the Component Lists that have been modified override (replace) the existing items in the destination environment, if they exist in the destination environment.
There are cases that require the new configuration package not to override (replace) the existing items in the destination environment.
Example
In the Production environment, a user changes the:
- Values associated with a drop-down (pulldown) data definition.
- Data Views
- Custom Templates
In this case, the user does not want those values to be replaced when a new configuration package is being imported.
You (the Administrator) can define whether certain types of elements in the Component Lists of the configuration package can override (replace) the existing items in the destination environment, if they already exist in the destination environment, or not. As a result, as an Administrator, when you import a configuration package, you can see the following after the import:
- Components that exist in the destination environment and are set to not be replaced are not replaced or overridden.
- Components that exist in the destination environment and are set to be replaced are replaced or overridden.
- Components that did not exist in the destination environment are created.
See Replace in Destination Column (Import and Export) for details.
To import Configuration Packages:
Click Import to activate the Configuration Package Import wizard. Select a valid zip file and click Next.
When you click Next in the Package Components step, the system displays the package components from the selected zip file.
Only the components available in the zip file are displayed in the Package Components preview.
Example
If the user selected a zip file (with categories Designs, Analytics, and Configuration), the Package Components preview displays the following Categories:
- Designs
- Configuration
- Analytics
Because the configuration includes component Business Process, Business Process components are displayed under Configuration.
The Designs node will also have separate sub node Published Designs to show the published designs coming in as part of the configuration file. The Group sub node will also appear in the categories Shell Templates and Single Instance Shells. For Groups, the column that will be seen is the Name where the group name should be seen.
There will be a filter option available to enable you to filter data for search for every column. The print option prints the consolidated report based on the user selected components.
In the Package Components preview, the Status column is displayed for all the components with the following indicators:
- Add
When imported successfully, the component will be added in the destination environment.
- Update
When imported successfully, the component will be updated in the destination environment.
- No Change
When imported successfully, there will be no changes applied to the component in the destination environment.
When you click Next in the Package Components step, you go to the User Mapping step, and the following operations take place:
- The system extracts the following information, for user mapping:
- Shell administrator.
- Auto Creator for Business Process records or line items.
- BP Auto Creator in the BP Setup.
- For other component where users/groups are assigned, for example, Workflow Setup, Access Control, column restrictions in Cost Sheet, or Portfolio Manager:
- If all assignees are Groups, then the Groups will be extracted.
- If the assignees are a mix of users and groups, then only the groups will be extracted and the users will be ignored.
- (Portfolio Manager) If the assignees is a list of users only, then during error check, the following error message appears, while creating component list and during export of Configuration Package:
The users assigned to {name of PPM} cannot be extracted. Include at least one group to proceed further
- The other creator users for components that the user does not select or cannot be changed, for example, creator of Cost sheet, then those creator users are replaced with the user who is performing the import.
- When performing import for the first time in the destination environment, by default, the destination login name (present in the destination environment) is displayed in the column for users who are present in the environment. The destination login name will be empty for users who are not present in the environment.
- The last entered values for the User Mapping (from the last import) will be remembered in the same environment. The system auto-populates the last User Mapping values once the user reaches the User Mapping step.
- You can enter the mapping details.
- You can edit the destination login name for any value.
- You can map different imported users to the same user in the destination environment.
Note: Although group name and the group permission is available, the members of the group cannot be extracted.
After you click Next from the User Mapping step, you go to the Import step.
You can select/deselect to download the impact analysis report in the Import step. If you deselect this option, you can download the impact analysis report using the gear menu in the Configuration Package log.
In This Section
Configuration Package Report and Audit Log
Conditions for User Mapping in Configuration Package
Configuration Packages Import Rules
Last Published Monday, August 28, 2023