Salesforce Updated OmniStudio-Developer Exam Questions and Answers by finnley

The LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript

For an active OmniScript, the correct practice is to create a new version, make the change in that new version, test it, and activate it only when it is ready. Editing the active version directly is risky because users can be affected immediately, and in-flight users may experience inconsistent behavior. Cloning creates a separate component and is useful when the new script must be independent, but it is not the best approach for a minor controlled change to the same OmniScript. Waiting for a Salesforce release is irrelevant because this is a configuration lifecycle issue, not a platform-release dependency. Salesforce’s OmniStudio versioning guidance supports using versions so changes can be validated before replacing the active version used by end users.

================

The required SOQL behavior has two separate parts: ORDER BY and LIMIT. Ordering controls the sort sequence, such as sorting Tasks by CreatedDate descending so the newest Tasks appear first. Limit restricts how many records are returned, so setting the limit to five produces only the five most recent records. Filter is used to define matching criteria, such as records related to a specific Contact, but it does not create a LIMIT clause. Output Path controls where returned data appears in the JSON structure, not the query ordering or row count. Therefore, the necessary properties are Limit and Ordering. Salesforce’s Data Mapper configuration guidance confirms that Extracts read Salesforce data, can filter/select returned fields, and support extract configuration properties for returned records.

================