Add a Term

Add a Term

To create a new Term in a Model Object, access the Term overview page for a Model Object:

Then click on the Add Term button:

The Add Term side panel window is opened:

Fill in the following information:

1. Name: Term's name
2. Description (optional): Term's description
3. DataType: The Data Type list depends on the Semantic configuration of the Generator. In this example, you can choose the following Data Types:
   
4. Length (optional): Term's maximum length. Relevant for a Data Type varchar, for example. For Data Type varchar(50), the text can have 50 characters.
5. Scale (optional): Term's scale. It is the number of digits to the right of the decimal point in a number. Relevant for a Data Type decimal, for example. For Data Type decimal(38,17), the number can have 17 digits to the right.
6. Precision (optional): Term's precision. It is the number of digits that make up a number. Relevant for a Data Type decimal, for example. For Data Type decimal(38,17), the number can have 38 digits, and 38 - 17 = 21 digits on the left.
7. Nullable (optional): Check the box if the Term can be nullable.
8. Business Key (optional): Check the box if the Term is the Business Key of the Model Object (or a part of the Business Key in case of composed Business Key).
9. Identity (optional): Check the box if the Term is an Identity. 
   
   Historization Type (optional): This is displayed depending on the Generator Configuration. It can be one of the following values
   
   
   1. -: The Term is not historization relevant.
   2. SCD0: We load the term once and never change it, even if the source data changes.
   3. SCD1: The value of this Term can be updated.
   4. SCD2: If new arriving data has changed for any term configured as SCD2, the status of the existing current row is set to close, and the ValidTo column is set to the transaction date. A new row is added to the table with the status open, and ValidFrom set to the transaction date.
10. Hide for mapping source (optional): Check the box if you want to hide the Term in Term Mappings when the Model Object is used as the Source.
    1. Mostly set to true by Generator Configuration.
       A use case is: the Foreign Key created in a Satellite, when a Relationship to the Hub is made, is checked Hide for mapping source. This Term will stay part of the Model Object in the application but will not be part of the result view and table in the generated artifacts. It is only helpful to calculate the correct HK.
11. Hide for mapping target (optional): Check the box if you want to hide the Term in Term Mappings when the Model Object is used as the Target
12. Data Classification (optional): Data Classification level of the Term. It can be one of the following values:
    
    
    1. Public Data
    2. Internal Data
    3. Confidential Data
    4. Restricted Data

Then click on the Save button:

• The new Term appears in the Terms list:
  
• A notification confirms the correct insert:
  

Demonstration video