CMDB Data Manager Certification Policy

[DaisyB057891995]

I am trying to create a certification policy. I need to get few field from the CI table and few fields from the related tables (I have custom related tables, but for instance lets take CI relationship as an example) to be validated.

What's the best way to achieve this, as the certification field does not allow fields from other tables?

[Matthew_13]

Indeed, this is just how Data Certification works I believe. it’s a bit restrictive by design. The fields to certify picker only lets me choose fields that live on the table you’re certifying. You can’t dot-walk into related tables like CI Relationships so you’re not missing anything.

What I have seen done is one of these:

• Split it up
  Certify the CI fields on cmdb_ci, then create a second certification for the related table like cmdb_rel_ci or your custom relationship table. Run them on the same schedule so it still feels like one review.

• Roll things up onto the CI
  If you really want a single certification, add a couple of helper fields on the CI for example, Has required relationships or Primary related CI and populate them with a rule or scheduled job. Then ya just certify those CI fields.

There isn’t a supported way to pull relationship fields directly into a CI certification, so one of the above patterns is usually the cleanest way forward.

@DaisyB057891995  - Please mark Accepted Solution and Thumbs Up if you found Helpful!!

[PaulBecker]

It's by design that certification fields are limited to the main table—no dot-walking to related ones like relationships or custom tables. Common fixes are running separate policies for each table on the same schedule, or adding calculated helper fields to the CI table and certifying those instead. Works well for most setups.

[DaisyB057891995]

Thank you all for your response. Do you have any thoughts on what would be the best way for my requirement to be implemented?

[Dr Atul G- LNG]

No @DaisyB057891995 

You need to create two separate policies for this to work, as system dot-walking is not allowed. Also, adding custom scripts will increase technical debt.