New functionalities in the ECLASS import sheet

Possible so far:

• Assignment of already existing AS to CCs
• Removing the assignment of already existing ASs to CCs

Now possible in the tab “classes”

• New creation of an AS (CR type: NEW AS) incl. specification of the aspect type (e.g. in the form of the ID of the aspect).
• Textual changes of an existing AS (EDIT AS)
•  Global withdrawal plus deletion of an existing AS (DELETE AS)

Now possible in the tab “classes_aspects”

• Assignment of an aspect to a CC (ADD CC_AS)
  • Aspect may have been created as follows
    • Newly created in the import sheet (id_class_non_existing)
    • Newly created in CDP (8-digit CR ID)
  • CC may have been created as follows
    • Newly created in the import sheet (id_class_non_existing)
    • Newly created in CDP (8-digit CR ID)
    • Already existing in CDP as IRDI (6-digit item code)

Now possible in the tab “classes_properties”

• Zuordnung eines Aspekts an eine CC (ADD CC_AS)
  • Aspekt kann folgendermaßen angelegt worden sein
    • Im Importsheet neu angelegt (id_class_non_existing)
    • Im CDP neu angelegt (8-stellige CR ID)
  • CC kann folgendermaßen angelegt worden sein
    • Im Importsheet neu angelegt (id_class_non_existing)
    • Im CDP neu angelegt (8-stellige CR ID)
    • Im CDP als IRDI bereits existierend (6-stelliger Item-Code)

Now possible in the tab “classes_properties”

• Assign properties (newly created in the import sheet, newly created in the CDP or already existing in the CDP) to an AS (newly created in the import sheet, newly created in the CDP or already existing in the CDP) (ADD AS_PR) or remove the assignment (UNASS AS_PR)

Possible so far:

• Assignment of an existing BL to its corresponding reference property (always new) (tab “properties”)
• Assign the reference property (new Import sheet ID or existing in CDP) of a corresponding existing BL to a parent SE (CC, AS, BL) or remove the assignment (tab “classes_properties”).

Now possible in the tab “classes”

• Creation of a new BL (CR type: NEW BL)
• Textual changes of an existing BL (EDIT BL)
• Global withdrawal plus deletion of an existing BL (DELETE BL)

Now possible in the tab “classes_properties”

• Assign properties (newly created in the import sheet, newly created in the CDP or already existing in the CDP) (ADD BL_PR) or remove the assignment (UNASS BL_PR)

Now possible in the tab “properties”

• Assignment of a newly requested BL (Import sheet ID or CR ID) to its corresponding reference property (always new) (NEW PR, column BF "id_bl_non-existing")

Until now, the tab valuelist did not exist in the import sheet. Values were previously assigned directly to a property. According to the data model, values are assigned to a valuelist and the valuelist is assigned to a property. The import routine and the import sheet now follow this logic.

Three tabs have been added for submitting CRs on values and valuelists:

• tab "valuelists": NEW VL, EDIT VL, DELETE VL
• tab "valuelists_values": ADD VL_VA, UNASS VL_VA
• tab "properties_valuelists": ADD PR_VL

Up to now, CRs of type REPLACE PR could only generated globally in the CR import sheet. In the CDP there is the possibility to differentiate between local and global replacements. Furthermore, it is possible in CDP to specify the type of match for a REPLACE PR.

The import routine and the CR import sheet now follow this logic, the functions have also been integrated in the import sheet on the tab “properties”.

In column K in the tab “properties”, it is possible to specify whether the REPLACE PR is to be generated locally or globally (local vs. global). In the case of a local REPLACE PR, the ID of the class in which the local CR is to be generated is entered in the column L. In the column M the type of the REPLACE PR is to be indicated. A distinction is made between:

• hard type: Source and target property must be of the same data type, otherwise an ERROR is issued.
• weak type: Source and target property must be of the same data type, otherwise an ERROR is issued. The number of values can differ in weak types.
• no consistency: Source and target properties do not have to be of the same data type.

When a user assigns structural elements to a class, the order of the lines in the import sheet is adopted for the CDP. Newly assigned SEs are appended after already assigned SEs and numbered consecutively (index number).

With the help of the column “order_index” you can define the position of a newly assigned structure element in the hierarchy.

In the example in Figure 1 (see below), the property "UMTS card integrated" is assigned to the class "PDA". In column M “order_index” it is defined that the property is assigtned to the class at position 3.

Note: The property that was previously in position 3 under the class is moved to position 4 and the subsequent properties are also moved back by one position.

This functionality is implemented on the assignment tabs "classes_aspects", "classes_properties" and "valuelists_values".

Referencing to CR IDs is possible depending on the selected change request (CR) and in the assignment worksheets.

In the columns for specifying identifiers, a differentiation is now made between

• "...non-existing"
  Either the internal Import sheet Identifier or an existing CR ID in the CDP
  must be entered here

• "...existing"
  An existing item code in the CDP (e.g. AAA123) must be entered here