Property

General Information

The workspace area for the management of Properties can be accessed via menu Properties. 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

Details Page

In order to view more details related to a Property, users may open the Property in view mode by clicking on it from the list view. 

The view mode of a Property is subdivided into different tabs. The visibility and order of the displayed tabs is configurable by users with configuration rights. Furthermore, custom tabs can be created. The 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 Properties:

Export 

Users may export all or a selection of Properties in one of the available export formats.

Following export formats are available:

→ from the tabular view of Properties:

• DIN 4002

• Spec Sheet XLSX

→ from the tree view of Properties:

• 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. 

DIN 4002 Export Format

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.

Spec sheet XLSX Export Format

Create

This functionality allows the user to create new Properties of different Data types and Property Types

Mandatory attributes are marked with an asterisk. Non-editable attributes are displayed as read-only. 

When the work is finished, the user may save the new Property 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.

In Create / Edit views, user has the possibility to select a Rounding Rule out of a comprehensive list of rounding rules.

Desired Rounding Rule needs to be set for relevant Property e.g. “round to 2 fixed digit“, then Property may be valuated to full extent in Item e.g. 123.123

When user exports relevant Item in Extended ISO29002P10 profile, the rounding rule is applied as follows: “123.123” is rounded up to “123.12”.

Once set, the Rounding Rules will only have effect in the Publication Manager. For complete description of Rounding Rules and examples, please consult Item Manager User Guide, chapter 'Rounding Rules'.

Valency type can be configured at Dictionary level (not only globally at system level as until now) pro Property type as univalent or multivalent from Dictionary configuration “Property Datatypes with Univalence“.

If in Create/ Edit Dictionary view, users adds/copies in the selected values section of this configuration Property data type Integer (count) for example and saves changes, then in Create Property view on this Dictionary, when selecting data type Integer (count), Valency type field is no longer editable (Multivalent/Univalent), but has Univalent preselected and view-only.

Data types

Properties have different data types. User may select them in the create property interface.

Property data types:

Property types

Properties have different types. User may select them in the create property interface.

Property types:

Change Text

With this functionality users can edit the textual attributes of a Property. Mandatory attributes are marked with an asterisk. Non-editable attributes are displayed as read-only. The user has also the possibility to change the Data type of the property if needed. 

When the work is finished, the user may save the new Property 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.  

Note, that changing the Data Type of a Property is an incompatible change and will lead to a change of the unique object code. On performing a data type change via Change Text, the following actions happen:

• a new property with the changed data type is created and receives a new ID

• the "old" property is replaced by the new property with the changed data type (change request of type Replace property)

• the "old" property is deprecated and cannot be used anymore

Compare 

Two or more Properties can be opened side by side in a compare view. The attributes (standard and extended) displayed in the Compare graphical user interface are configurable. 

Different values of the attributes are highlighted by the system in color.

The compare view offers users two options:

• Equal values: this options will include in the compare view also the attributes having equal value.

• Empty values: this option will include in the compare view also the attributes having no value. 

The Value lists displayed on the first position in the compare view may be changed by using the pin-button on the header of the column. Value lists may be removed from the compare view by using the trash-bin button.

Delete

This functionality allows users to delete existing Properties.

Note: on deletion, the Property 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 Property selected for deletion. User may check the attributes/relations of the Property 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 Property 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 Property will be automatically executed (released). As a result, the Property is immediately withdrawn from further usage and is displayed as inactive within a given release (grayed out). 

Copy

This functionality allows users to create assignments of Property to other elements (Aspect, Block, Application class) by means of copy and paste. 

The user may select a Property in the tabular view or in the tree view and press button Copy. In the tabular view or tree view of Application class (Aspect, Block), the user may select an Application class (Aspect, Block) where the copied Property should be assigned.

Note: The Paste button will appear only if the copied element type is compatible with the selected item (i.e. only if the selected Application class (Aspect, Block) allows an assignation of the copied Property).

On pressing the Paste button, the system will lead to the Assign Property page where user may confirm the assignment by pressing button Save or Save and Release. 

On Save, a Change Request for the assignment of the copied Property to the selected Application class (Aspect, 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 assignment of the copied Property to the selected Application class (Aspect, Block) will be automatically executed (released). As a result, the Property is immediately connected to the Application class (Aspect, Block).

Reactivate

This functionality allows users to reactivate (to make them available for usage within a certain release) the deprecated Properties. The button "Reactivate" is active only if the selected Property is deprecated.

For the reactivation of Property, the Reactivate graphical user interface consists of a detailed view of the selected Property. The user may save the Property Reactivation 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. 

Replace

This function allows users to replace a property that is no longer needed/obsolete with an actual one.

The replacement can be either local or global. If the user chooses local replacement, the system offers a list of all classes to which the property is assigned and the user can select the classes in which the property should be replaced. In this case, only the connections between property and class are deprecated and replaced with a connection to a new property. If the user selects the global replacement, the property will be replaced in all classes where it is used and then it will be deprecated. 

The starting point of this functionality is the tabular view of Properties, where the user can select the Property to be replaced. In the next step, the user chooses if the replacement is global or local and with or without successor. 

Depending on the selected options, the user continues the process on the following pages:

• Type of replacement: Global / Without successor - the system displays the details page of the Property to be replaced. On Save, a Change Request for the replacement of the Property will be created. On Save and Release, the Change Request for the replacement of the Property will be automatically executed (released). As a result, the Property and its connections are immediately withdrawn from further usage and it is displayed as inactive within a given release (grayed out). 

• Type of replacement: Global / With successor - on the next page the user selects the replacing Property (Successor). In the next step, the system displays the details page of the Property to be replaced and the details page of the replacing property. On Save, a Change Request for the replacement will be created. On Save and Release, the Change Request for the replacement will be automatically executed (released). As a result, the replaced property and its connections to the classes to which the property is assigned are immediately withdrawn from further usage and are displayed as inactive within a given release (grayed out). The connections are replaced by connections between the classes and the replacing property (successor).  

• Type of replacement: Local / Without successor - on the next page the user selects the classes where the property is to be replaced. In the next step, the system displays the details page of the Property to be replaced and a list of Classes where change applies. On Save, a Change Request for the replacement of the Property will be created. On Save and Release, the Change Request for the replacement of the Property will be automatically executed (released). As a result, the connections between the property and the selected classes are immediately withdrawn from further usage and it is displayed as inactive within a given release (grayed out). 

• Type of replacement: Local / With successor - on the next page the user selects the classes where the property is to be replaced and continues to the page where the replacing Property (Successor) is selected. In the next step, the system displays the details page of the Property to be replaced and the details page of the replacing property. On Save, a Change Request for the replacement will be created. On Save and Release, the Change Request for the replacement will be automatically executed (released). As a result, the replaced property and its connections to the classes to which the property is assigned are immediately withdrawn from further usage and are displayed as inactive within a given release (grayed out). The connections are replaced by connections between the classes and the replacing property (successor).  

Note that Change Requests usually undergo an approval process before they are released and become effective. 

Clone

This functionality allows users to create a new Property using an existing Property as master copy. 

The starting point of a clone-action is an existing Property. After selection of the Property to be used as master copy and pressing button Clone, the system displays the Create graphical user interface, enriched with information copied from the master copy:

• the attributes of the new Property are pre-filled with information from the master copy

When the work is finished, the user may save the new Property 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. 

Restrict value list

This functionality allows users to define which Values from a Value list are valid for a Property in the context of a specific class (Application class, Block, Aspect). This functionality is used to restrict the Values of a Property in the context of a specific class if specific values cannot be used as valuations of the Property when describing a product on respective class. For example a Property Material can have a value list containing different materials: iron, steel, plastic, glass, cotton, leather, synthetics etc. but in context of a class e.g. Gloves, certain materials like iron, steel, plastic and glass are not useful. Therefore, the list of values can be restricted so that only the values leather, cotton and synthetic can be used in the context of this class.

The starting point of this functionality is the tabular view of Properties, where the user can select the Property for which the Value list should be restricted. 

For the value list restriction, the graphical user interface consists of:

• the Property details page

• the Class details page; Note: the class must first be selected using the 'Select' option. Only Classes in which the selected Property is used are allowed.

• the list of all values in the Value List assigned to the Property

From the list of all possible Values, the user can select the values which will remain usable for the selected Property in relation to the selected Class.

When the selection is finished, the user may confirm the Value List restriction by pressing button Save or Save and Release. 

On Save, a Change Request for the restriction of the Value list of the selected Property will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the restriction of the Value list for the selected Property will be automatically executed (released).

Once Change Request is released, the Value restrictions are visible on the Constraints tab of the selected Property and of the Class(es) in which the Property's Values List was restricted.

Assign

The connection between Property and Synonym, Value list, Condition or Relation can be created using the Assign function. 

The Assign functionality (Button Assign) groups together all these four options.

• Assign Synonym

• Assign Value list

• Assign Condition

• Assign Relation

Assign Synonym to a Property

This functionality allows users to assign Synonym(s) to the selected Property.

The starting point of this functionality is the tabular view of Properties, where the user can select the Property to which a Synonym should be assigned. In the next step, the user can select the Synonym(s) to be assigned from the list of available Synonyms.

For the assignment of a Synonym(s) to a Property, the graphical user interface consists of the list of selected Synonyms and the Property details page.

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 Synonym(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 assignment of the Synonym(s) will be automatically executed (released). As a result, the connection between the Property and Synonym(s) is immediately available.

Assign Value list to a Property

This functionality allows users to assign Value list to the selected Property.

The starting point of this functionality is the tabular view of Properties, where the user can select the Property to which a Value list should be assigned. In the next step, the user can select the Value list to be assigned from the list of available Value lists.

For the assignment of a Value list to a Property, the graphical user interface consists of the list of selected Value list and the Property details page.

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 Value list 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 Value list will be automatically executed (released). As a result, the connection between the Property and Value list is immediately available.

Assign Condition to a Property

This functionality allows users to assign a Condition (Property of type Condition and data type Integer (count)) to the selected reference Property (Property of type dependent and data type Reference.) This assignment is used to create a cardinality in the dictionary structure.

The starting point of this functionality is the tabular view of Properties, where the user can select the reference Property to which a condition should be assigned. In the next step, the user can select the Condition to be assigned from the list of available properties of type Condition.

For the assignment of a Condition to a Property, the graphical user interface consists of the Condition Property details page and the Dependent (Reference) Property details page.

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 Condition list 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 Condition list will be automatically executed (released). As a result, the connection between the Reference Property and Condition is immediately available.

Assign Relation to a Property

This functionality allows users to create relations between Properties. 

The starting point of this functionality is the tabular view of Properties, where the user can select the first Property which will be End 1 of the relation. In the next step, the user can select the second Property which will be End 2 of the relation. 

For the assignment of a relation, the graphical user interface consists of the indication of the Preferred Name and IRDI of the two Properties between which the relation will be created.

The user may confirm the assignment by pressing button Save. 

The relation between the two Properties is immediately available and can be viewed in tab Relations of respective Properties.

Add to

The connection between Property and the superordinate structure element can be created using the add function. The possible connections to the superordinate structure elements are:

• assigned to an Application Class

• assigned to an Aspect

• assigned to a Block

The Add functionality (Button Add to) groups together all these three options.

Add Property to Application class

This functionality allows users to add selected Property to an Application Class. 

The starting point of this functionality is the tabular view of Properties, where the user can select the Property to be added to an Application Class. In the next step, the user selects the Application Class to which the assignment should be made.

For the assignment to an Application Class, the graphical user interface consists of the Application Class details page on one tab and the list of properties to be assigned on the second tab.

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 Property 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 Property will be automatically executed (released). As a result, the connection of the Property to the Application Class is immediately available.

Add Property to Aspect

This functionality allows users to add selected Property to an Aspect. 

The starting point of this functionality is the tabular view of properties, where the user can select the Property to be added to an Aspect. In the next step, the user selects the Aspect to which the assignment should be made.

For the assignment to an Aspect, the graphical user interface consists of the Aspect details page on one tab and the list of properties to be assigned on the second tab.

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 Property 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 Property will be automatically executed (released). As a result, the connection of the Property to the Aspect is immediately available.

Add Property to Block

This functionality allows users to add selected Property to a Block. 

The starting point of this functionality is the tabular view of properties, where the user can select the Property to be added to a Block. In the next step, the user selects the Block to which the assignment should be made.

For the assignment to a Block, the graphical user interface consists of the Block details page on one tab and the list of properties to be assigned on the second tab.

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 Property 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 Property will be automatically executed (released). As a result, the connection of the Property to the Block is immediately available.

Withdraw

If the connection of a Property to a Synonym, Condition or Value list is not needed anymore, the assignment can be deprecated using the Withdraw functionality.

The Withdraw functionality (Button Withdraw) groups together the following options:

• Withdraw Synonyms - available if the Property has an active connection to a Synonym

• Withdraw Condition - available if the Property has an active connection to a Condition Property

• Withdraw Value list - available if the Property has an active connection to a Value list

Withdraw Synonym

This functionality allows users to deprecate (withdraw from usage) the connection between Synonym and a specific Property.

The starting point of this functionality is the tabular view of properties, where the user can select the Property. In the next step, the user can select the Synonym(s) to be withdrawn from the list of the Synonyms assigned to the selected Property.

For the withdrawal of Synonym, the graphical user interface consists of the details page of the Property and the list of Synonyms 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 Synonym(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 Synonym(s) will be automatically executed (released). As a result, the connection of the Synonym to the Property is immediately deprecated and displayed grayed out.

Withdraw Condition

This functionality allows users to deprecate (withdraw from usage) the connection between a condition and a dependent Property.

The starting point of this functionality is the tabular view of properties, where the user can select the dependent Property. In the next step, the user selects the Condition to be withdrawn.

For the withdrawal of Condition, the graphical user interface consists of the details page of the dependent and of the condition Property.

The user may confirm the withdrawal by pressing button Save or Save and Release. 

On Save, a Change Request for the withdrawal of the Condition 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 Condition will be automatically executed (released). As a result, the connection of the Condition to the Property is immediately deprecated and displayed grayed out.

Withdraw Value list

This functionality allows users to deprecate (withdraw from usage) the connection between a Value lists and a specific Property.

The starting point of this functionality is the tabular view of properties, where the user can select the Property. In the next step, the user selects the Value list to be withdrawn.

For the withdrawal of Value list, the graphical user interface consists of the details page of the Property and the Value list.

The user may confirm the withdrawal by pressing button Save or Save and Release. 

On Save, a Change Request for the withdrawal of the Value list 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 Value list will be automatically executed (released). As a result, the connection of the Value list to the Property is immediately deprecated and displayed grayed out.

Move

This functionality allows users to move Properties from any type of class to any type of class (Aspect-Block, Block-Block, Block-Aspect, Block-Application Class etc.). Only one Property can be moved at a time.

The starting point of this functionality is the tabular view of properties, where the user selects option "Move" in the Move-drop-down, without selecting any Property. As a next step, the class from where to move the Property needs to be selected and then the actual Property to be moved.

In the next step, the target class where Property will be moved to needs to be selected. 

For Move Property, the graphical user interface consists of three tabs:

1. "Move from class" - containing the details of the source Class, structured in tabs.

2. "Moved properties configure assign" - containing the Property to be moved, possibility to remove it and select a different one.

3. "Move to class" - containing the details of the target Class, structured in tabs with possibility to select a different target.

On Save, a Change Request for Move Property 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 Move Property will be automatically executed (released). As a result, the connection of the Property to the old class is immediately deprecated and displayed grayed out.

Join

This functionality allows users to join Properties belonging to all types of classes (Application Classes, Aspects, Blocks). There should be at least two source Properties to be joined into one target. The source Properties, as well as the target Property must all share the same data type.

The starting point of this functionality is the tabular view of properties, where the user selects option "Join" in the Move-drop-down, without selecting any Property. As a next step, the class where join of Properties takes place needs to be selected. System displays the Properties assigned to selected class. In this list, the Properties to join need to be selected. 

In the next step, the Property to join into will be selected.

For Join Property, the graphical user interface consists of four tabs:

1. "Configuration of joined property removal" - here the Consistency type needs to be selected. Additionally, the user has the option to decide whether deprecation should apply to child classes or not.

2. "Joined properties" - containing the list of Joined Properties and possibility to Remove them.

3. "Assign of join-target property" - contains the target Property into which the ones from previous tab will be joined, as well as possibility to set new index number.

4. "Class where join takes place" - containing the details of the Class where join takes place, structured in tabs.

On Save, a Change Request for Join Property 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 Join Property will be automatically executed (released). As a result, the connections of the joined Properties to the selected class are immediately deprecated and the new join-target Property is assigned in the indicated position.

Transform (Merge into Cardinality)

This functionality allows users to create Change Requests of type "Merge property into cardinality". These Change Requests are useful for the transaction update because they can tell an item convertor that migrates items from old to new release that the cardinal counter needs to be set to a certain value (in our example the value 4) and in which of the cardinal multiplied block instances (Wheel 1, Wheel 2, Wheel 3, Wheel 4 in our case) the value of the property is meant to go into.

The starting point of this functionality is the tabular view of properties, where the user selects option "Transform" in the Move-drop-down, without selecting any Property. In the next step the Class from where numbered Properties are merged needs to be selected. Then, the user selects the numbered Properties to be merged. These must have the same data type.

As a next step, the user needs to select the target Class where numbered Properties are merged and then the Property into which merge takes place.

For Transform Property, the graphical user interface consists of four tabs:

1. "Merge numbered properties from class" - in which the details of the source class are displayed in the specific tabs, as well as possibility is given to select the desired Consistency type. Additionally, the user has the option to decide whether deprecation should apply to child classes or not.

2. "Merged numbered properties" - here the list of merged numbered Properties is displayed, with possibility to remove.

3. "Assign of merge-target property" - displays the Property selected as target of the merge operation.

4. "Cardinal class where numbered properties are merged" - displays the details page of the target class for the merge operation, structured in tabs.

On Save, a Change Request for Merge Property into cardinality 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 Merge Property into cardinality will be automatically executed (released). As a result, the connections of the merged Properties to the selected class are immediately deprecated and the new merge-target Property is assigned in the indicated position.