Debugging a Business Rule with details includes which of the following about fields changed by the rule?

Debugging a Business Rule with details includes which of the following about fields changed by the rule?

• A. Old and new values for fields changed by the rule
• B. Field data types only
• C. User roles affected
• D. Execution timestamps only

Answer: (A)

When debugging a Business Rule, the crucial information is the exact change it makes to the record’s fields. You want to see the values before the rule runs and the values after it finishes—old and new values for each field the rule updates. This before-and-after view shows precisely what the rule did, confirms that the logic updates the intended fields, and helps identify any unintended changes or new states the rule creates. It’s this pair of values that reveals whether calculations, condition checks, or field dependencies behave as expected. Details like a field’s data type or which user roles can access the field don’t reveal what was changed by the rule, and a timestamp only tells you when the rule ran, not what changed. So the key debugging detail for fields changed by the rule is the old and new values.

When debugging a Business Rule, the crucial information is the exact change it makes to the record’s fields. You want to see the values before the rule runs and the values after it finishes—old and new values for each field the rule updates. This before-and-after view shows precisely what the rule did, confirms that the logic updates the intended fields, and helps identify any unintended changes or new states the rule creates. It’s this pair of values that reveals whether calculations, condition checks, or field dependencies behave as expected. Details like a field’s data type or which user roles can access the field don’t reveal what was changed by the rule, and a timestamp only tells you when the rule ran, not what changed. So the key debugging detail for fields changed by the rule is the old and new values.