New attestation fields in the CMDB (cmdb_ci).

[Syed14]

Hi,

We have recently noticed following new fields in the CMDB:

Attested (attested)
Attested by (attested_by)
Attested Date (attested_date)

The 'created' and 'updated by' shows 'system' so we are not aware that what created these fields. I have tried but not able to find the documentation of these fields. 

Are these fields a part of new release?

Is there any documentation link for these fields?

Also what is the purpose of these fields? Is there any best practice to use them?

Thanks

Syed

[ANIKETGAURIKAR]

Hi Joshua Chen FX,

Can you share the youtube link from where you executed this job.

Regards,

Aniket Gaurikar

[Aniket Gaurikar]

Hi Joshua,

Can yo share me the YouTube link from where you executed this job.

Regards,

Aniket Gaurikar

[Aniket Gaurikar]

Hi Joshua,

Can yo share me the YouTube link from where you executed this job.

Regards,

Aniket Gaurikar

Spoiler

[Jugmaz]

Hi Syed, 

even thou this is old thread, it seems that even for today and latest version of Washington DC, all of the attestation is not in place.

Haven't yet created any ticket to SN as we are getting along 😉

What i would love to know is how and when "Attestation Score" (attestation_score) is updated, or even the reason why it is there!? Internet doesn't seem to know (even docs.sn is unaware). field is created on 2022 march.

Second field for information gathering is the "Attested" (attested) - created same time as previous. Not updated on any time? 

I have tried all possible and imaginable ways to and try but without avail!

So - we work without (don't want to create any own flows/processes for those as they might be utilized later on) in a way that is left:
Attestation - in our case all hardware that is not discovered for last 7 days, are added to attestation task which is for managed by group - they will decide whether it is attested or rejected

Retirement - every morning we run policy to create retirement tasks to managed by group to verify that these hardware ci's can be retired

Archive - every day we run the archive policy to identify if there are any retired CI's ready to archive (being attested before start of previous month), managed by group will decide.

then as a cherry on top we have Certification task to make sure Managed by group is kept uptodate!

BUT, will wait for answer or anything related to those few fields!