This page describes the Solution object in Anjana Data Platform. It covers, on one hand, the attributes that make up its primary key (PK) - and which form its ARI, the identifier with which each object is uniquely represented in Anjana - and, on the other hand, the tabs that display the object's information in its detail view.
Primary key (PK) and ARI
Each object in Anjana Data Platform is uniquely identified by its ARI (Anjana Resource Identifier), which is built from the attributes that make up its primary key (PK). In the case of the solution, the attribute that makes up the PK (with its internal naming in parentheses) is:
-
name
The ARI also includes the object's organizational unit (organizationalUnit). For example, for a solution with ID 66:
ANJA:OBJECT:ENTITY:SOLUTION:66:Analítica de SPA Finance:Europe/SPA/Finance
where the structure is:
ANJA:OBJECT:ENTITY:SOLUTION:<idSolution>:<name>:<organizational unit>
NOTES:
-
The name attribute must not contain the ':' character, since it is the separator for the ARI components and would interfere with the application's internal logic.
-
To ensure that the fields making up the ARI are not editable, it is the administrator's responsibility to configure those attributes in the templates with "not editable" validations. Any manual intervention to modify these values will break the object's referential integrity.
-
The organizationalUnit value that appears in the ARI does not necessarily match the one the user sees in the template. If multi-language support has been configured, the translation key is the one that forms part of the ARI, while the user sees in the template the translated value of that key for the language selected in their profile.
Detail tabs
The detail view of a solution is organized into several tabs, each containing a type of information about the object. When accessing the detail view, the screen shown by default is Attributes.
The availability of the "Relationships", "Lineage", "Stakeholders", "Audit" and "Versions" tabs depends on the permissions assigned to the user's role. When access to a tab is disabled, it is displayed in gray and the user cannot navigate to it. If a user believes they should have access and do not, they should contact the Anjana Data Platform administrator.
Attributes
When a user accesses the detail view of a solution, the screen shown is Attributes, where the user can access the different functional, technical, operational, etc. attributes defined in the template, within the corresponding menus and sections, as well as the specific attributes that are not part of the template but have been included in that particular solution.
The solution template must contain an attribute to indicate the related instances. This attribute can be defined in any menu and section of the solution template and must be of type ENTITY_CONTAINER. The attribute name must be solutionRelatedInstance.
Own Instances
When creating a process instance, it is necessary to select the solution it will belong to, from which it 'inherits' its organizational unit. A solution can therefore include several process instances as its own. The list of these instances is displayed on this screen, from which the detail view of each one can be accessed.
Relationships
On the relationships screen, the user can view the existing relationships between the solution and other entities in the Anjana repository.
Relationships can be:
-
Direct: Relationships in which the solution is the source or target
Relationships can also be filtered by the name and subtype of the related entity, the relationship type (source or target), and the name and subtype of the relationship.
Lineage
On this screen, the user can view the lineage of the solution, and can expand the solution to see, for example, the organizational unit it belongs to, the instances associated with it,..
The objects displayed in this graph depend on the chosen lineage layer and its relationship with the solution (whether it is source, target, and what type of relationship). It is possible to filter which entity types, relationships and statuses are to be shown.
More detail about the graph is included in the Lineage section of this Guide.
Stakeholders
On the Stakeholders screen, the user can view all the interested parties of the solution.
Users appear typed as:
-
Primary: user who created or owns the solution
-
Secondary: user assigned in some template attribute (if the object has an attribute of type Named User)
Stakeholders can also be filtered by stakeholder type, role, or name.
Audit
On the Audit screen, the user can access Anjana's internal audit trail, where the evolution of the Solution can be seen throughout its entire life in the tool: creation, workflow validations, modifications made, inclusion of instances, etc.
It is possible to filter according to whether it is a search action or not, what, who, and when an action was performed on that process.
The origin makes it possible to distinguish between the different sources that generate audit records: "anjana" for internal audit, and the system name for external audit.
Versions
On the Versions screen, the user can view the list of versions of the solution, from which the detail view of each of them can be accessed.
In this window, the user can:
-
Navigate to each of the solution's versions
-
Download the snapshot of each version of the solution
-
If there is a version pending approval, navigate to its validation workflow