General tab
This tab shows not only the Change description but also a lot of technical information.
The following table describes the fields shown above.
Description | Description of the Change, can be maintained in several languages |
Object type | For Changes "SWFM: Change" |
Object state | Status of the repository object: The status "Active" is displayed here for most objects. For objects that are no longer actively used, such as obsolete users or user groups, the status "Inactive" can be displayed. In addition, the status "Ghost" exists for objects that cannot be instantiated for technical reasons (for example, SAP systems that cannot be accessed) and the status "Template" for objects that only serve as a copy template. Internally there are other values such as "Deleted", "Recovered" and "Permanently deleted", but these have no practical relevance for the end user. |
Repository | The Repository encapsulates Conigma CCM Customizing, master data and transaction data (conceptually similar to the client separation of an SAP system). Conigma CCM customers sometimes maintain a sandbox or test repository in addition to the production repository. |
Unique ID | The unique ID consists of a combination of key fields that uniquely describe the object. In most cases, the UID 1.00 format is used. Here the unique ID consists of the literal "CRO.UID.100" followed by the fields "Repository ID", "Object Type" and "Object ID". The individual fields are separated by a period. In the Object search the last 10 digits of the unique ID can be used (search field "Object ID"). |
Created | Conigma CCM user who created the object and time of creation. This is the user whose ID triggered access to the database. For objects created from external systems, this is usually the interface user. This field is therefore not suitable for deriving functional responsibilities - this should always be done using partner functions. |
Last modified | Last person to change the Change. With regard to the user ID, the same applies as for creation. |