Skip to end of metadata
Go to start of metadata

Introduction

Cloud Studio is entirely web-based, accessible through the Jitterbit Harmony Portal.

When you access Cloud Studio, you arrive at the project index, which contains a repository of all your projects, or you can switch to the Connector Builder index to see custom connectors created with Connector Builder.

After opening a project, you design it using the tools provided in the project designer, including the project pane, design canvas, and design component palette. Each component is configured separately. As you work on projects, Cloud Studio remembers the display states that a given user was last using for a given project.

Project Index

The project index, displayed using the My Projects dropdown, provides a listing of all your Cloud Studio projects, and is where you create a new project or import an existing project. Existing projects can be displayed as index cards that can be flipped over to reveal additional information about the project, or can be displayed in a list view. From either view, you can also open the project, project logs, or project variables list; export the project; or delete the project. For more information, see Project Index.

Creating a new project (New Project), importing a project (Import), or viewing/editing an existing project (View/Edit) will open the project and display the project designer interface.

Connector Builder Index

The Connector Builder index, displayed using the Connector Builder dropdown, provides a listing of custom connectors created with Connector Builder. Existing connectors can be displayed as cards or in list view, similar to projects. From either view, you can create a new connector, import a connector, or edit, delete, or export an existing connector. For more information, see Connector Builder Index.

The Connector Builder user interface is covered in a separate section of the documentation, under Connector Builder.

Project Designer

The project designer is the design interface that displays upon opening a project. This interface includes three parts: the project panedesign canvas, and design component palette:

Project Pane

The project pane is the panel on the left of the project designer that contains the project name, environment name, actions menu, and project navigator. The project navigator allows you to navigate the project from either of two views accessed by tabs along the top:

  • Workflows: This tab focuses on individual workflows, their operations, and the steps used to execute those operations.
  • Components: This tab shows all project components and identifies whether they are used in support of an operation.

For more information, see Project Pane.

Workflows

Components


Design Canvas

The design canvas is the central area of the project designer serving as the primary workspace where you visually design integrations. Within the design canvas, you can create multiple workflows, accessed in tabs along the top of the design canvas. You then design workflows within the canvas by creating an linking operations using the tools provided in the component palette, project pane, and design canvas itself. For more information, see Design Canvas.

Component Palette

The two types of component palettes each provide access to components that can be used within the project: the design component palette and the script component palette. For more information, see Component Palette.

  • Design Component Palette: The design component palette is the collapsible panel on the right of the project designer that provides access to project components that can be used on the design canvas. Within the Connectivity tab of the design palette, connectors are first configured to create connections. Activities associated with those connections can then be added to operations on the design canvas. 
  • Script Component Palette: The script component palette is the collapsible panel on the right of the script and script mode transformation configuration screens that provides access to project components that can be used within scripts. Each component within the Source Objects (present only for transformations), FunctionsVariablesPluginsOperationsNotificationsScripts, and Endpoints tabs can be added to the script by dragging them from the component palette.

Design Component Palette

Script Component Palette

Configuration Screens

Many types of project components and other areas of the user interface require configuration with user-provided input. The interface where you provide this input is referred to as the configuration screen or editor for the specific type of component or area of configuration.

For example, after adding a file share activity to an operation, you double-click it to open its activity configuration screen, where you provide information such as the files you want to interact with and optional file schemas. Some editors may be made up of multiple steps, requiring the user to step through the configuration, such the file share activity editor:

TIP: If you are experiencing issues with names and passwords auto-populating in configuration fields, try adjusting your browser settings (by clearing the cache and disabling autofill) or disabling your password manager. 

At the top of each activity configuration screen is a link to the configuration of the connection with which the activity is associated. To navigate to the connection configuration, click the name of the associated connection:

Many screens also include the name the component you are configuring. Depending on the component you are configuring, the displayed name may automatically update based on the user-provided name for the component or associated operation. For other components, such as activities, the name may be static and indicate a specific type of component, such as Read for a file share Read activity:

On screens that have multiple configuration steps, the step numbers are displayed, with the current step number enlarged with a dark background:

Once a configured step is saved, you can navigate to that step by clicking the step number. Steps that are navigable show an orange background when you hover over them and are clickable:

In order for steps to be navigable, the step must have first been saved. For example, upon initial creation of the component, you cannot navigate to step 2 without first having configured step 1 and saved it by using the Next or similar button to proceed to the next step in order. Similarly, if you make changes to the configuration of a existing configured step, you must save it using the Next or similar button before you can reach subsequent steps. The Next button and other buttons and links shown at the bottom of the screen are covered in the documentation of each component.

Within each configuration screen, required fields are indicated by a red asterisk following the field name:

The absence of the red asterisk indicates the field is optional and is not required to be filled out.

Many configuration screens have a close icon in the upper right that is used to close out of the configuration screen:

When using this method of closing a configuration screen, user input is not saved on configuration screens that use buttons to manually save input, as is the case with activity configuration screens. Other types of configuration screens, such as those for scripts and transformations, use auto-save, as indicated by the save status being listed along the top of the screen. For more information about manual save and auto-save, see Saving under Project Permissions, Collaboration, and Saving.

After closing a configured component that uses steps, when you reopen the component you are brought to the last step of configuration. The last step is often a review step, which enables you to review the existing configuration without needing to resubmit the configurations made in previous steps.

The file share Read activity used as an example above is just one example of a configuration screen. These are some additional examples of how the configuration screen for other components may be referred to:

  • If you add a script to the operation, you would then configure using the script configuration screen, which is also called the script editor.
  • After adding a transformation to the operation, you may define a schema manually, using the file schema editor.
  • You may later add a schedule to the operation, which you configure from the schedule configuration screen or schedule editor.

The transformation configuration screen is unique in that it can be accessed in several display modes: Mapping ModeScript Mode, or Preview Mode, as covered below.

Mapping Mode

Mapping mode provides an overview of the mapping and the basic tools to perform the mapping:

Script Mode

Script mode provides detailed views of fields and advanced tools for adding scripts to the mapping:

Preview Mode

Preview mode allows you to use sample data to test how the transformation will process the data:

On This Page

Last updated:  Feb 18, 2020

  • No labels