Creating a Configuration Package for Export
When creating a configuration package for export, if the selected components have references to the custom user attributes, you are not required to tag the user attribute design.
When you create a component list, or when you edit an existing component list, if the tagged components have dependency on the user attribute design, then the Component Analysis window does not displays the dependency errors, instead the Component Analysis window displays the warnings related to the user attribute design that were not selected.
Note: If there are component lists that are in Error Status because the user attribute design was not included before an upgrade, the Error Status will remain unless you run the error check again.
Example
The "EmployeeID" data element, in the user attributes, is referenced in filtering conditions in the "Action Items" BP workflow setup. In this case, the "EmployeeID" data element will be included in the packaged components, and the following warning messages will be displayed, with the first warning message indicating that the user attribute design is not included in the component list:
- The selected components have references to the custom user attributes and <user attribute design name> is missing in the component list.
- The additional filtering conditions in the component list, defined in the workflow business process setup of Action Items, requires the "EmployeeID" data element in user attributes and will be included.
The first warning message indicating that user attribute design will not be included in the component list will be shown only when user attribute design is not selected and the design is not published.
- Component Name should be User Administration.
- Location Column should be shown as Design.
- Name should be shown as <user attribute name>.
There will be an additional note displayed in the top section of the Component Analysis window, and it will be as follows: "Note: The package created using this component list does not include user attribute design. You can include the user attribute design by fixing the dependency warning to create a package for production."
In this case, the Component Analysis window will show warning messages detailing the inclusion of customer user attributes referenced by user pickers, user data pickers, BP setup filter conditions, and so forth that are in the selected components.
All of the custom user attributes referenced by the selected designs, setups, and so forth, in the component list, will be included without including the user attribute design.
In the Component Analysis window, the Fix Action option is provided to enable you to include the dependent user attribute design into the component list created and apply the changes.
The components which have custom user attributes references will be displayed as warnings in the Component Analysis window, and there will be a resolving action (minus sign in a circle) to enable you to exclude those components.
Note: If in the source environment the user attribute design is already published, then the design will always be included and no additional warnings will be seen.
If the published user attribute design does not have all of the data elements that are referenced by the selected components (such as BPs), then an error message will be displayed.
If, in the source server, the components selected in the component list have custom user attributes that are data pickers that refer to another design, then Unifier displays errors when you are creating the configuration package, or performing error check in the component list. You must select the user attribute design if there are pickers in the custom user attributes in the package.
Example
When a BP WF setup assignee filter conditions have Space DP display as one of the conditions, the following error message will display while performing export: "The additional filter conditions defined in the workflow for Action Items business process setup requires data picker elements Space DP in user attribute design [User Attributes]. The user attribute design that has data picker elements must be included in the component list."
The above error can be resolved by including the user attribute design into the component list.
Exporting CBS Picker Query Modifications
You can export a BP configuration package that contains a CBS Picker with defined query condition into the shell template.
If you select the Replace in Destination option, then you ensure that your CBS Picker with defined query condition are accessible in the destination server, after importing the added configuration package (as add-on) in the development environment.
Pickers in Add-on Component List
In the New Add-on Component List window, left pane, you can click the Pickers configuration component to see the list of BPs that contain CBS Picker data element (bitemID).
The Selected Components window lists the added BPs, which contain the CBS Picker data element (bitemID), under the Configuration category, with Picker as the Component.
Add-on Component Analysis
After you tag a component in the add-on component list, the system opens the Add-on Component Analysis window and displays errors and warnings, if applicable.
Note: You cannot include a shell design in the add-on component list.
If pickers are added in the add-on configuration package for export, then after importing the add-on configuration package the system will include Add-on Configuration Components as a functional node under the Configuration Package group node, in the left Navigation.
The system will also include an entry for pickers under Configuration in the Selected Components window. Additionally, in the Impact Analysis Report, there will be an entry for pickers under Configuration including the status (Added, Updated or No change) and the BP name.
See Also
Creating Configuration Packages
Creating a Configuration Package for Import
Last Published Thursday, December 14, 2023