Question 350
A high-priority incident fires an outbound integration twice because two rules emit the same event on state change. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
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 high-priority incident fires an outbound integration twice because two rules emit the same event on state change.
Incorrect Answers
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 approach instead addresses Client script versus Business Rule and API persistence. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. The targeted 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 high-priority incident fires an outbound integration twice because two rules emit the same event on state change.
Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access. This approach instead addresses Client server scripting with GlideAjax and scoped APIs. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. The targeted 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 high-priority incident fires an outbound integration twice because two rules emit the same event on state change.
Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. This approach instead addresses Virtual Agent topic routing and conversation state. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. The targeted 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 high-priority incident fires an outbound integration twice because two rules emit the same event on state change.


