An operation is the smallest unit within a workflow that is independently executed on an agent and recorded by Harmony (start and run time, success, failure, errors, debug log files, etc.). Operations are used to define what an integration should do and when it should be done.
An operation consists of at least one operation step, and often contains multiple operation steps. Operation steps are the discrete components that make up an operation and are visually represented by blocks on the design canvas, created by adding activities, scripts, or transformations to the operation.
Operations must follow a valid operation pattern in order to be valid. Combinations that are not allowed in a single operation may be functionally possible by chaining together multiple operations using operation actions.
These pages are included in this topic:
- Operation Creation and Configuration
After you create a workflow, you create operations by adding operation steps. This page explains the parts of an operation, then covers adding steps to operations, accessing menu options, renaming operations, expanding/collapsing operations, reordering operations, and removing, reusing, or moving operation steps.
- Operation Settings
After an operation is created, you can further configure the operation through its operation settings. The operation settings screen includes three tabs, covered separately in Operation Schedules, Operation Actions, and Operation Options.
- Operation Deployment and Execution
This page describes how to deploy operations or selected project components to the Jitterbit Harmony cloud. Once all components that an operation is dependent on are deployed, those operations can be executed. For convenience, dependent components are automatically deployed when manually executing an operation.
- Operation Logs
After you have deployed and executed operations within a project, you can view operation logs directly within Cloud Studio. Logs can also be viewed through the Activities page of the Management Console.
- Operation Dependencies, Deletion, and Removal
Viewing the dependencies of an operation lists the other project components that the operation is dependent on. If other components are dependent on the operation, those dependencies must be removed before an operation can be deleted. In addition, operations that are contained in a workflow can be removed from the workflow.
- Operation Reuse
Operations can be reused either by refencing the operation multiple times, or by creating a copy of an existing operation configuration to create a new, independent component.
- Operation Validity
Operations must be valid in order to be deployed. This page covers how to identify invalid operations and view the validation errors associated with them, as well as how to resolve validation errors. Examples of common operation arrangements are also provided.
- No labels