This topic explains the importing of a Configuration Package with custom User Attributes that includes pickers without user attribute design.
Note: The import process applies to both the configuration packages and the add-on configuration packages.
When you select the component package that has custom user attributes without including user attribute design in the import wizard, navigate to the last step, and click Import, the Import User Attributes window opens.
Note: The Import User Attributes window will be displayed only if the component package have custom user attributes without the source user attribute design.
In Import User Attributes window:
- The list of data elements will include all the custom user attributes that are a part of the source package and do not exist in destination environment user attribute design.
- The list of data elements will also include the pickers like shell data picker, shell pickers, and other data pickers that are referenced in the components in the source server. In case that the user data picker is a custom user attribute, the display data element of the user data picker will also be seen in the list of data elements.
- You can see the list of data elements from the component package that do not exist in the destination environment user attribute design.
- You can add the data elements into the destination environment user attribute design by selecting the Continue option. If you decide not to change the destination environment user attribute design, then you can select Cancel or close the window to cancel the importing process.
Importing Data Elements that are not Pickers
This topic explains the importing of a Configuration Package with custom User Attributes that do not include pickers.
When you select the component package that has custom user attributes that are not present in the destination environment user attribute design, the Import User Attributes window opens.
In Import User Attributes window, the list of data elements will include all the custom user attributes that do not exist in the destination environment user attribute design. You (the administrator) will have an option to continue with the import of custom user attributes into destination environment user attribute design, or they can cancel the import.
When importing the data elements into the destination environment user attribute design:
- If the data elements and data definitions do not exist in destination environment user attribute design, then Unifier creates the data elements and data definitions and adds them to the destination environment user attribute design.
- If the data elements do not exist, but the data definitions exist with same definition type, then Unifier creates the data elements and adds them to the destination environment user attribute design.
- If the data elements do not exist, but the data definitions exist with a different definition type (different than that of the source), then Unifier does not create the data elements, and the import fails.
Impact Analysis Report
In case of the import being successful, the impact analysis report shows that the user attribute design in the destination environment as updated. An additional section for Data Structure Setup Components will be included in the impact analysis report, and the custom user attributes will be added.
In the case where the data elements are added, Unifier displays the message: Added to the Data Structure Setup and included in the destination user attribute design.
The Data Structure Setup Components section in the impact analysis report will show the user attributes (data elements) that are added or not changed only when the import of adding custom user attributes into the destination environment user attribute design is successful. The Status column will show the status of the data element accordingly as either added or not changed. The Description column will show the details.
Importing Data Elements that are Pickers
This topic explains the importing of a Configuration Package with custom User Attributes that include pickers, but the pickers do not exist in destination user attribute design.
When you select the component package that has custom User Attributes that include pickers, but the pickers do not exist in destination user attribute design, the Import User Attributes window opens.
In Import User Attributes window, when the custom user attributes are picker elements, the list of picker data elements are shown in the Import User Attributes window, similar to other data elements if they do not exist in the destination environment user attribute design. The following provides more details:
- When the data picker element, data source, and display element do not exist in the destination server
- If in the destination server the custom user attribute which is a data picker element does not exist, then the data picker definition will be added to the destination server by adding the data source and display element. The user attribute data picker element will be created and added to the destination user attribute design. Similarly, the display element will be added, if the display element does not exist in the destination.
- If the display element exists with different definition, then the import will fail and no data picker definition will be created in the destination server.
- If the data source has referenced another design, then the referenced design is imported to the destination server. The import will fail if the referenced design exists with different ID and so forth. All of the existing import logic for the referenced designs will remain as is.
- When the data picker element and data source do not exist, but the display element exists in the destination server
- If in the destination server the custom user attribute which is a data picker element and the referenced data source do not exist but the display element exists, then the data picker definition will be added by adding the data source. Also, the referenced data picker user attribute will be created and added to the destination user attribute design.
- If the display element does not exist but the data definition of the display element exists with different definition from the source, then the import will fail while adding display element and no data picker definition will be added. All of the existing import errors will be displayed in this case.
- When the data picker element does not exists but data source exist in the destination server
- If in the destination server the custom user attribute which is a data picker element does not exist but the data source exists with the same ID or Design, then the data picker definition will be added, and the element will be created successfully. The display element will be added if it does not exist in the destination server, and the referenced picker element will be added to the destination user attribute design.
- The import will fail if:
- The data picker source design does not match with the source, or
- The display element exists with different data definitions, or
- The display element data definition name exists with different definitions
All of the existing import errors will be displayed in this case.
- When the data picker element exist with different data source in the destination server
If in the destination server the data picker element data definition exists with source different that the one in the package, then the data picker element creation will result in error, and the import will fail. All of the existing import errors will be displayed in this case.
- If in the destination server the data picker element with data definition exists but the display element is different than the one in the source, then the destination data picker element will not change, and the import will be successful after adding the data picker element to the destination user attribute design.
- When the data source has picker elements which refer to another designs
- When the data picker data source has referenced other designs, the referenced designs will be imported into the destination along with the data source import. All of the existing import errors will be displayed in the case where the referenced design ID or name exists, but it does not match with the source.
Impact Analysis Report
The impact analysis report will show the custom user attributes which are data pickers, or shell pickers, that were added, not added, or not changed along with other user attributes, in case of successful and failed imports. The Status and Description fields will provide details.