CMDB

[MALLIKARJUNY]

Hi,

Can you please explain the Horizontal Discovery,  Service Mapping,  Top Dow Discovery,  Tag Based Discovery?

[GlideFather · Accepted solution]

Hi @MALLIKARJUNY,

it's very complex topic, do you have any particular question?

If you want to extend your knowledge, go to the following places:

• What is CMDB?
• Configuration Management Database (CMDB)
• Introduction to the Configuration Management Database (CMDB) 
• CMDBF

Let me know if this helped you

[MALLIKARJUNY]

Hi @Kamil,

1. Can you please explain the Fix Script & Background Script, with example ?

2. One more with Examples Business Rules (Before,  After, ASYNC,  Display) the Relationship Parent & CHAILD?

[GlideFather]

Hi @MALLIKARJUNY,

As per 1., both fix script or background script can be rollbacked (if selected that option) so it means if you do some changes by a script, you have a record to take that changes back, however there might be some steps that cannot be taken back - for example you update an incident by either on of these two scripts, it will trigger notification, and then you rollback the change, so the incident will have the same values as prior to the script execution but the notification was already sent...

Fix script can be saved like a standard record, background script not. Both are executed manually - you write a script and nothing happen until you manually click the execute button. That's very important.

Learn more: Updating Applications with Fix Scripts

As per 2., it's a very complex topic. BR is piece of code (can be no code but it's not so often) that is executed automatically after conditions are met (!!!). Each BR is related to a table, if you need the same behaviour for different tables, you need to have more BRs.

Example of conditions - Incident is updated and assignment group is not empty, An Assignee in Incident record is populated, Etc. Go to Business rules and check the existing ones to have an idea about them.

ALso, business rules are applied for Update or Insert in that table and BEFORE or AFTER writing to database. So before the incident is updated or after... these two types are the most frequent.

Async means that it happens "behind the scenes".. with other BR the user needs to happen the code and it takes a moment, but async kind of "decides on its own" and you don't need to wait, or it's not noticeable in your user session.

more about business rules: HERE

It's difficult to explain it simply here, but check this class, it will help you a lot: Scripting in ServiceNow Fundamentals

Let me know if this answered your question as well, 

[MALLIKARJUNY]

Hi@Kamil,

nice 

---

@GlideFather wrote:

Hi @MALLIKARJUNY,

As per 1., both fix script or background script can be rollbacked (if selected that option) so it means if you do some changes by a script, you have a record to take that changes back, however there might be some steps that cannot be taken back - for example you update an incident by either on of these two scripts, it will trigger notification, and then you rollback the change, so the incident will have the same values as prior to the script execution but the notification was already sent...

Fix script can be saved like a standard record, background script not. Both are executed manually - you write a script and nothing happen until you manually click the execute button. That's very important.

Learn more: Updating Applications with Fix Scripts

As per 2., it's a very complex topic. BR is piece of code (can be no code but it's not so often) that is executed automatically after conditions are met (!!!). Each BR is related to a table, if you need the same behaviour for different tables, you need to have more BRs.

Example of conditions - Incident is updated and assignment group is not empty, An Assignee in Incident record is populated, Etc. Go to Business rules and check the existing ones to have an idea about them.

ALso, business rules are applied for Update or Insert in that table and BEFORE or AFTER writing to database. So before the incident is updated or after... these two types are the most frequent.

Async means that it happens "behind the scenes".. with other BR the user needs to happen the code and it takes a moment, but async kind of "decides on its own" and you don't need to wait, or it's not noticeable in your user session.

more about business rules: HERE

It's difficult to explain it simply here, but check this class, it will help you a lot: Scripting in ServiceNow Fundamentals

Let me know if this answered your question as well, 

---