The MSPro Boomi Collection
About
Good Practices & Patterns
Good Practices & Patterns
  • Markus' Boomi Integration
  • Implementation Patterns
    • The Cache Challenge
      • The Get-Or-Create Use-Case
      • PropCache Scripts
    • State Management
      • Example Scenario
      • State-Management in general
      • State-Management Functionality
      • Technical Solutions
        • Boomi File-System Implementation
          • saveState
          • readState & fetchStates
    • Exception Handling
      • Exception vs Error
      • Basic Rules
        • Aggregating Exceptions
      • Exception Handling Pattern
        • User-Defined Exception Messages
        • Catch Exceptions
      • The pattern in practice
        • API Error Handling
          • Single Record Strategy
            • Single Record RES
          • Many Records Strategy (Array)
            • Many Records RES
        • Pre-Condition Check
    • SQL Patterns
      • Script Header
      • General Rules
        • Check using RowCount
        • Check if record exists
        • Pagination and Sorting
        • Parameter - Best Practices
        • Use JSON as a complex parameter
    • Process Patterns
      • Process Route Implementation Pattern
      • Sub-Process or Process Route
    • DateTime
      • The Boomi datetime dilemma
      • Database and Flow
      • Groovy
      • Data Hub
      • Get Current Date
    • Groovy Script Patterns
      • Dynamic Document Properties
      • Dynamic Process Properties
      • Documents
    • Array Elements to Documents
  • MSPro Services
    • Intermediate Storage
      • Example Processes
        • Docs 01 - Update and Create
          • sub.SampleData.Invoice
        • 02 - Upsert and Get
    • Render Templates
  • Tips
Powered by GitBook
On this page
  • Sub-Process
  • Process Route
  1. Implementation Patterns
  2. Process Patterns

Sub-Process or Process Route

Last updated 1 year ago

If you want to break down you Boomi Integration application into pieces, you have two options:

  1. Sub-Processes

  2. Process Routes

Sub-Process

  • A sub-process is deployed with its parent process.

  • A sub-process does not exist stand-alone.

    • Parent and children (sub-processes) belong inseparably together.

  • A sub-process is always “baked into” another process.

  • Do use a sub-process if it is used by only one parent process.

See also: Sub Process & Routes Naming Conventions, Façade Concept

Process Route

A route with one target (one route) is a Call: we are calling another process.

  • Do use a route (call to a sub-process) over a “direct” sub-process, if the called target process is used by more than one parent processes.

  • If a process route has only one path (one target) we name it “process call”.

The advantage of a process route is that the implementing process is deployed separately. If the sub-processes changes there is no need to deploy the parent processes.

See also Process Route Implementation Pattern