Question 860
A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. Verify prerequisites with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.
Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The appropriate response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.
Incorrect Answers
Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs. This step may apply to Business Rule timing and before after async display behavior but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.
Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths. This step may apply to Client script versus Business Rule and API persistence but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.
The user navigates from the authorized list to the intended form or workspace and changes the correct record with an audit trail. This step may apply to Core platform lists versus forms and workspaces but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.


