Master data objects
Master data is information about products, suppliers and customers, for example. It is usually saved once and is available to the user to be used and changed by them. The master data objects are managed and maintained via the data management module.
The data records are displayed as a table. The columns are the information from the detailed view. (Depending on the template, the content may vary depending on the customer).
The following functions are available for master data:
-
Create new element
-
Update element (reload)
-
Module jump
-
Trigger actions for element
-
Manage data records
The following functions are available for data records:
-
Delete data record
-
Open data record
-
Module jump
The list contains all created master data objects. To display the list or a master data object, double-click on it. a master data object can be viewed by double-clicking on the corresponding line. The detailed view for the respective master data object (or attribute) opens.
Master data
Data management is used to map all the necessary master data of an application and offers extensive interfaces for embedding the data and meta information in the processes and application workflows. Data object structures can be flexibly created, changed or extended on the basis of templates. Different data objects can then be set in relation to each other as superordinate or subordinate elements and managed as dependent on each other. Master data can be created and changed manually or automatically, with all changes validated, versioned and approved.
Templates
Master data is mapped by configuration (modeling) on the basis of so-called templates. By activating these templates, the data storage is automatically generated in the database - including the interfaces for master data search and maintenance. This flexible approach makes it possible to map customer-specific master data without programming.
The basic installation includes templates that can be created or adapted individually. The design can also be configured. All common data types (string, date, lists, numbers, checkboxes) are supported when creating templates.
Optionally, Data Management can be expanded to include the option of defining template-based views for maintaining the respective data in order to enable role-specific data maintenance when roles are assigned to a master data object multiple times. Role-specific process execution of check processes can be enabled by default via the configuration of the technical workflows.
Relationships between objects
The ranking of the attributes also places them in a hierarchical relationship to each other. They form a tree, i.e. each attribute has exactly one superordinate and subordinate attribute. The attributes are related to each other and refer to other entries.
As an example for the "Area structure" area, the relation can be as follows:
The parent element of the "District" master data object displayed is the "Federal state" and the subordinate elements are the "Municipalities".
See also Linking master data objects
The main master data of an attribute is displayed in this area and can be edited accordingly using the following functions:
-
Add attribute
-
Edit
-
Open attribute
Parent elements
The attribute has exactly one parent attribute. The attributes are related to each other and refer to other entries. The parent attribute is displayed in this window.
The following functions are available for parent elements:
-
Create new element
-
Link element
-
Display elements
-
Unassign
-
Open element
-
Search
Subordinate elements
The attribute has exactly one subordinate attribute. The attributes are related to each other and refer to other entries. The subordinate attribute is displayed in this window.
The following functions are available for subordinate elements:
-
Create new element
-
Link element
-
Display elements
-
Unassign
-
Open element
-
Search
Versioning
All changes (both to workflows and modules) are versioned. It is easy to trace the changes made. It is also possible to switch to old versions and create tags that combine several workflows into one overall package (tag).
The following functions are available for versioning:
-
Open selected version
-
Search
-
"Star" means: currently active version
-
Open any version
-
Display version differences (opt.)
Active version: The current validity of a version can be activated via the "asterisk". This means that an older (or newer) version is also assigned validity.