Solution

PK Fields

The field that makes a solution unique in Anjana is:

• name

NOTES:

• The “name” attribute must not contain the character ‘:’ to avoid interfering with the internal logic of the application.

Attributes

When a user accesses the detail of a solution, the screen displayed is the Attributes screen, where the user can access the different functional, technical, operational, etc. attributes that have been 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 the 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, and from it the instance ‘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 where the detail 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 destination

Relationships can also be filtered by the name and subtype of the related entity, the type of relationship (source or destination), 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, etc.

The objects shown in this graph depend on the chosen lineage layer and their relationship with the solution (whether it is source, destination, and what type of relationship). It is possible to filter which entity types, relationships, and statuses are to be displayed.

More detail about the graph is included in the Lineage section of this Guide.

Stakeholders

Within the Stakeholders screen, the user can view all stakeholders of the solution.

Users appear typed as:

• Primary: creator or owner user of the solution

• Secondary: user assigned to an attribute in the template (if the object has any attribute of type Nominal User)

Stakeholders can also be filtered by stakeholder type, their role, or name.

Audit

Within the Audit screen, the user can access the internal audit of Anjana where the evolution of the Solution throughout its entire lifecycle in the tool can be viewed: its creation, the validations of its workflows, the modifications it has undergone, the inclusion of instances…

It is possible to filter by whether it is a search action or not, what, who, and when an action was performed on that process.

The source allows distinguishing between the different sources that generate audit records: “anjana” in the case of internal audit and the system name in the case of external audit.

Versions

Within the Versions screen, the user can view the list of versions of the solution, from where the detail of each one can be accessed.

In this window, the user can:

• Navigate to each of the versions of the solution

• Download the snapshot of each version of the solution

• In the event of a version pending approval, navigate to its validation workflow