Attestation tasks will only schedule to run at midnight (and other questions)?

[David77]

We are trying to move from our old Data Certification process to the newer Data Attestations and running into questions and odd behavior, using Xanadu. 

1. When scheduling an Attestation, it seems you can only set them to run at midnight.
I   set a time but it doesn't take it and runs at midnight

2. After doing an Attestation, the CI fields Attested by and Attested Date are updated, but "Attested" is still FALSE.  Just opened up a Case w NOW Support on that one. 

3. The On Demand and Once options for scheduling on the Policy don't seem to work

4. The CMDBTASKs that get created should have a default message in them to direct the Assignee to process these thru the CMDB Workspace to avoid confusion. 

5. While I like that the Attestation process updates the CIs to indicate attestation was completed, the whole Attestation configuration process seems buggy and not yet ready for use. Do others agree or is it just me?

Thanks!

[Mannapuram]

@David77  Attestation process is working fine in CMDB. To answer your concerns added comments:

1. When scheduling an Attestation, it seems you can only set them to run at midnight.
I   set a time but it doesn't take it and runs at midnight -> Did you check the tables, 

cmdb_data_management_policy - For the correctness of Policy

cmdb_data_management_policy_execution - to check the old runs and related data

sysauto - Search here with 'your Attesation job +Policy Processor', to check when it's scheduled

2. After doing an Attestation, the CI fields Attested by and Attested Date are updated, but "Attested" is still FALSE.  Just opened up a Case w NOW Support on that one.  -> "Attested" would get updated to TRUE, after the concern CMDBTASK related to the CI gets closed/ when the Attestation task person selects 'Attest' option in the CMDB workspace. If he selects 'Rejected', then it will be FALSE

3. The On Demand and Once options for scheduling on the Policy don't seem to work -> Set them for an attestation task in the lower environments and try to check the tables mentioned in the point 1. Also, try to run them in the next 1-2 min and then check exactly, what is happening. 

4. The CMDBTASKs that get created should have a default message in them to direct the Assignee to process these thru the CMDB Workspace to avoid confusion. -> There is an automated mail (OOB) goes to Assigned to, check the emails log in lower environment, and there is a link to re-direct to CMDB workspace.

5. While I like that the Attestation process updates the CIs to indicate attestation was completed, the whole Attestation configuration process seems buggy and not yet ready for use. Do others agree or is it just me? -> Run the attestation in lower environment and explore. That might change your opinion. 

[David77]

We have not found your response to item 2 as correct, we were informed that the Attested field is to be manually manipulated. There is no workflow in the Attestation process that sets it to True or False. 

[Tony Branton]

Regarding the problems:

1. With the exception of On-Demand schedules, policies will run at the time specified for the Start Time.  If this isn't working please raise a support case.
2. Attestation Status is the field used to mark a CI record as Attested or Failed. Attestation boolean field is not used for status.  It was intended for tracking progress while working through a task.
3. The OnDemand schedule currently requires you to locate the scheduled job associated with the Attestation policy in the list of Schedule Job Definitions and execute it manually.  We will introduce the ability to execute a published Attestation/Certification policy from within Data Manager in a forthcoming release of CMDB Workspace.  "Once" schedules are provided to suit policies that only need to run a single time.
4. Links in the Data Manager task email notifications will be changed to open an assigned task in CMDB Workspace instead of the core UI, in a forthcoming release of CMDB Workspace.
5. The Attestation process is straightforward, focusing on verifying if a CI should be retained in the CMDB.  Improvements were made to the Policy creation flow earlier this year that addressed usability and performance.  If you have feedback on specific areas of the Policy UX please submit feedback via the Idea portal.

[David77]

Tony, thanks. I did open a case for the 2nd item, and the technician did not seem to know that "Attestation Status" was intended to be manually manipulated by the customer.  

Item 4 - that will be a great improvement!

Item 5 - I and my customers would respectfully disagree that the process is straightforward as compared to the old Data Certs. Viewing the CI data in the CMDB workspace is difficult as the details of the CI appear in a small scrollable window that's almost impossible to work with on just a laptop.