Cloud Studio Best Practices and How-tos¶

Overview¶

This section provides guidance and recommendations for common integration scenarios when using Cloud Studio.

Additional best practices for using Jitterbit Harmony are available at Jitterbit Harmony Best Practices and Jitterbit Tech Talks.

Pages¶

These pages are included in this topic:

• Filter Records Using Conditions
  A common use case for determining if a record (or part of a record) should be processed or skipped.

• Handle Arrays Using Get and Set
  An overview of how to handle arrays and when to use global variables.

• Manage Asynchronous Operations
  An introduction to project organization including topics such as workflows, custom groups, asynchronous operations, and endpoint credentials.

• Manage Endpoint Credentials
  Guidance on managing endpoint credentials within projects.

• Manage Workflows Using Controller Scripts
  An example for managing how and when an operation should run.

• Persist Data Using Project Variables, Cloud Caching, or Temporary Storage
  How and when to use the various methods for storing data in the Harmony cloud.

• Populate and Use a Dictionary
  A how-to on populating and reading a dictionary.

• Read a Zipped Base64-encoded File
  A how-to on using Jitterbit functions to encode and decode files.

• Reuse Endpoints and Scripts
  Ways to incorporate reusability into the design of a Cloud Studio project, including by using a starter project, reusing endpoints, and reusing scripts.

• Send Changed Salesforce Object Records to a Database via Salesforce Workflow Rule and API Manager
  How to send changed Salesforce object records to a database via a Salesforce Workflow Rule and an API Manager API.

• Send Changed Salesforce Object Records to a Database via Salesforce Flow and API Manager
  How to send changed Salesforce object records to a database via a Salesforce Flow and an API Manager API.

• Split a File into Individual Records Using SCOPE_CHUNK
  A design pattern for splitting the data in a multi-record file into multiple files, each containing a single record, using the SCOPE_CHUNK prefix syntax of the Set function. This pattern is recommended when the source data is flat (non-hierarchical).

• Split a File into Individual Records Using SourceInstanceCount
  A design pattern for splitting the data in a multi-record JSON file into multiple files, each containing a single record, using the SourceInstanceCount function. This pattern is recommended when the source data is complex (hierarchical).

• Use a Naming Convention for Variables
  Guidance on user-provided names of local and global variables.

• Use Scripts to Chain or Control Operations
  A summary of the variety of uses of scripts in projects.