Overview
A block is a subset of Properties within an Application Class. If all Properties of a device type are arranged with equal importance on one single level, the list will become less understandable while more Properties are added. Clarity can be achieved by structuring the Properties into sub-concepts, which are described by Properties. These sub-concepts are called Block (of Properties). Every Block has a name and definition.
A Block - in contrary to the related concept of an Aspect - describes characteristics of the product itself.
A Block consists of one or more Properties describing an abstraction of a feature of an object or of a part of a composite device. A Block of Properties may contain other Blocks of Properties nested to the necessary level as dictated by the technical requirements. At the lowest level, a Block will contain only properties.
If sub-blocks are present, a Reference Property is included in the higher-level block to refer to the respective sub-block and to fix the place where the sub-block should be introduced.
When creating complex structures, Blocks are used to create cardinality and /wiki/spaces/EDMD1/pages/209453319.
A cardinality structure consists of an Integer condition property(number of..) and a dependent reference Property pointing to a specific Block. This structure allows multi-valuation of respective Block in the product description. Example: a car has four wheels. In the dictionary structure, a cardinality is created around Block "Wheel". In the product description, Block "Wheel" can be valuated 4 times for each specific wheel of the car.
A polymorphism consists of a generic - specialized Block structure and allows selection and valuation of needed specialization in the product description. Example: a device has different outputs, but the outputs implemented for a specific device are known only on product description. In the dictionary structure, a polymorphism is created around generic Block "Output" and all of its specializations (Digital output, Analog output, Hybrid output etc.) allowing the selection of the needed specialization when creating the product description.
/*<![CDATA[*/ div.rbtoc1770892090959 {padding: 0px;} div.rbtoc1770892090959 ul {list-style: disc;margin-left: 0px;} div.rbtoc1770892090959 li {margin-left: 0px;padding-left: 0px;} /*]]>*/ Overview General Information Details Page Export Export Options DIN4002 Export Options Spec Sheet XLSX Create Change Text Delete Reactivate Reactivate Block Reactivate Property Assignment Assign Assign Block Reference Assign Property Withdraw Withdraw Block Reference Withdraw Property Create Range Constraint
General Information
An introduction to the structure elements of the dictionary can be found on page Introduction.
The workspace area for the management of Blocks can be accessed via menu Block. Information on the graphical user interface and basic functionalities can be found on page Graphical User Interface and Basic Functions.
This workspace offers users different functionalities described in brief in the following table as well as in more detail in the next chapters.
Toolbar in Browse View
|
Button Icon |
Button Name |
Description |
|---|---|---|
|
|
Search |
Triggers a search in the available content, considering the search options set in the advanced search. |
|
|
Tree view |
Allows navigation to the hierarchical view of Blocks. |
|
|
Perspective view |
Allows navigation to the perspective view of Blocks. |
|
|
Compare |
Allows the comparison of two or more Blocks. |
|
|
Export |
Allows the export of desired Blocks. |
|
|
Create |
Allows the creation of new Blocks. |
|
|
Change text |
Allows editing the attributes of a selected Block. |
|
|
Delete |
Allows deletion of a selected Block. |
|
|
Reactivate |
Allows reactivation of a deprecated Block or deprecated Properties assigned to a Block. |
|
|
Assign |
Allows assignation of dictionary elements (Block Reference, Property) to a selected Block. |
|
|
Withdraw |
Allows withdrawal of dictionary elements (Block Reference, Property) from a selected Block. |
|
|
Create range constraint |
Allows creation of range constraints. |
|
|
Start workflow |
Allows starting a workflow for selected Block. |
Details Page
In order to view more details related to a Block, users may open the Block in view mode by clicking on it from the list view. Note: opening a Block in view mode is also possible from the tree view of Blocks.
The view mode of a Block is subdivided in different tabs. The visibility and order of the displayed tabs is configurable by users with configuration rights.
Furthermore, custom tabs can be created. Custom tabs allow customers to organize the standard and extended attributes as required by their business use cases.
Tabs which do not contain any information are grayed out.
The following table gives an overview of the tabs available for a Block.
|
Tab Name |
Description |
|---|---|
|
General |
Tab General displays the standard and extended Attributes of a Block. The visibility and order of the attributes displayed in tab General is configurable by users with configuration rights via the Validation Framework. |
|
Admin |
Tab Admin displays administrative information such as creation date, version date and creator of the selected Block. |
|
Attribute |
Tab Attribute displays extended attributes of the selected Block. |
|
Change request |
Tab Change request displays the Change requests in connection with the selected Block. |
|
History |
Tab History displays historical information on the selected element. |
|
Release |
Tab Release displays the release(s) the Block is part of. |
|
Keywords |
Tab Keywords displays in a tabular view information related to the Keywords assigned to the selected Block. |
|
Synonyms |
Tab Synonyms displays in a tabular view information related to the Synonyms assigned to the selected Block. |
|
Property |
Tab Property displays in a tabular view information related to the Properties assigned to the selected Block. |
|
Reference |
Tab Reference displays in a tabular view information related to the Classes ((6.2) (dicmgr user) Application Classes, other Blocks) and Block References in which the selected Block is used. |
|
Mapping |
Tab Mapping displays in a tabular view information related to the Mappings of the selected Block to other Blocks. Note: Tab Mapping is only available if the Dictionary Transformation Manager is licensed and the user has Dictionary Transformation Manager Viewer or Editor rights. |
|
Impacted groups |
Tab Impacted groups displays the groups that are impacted by a change of the selected element. Precondition: owner groups are set via Access Control. |
|
Document |
Tab Document displays in a tabular view information related to the documents connected to the selected Block. Note: Tab Document is only available if the Document Manager is licensed and the user has Document Manager Viewer or Editor rights. |
|
Template |
Tab Template displays in a tabular view information related to the Templates of the selected Block. Note: Tab Template is only available if the Template Manager is licensed and the user has Template Manager Viewer or Editor rights. |
|
Constraints |
Tab Constraints displays in a tabular view the Constraints existing for the selected Block. |
|
Relations |
Tab Relations displays the Free Relations the selected Block has to other elements. |
|
Log |
Tab Log contains logging information related to the selected Block and is visible only for users with administrator rights. |
Export
Users may export all or a selection of Blocks in one of the available export formats.
The following export formats are available:
→ from the tabular view of Blocks:
-
DIN 4002
-
Spec Sheet XLSX
→ from the tree view of Blocks:
-
Spec Sheet XLSX
After defining the export options in the graphical user interface, the user may press the export button and the export will be started in the background. The exported file will be sent per e-mail to the specified e-mail address.
Export Options DIN4002
Through a redesign of the eptos export pages, the external appearance of the exports has now been fully adapted to the defined Usability Guidelines.
This has significantly improved the look and feel of these pages.
In a harmonized DIN 4002 Export dialog the user can save and load favorite dialog settings in tab “Selection of attributes” to access those settings faster instead of selecting them again for each new export.
|
Tab |
Option |
Description |
|---|---|---|
|
General |
Export range |
The Export range option offers the following selection possibilities:
|
|
General |
Split file into chunks |
Allows user to decide via check-box whether the file should be exported in one complete file or separated in more, smaller files. |
|
General |
Release* |
The release selector is displayed if Export range option "all" is selected. In this case the system will export all Blocks existent in the release selected by the user. |
|
General |
Table result renderer |
Allows users to select the export format (xlsx, csv). |
|
General |
Export languages |
Contains list of all available content languages, including check-box for selection. As soon as box is checked, respective language is added in the Export languages field, including option for removal. |
|
General |
To/CC |
Allows users to input the e-mail address where the exported file will be sent. |
|
Selection of attributes |
Export attributes |
Allows users to select from a set of predefined Attributes of Blocks the ones which will be exported. All three columns from this Tab ("Column name", "Column code" and "Export languages") are sortable and have also filtering possibility. Column "Export languages" contains the languages selected in previous Tab "General". |
Export Options Spec Sheet XLSX
|
Tab |
Option |
Description |
|---|---|---|
|
Data Source |
Export range |
The Export range option offers the following selection possibilities:
|
|
Data Source |
Release* |
The release selector is displayed if Export range option "all" is selected. In this case the system will export all Blocks existent in the release selected by the user. |
|
Data Source |
Export type |
Allows users to select the export type (DIN 4002, Spec Sheet XLSX). |
|
Data Source |
Template type to apply |
Allows users to select the template type to apply (default, nondefault). |
|
Data Source |
Define display |
The Define display option offers the following selection possibilities:
|
|
Data Source |
Perform expansion of value and unit lists as structure |
The Perform expansion of value and unit list as structure offers the following selection possibilities:
|
|
Data Source |
To/CC |
Allows users to input the e-mail address where the exported file will be sent. |
|
Selection of attributes |
Export attributes |
Allows users to select the languages in which the export will be done. |
Note: in case the exported structure contains Elements that form a loop in the structure, the export detects this infinite loop and, instead of running endlessly, it considers the loop as a content error, highlights the export row in red and indicates to user the message that 'An infinite loop was detected'.
Create
This functionality allows users to create new Blocks.
Since Blocks are hierarchical structures, the first step when creating a Block is the selection of its placement in the hierarchy. The new Block can be placed on the first level in the hierarchy (in this case the root of Blocks, i.e. the uppermost folder in the hierarchical view needs to be selected) or on a lower level (in this case a parent Block needs to be selected in the hierarchical view).
Note: if all Blocks in a system are only on the first level, the system can be configured to set the root automatically. In this case, the step of the root selection from hierarchy is skipped and the Create graphical user interface will be displayed on pressing button Create.
After the placement of the Block was defined, the user may continue with filling in the attributes of the new Block in the Create graphical user interface displayed in the next step.
Mandatory attributes are marked with an asterisk. Non-editable attributes are displayed as read-only. Translatable fields are marked with a country flag.
When the work is finished, the user may save the new Block as Change Request (using button Save) or directly as structure element (using button Save and Release).
Change Requests usually undergo an approval process before they are released and become effective.
Change Text
This functionality allows users to edit the textual attributes of a Block. Mandatory attributes are marked with an asterisk. Non-editable attributes are displayed as read-only. Translatable attributes are marked with a country flag.
When the work is finished, the user may save the changed Block as Change Request (using button Save) or directly as structure element (using button Save and Release).
Change Requests usually undergo an approval process before they are released and become effective.
Delete
This functionality allows users to delete existing Blocks.
Note: on deletion, the Block will be marked as deprecated, meaning that it is withdrawn from further usage. Deprecated elements are displayed grayed out in the system and they cannot be worked on or used anymore.
On pressing the Delete button, the system displays the details page of the Block selected for deletion. User may check the attributes/relations of the Block before proceeding with the deletion.
The user may confirm the deletion by pressing button Save or Save and Release.
On Save, a Change Request for the deletion of the Block will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the deletion of the Block will be automatically executed (released). As a result, the Block is immediately withdrawn from further usage and is displayed as inactive within a given release (grayed out).
Reactivate
This functionality allows users to reactivate (i.e. to make them available for usage within a certain release) the following elements:
-
a deprecated Block
-
a deprecated assignment of a Property to the selected Block
The options in the drop-down button are active only if the selected Block meets certain conditions:
-
Block → the selected Block is deprecated
-
Property assignment → the selected Block has at least one deprecated Property assignment
Reactivate Block
In order to reactivate a deprecated Block, the user needs to select a deprecated Block in the tabular view or tree view and press button Reactivate / Reactivate.
The system displays the Reactivate graphical user interface, which consists of the detailed view of the selected Block. Therefore, user can first check the detailed information of the Block before confirming the reactivation by pressing button Save or Save and Release.
On Save, a Change Request for the reactivation of the Block will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the reactivation of the selected Block will be automatically executed (released). As a result, the Block is immediately activated and can be used.
Reactivate Property Assignment
In order to reactivate deprecated Property assignments for a specific Block, user has to first select the Block in the tabular view or tree view and press button Reactivate / Property assignment.
Note: the button is active only if the selected Block has deprecated Property assignments.
In the next step, the system displays a list of Properties having a deprecated assignment to the Block. The user can select one or more Properties and then proceed with the reactivation.
For the reactivation of Property assignments, the Reactivate graphical user interface consists of the details page of the Block and the list of Properties to be reactivated.
The user may confirm the reactivation by pressing button Save or Save and Release.
On Save, a Change Request for the reactivation of the Property assignments will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the reactivation of the Property assignments will be automatically executed (released). As a result, the connection of the Blocks to the Properties is immediately activated.
Assign
The connection between Block and its generic set of properties is called assignment. The properties forming the generic set can be:
-
assigned directly to the Block
-
grouped in
Blocks
and then assigned to the Block via another Block. Note: the assignment of Blocks to other Blocks is done via Block References.
Assign Block Reference
This functionality allows users to assign one or more Block References to a selected Block.
The starting point of this functionality can be the tabular view or the tree view of Blocks, where the user can select the Block. In the next step, the user can select the Block References to be assigned from the tabular view of available Block References (tabular view filtered on Properties with datatype Reference).
For the assignment of Block References, the graphical user interface consists of the details page of the Block and the list of Block References to be assigned.
The user may confirm the assignment(s) by pressing button Save or Save and Release.
On Save, a Change Request for the assignment of the Block References will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the assignment of the Block Reference(s) will be automatically executed (released). As a result, the connection of the Block to the Block References is immediately available.
Assign Property
This functionality allows users to assign one or more Properties to a selected Block.
The starting point of this functionality can be the tabular view or the tree view of Blocks, where the user can select the Block. In the next step, the user can select the Properties to be assigned from the tabular view of available Properties.
For the assignment of Properties, the graphical user interface consists of the details page of the Block and the list of Properties to be assigned.
The user may confirm the assignment(s) by pressing button Save or Save and Release.
On Save, a Change Request for the assignment of the Properties will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the assignment of the Properties will be automatically executed (released). As a result, the connection of the Block to the Properties is immediately available.
Withdraw
The connection between Blocks and their generic set of properties is called assignment. The properties forming the generic set can be:
-
assigned directly to the Block
-
grouped in
Blocks
and then assigned to the Block via another Block. Note: the assignment of Blocks to other Blocks is done via Block References
If the connection of a Block to a Property or Block Reference is not needed anymore, the assignment can be deprecated using the Withdraw functionality.
The Withdraw functionality (Button Withdraw) groups together these two options.
Withdraw Block Reference
This functionality allows users to deprecate (withdraw from usage) the connection between Block References and a specific Block.
The starting point of this functionality can be the tabular view or the tree view of Blocks, where the user can select the Block. In the next step, the user can select the Block Reference(s) to be withdrawn from the list of the Block References assigned to the selected Block.
For the withdrawal of Block References, the graphical user interface consists of the details page of the Block and the list of Block References to be withdrawn.
The user may confirm the withdrawal by pressing button Save or Save and Release.
On Save, a Change Request for the withdrawal of the Block References(s) will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the withdrawal of the Block References(s) will be automatically executed (released). As a result, the connection of the Block to the Block References is immediately deprecated and displayed grayed out.
Withdraw Property
This functionality allows users to deprecate (withdraw from usage) the connection between Properties and a specific Block.
The starting point of this functionality can be the tabular view or the tree view of Blocks, where the user can select the Block. In the next step, the user can select the Properties to be withdrawn from the list of the Properties assigned to the selected Block.
For the withdrawal of Properties, the graphical user interface consists of the details page of the Block and the list of Properties to be withdrawn.
The user may confirm the withdrawal by pressing button Save or Save and Release.
On Save, a Change Request for the withdrawal of the Properties will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request for the withdrawal of the Properties will be automatically executed (released). As a result, the connection of the Block to the Properties is immediately deprecated and displayed grayed out.
Create Range Constraint
This functionality is available in all classes lists (Application Classes, Blocks and Aspects). It allows users to define range (min/max) constraints for Integer (count) and Real (count) properties used within a Class.
e.g. In case of cardinality structures used in the context of a specific Application Class, the customer wants to restrict the possible valuations of a block by defining a specific range (e.g. for a car, the number of doors can be for example minimum 2 and maximum 5).
After pressing the button (Create Range Constraint), the system displays the tree view of classes. Starting point for the creation of range constraints is a Property with datatype Integer (count) and Real (count).
After selection of the Property the system displays the Create Range Constraint graphical user interface which consists of:
-
the details page of the selected Property
-
the details page of the Class in which the selected property is used
-
field for entering the Minimum Value for the Property
-
field for entering the Maximum Value for the Property
After filling in the desired minimum and maximum Value and entering a Reason, the user may confirm the entered value range via button Save or Save and Release.
On Save, Change Request of type New Range Constraint will be created. Change Requests usually undergo an approval process before they are released and become effective.
On Save and Release, the Change Request of type New Range Constraint will be automatically executed (released). As a result, the minimum and maximum values are displayed in brackets beside the name of the Property.