CMDB Simulator Task 09: Configure Reconciliation Rule

MGHandy
Tera Contributor

I have been working through the self-paced CMDB Fundamentals course on NowLearning, I am stuck on the Configure the CMDB Simulator (Rome) > Task 09: Configure Reconciliation Rule.

It appears i may not be understanding something simple or there just isn't enough information given (which might be rather unlikely).

The requirement states:

Being part of the Cloud Dimensions CMDB implementation team, using CI Class Manager, you are tasked to update the Windows Server class with a reconciliation rule that achieves the following:

- Windows Server record in CMDB with discovery source LANDesk CAN be updated by discovery source ServiceNow

- Windows Server record in CMDB with discovery source ServiceNow CANNOT be updated by discovery source LANDesk

 

I have made rules where servicenow has priority over landesk to update all attributes where discovery source is servicenow OR landesk

I have created rules where landesk has priority over servicenow to update all attributes where discover source is NOT landsek.

I have taken each bullet above literally and made a rule specifically for what each says.

I have spent a total of almost three hours on this one simple little thing coming up with rules for everything in between and including the above. nothing appears to validate correctly. I don't know what i'm missing.

 

Can someone help me out. I don't necessarily want the answer, just help understanding what requirements are asking.

 

28 REPLIES 28

Hi MGHandy, PFA screenshot for the solution.

Note : Do not provide any fliter condition and save. 

cs10_0-1722991075795.png

cs10_1-1722991117961.png

 

cs10_2-1722991167020.png

 

remove the filter condition to achieve your goal, it is not necessary

This is the answer, this is the only thing that actually made the Verification pass after I spent half an hour trying out different combinations, watching videos, reading the docs like 10 times, etc.

 

Literally just list both LanDesk and ServiceNow disco sources with proper priority, make sure all fields are selected from the toggle, and leave the filter condition (3rd step) completely blank. I still have no idea why this works for the simulator and would not do it like this IRL.

Exactly 

Eloy3_0-1710350388208.png

Select all and move them to the other column 

Eloy3_1-1710350416928.png

And leave this filter empty

Eloy3_2-1710350441694.png

And success !!! 

Eloy3_3-1710350483400.png

 

This helped me to understand and validate the task. Need to create a basic Reconciliation Rule (only first step with Data source and priority and rest with no selection). The only thing to take care is, lower number meant high priority. Thus, if ServiceNow to be prioritized before LANDesk, then lower priority number for ServiceNow.