Template validations

In Anjana Data there is the possibility of defining a set of validations on the metadata attributes configured in the templates of each object. The goal of these validations is to ensure correct data entry and guarantee coherence, consistency and control in the documentation of data assets.

Template Attribute Validations table in the Configuration Panel (Administrator view)

These validations are recorded in the Template Attribute Validations table and allow rules to be applied to the attributes assigned to a specific template.

Supported validation types

Validations can cover different functional needs:

• Mandatory attributes (REQUIRED)
  Identify the attributes that must mandatorily be filled in on a template.

• Non-editable attributes (NOT_EDITABLE)
  Restrict the editing of an attribute, blocking its modification in the templates.

• Dependency between values (DEPENDS_ON)
  Link the values of a selector-type attribute (SELECT, SELECT_IMG, SELECT_IMG_TXT, MULTI_SELECT, etc.) to the value chosen in another attribute.

• Value inheritance (HERITABLE)
  Identify boolean attributes whose value is inherited from other related objects according to the metamodel (e.g.: a dataset inherits the boolean value true that indicates it has personal data if any of its dataset fields has it set to true). Inheritance can only occur between entities that have a relationship according to the Anjana Data native metamodel, i.e., the following cases:

  • DATASET attributes inherit boolean values from DATASET FIELD attributes.

  • DSA attributes inherit boolean values from attributes of the entities contained in the dsaContent attribute.

  • INSTANCE attributes inherit boolean values from attributes of the entities contained in the datasetsinputininstance and datasetsoutputininstance attributes.

• Value ranges (MIN / MAX)
  Define minimum and maximum values for numeric attributes.

• String lengths (MIN_LENGTH / MAX_LENGTH)
  Set restrictions on the number of characters in short/long text attributes.

• Decimal precision (MIN_DECIMAL_PRECISION / MAX_DECIMAL_PRECISION)
  Define the minimum or maximum number of decimals in decimal attributes.

• Array restrictions (MIN_LENGTH_ARRAY / MAX_LENGTH_ARRAY)
  Control the minimum or maximum number of values in multivalued attributes.

• Subtype filter (SUBTYPE_FILTER)
  Limits the entity subtypes that can be associated in attributes of type ENTITY_CONTAINER, ENTITY_SEARCH or ARRAY_ENTITY.

• Relationship type (RELATIONSHIP_TYPE)
  Determines the native relationship that is automatically created from an ENTITY_CONTAINER attribute.

Validation matrix by attribute types

Structure of the Template Attribute Validations table

Each registered validation is characterized by the following elements:

• templateAttribute: Unique identifier of an attribute within the object's template for which the validation is defined.

• key: validation key. It must correspond to one of the following values:

  • DEPENDS_ON: dependency on another attribute of the same template. It is configured for the target attribute, i.e., the attribute whose reference values appear pre-filtered based on the values selected in the attribute it depends on.

    • Applies to: value-selection attributes (SELECT, SELECT_IMG, SELECT_IMG_TXT, MULTI_SELECT, MULTI_SELECT_IMG, MULTI_SELECT_IMG_TXT, TREE_SELECT, TREE_MULTISELECT)

  • HERITABLE: in the case that its value is inherited from another metadata field.

    • Applies to: boolean attributes (INPUT_CHECKBOX) and boolean arrays (ARRAY_BOOLEAN).

  • MAX: maximum number.

    • Applies to: numeric attributes (INPUT_NUMBER, INPUT_DECIMAL, INPUT_RANGE, ARRAY_NUMBER, ARRAY_DECIMAL).

  • MIN: minimum number.

    • Applies to: numeric attributes (INPUT_NUMBER, INPUT_DECIMAL, INPUT_RANGE, ARRAY_NUMBER, ARRAY_DECIMAL).

  • MAX_DECIMAL_PRECISION: maximum precision for decimal values.

    • Applies to: decimal attributes (INPUT_DECIMAL, ARRAY_DECIMAL).

  • MIN_DECIMAL_PRECISION: minimum precision for decimal values.

    • Applies to: decimal attributes (INPUT_DECIMAL, ARRAY_DECIMAL).

  • MAX_LENGTH: maximum length in number of characters.

    • Applies to: text attributes (INPUT_TEXT, TEXT_AREA, ENRICHED_TEXT_AREA, INPUT_TEXT_INTERNATIONAL, TEXT_AREA_INTERNATIONAL, ENRICHED_TEXT_AREA_INTERNATIONAL, ARRAY_ALPHANUMERICAL).

  • MIN_LENGTHMIN_LENGTH: minimum length in number of characters.

    • Applies to: text attributes (INPUT_TEXT, TEXT_AREA, INPUT_TEXT_INTERNATIONAL, TEXT_AREA_INTERNATIONAL, ENRICHED_TEXT_AREA_INTERNATIONAL, ARRAY_ALPHANUMERICAL).

    • Should not be applied to: ENRICHED_TEXT_AREA, ENRICHED_TEXT_AREA_INTERNATIONAL due to html tags.

  • MAX_LENGTH_ARRAY: maximum number of array elements.

    • Applies to: multivalued attributes (ARRAY_BOOLEAN, ARRAY_DATE, ARRAY_NUMBER, ARRAY_DECIMAL, ARRAY_ALPHANUMERICAL, ARRAY_UPLOAD_FILE, ARRAY_UPLOAD_URL, MULTI_SELECT, MULTI_SELECT_IMG, MULTI_SELECT_IMG_TXT, MULTI_USERS, MULTI_ORGANIZATIONAL_UNIT, TREE_MULTISELECT).

  • MIN_LENGTH_ARRAY: minimum number of array elements.

    • Applies to: multivalued attributes (ARRAY_BOOLEAN, ARRAY_DATE, ARRAY_NUMBER, ARRAY_DECIMAL, ARRAY_ALPHANUMERICAL, ARRAY_UPLOAD_FILE, ARRAY_UPLOAD_URL, MULTI_SELECT, MULTI_SELECT_IMG, MULTI_SELECT_IMG_TXT, MULTI_USERS, MULTI_ORGANIZATIONAL_UNIT, TREE_MULTISELECT).

  • NOT_EDITABLE: not modifiable.

    • Applies to: all attribute types

  • RELATIONSHIP_TYPE: relationship subtype that is created

    • Applies to: native attributes of type ENTITY_CONTAINER

  • REQUIRED: mandatory attribute

    • Applies to: all attribute types

  • SUBTYPE_FILTER: allowed entity subtype.

    • Applies to: entity-type attributes (ENTITY_CONTAINER, ENTITY_SEARCH, ARRAY_ENTITY)

• params: parameters to fill in according to the following table

Creating a validation in the Template Attribute Validations table

Creating a new validation on a template involves registering a new record in the Template Attribute Validations table that links a template attribute with a validation rule.

To add the record and create a new validation:

1. Click the New button in the top right corner. This will open a wizard with the fields defined in the section Structure of the table Template Attribute Validations.

2. Fill in the fields according to the structure described:

   • templateAttribute: select the template attribute to which the validation is to be associated (e.g.: 10383-destination-GENERA).

   • key: select the validation key that will be applied (e.g.: SUBTYPE_FILTER).

   • params: indicate the parameters required for the selected validation.
     In this example, the destination of the relationship is limited to certain entity subtypes only, listed in the field separated by _- and without spaces:

     AI_MODEL_-AGENTE_LLM_-MODELO_ML
     

     This means that the destination attribute of the GENERA relationship will only allow entities of type AI_MODEL, AGENTE_LLM or MODELO_ML as the destination.

3. Click Save to save the validation or Cancel to discard it.

Modifying a validation on a template attribute in the Template Attribute Validations table

Modifying an existing validation on a template is managed from the Template Attribute Validations table in the Configuration Panel.

Important considerations

• It is only possible to modify the params field of an already created validation.

• The templateAttribute and key fields are not editable.

• If it is necessary to change the associated template attribute (templateAttribute) or the validation key (key), the existing validation must be deleted and a new one created with the correct values.

Procedure to modify params

1. Locate the validation to be edited in the Template Attribute Validations table.

2. Click the Edit button (green icon).

3. In the wizard, modify the value of the params field according to the selected validation rule.

   Examples:

   • For a SUBTYPE_FILTER type validation, update the list of allowed entity subtypes, separated by _- and without spaces (example: AI_MODEL_-MODELO_ML).

   • For a MAX_LENGTH type validation, adjust the maximum number of characters (example: 300000).

   • For a HERITABLE type validation, indicate whether inheritance applies with the value HIGH or LOW.

4. Click Save to save the changes or Cancel to discard them.

Configuring attribute validations on templates via direct database access (Developer view)

The attribute validations for each template are stored in the anjana.template_attribute_validation table.

Below is a sample script to configure several validations on the destination attribute of the GENERA relationship:

INSERT INTO anjana.template_attribute_validation
  (id_template_attribute, validator_key, validator_params)
VALUES
  (10383, 'NOT_EDITABLE',   'true'),
  (10383, 'REQUIRED',       'true'),
  (10383, 'SUBTYPE_FILTER', 'AI_MODEL_-AGENTE_LLM_-MODELO_ML_DL');