Recursive CMDB Task
You may want to rerun transactions on CMDB items linked to a request in case the first attempt to apply these transactions failed, or if changes have been made to linked CMDB items elsewhere.
Last updated
You may want to rerun transactions on CMDB items linked to a request in case the first attempt to apply these transactions failed, or if changes have been made to linked CMDB items elsewhere.
Last updated
In both cases, you would want to run the Manage CMDB task again in order to apply the transactions.
You can do this by re-opening this task through a recursive branch (See below) in your workflow or by manually reopening the task.
To manually re-open a Manage CMDB task, access the task from the task palette and click Re-Open. Re-opening a Manage CMDB Task will re-open all the transactions that were defined as part of this task. When you re-open this task, one of the following actions will be taken:
If the transactions were applied to the linked CMDB items, and this task is invoked through a recursive branch, the transactions will be applied again.
If changes have been made to the linked CMDB items subsequent to this task running, re-opening this task will apply the transactions to the linked items again.
You can specify whether a transaction will re-run or not when adding the Transaction Details.
If you update any request fields mapped to a transaction for the Manage CMDB task, you must save the request before these changes will be picked up by the task on re-opening.
For example, if you have set up the task to update the configuration item linked to the request, but on running, the task fails because no matching item is found, and you then update the request to link a configuration item, if you do not save the request, the task will fail again. However, on saving the updated request, the task will succeed on re-opening.