Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

SFDC style


The Jitterbit Design Studio is entirely wizard-driven, taking you step by step through the creation of data mappings, connectivity and transformations. The Studio features automatic data mapping and enterprise connectors to make connectivity as easy as possible. Complex data models are supported including and dynamic schemas, as well as connecting to SOAP API, REST API and Cloud-based APIs such as the Salesforce Bulk API.

The user friendly graphical interface provides multiple tools for easy definition of complex business processes including predefined Formula Builder functions , enhanced scripting and validation tools, chained operations to be sequentially triggered by events in a prior operation , user defined local variables that run only in real-time operation of a specific process and pre-defined global variables that are defined throughout the entire project.

In the Design phase, you can test a query or other operation to make sure all components are valid. Or you can actually run the operation, which brings up an operations monitor at the bottom of your screen to report start/end times and progress, number of records processed, and success or failure.   

Every element you create in Studio is defined in metadata. The metadata is deployed to an Environment to be stored, and is then managed by the Web Management Console.

You can navigate the Design Studio User Interface by using the following components:

  1. Main Menu : Access most of the functionality provided by the system

  2. Main Toolbar : Fast access to commonly used functionality

  3. Project Tree : Organize and manipulate integration components

  4. Transformation Toolbar : Special functions used when creating transformations

Frequently Asked Questions

Q: What is the [E]   [E*]?

A: [E] and [E*] are node identifiers. Node identifiers are used only for XML-based structures, such as XML and Web Service requests and responses. See Hierarchical Entity Path Notation Explained (Node Identifiers) .

Pages in this Category

  • No labels