Managing Import jobs

General

Imports in Conigma are carried out by means of import containers.
The import containers are displayed in Conigma in the import monitor and can be managed there.

Display of import containers in the Conigma repository tree

By default, the Import Monitor contains the following sub folders:

Sub folder ‘By step’

In the sub folder 'By step', the individual steps from the corresponding development environment (delivery matrix) can be seen.
There are 3 different development environments here. By double-clicking on the corresponding development environment, you can see the defined steps in the right-hand window in the 'Steps' tab. The first step is not displayed here.

If you expand a step here, you will see the import containers in this step. By default, the completed import containers of the last 7 days are displayed here. Import containers in a different status are permanently displayed here. The duration of the display for successfully completed import containers can be changed by the Conigma administrator via the tab 'Object editor' by a different value (in days) in the external ID.

Sub folder ‘By state’

In the sub folder 'By state' you can see all defined statuses that an import container can pass through.
This display is global across all development environments and independent of the import progress.
The statuses are identical for all import containers.

When you open a status, you see the import containers in this status. By default, the completed import containers of the last 7 days are displayed here. Import containers in a different status are permanently displayed here. The duration of the display for successfully completed import containers can be changed by the Conigma administrator via the tab 'Object editor' by a different value (in days) in the external ID.

Sub folder Archive

In the sub folder 'Archive' you can see all import containers independent of the import progress and status according to time aspects. The start year of the display can be adjusted by the Conigma administrator via the tab 'Object editor'. The display of the start year does not change the archiving but only shows containers from this year. As soon as the administrator sets an earlier year again, the older containers become visible again.

Status model of the import containers

All import containers are created in the status 'Waiting for execution'.
In this status, you can add objects to the import container.
The context menu 'Add objects' opens the following pop-up by default

Here you can manually add transport-relevant objects to the import container.
Tip: If you have previously added the relevant objects, such as transports or change requests, to your favorites, you can easily find them in the 'Favorites' folder and add them selectively.

Notes:

• The pop-up can also be replaced/ supplemented by a pop-up defined according to customer requirements.

• If the context menu does not appear, there is probably a collective import container with a so-called collector expression.
  In this collector expression, all CRs are collected according to customer-specific requirements, e.g. those that have a certain status or belong to a certain release. Complex rules can be stored here.

You can simulate the import for the attached objects via the context menu 'Simulate'.
The simulation is started in the background. This is also indicated in the message area by a corresponding message.
Even after the simulation is finished, the container remains in the status 'Waiting for execution'.
In order to see the result of the simulation or to be able to "observe" the simulation, you can open the import container with a double click.
If there is no entry in the job table after opening the import container, there is a general problem.

You can see the cause in the 'Error log' tab.

Background: In Conigma, there are missing transport predecessors as well as missing CR predecessors, i.e. relationships can also be defined between different CRs. These relationships are checked before the import is actually started and the process is aborted if necessary.

You can carry out the import via the context menu 'Execute'.
You will then be asked whether you really want to execute the container.
If you confirm the security question, the import is started in the background.
The import container changes to the status 'Currently being executed'.
After successful execution, the import container changes to the status 'Execution completed'.
To see the result of the execution or to "observe" the execution, you can open the import container with a double click.

If missing transport predecessors are detected during the execution, the container changes to the status 'Execution stopped'.
You can open the import container with a double click and then continue this container after checking/evaluating the missing predecessors.

The missing predecessors are ignored.
Alternatively, you can also set the container back to 'Waiting for execution' as follows.

If errors occurred during execution, e.g. transports with RC 8, the container goes into the
status 'Execution error'.
Double-click to open the import container and then analyse the cause of the error.
You can then reset the container to 'Waiting for execution' or, if the problem has been solved in the meantime by other imports, set it to 'Execution error fixed'.

Before this, it should be verified on the container in the 'Delivery Status' tab that all imports have been carried out.

Please note that this import container also changes to the status 'Execution finished successfully'.

	To distinguish that this import container was previously in an error status, these import containers receive a different icon
	Normally, import containers in this status have the icon