Skip to end of metadata
Go to start of metadata

Introduction

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.

Definitions

It is important to understand the terminology when discussing dependencies. Two distinct phrases are used: "dependent on" and "dependency of." In these examples, Component A is said to be dependent on Component B. Component B is said to be a dependency of Component A:

  • Dependent on: If a component is dependent on another component, it needs that component in order to function properly. A component that is dependent on another component cannot stand alone without that component. When Component A needs Component B in order to execute successfully, Component A is said to be dependent on Component B. Another way to say this is that Component A depends on Component B.
  • Dependency of: If a component is a dependency of another component, it is needed by the first component in order for the first component to function properly. A component that is a dependency of another component is the component that is needed by another. When Component A needs Component B in order to execute successfully, Component B is said to be a dependency of Component A.

Viewing Dependencies

The option to view operation dependencies is accessible from the project pane and the design canvas:

  • Project Pane: In the Workflows or Components tab of the project pane, hover over an operation name and click the actions menu icon  to open the actions menu. From the menu, select View Dependencies.

  • Design Canvas: In the top right of an operation, hover over the actions menu icon  to open the actions menu. From the menu, select View Dependencies.

Upon selecting this option, the dependency view opens in the Workflows tab of the project pane:

In dependency view, the name of the selected operation appears along the top, below the existing search and filter capabilities.

The operation name is followed by a list of Dependencies that the operation is dependent on. This list is organized by categories such as Outcome (which lists operations that are linked by operation actions), ActivityTransformation, and Schedule. Each category can be expanded or collapsed using the disclosure triangles  .

Only dependencies of the operation that are a single level deep are displayed. For example, while the listed transformation "Magento Product Response" is a dependency of the operation, other components that are a dependency of the transformation are not displayed. Neither are components that are dependent on the operation displayed (that is, components that the operation itself is a dependency of are not listed).

To close out of dependency view, click the close icon .

Deleting an Operation

The option to permanently delete a workflow is accessible from the project pane and from design canvas:

  • Project Pane: In the Workflows or Components tab of the project pane, hover over an operation name and click the actions menu icon  to open the actions menu. From the menu, select Delete.

  • Design Canvas: In the top right of an operation, hover over the actions menu icon  to open the actions menu. From the menu, select Delete.

Upon selecting this option, you will not be able to delete the operation if there are other project components that are dependent on the operation or if the operation is being called by an external API. If neither of these is true, you will be asked to confirm you want to delete the operation. Each of these situations is described below.

Other Project Components Are Dependent on the Operation

If there are other project components that are dependent on the operation, those components will be listed:

Note that the text in this message incorrectly states that dependencies of the operation are listed. This is not true, and in fact any components that are dependent on the operation are actually what is actually listed. Click Continue to return to the project designer without any action taking place.

To make it so the operation can be deleted, you must modify the project so that the operation is not dependent on these components. For example, if Operation B is linked downstream of Operation A using operation actions, first remove the link and then try again to delete the operation.

Operation Is Being Called by an External API

If the operation is being called by an external API, a message similar to that below will be displayed:

This message will appear if you currently have a Jitterbit Custom API configured through the API Manager that calls this operation.

To make it so the operation can be deleted, use the API Manager to first delete the API or to change the API's configuration so it does not use this operation, and then try again to delete the operation.

Confirming Deletion

If there are no other components that have this operation as a dependency of any component, and the operation is not being called by an external API, a message will ask you to confirm you want to delete the operation:

Click Continue to permanently delete the operation. Note that any project components used within those operations will not be deleted and can still be accessed or referenced in other operations.

To permanently delete a component within an operation, delete it individually from the project pane (see Project Components).

On This Page

Last updated:  Dec 11, 2019

  • No labels