Conigma CCM

Creating a Change

Conigma CCM has three ways to create a change.

  • Automated via the API (see also SOAP API ) from external tools such as Incident Management systems

  • Automated via internal functions (e.g. via selective copies when using Conigma DevSync or Change templates)

  • Manually via the Conigma CCM interface

This chapter refers to the last of the three options mentioned above.

You can create a Change in Conigma CCM via the corresponding context menu. This option depends on your role and other customizable settings (for example, status of the underlying project or release). In the adjacent example, a change is created for Release 3.04. The release has the status "In Maintenance" and thus allows the assignment of Changes.

Mandatory fields

When you create a Change, you must maintain the following fields:

  • Description

  • Change Type

  • Priority

Like all other text fields in Conigma CCM, you can maintain the description in several languages. This maintenance can be done independently of the login language and automatically (see Changing a Change ).
Further fields are not required at first. Depending on other Customizing settings, additional mandatory fields can be defined on other tabs of the Change (for example, on the tab for roles or on the tab for customer-specific fields).

Furthermore, with the help of the Conigma CCM rule engine, fields can be preassigned automatically when they are created. Partner functions are a typical example of this. In the adjacent Change, the corresponding user groups were assigned to the partner roles Change Coordinator, Developer and Tester during creation. However, the requester role has been assigned to the Conigma user who created the Change (see the following figure).

In the status model of this example, the new Change has the status New. This is also determined by the Conigma rule engine.