A new OmniScript includes a Set Values element with a ContextId used for testing. What should you do before moving to production?

A new OmniScript includes a Set Values element with a ContextId used for testing. What should you do before moving to production?

• A. Delete or Deactivate the Set Values element.
• B. Update the ContextId value to specify an id from the Production org.
• C. Deactivate the contextId key/value pair
• D. Add a Show/Hide condition on the Set Values element

Answer: (A)

The main idea is to remove testing artifacts before moving to production. A Set Values element that uses a ContextId for testing can introduce test-specific data, mocks, or flows into the production environment if left in place. To ensure the production OmniScript runs with clean, real production data and behavior, you should delete or deactivate the Set Values element that contains the test ContextId. This prevents any test context from being executed in production. Keeping the element but updating the ContextId to a production id could still carry the risk of unintended side effects if the test logic runs, and it also blurs the line between testing and production configurations. Deactivating only the contextId pair or adding a Show/Hide condition doesn’t fully address the artifact itself or guarantee it won’t be executed in production. Removing the testing artifact is the clearest, safest approach.

The main idea is to remove testing artifacts before moving to production. A Set Values element that uses a ContextId for testing can introduce test-specific data, mocks, or flows into the production environment if left in place. To ensure the production OmniScript runs with clean, real production data and behavior, you should delete or deactivate the Set Values element that contains the test ContextId. This prevents any test context from being executed in production.

Keeping the element but updating the ContextId to a production id could still carry the risk of unintended side effects if the test logic runs, and it also blurs the line between testing and production configurations. Deactivating only the contextId pair or adding a Show/Hide condition doesn’t fully address the artifact itself or guarantee it won’t be executed in production. Removing the testing artifact is the clearest, safest approach.