What additional information does debug Business Rule(details) show compared to a standard debug run?

What additional information does debug Business Rule(details) show compared to a standard debug run?

• A. Old and new values for field values changed by the business rule
• B. Execution time only
• C. User who triggered the rule only
• D. All fields and their values

Answer: (A)

When you use debug with details for a Business Rule, you get visibility into exactly what the rule changed on the record. The key addition is the old and new values for the fields that the rule modifies. This lets you see the before-and-after state for each field the rule touched, so you can verify that the rule produced the intended updates. A standard debug run shows that the rule ran and may outline what code path was taken, but it doesn’t expose the specific deltas for each changed field. It also doesn’t focus on every field on the record—only the fields affected by the rule—so you won’t get a dump of all fields and values. The extra detail about before and after values is what makes the debug with details most useful for validating the rule’s effects.

When you use debug with details for a Business Rule, you get visibility into exactly what the rule changed on the record. The key addition is the old and new values for the fields that the rule modifies. This lets you see the before-and-after state for each field the rule touched, so you can verify that the rule produced the intended updates.

A standard debug run shows that the rule ran and may outline what code path was taken, but it doesn’t expose the specific deltas for each changed field. It also doesn’t focus on every field on the record—only the fields affected by the rule—so you won’t get a dump of all fields and values. The extra detail about before and after values is what makes the debug with details most useful for validating the rule’s effects.