Salesforce Decode
Salesforcedecode
Back to questions
OmniStudioAdvancedintegration-procedureratingcallouts

Architect Integration Procedure orchestration for external rating engines

Real World Scenario

Premium calculation requires calling external rating API, applying Salesforce underwriting rules, and returning quote to OmniScript within 5 seconds.

Expected Answer

• Integration Procedure chains: DR Extract context → HTTP Action rating API → DR Transform response → Decision Matrix rules • Set IP timeouts and fallback premium or agent referral on API failure • Cache rating factors in platform cache or custom object for static tables • Correlation ID passed to rating API for support tracing • Never store raw API secrets in IP—use Named Credentials • Unit test IP with mock HTTP actions in OmniStudio designer • Log IP execution times identifying slow steps for optimization

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Integration Procedure chains: DR Extract context → HTTP Action rating API → DR Transform response → Decision Matrix rules. Set IP timeouts and fallback premium or agent referral on API failure. Pick based on your integration pattern and team capability. Integration Procedures are server-side orchestration—architect timeout and fallback before UX deadline breach. Optimize for scale and operational observability.

Architect Perspective

Integration Procedures are server-side orchestration—architect timeout and fallback before UX deadline breach.