So let me rephrase: You are using CMDBOutput to push to a CMDB class and to modify the "Priority" field, but this modification is not triggering an Audit?
How is the Audit setup?
Is the Audit working from other parts... like midtier or other tools?
Yes... Thar's correct.
Auditing is working fine if I update the field manually through mid-tier or if it happens through the reconciliation process.
1 of 1 people found this helpful
In your CMDBOutput step you will see a configuration item call CMI Commit Size. By default this value is set to 100. Can you try setting this value to 1 and retest and check if the audit is now triggered?
I opened a ticket with BMC Support and they also suggested the same which fixed the issue. Following is the explanation that BMC provided about CMI:
CMDB has two ways for Creating/Modifying instances. One by one, or in bulk.
The API, for ex.
CI is for CreateInstance.
CMI is for CreateMultipleInstances.
The same is true for modifications.
The API in that case is:
SI, for SetInstance
SMI, for SetMultipleInstances.
The difference is mainly that when you do CI or SI you make the API call and pass the CI to be modified/created at the same time.
For CMI or SMI, you first open the API call, then pass a list of CIs to create/modify and then you close the API. Only when you close the API, the ARS will start processing your data and it will happen all in bulk, which normally can mean it is quicker. Most of the times this is not necessarily true.