# Trigger Machine Flows via BPA using commands ## IFS Workflows/BPA Workflows in IFS cloud is their take on Low Code workflows powered by Camunda. It doesn’t come close to Novacura Flow but has the advantage that it’s integrated into IFS cloud. You can for example prompt for input directly inside of Aurena, you can also connect it to a particular projection being triggered. Much like how events used to work. #### **Read more:** {% embed url="" %} {% embed url="" %} ## How to trigger a Machine Flow via IFS workflows using REST ### Creating the IFS Workflow 1. Navigate to **Workflows** and press **New.**

2. Give the workflow a meaningful name. Press **ok.**

3. Press **Expand.**

4. Select the version you want to edit. Then press **Design.** This will open the Workflow Designer.

5. Pull the **Task** and **EndEvent** element to the design area.

6. Options appear when clicking an element. Connect the elements with **arrows**.

7. Change the task element to **IFS REST Call.**

8. Time to configure the REST call. For simplicity a GET request with no input parameters is used in this example. It is possible to pass parameters as well. The URL to the Flow can be found in Flow studio.

Fill in the highlighted fields. Basic auth header is in the format username:password and is Base64 encoded.

{% hint style="warning" %} In the example above the URL and Auth is **hardcoded**. This is **not recommended**. If you find a good solution to store and fetch them as global variables within IFS Cloud please contact **Project Office,** so we can update the guide. {% endhint %} 9. Save the workflow and publish.

Click the **refresh symbol** to load the latest save. Select the version you want to deploy and click **Deploy.** Now the workflow is ready to be connected to a command.

{% hint style="info" %} This guide is focused on how to setup a REST call to trigger a Machine Flow. Please refer to IFS docs for more info on IFS Workflows. {% endhint %} {% embed url="" %} {% embed url="" %} ### Adding custom command {% hint style="warning" %} Make sure that your Flow server is accessible from the IFS cloud instance. {% endhint %} 1. Navigate to the page where you want your button and open the **page designer** to add your command.

{% hint style="info" %} The **page designer** won't be covered here but it's recommended you are familiar with it and how to handle **contexts** before proceeding. Here's the section on Page Designer in IFS Docs : {% endhint %} 2. Click the "+"-sign next to Commandgroups. {% hint style="warning" %} Make sure you put the command in the correct **context.** {% endhint %}

3. Choose **ExecuteWorkflow**

4. Give the button a name and select the Workflow from the drop down list. And click **confirm**. Here you can also specify the parameters you want to pass to the workflow. Use the same, **${\},** annotation to point to that variable in the workflow.

5. Now your custom button should be visible if **"Preview of custom config..."** is enabled. Press the button and **VOILA!**

6. The button command can now be **saved** and **deployed**.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/trigger-flows-from-ifs-cloud/trigger-machine-flows-via-bpa-using-commands.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.