Change Business Process Version

Attention!

The information in this article applies only to ELMA 3.13.3 and higher.

Migration package list page

When you open the Change Version section, you can see the list of migration packages that are being processed at the moment.

Fig. 1 Shows an example of the Change Version – Processed page.

Fig. 1. Change Version – Processed subsection

The Change Version section includes two pages:

Current operations – this page shows migration packages, that are currently being changed (fig. 2).
Processed – this page shows already processed migration packages (fig. 1).

Fig 2. Change Version – Current operations subsection

The Change Version page contains a table with the following columns:

Name – the name of the migration package, which is specified when creating it. By default, the name includes the version change date. Click on a migration package name to open its content;
Author – the user who initiated the process instance version change;
Date created – the date and time of starting the procedure of changing the process instance version;
Status – the current migration package status

Migration package statuses

The migration package status is displayed (fig. 2) in the Status column and in the Status drop-down list on the search form.

There are four migration package statuses in ELMA:

New – this status is assigned when starting instance version change;
Executing – this status is assigned during the change version operation;
Completed – this status is assigned in case of a successful version change;
Completed with errors – this status is assigned if errors occur when changing the version.

Migration package search form

You can search migration packages on both pages of the Change Version section.

To start searching, specify the search parameters and click Find (fig 3, 1).

The following search parameters are available:

Status – migration package status
Active:
Yes – active instance change procedure;
No – completed instance change procedure.

Fig. 3. Migration package search

Under the search form, you will see the search results (fig. 3, 2).

Migration package contents

The migration package contents page opens automatically when bulk changing process instance versions, and when selecting a migration package on the migration package list page.

The Migration package contents page displays the information about the process instances, whose version was changed when creating a migration package (fig. 4).

Fig. 4. Migration package content

This page contains a table with the following columns:

Process Instance – the name of the process instance, whose version was changed when creating the migration package. When you click on it, the process instance page opens;
Process – the name of the process, whose instance was added to the migration package;
Version – the number of the version, to which the process instance was switched;
Status – the migration package content status;
Comment – a comment on the version change; it is added in case of an error;
Link – a link for manually changing the version of a separate process instance. This column is filled in if it is impossible to automatically change version, for example, when there are incompatible changes in versions of the instance.

Migration package content statuses

Migration package content statuses are displayed in the table on the migration package content page (fig. 4).

There are the following migration package content statuses in ELMA:

New – this status is assigned when starting the instance version change;
In progress – this status is assigned during the change version operation;
Switched to the new version – this status is assigned after the version is changed successfully.

If errors occur, the migration package content may have the following statuses:

Critical errors – different system versions are critically incompatible. For example, after updating, new capabilities were added, which were not available in the previous system versions;
Busy – the selected instance is already being switched to a new version;
Manual processing is required – manual processing is required to successfully change the instance version. If this status is assigned, a link for manual processing appears;
Another error – an error occurred that cannot be processed;
Does not match – the selected instance does not meet the prerequisites for changing the version;

Update is not required – the selected instance is already updated to the latest version.