OMNISTUDIO-DEVELOPER practice question 14 of 15

A developer needs to retrieve data from an external system that stores policy dat a. The external system supports REST APIs to access and update…

Full set: 86 questions
A developer needs to retrieve data from an external system that stores policy dat a. The external system supports REST APIs to access and update thepolicies. Due to the volume of the policy data and peak hours of business, calls to the REST APIs sometimes take longer than expected to respond. The developer creates an Integration Procedure to retrieve the policy data for use in an OmniScript. Given theexternal system's known performance issues, which two configurations should be used to implement the call to the external system? Choose 2 answers
Answer options
A: Set the Timeout property on the HTTP Action in the Integration Procedure Correct answer
B: Check the Chainable checkboxon the Integration Procedure Action in the OmniScript
C: Configure a Remote action with timeout settings of 120000 Correct answer
D: Check the Chain On Step checkbox on the HTTP Action in the Integration Procedure
Correct Answer:
A. Set the Timeout property on the HTTP Action in the Integration Procedure; C. Configure a Remote action with timeout settings of 120000
Explanation

To manage potential delays from a slow external system, two timeout settings must be configured. First, the Timeout property on the HTTP Action (A) within the Integration Procedure sets a specific limit on how long the procedure will wait for the external REST API to respond before aborting the callout. Second, the Remote Action timeout setting (C) on the Integration Procedure Action element within the OmniScript must be configured. This setting controls how long the OmniScript will wait for the entire Integration Procedure to complete. If the external system is slow, the default 30-second timeout may be insufficient, so increasing it is necessary to prevent the user interface from timing out prematurely.

Why Incorrect

B. Check the Chainable checkbox on the Integration Procedure Action in the OmniScript: This option bundles multiple server-side calls to reduce round trips but does not manage the duration of a single, long-running external API call.
D. Check the Chain On Step checkbox on the HTTP Action in the Integration Procedure: This makes the callout asynchronous (fire-and-forget), meaning the Integration Procedure would continue without waiting for the data, which is incorrect as the OmniScript needs the data to be returned.

References

1. HTTP Action for Integration Procedures: The official documentation details the properties of the HTTP Action element, including "Timeout in Milliseconds". This property specifies the timeout for the HTTP request, directly addressing the need to control the wait time for the external system.

Source: Salesforce Help & Training, OmniStudio Documentation, "HTTP Action for Integration Procedures".

2. Integration Procedure Action: The documentation for the OmniScript element that calls an Integration Procedure describes the "Remote Options" section. This section includes a "Timeout" property, which defaults to 30000 ms and can be increased up to 120000 ms. This is the timeout for the OmniScript waiting for the server-side procedure to respond.

Source: Salesforce Help & Training, OmniStudio Documentation, "Integration Procedure Action".

3. Chainable Server-Side Calls: Documentation explains that the "Chainable" property is used to queue up server-side calls to be executed sequentially without returning to the client between each one. This is a performance feature, not a timeout-handling mechanism for a single slow call.

Source: Salesforce Help & Training, OmniStudio Documentation, "Make Server-Side Calls from an OmniScript".

Scroll to Top