The Set Values element with a hardcoded ContextId is a standard practice for testing an OmniScript in isolation, simulating its launch from a specific record page. However, when moved to production, the OmniScript is expected to receive the ContextId dynamically from the record page it is launched from. Leaving the testing-specific Set Values element active would override the dynamic ContextId, forcing the OmniScript to always run against the hardcoded test record's ID. Therefore, the developer must either delete this element or deactivate it to ensure the OmniScript functions correctly in the production environment.

1. Salesforce Industries OmniScript Developer Guide: The guide emphasizes that for an OmniScript to be context-aware (e.g.

when placed on a Lightning Record Page)

it relies on the ContextId being passed in the URL. A Set Values element that defines ContextId will override this dynamic value. The guide's best practices for deployment state that test-specific configurations must be removed. (Refer to sections on "Passing Data to an OmniScript" and "Preparing OmniScripts for Deployment").

2. Salesforce Help & Training - Pass the ContextId to an OmniScript: "To pass a Salesforce object's record Id to an OmniScript

the ContextId is passed as a URL parameter... When you hard-code a ContextId in a Set Values element for testing

you must remove it before you deploy the OmniScript to production." (This concept is detailed in the "Test an OmniScript" section of the documentation).

3. Salesforce Help & Training - OmniScript Set Values Element: This documentation describes the function of the Set Values element for setting static or dynamic values. It implicitly supports the understanding that a static

hardcoded value used for testing is not suitable for a dynamic production environment where the context changes.