Configuration Panel

Anjana Data Platform is a Data and AI Governance Platform designed to adapt to the needs of each organization. Its flexible configuration model allows any entity to operationalize its own governance framework without depending on a predefined model, simply by parameterizing the tool.

To this end, Anjana Data Platform provides the administrator user with a configuration panel that centralizes and facilitates the management of all elements that make up the solution.

Configuration Panel Navigation Elements

In the header of the Configuration Panel (see image) three main access points are presented that allow managing the different functional components of Anjana Data Platform. These access points lead to the key modules for managing the parameterization of the operational model, the design of validation workflows, and the execution of administrative actions. From here, the administrator user can navigate centrally to Schemas, BPM, and the Actions dropdown menu, which group the essential capabilities for configuring and maintaining the solution.

Schemas

The Schemas section is the central access point for all internal parameterization of Anjana Data Platform. From this module, the administrator user can consult and manage the tables that define the functional behavior of the platform, including elements such as the operational model, the metamodel, templates, lineage layers, portal filters, and other key components.

In Schemas, each configuration table can be fully managed through the standard actions:

• Create new records

• Update existing records

• Delete records

This view provides direct and transparent management of the internal structure that supports the functioning of Data and AI Governance within Anjana Data Platform.

It is important to note that the functional logic associated with each parameterization table, as well as the relationships between them, is not detailed in the User Guide. To gain an in-depth understanding of the purpose and behavior of each configuration entity, the user should consult the specific Functional Configuration section available in the official documentation. This resource describes the internal parameterization model and provides the context needed to maintain a coherent configuration aligned with the organization's needs.

BPM

The BPM option provides access to the workflow editor. From here it is possible to:

• View the currently loaded workflows

• Create new workflows

• Edit existing workflows

• Delete workflows

The editor allows modeling and maintaining Anjana's approval flows and internal operational processes.

Actions

The Actions section includes a set of administrative actions executable on the system. Each one is described below:

• Validate fields ( Actions > Validate fields ): action that checks whether the attributes that form part of the PK of objects have the required attribute and non-editable validations configured, and that the values configured for taxonomy-type attributes generate valid trees (without cycles, for example).

• Upload translations files( Actions > Upload translation files ): action that updates the application's translation files for multi-language configuration. The files are located in Minio or S3, with all the content of the translations table (Translations). Users will not have the changes available in the Data Portal until caches are cleared ( Actions > Clear cache ) and the page is reloaded.

• Insert default translations( Actions > Insert default translations ): action that inserts the missing default Anjana Data translations. Exclusive action for Spanish (es-ES) and English (en-US) languages. This action does not overwrite existing translations that may have been modified by the administrator.

• Clear Cache ( Actions > Clear cache ): action that clears the application caches, recommended before any configuration change, authentication, identity providers for authentication, translations, or iconography and CSS.

• Load lineage ( Actions > Load lineage ): action that regenerates the full lineage of entities and relationships for subsequent visualization in the Anjana Portal. This action is recommended when lineage access errors occur as a result of errors or manual interventions.

• Force indexing ( Actions > Force indexing ): action that forces a complete indexing of all entities and relationships. This action is recommended when a desynchronization or inconsistency is detected between the data contained in the database (DB) and Solr, or when the weightings in the searches of the object search engine of the Data Portal are modified.

• Reset DB sequences ( Actions > Reset DB sequences ): action that updates database sequences by adjusting to the highest existing value for each table associated with the sequences. This action is recommended when the content of the Anjana Data data model is modified.

• Clear data ( Actions > Clear data): Action that deletes the data stored in Anjana Data's persistences, including objects and their associated attributes. ⚠️ Recommended use: clean up test data generated during functional configuration, before starting the actual governance of use cases. Should be accompanied by a Force indexing.

• Clear data & config( Actions > Clear data & config ): Action that deletes all information and configuration of the platform in the database persistences of Anjana Data. Equivalent to running Clear data, but also deletes the configuration (templates, organizational units, domains, etc.). ⚠️ Recommended use: only to restore an environment to factory state

• Synchronize users ( Actions > Synchronize users ): Action that synchronizes in Anjana Data Platform's internal database the users available in the external providers configured for authentication (AD/LDAP, Azure EntraID, Google IAM, AWS IAM, etc.). When executed, the platform retrieves the users from the provider and stores in the configuration panel's user table ( Users) the available properties (e.g., email, first name, last name, identifiers).