The Component Lists functional node is a central repository which contains all the component lists existing in an environment and has the following toolbar options:
Create
Click Create to open the New Component List window. The New Component List window is divided into two panes. The left pane lists all of the modules that you can select to include their components in your new component list, and the right pane lists the corresponding components to select. So, if you select the Data Cube Definitions from the left pane, the right pane displays the names of the components (under the Name column), the descriptions of the components (under the Description column), and the option to replace the component in the destination, or not.
Name
This is a required field and enables you to enter the name for the new component list.
Error Check
This option enables you to check to see if there are any errors or warnings related to the component list.
Cancel
This option enables you to cancel creating the new component list.
Save
This option enables you to save the created component list.
Save As
This option enables you to save a created component list as a different list.
Once you create a new component list, Unifier places the newly created component list in the Component Lists log or window. You can use the gear icon menu, next to the newly created component list to conduct the following operations:
- Open
- Delete
The user can delete the component list; however, if the component list is a part of any Draft status configuration package, then the user will not be able to delete the component list, and the user will see the following alert message: "The component list is used in a Draft Configuration Package and cannot be deleted."
- Download last checked error/warning report
The Component Lists log or window displays all of the created component lists and provides the following details in column format:
- List Name
The name assigned to the component list by the user at the time of creation. The component list name will be unique. If the user tries to create a duplicate list the system displays an alert message. See the Creating Component List for for more information.
- Last Error Check Status
The status for component list is determined by the Error Check action. There are three different statuses for the component list:
- Pending: This status will be seen for the list which has not been error checked by the user.
- Complete: This status will be seen when the user has performed the error check and there are no errors existing for the component list.
- Error: This status will be seen when the user performed error check and there are errors which need to be resolved for the component list.
- Creation Date
The date that the component list was created. This will retain the user's date preferences.
- Last Error Check
The date that the error check was performed. This will retain the user's date preferences. If the list is in Pending status then the Last Error Check column will show empty for the corresponding list.
- Last Modified Date
The date the component list was last modified on.
The Component Lists log or window is sorted by default on the Creation Date column. All other columns can be sorted as desired.
Replace in Destination column
When creating an export configuration package, you can select which components will override the existing components.
- Go to the Company Workspace (Admin mode).
- Click the Configuration Package Management grouping node to expand.
- Click the Component Lists functional node to open the Component List log or window.
- Click on the component that you want and open it. The Edit Component List log or window opens. The Edit Component List log or window has two panes. The left pane is the components navigation pane, and the right-pane is the components log pane, corresponding to the component select from the navigation pane.
In the Edit Component List log or window, from the components navigation pane, when you click on any component, the corresponding component log includes the Replace in Destination column (the last column).
When you select component, you have the option of selecting whether your selected component can replace the existing component in the destination, or not, by way of selecting, or not selecting, the checkbox in the Replace in Destination column, corresponding to your selected component.
In case of Business Processes (from the components navigation pane click Setup, under the Company Workspace), you can do the same and determine whether your selected BP can replace the existing BP in the destination, or not, by way of selecting, or not selecting, the checkbox in the Replace in Destination column, corresponding to your selected BP.
Note: For a single-record BP, whether you select the option Replace in Destination, or whether you do not select the option Replace in Destination, the system will replace the destination BP.
When importing the configuration package, the components that have additional checkbox Replace in Destination unchecked will not override the component values if they already exist with the contents from the package. The After Import Status value for those components will be No Change.
If the component already exists in the destination, then it will get overridden, based on selecting Replace in Destination for that components in the package. If the component does not exist in destination, then it will be added by default.
Example
If a string drop-down (pulldown) DD such as Assigned Department which has been used in user attributes is modified in the destination server, and if the configuration package has same string drop-down (pulldown) DD (Assigned Department), where the Override option is not selected, then it will be ignored while importing the configuration package and in the destination server the Assigned Department values remains the same after the configuration package import.
Note: Currently, all of the associated groups for the tagged components will be part of the configuration package (for some components users will also be tagged), and when the configuration package is imported, even though the components do not get updated because the Replace in Destination is set to No Change, the associated groups and users will be added into the destination.