Pass the Salesforce Developer OmniStudio-Developer Questions and answers with Dumpstech

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

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

Integration Procedure is the correct tool because the requirement goes beyond a simple Salesforce record extraction. Complex filtering, sorting, aggregation, orchestration, and preparation should be handled server-side before the OmniScript displays the result. A Data Mapper Extract is appropriate for retrieving Salesforce data, but it is not the best orchestration layer when multiple operations and preparation logic are required. An HTTP Action only calls an external endpoint; it does not by itself manage the full data-preparation workflow. A Set Values Action is useful for assigning values in the OmniScript data JSON, not for complex server-side data shaping. Salesforce describes Integration Procedures as server-side processes used to automate data operations between Salesforce and external systems, which matches this requirement.

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