- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
Hey all,
Is there a way to configure the attestation tasks to allow the auto-attestation/smart detection to be re-run, even if it already completed successfully for a CMDBTASK? (I am already familiar with cancelling the attestation and running it later.)
We have a number of areas where devices may be on and offline intermittently. Allowing the re-run of the auto attestation multiple times for a single task, will greatly reduce the need of manual validation.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
That is part of it, however if the the auto attestation has already been run and accepted, there is more to it. What I should have specified is that I need the smart detection to run again as well.
I found the answer:
There is a "related" table: sn_cmdb_ws_attestation_task_state . Find the corresponding entry for the CMDBTASK and remove the Smart Detection Run On date and uncheck the Smart Detection Accepted. Then perform the reassignment. With this I can add a button or some action on the workspace variant to "reset" the smart detection and provide the ability to run auto-attest against the newly detected CIs.
Thanks,
Josh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
@Josh P1 You can reassign the task to another user and they will again get chance to auto attest in the CMDB workspace portal on the task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
That is part of it, however if the the auto attestation has already been run and accepted, there is more to it. What I should have specified is that I need the smart detection to run again as well.
I found the answer:
There is a "related" table: sn_cmdb_ws_attestation_task_state . Find the corresponding entry for the CMDBTASK and remove the Smart Detection Run On date and uncheck the Smart Detection Accepted. Then perform the reassignment. With this I can add a button or some action on the workspace variant to "reset" the smart detection and provide the ability to run auto-attest against the newly detected CIs.
Thanks,
Josh