CMDB Simulator Task 09: Configure Reconciliation Rule

[MGHandy]

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.

 

[Priyanka Rai]

Filter condition is not required in this task

[glenn_pinto]

This simulator is part of the CMDB Fundamentals path and there is a lesson on Reconciliation Rules, in addition there is a CMDB Paris Delta section that includes updates to the Reconciliation Rule functionality in the Paris release. There are videos and lots of instructions and demos on how to put these rules together. But basically you only need 1 rule giving ServiceNow the highest priority. ServiceNow 100, LANDesk 200 as shown by Maik. This will suffice the two requirements in the bullet. ServiceNow can update LANDesk records but LANDesk cannot update ServiceNow records. Hope this helps. Thanks.

[MGHandy]

It wasn't that i didn't understand how the rules work, it was me overthinking what i actually needed in each rule.

[Michael Hoff]

Thank you! I thought there were additional filters needed and was banging my head against this for a few minutes. As soon as I removed the extra filters everything worked as expected.

[MGHandy]

@Maik Skoddow Thank you for the attempt at helping I do appreciate it, what you gave was mostly correct I found out what was wrong.

I had someone from work help me out and it turned out to be as simple as I thought it was. He told me to take out the filters and it worked.

He explained that the order alone should take care of it without the need for filters. It was the one thing I thought of but didn't actually try because I was overthinking it and thought it would require filters.

I left it as ServiceNow > Priority 100 and LANDesk > Priority 200 with no filters.