--- title: "Run the Workflow - Web Interface - Connectors and Scripts" slug: "users-guide-configure-and-run-the-workflow-1" updated: 2026-06-26T16:27:48Z published: 2026-06-26T16:27:48Z canonical: "support.fortanix.com/users-guide-configure-and-run-the-workflow-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # Run the Workflow - Web Interface - Connectors and Scripts ## 1.0 Introduction This article describes how to create, manage, and execute the **Workflows** using **Connectors** and **Scripts** in Fortanix Confidential Computing Manager (CCM) using the Workflow **RUN** that allows users to start the application job and monitor it. Using the Workflows menu item on Fortanix CCM user interface (UI), you can access visual mapping of the workflow. This mapping illustrates the interconnection of various components, including data connectors and scripts. ## 2.0 Execute the Script using Azure Service Principal ### 2.1 Prerequisites Ensure that the **Compute Clusters** are configured in Fortanix CCM. A compute cluster is a set of nodes that run containerized applications. Compute clusters are used to run Fortanix CCM workflows. *For more information on how to configure a compute cluster in Fortanix CCM and access the cluster, refer to* [*Section 3.0: Configure the Cluster using Azure Service Principal*](/v1/docs/users-guide-run-the-workflow-web-interface-aci-applications-1#30-configure-the-cluster-using-azure-service-principal)*.* ### 2.2 Create a Cluster Ensure that you have set up a cluster using Azure Service Principal as a worker node in the Fortanix CCM. *For more information, refer to* [*Azure Service Principal with Fortanix Confidential Computing Manager*](/v1/docs/azure-service-principal-with-fortanix-confidential-computing-manager-1)*.* ## 3.0 Configure the Cluster using Azure Service Principal Perform the following steps to configure the Azure Service Principal credentials in Fortanix CCM: 1. Click the **Infrastructure** → **Compute Clusters** menu item in the Fortanix CCM UI left navigation panel and click **+ ADD COMPUTE CLUSTER** to configure a new compute cluster. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3617)(2).png) **Figure 1: Add Compute Cluster** 2. On the **Cluster** page: 1. **Name**: Enter a required name of the cluster. 2. **Description**: Enter the required details about the cluster. However, this is optional. 3. **Type**: Select **ACI via Service Principal** from the drop down menu. 3. After you select **ACI via Service Principal**, rest of the parameters appear on the screen. 1. **Location**: The Azure region where the deployment occurs . If the required location is not available in the provided list, select **Other** and manually enter the specific location. 2. **ACI configuration**: - **App ID**: The Azure Active Directory application ID or client ID used for application identification. - **App Passcode**: The application secret required for authentication. - **Tenant ID**: The unique identifier of the Azure Active Directory instance, known as the Directory ID. - **Subscription**: The subscription ID where all resources are managed; it contains information related to resources. - **Resource Group**: The resource group designated for managing all containers and deployments. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3627)(3).png) **Figure 2: Other Parameters** 4. Click **ADD CLUSTER** to save the cluster configuration. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (3625) - Copy(1).png) **Figure 3: Compute Cluster Created** The compute cluster is now successfully created. ## 4.0 Creating a Workflow In this section, you will establish connections among the Inbound Connector, Scripts, and Outbound Connectors to formulate a comprehensive workflow. Within this workflow, the Inbound Connector is utilized to access the input data, which is then processed using an SQL query or Python within the Script. The resultant output is then generated and made accessible in the designated location specified by the Outbound Connector. This interconnection facilitates the seamless execution of data processing and transmission operations within Fortanix Confidential Computing Manager. Perform the following steps to create a workflow: 1. Click the **Workflows** menu item in the CCM UI left navigation panel. 2. On the Workflows page, click **+ WORKFLOW** to create a new workflow. 3. In the **CREATE NEW WORKFLOW** dialog box: 1. **Name**: Enter a required a name for the workflow. 2. **Group**: Select the required group name from the drop down menu to associate the workflow with that Group. 3. **Description** (Optional): Enter the required short description for the workflow. ![Screenshot (119).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488193094164.png) **Figure 4: Add a workflow** 4. Click **CREATE WORKFLOW** to add a new workflow. The workflow is added to the Fortanix CCM application successfully. ### 4.1 Add Scripts and Connectors to the Workflow Perform the following steps to create the workflow: 1. **Adding an Inbound Connector**: 1. Drag the Inbound Connector icon and drop it into the working area. Click the **ADD INBOUND CONNECTOR** node. 2. In the **INBOUND CONNECTOR** dialog box, you can either create a new inbound connector or select an existing inbound connector name. *For more information on how to create a new inbound connector, refer to* [*Inbound Connectors*](/v1/docs/users-guide-inbound-connector-1)*.* 3. Click **ADD INBOUND CONNECTOR** to add an inbound connector or select an existing one. 2. **Adding an Outbound Connector**: 1. Drag the Outbound Connector icon and drop it into the working area. Click the **ADD OUTBOUND CONNECTOR** node. 2. In the **OUTBOUND CONNECTOR** dialog box, you can either create a new outbound connector or select an existing outbound connector name. *For more information on how to create a new outbound connector, refer to* [*Outbound Connectors*](/v1/docs/users-guide-outbound-connector-1)*.* 3. Click **ADD OUTBOUND CONNECTOR** to add an outbound connector or select an existing one. 3. **Adding a Script**: 1. Drag the Script icon and drop it into the working area. Click the **ADD SCRIPT** node. 2. In the **SCRIPT** dialog box, you can either create a new script or select an existing outbound connector name. *For more information on how to add a new script, refer to* [*Scripts*](/v1/docs/users-guide-scripts-1)*.* 3. Click **ADD SCRIPT** to add a script or select an existing one. 4. **Establish the connections**: Connect the inbound connectors to scripts written in either SQL, Python, or SQL Aggregate. Then connect these scripts to the SQL Aggregate scripts. Next, establish connections between these aggregate scripts with one or more outbound connectors (s) to facilitate the output. It is deemed invalid to have unattached Fortanix CCM nodes, except when they are part of a draft. > [!NOTE] > NOTE > > Ensure the following: > > - The SQL nodes must have at least one connection originating from either an inbound data connector or a Python script. > - The SQL Aggregate nodes must have exactly one connection originating from either a SQL node, Python node, or an inbound data connector. > - The Python scripts must have at least one connection originating from either an inbound data connector or a SQL/Python script. > - The Python scripts must have at least one connection leading to any script (Python/SQL/SQL aggregate) or outbound connector. > - Only one Python script per workflow is supported for this release, along with one SQL script per workflow. > - The Outbound Connectors must have at least one connection originating from: > - If there is exactly one incoming connection, it may be from a SQL, Python, or SQL Aggregate node. > - If there are multiple incoming connections, they must all be SQL Aggregate nodes. > - All other types of inbound connections are not permitted. > - Avoid disconnected components: > - The Inbound Connectors, Script nodes, and Outbound Connectors must be connected to another node. > - It is not allowed to have unattached Windsor nodes, except as part of a draft. > - There should be no connections between legacy nodes and Windsor nodes. > - Connections such as App to Data Connector and Dataset to Data Connector or script are not allowed. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(88).png) **Figure 5: Created the workflow** ## 5.0 Requesting the Workflow Graph Approval After the workflow is complete, click **REQUEST APPROVAL** to initiate the approval process for the Workflow. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(89).png) **Figure 6: Request the approval** > [!WARNING] > WARNING > > Submitting a draft workflow for approval removes it from the drafts list. After it is in a Pending or Approved state, you can no longer directly edit the workflow. Perform the following steps to accept the workflow request: 1. The workflow remains in a pending state until it receives approval from all users. In the Pending menu item, click **SHOW APPROVAL REQUEST** to approve a workflow. ![Screenshot (123).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488193242004.png) **Figure 7: Show approval request** 2. In the **APPROVAL REQUEST – CREATE WORKFLOW** dialog, you can either **APPROVE** or **DECLINE** a workflow. > [!NOTE] > NOTE > > - A user can also approve/decline a workflow from the Fortanix CCM **Tasks** tab. > - The users who have approved the workflow display a green tick against their icon. 3. Approval from at least 1 admin user is necessary to finalize the workflow. If a user declines, the workflow is rejected. When all the users approve the workflow, it is deployed. 1. Fortanix CCM configures apps to access the Datasets. 2. Fortanix CCM creates the Workflow Application Configs. 3. Fortanix CCM returns the list of hashes required to start the apps. The workflow approval is now requested successfully. ## 6.0 Configuring the Workflow Graph Perform the following steps to configure the workflow: 1. Navigate to the **Workflows** → **Approved** menu item in the Fortanix CCM UI left navigation panel. 2. From the list of approved workflows, select a workflow that has a single application since Fortanix CCM supports only single job deployments. 3. In the detailed view of the selected workflow, you will notice the disabled **RUN**. This button will be disabled if you have not configured the **Azure account** and **Location**. Click the icon to configure these details and enable **RUN**. 4. In the **RUN WORKFLOW** window: - **Deployment Type**: The workflow deployment type. Select **Azure Confidential Instances (Single Job)** from the drop down menu. - **Azure account**: Select the ACI cluster (**Test Cluster**) created in [*Section 3.0: Configure the Cluster using Azure Service Principal*](/v1/docs/users-guide-configure-and-run-the-workflow-1#30-configure-the-cluster-using-azure-service-principal) from the drop down menu. - **Location**: The Azure region where the deployment occurs. ![Screenshot (126).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488193273364.png) **Figure 8: RUN configuration** 5. Click **SAVE CONFIGURATION** to save the changes. **RUN** is now enabled on the screen. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(90).png) **Figure 9: RUN enabled** ## 7.0 Running the Workflow Ensure that you have created an image registry in the Fortanix CCM UI. *For more information, refer to* [*Image Registry*](/v1/docs/users-guide-image-registry-1)*.* A registry for the image used in the ACI application workflow is required to be created in the Fortanix CCM account, so at runtime, the credentials are passed to the Azure container instance to pull the image. Perform the following steps to run the ACI workflow application: 1. Configure the image pull secret. 2. Click **RUN** in the detailed view of an approved workflow enabled in [*Section 4.0 : Configuring the Workflow Graph*](/v1/docs/users-guide-configure-and-run-the-workflow-1#40-configuring-the-workflow-graph). ![Screenshot (128).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488146891540.png) **Figure 10: Run configuration workflow** 3. In the **RUN WORKFLOW** window, confirm the values of each parameter and click **RUN** to run the workflow. Observe the running indicator at the bottom of the workflow. ![Screenshot (129).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488193300500.png) **Figure 11: Run the workflow** > [!NOTE] > NOTE > > The workflow execution status is not updated in real-time and must be fetched from the cluster manually. Therefore, click the **Refresh** icon to get the latest execution status. If there is a need to halt the execution at any point, click **STOP**. This action will re-enable **RUN**. 4. If the application is executed successfully, the execution status will be displayed under the **Execution Log**. Click the **View detail** link to view the log details. The **EXECUTION LOG** window provides a detailed log of the run. You can also download the log using **DOWNLOAD**. ![Screenshot (130).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24488146918548.png) **Figure 12: Execution logs** > [!NOTE] > NOTE > > Attempting to execute a workflow containing more than one application will result in the mentioned error. The Fortanix CCM supports the execution of workflows with a single application only. Additionally, users can access the output CSV file to verify the output data. ## ## Related - [Fortanix Confidential Computing Manager - Simple Use Case - SQL](/fortanix-ccm-simple-use-case-sql.md) - [Account and Users](/fortanix-armor-system-administration-account-and-users.md) - [Deploy the Workflow - Manual - AWS Nitro Applications](/fortanix-ccm-deploy-the-workflow-manual-aws-nitro-applications.md) - [Fortanix Confidential Computing Manager - Simple Use Case - Python](/fortanix-ccmanager-simple-use-case-python.md) - [Fortanix Confidential Computing Manager - Complex Use Case - SQL](/fortanix-ccm-complex-use-case-sql.md)