Data Structure Setup
The Data Structure Setup components can be selected and included in the component list required for creating configuration packages. The selected Data Structure Setup components overwrite, or insert, data set/default values in the destination environment. Overwrite only occurs if the Replace in Destination check box is selected for the component. If the component does not exist in the destination environment, the configuration package will always insert the component into the destination environment.
The following are the sub-nodes available under Data Structure Setup:
- Basic Data Definitions
- Cost Code Data Definitions
- Data Cube Definitions
- Data Views
- Dynamic Data Sets
Each node, when selected, displays the columns:
- Basic Data Definitions
- Name
- Input Type
- Used in Selected Designs
- Replace in Destination
- Cost Codes Data Definitions
- Name
- Input Type
- Replace in Destination
- Data Cube definitions
- Name
- Description
- Replace in Destination
- Data Views
- Name
- Label
- Description
- Replace in Destination
- Dynamic Data Sets
- Name
- Description
- Used in Selected Designs
- Replace in Destination
The default column sort is the Name column.
Data Structure Setup - Basic Data Definitions
All basic data definitions are available for selection except for the:
- Picker type
- Data picker type
- Check box type DDs
When imported, the data sets/default values of the selected data definitions (included in the package) overwrite the existing data definitions in the destination environment only if the Replace in Destination field is checked.
If the data definitions do not exist in the destination environment, then all of the new data definitions imported as a part of the configuration package are inserted into the destination environment, by the system.
The data sets/default values are not included for the data definitions that are not selected.
If users have defined the data sets/default values in the destination server, then those values remain as they are.
Used in Selected Designs
The column will have a "Yes" value for the Data Definitions (DDs) which are being used in the selected designs. If you deselect any particular design in the Design node, then if you go back to the Data Definitions node, the value will be empty for respective DDs.
Note: The data set values are always included for Project phase data definition.
Data Structure Setup - Cost Codes
All cost codes are available for selection.
The selected Cost Codes (included in the package), when imported, overwrite as data sets values for the corresponding Cost Codes existing in the destination environment only if the Replace in Destination field is checked. If the Cost Codes do not exist in the destination environment, the new cost codes, imported in as part of the configuration package, are inserted into the destination environment.
The data sets/default values are not included for the data definitions that are not selected.
Data Structure Setup - Data Views
All Data Views are available for selection.
The selected Data Views (included in the package), when imported, overwrite in the destination environment only if the Replace in Destination field is checked. If the Data Views do not exist in the destination environment, the new Data Views, imported in as part of the configuration package, are inserted into the destination environment.
The dependency errors related to data views not selected will be checked when component analysis is performed during the configuration package creation.
Note: For a Data View that is dependent on another Data View, there are no dependency errors that are when component analysis is performed during the configuration package creation; however, publishing of the Data View fails because of the dependency and the system displays an error message upon import.
Data Structure Setup - Dynamic Data Sets (DDS)
The DDS are available for selection.
The selected DDS, included in the configuration package when imported, either create a new configuration or overwrite the existing configuration in the destination environment, only if the Replace in Destination field is checked.
If the DDS does not exist in the destination environment, then the new DDS imported as a part of the configuration package are inserted into the destination environment, by the system.
When a dynamic data set (DDS) is used in a uDesigner object (such as a business process), the DDS configuration that exists in the package must match the DDS configuration that exists in the destination environment; otherwise, Unifier will mark the process as a data definition conflict, and the import will fail.
Used in Selected Designs
The column will have a "Yes" value for the Dynamic Data Sets (DDS) which are being used in the selected designs. If you deselect any particular design in the Design node, then if you go back to the Dynamic Data Sets node, the value will be empty for respective DDS.
Last Published Thursday, December 14, 2023