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
  • Using Document Cache
  • Process Properties
  • The deal with Dynamic Document Properties
  1. Implementation Patterns

The Cache Challenge

Cache document properties

Last updated 4 months ago

By design, documents and their Dynamic Document Properties are discarded at the end of a branch.

Using Document Cache

If you need the documents in another branch you can store the documents in a document cache. However, sometime it is difficult to name and index for the documents or you will also need the original documents, and combining cached documents with the orginal documents is always a bit painful.

Process Properties

Another common pattern to save the results of a branch is to use a Dynamic Process Property in combination with a Flow-Control shape:

This pattern is often used with http-connectors and the major disadvantage is, it run document by document and http request and response run sequentially for all documents.

The deal with Dynamic Document Properties

Dynamic Document Properties are attached to a document. Basically, Dynamic Document Properties are a key-value list on a document. They live and die with a document. So, if you use a document cache, the document properties are also cached. If a document is discard at the end of a branch, its document properties go away with it.

End and continue - Documents are discarded
Document by document with flow-control and Process Property