Example Implementation BAdI ORDER_SAVE (REST API for Solution Manager)

To send a REST request to Conigma Connect when a ChaRM object changes, e.g. a request for change or a change document, a custom BAdI implementation is required. The easiest way is to implement the BAdI ORDER_SAVE, which is always called when a ChaRM object is saved.

Alternatively, a REST request can be sent to Conigma within an action (BAdI SOCM_PROCESS_ACTION) or a consistency check (BAdI SOCM_CHECK_CONDITION).

The following example shows a sample implementation of the BAdI ORDER_SAVE to trigger a webhook that sends the data of the currently processed ChaRM object to Conigma Connect.

In this sample implementation, objects processed with errors are placed in a queue that can be processed again using the /GAL/SM_REST_PROCESS_QUEUE program. This program can either be run manually on demand or scheduled periodically.