This section explains how to set up the information in the Data Structure Setup node. These include:
System Modules
Unifier functionality is loaded into the system through various Modules. Only the Site Administrator can load new modules.
Application Modules
Unifier Applications are deployed into the system through the Application Modules node.
Data Cube Definitions
A data cube definition is a query tool you can use to extract data and display it on a block of a configurable dashboard.
Data Definitions
Data definitions describe how data is entered into Unifier and stored. The definition consists of the data type (whether it is an alphabetical string or a number), the data size (in number of characters for strings), and the input method (from a text box, pull-down menu, radio button, or check box).
Notes:
- Users can translate custom defined strings into various supported languages. The Internationalization module (under the Configuration node in the left Navigator) contains a list of custom strings developed by the user, which provides the necessary details for translators.
- The numeric fields support international number formats (standards).
- Unifier displays all available currencies and their respective symbols
You must create data definitions before you specify the data elements for forms. For information on creating new data definitions, refer to the Unifier uDesigner User Guide. The data definitions dictate how the data element will enter and store the information in Unifier. A data definition can belong to one of the following categories:
- Basic: Predefined or user-defined Data Definitions that contain all Data Definitions except the Cost Code definitions.
For the SYS User Date Format Data Definition, the data set supports the 24-hour time format. In the User Preferences form, under the Regions tab, the field Date Format uses SYS User Date Format Data Definition.
- Line Item Data Picker: This is a system-defined Basic data definition.
- Cost Codes: Displays the type of cost code (fields that define the structure of the Cost Codes) specified in uDesigner for the project. The type of cost code available for Projects (Standard) is CBS.
- Data Picker: Data pickers work with master business process logs, shells, and configurable managers that function across a shell hierarchy. The purpose of a data picker is to make it easier for users to choose records:
- From a master business process log
- From a class in a configurable manager that operates across shells
- For auto-creation across shells
A data picker usually displays an extra navigation structure that makes it easier for users to choose records to work with. In operation, a data picker navigates to a specific business process, shell, or configurable manager and then extracts the records to display on the list by using a query the Unifier Administrator sets up.
Data Elements
Data elements combine a “Data Definitions” with a field label to become what users see on the forms in Unifier. The fields on the forms the users see are filled by data elements. A data element can be a text box, where the user types in information; a pull-down menu of choices (also known as a picker), such as dates or names; radio buttons, where the user must select one of the options presented; or a check box, where the user has the option of choosing something or not. Data elements are the name and form label only—the element is essentially an empty “shell” that will not contain values until they are specified in Unifier. For information on creating new data elements, refer the uDesigner User Guide.
Data Indexes
Allows the creation of user-defined database indexes that speed up the performance of large data sets. The database index name is constructed by a fixed prefix, UUU, plus internal row_id, followed by _ and a user-defined suffix and description.
Data Views
Provides a view of Unifier data obtained via SQL query. It allows access to all Unifier database tables in a company registry (registry dependency ensures data security). Data Views enable administrators to design and deploy custom reports (program- and shell-level), create user-defined reports (UDRs), and utilize data as a source for Data Cube Definitions (used to display live, or cached data in a custom company or shell dashboards).
Dynamic Data Sets
A dynamic data set is comprised of a "set" of data elements that includes a master data element and dependent data elements, which can be pull-down menus or radio buttons. You set up the elements and behavior of the set.
Public Searches
A public search is any set of criteria that was specified to search a log for specific records.
Reports
The System and Logs report modules are loaded by the Site Administrator.
Statuses
Statuses are created in the Data Structure Setup node and indicate the position of an asset, line item, record, and tag at any point in the business process, such as “approved,” “pending,” or “closed.” The status is what drives the workflow from one step to the next.
- Assets Statuses: An asset status controls which assets are displayed on an Asset class sheet, instead of impacting the disposition of a business process or line item like other statuses.
- Line Item Statuses: A line item status is part of the form that moves through the workflow, but it is not a visible part of a workflow.
- Record Statuses: At each transaction, the Unifier user must apply a status to the record. Each business process produces at least one, and sometimes many, transaction records during its workflow.
ER Views
Provides a tabular view of Data Elements and Data Definitions used in modules.