Business rules doubts

[NIHARADN]

Hi,

I am learning Business Rules in ServiceNow and I have a doubt.

When creating a Problem record from an Incident using a Business Rule, how many fields are typically mapped?

For example, in my script I am only mapping:

• short_description

• description

Is this sufficient, or should additional fields such as category, assignment group, impact, urgency, or configuration item also be mapped?

My script creates the Problem record successfully, but I would like to understand the best practice followed in real-world implementations.

Thank you.

[PoonkodiS]

Hi @NIHARADN 

The Scenario

An entire office building suddenly loses its internet connection, causing employees to flood the IT Service Desk with tickets.

How the Data Maps Over

Imagine your Business Rule automatically copies these specific fields from the major Incident over to a new Problem record:

• Short Description: "London Office completely offline – no internet connectivity."

  • The Use: The Problem team instantly knows the exact technical symptom they are investigating.

• Configuration Item (cmdb_ci): London-Core-Router-01

  • The Use: The network engineers don't waste time checking individual laptops; they know the exact piece of hardware that failed.

• Category / Subcategory: Network / Routing

  • The Use: The ticket is automatically categorized correctly for the end-of-month IT stability reports.

• Impact & Urgency: 1 - High / 1 - High (Priority 1)

  • The Use: The Problem Manager sees this is a P1 and instantly assigns a senior engineer to it, dropping all lower-priority work.

• First Reported By Task: INC0010432

  • The Use: The engineer can look back at this original incident to see the diagnostic logs and timestamps from when the ping dropped.