Conigma CCM

Periodic status update

Overview

In Conigma it is possible to assign one (or with precondition several) process(es) to each object type. Within the process a status workflow is defined with manual or automatic status transitions. Since the precondition of an automatic status transition is sometimes not immediately fulfilled in the dialog transaction, the status would be updated just by the next manual refresh or change with a time delay. Therefore it is sometimes necessary to check and execute the automatic transitions in a periodic background job. This can be done using the report /GAL/CCM_ADMTOOLS_STATUS_UPD.

Typical examples of usage:

  • Import takes place in STMS, status change for CR depending on return code 

  • Reminder email to the responsible person if the CR has been waiting for approval for n days 

  • Move the CR to an archive release if it has been in production for n days 

Since the report has been programmed to be very performance-optimized, it can be scheduled in short periods (5-10 minutes) if required. For performance reasons, however, the job should be scheduled on the central system if possible.

Selection parameters

Repository ID: the repository used to determine the data. If several repositories exist, the productive repository should normally be used here. 

Object type: the object type whose objects are updated. 

Object state: the status ID, where the objects to be updated are located. 

Use index: accelerates the object search if only equality check is defined in the selection field "Object status".

Top level CRs: for hierarchical CRs this level is taken into account. 

Bottom level CRs: for hierarchical CRs this level is taken into account. 

Mid level CRs: for hierarchical CRs this level is taken into account. 

Exclusive mode: this flag prevents parallel running status update jobs from blocking each other.

New TMS synchronization: Import- and export-histories of all systems connected to Conigma are updated and written to the Conigma cache tables.

Show all objects: Objects with unchanged status are displayed as well.

Trace output for all objects: Update logs are written into the trace viewer.