Integration Procedure naming, reuse and versioning practices
The documented best practices for Integration Procedures: camelCase Type, Sub Type and element names, modular and consolidated procedures, keeping caller-specific transforms out of reusable procedures, limiting Set Values to calculations, removing debug items before migration, asynchronous invocation settings, and why a new version doesn't affect callers.
Describe best practices for Integration Procedures.
~8 min read · 5 practice questions ·
What the exam expects
- Name an Integration Procedure's Type, Sub Type and elements the documented way: lower-case first letter, camelCase, no spaces or special characters.
- Apply the reuse practices: modular procedures, consolidating near-duplicates, and keeping per-caller transforms out of a reusable procedure.
- Use Set Values only for calculations, conditional values and static values, and remove debug items before migrating to production.
- Choose the asynchronous invocation setting the best practices name, and keep data calls within limits.
- Explain why a new version of a procedure doesn't require changes to its callers.
Key terms: Type and Sub Type (the procedure's unique identity, joined as Type_SubType to call it), camelCase (names like serviceGetAccountDetails), reusable Integration Procedure (one procedure called by several components), Set Values (an action that sets values in the data JSON), version (a numbered copy of a procedure; one per Type and Sub Type can be active).
Key facts
- Detail
- Lower case, for Lightning Web Component compatibility
- Detail
- camelCase, prefixVerbObjectDetail, such as serviceGetAccountDetails
- Detail
- Type_SubType, such as Auto_CreateUpdateQuote
- Detail
- Use Integration Procedures for all data calls; not too many per procedure
- Detail
- Consolidate; pass a variable or add conditional steps
- Detail
- No extra per-caller transform when the need is only relabeling
- Detail
- Calculations, conditional values, static values only
- Detail
- Remove or turn off before migrating to production
- Detail
- No impact on callers; one active per Type and Sub Type
- Why should the Type of an Integration Procedure start with a lower-case letter?
- Why remove debug statements before migrating a procedure to production?
- When should a calling Omniscript use Invoke Mode Non-Blocking?
- How many versions of one Type and Sub Type can be active at once?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams