--- title: "Basic External Form Process" slug: "basic-external-form-process" description: "This document demonstrates how to interact with Decisions externally via the External Form step. This step can pass and retrieve data from Forms externally, via HTML methods or service calls. " tags: ["JavaScript", "IIS", "External Data", "HTML"] updated: 2026-06-04T17:26:42Z published: 2026-06-04T17:26:42Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Basic External Form Process ## Overview The **External Form** step can interact with Forms by using HTML methods or service calls. This method can also pass data into and retrieve data from an External Form. WarningCross-origin resource sharing requires additional configuration. By default, requests originating from a different domain will be blocked. As a workaround, add an HTTP protocol****reference by visiting the [Forum](https://support.decisions.com/forum/topic120-cors-workaround.aspx).  --- ## Example The following example will demonstrate how to call an External Form in IIS. 1. In a code editor, enter the following code and save it as "TestForm.html" in a new Folder under **C:\inetpub\wwwroot\ExternalFormTestFolder**.Adding to the wwwroot Folder will require administrative permissions.  ```markup Decisions External Form Example

Decisions External Form Example

This web page is a simple HTML and javascript web page illustrating the use of Decisions flow engine using a completely custom build web

application to interact with the platform.

The following data were sent to this page from Decisions flow engine:

1.

2.

3.

Other Parameters:

In order to return to the Decisions flow engine you need to specify an "Outcome" to use in the callback url. The callback url should be composed

from the parameters in the list above and must include the following:

1. action=PostCustomFormDataToFlow

2. flowTrackingId = Use the value shown above

3. stepTrackingId = Use the value shown above

4. OutcomeName = value

5. Additional Data to Send (use name=value&)

Specify an outcome and click "Send to Decisions" when ready.

Outcome Name:

Additional Data:

``` 2. Open **I****IS Manage**r; expand **[Desktop Name] > Sites** on the left, then right-click **Default Web Site** and select **Add Virtual Directory**. 3. From the **Add Virtual Directory** window, name the **Alias**, then select the**Physical path** from the HTML file saved. Click OK to add the **Directory**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-26_10h17_27.png) 4. After the Directory is added, double-click **Directory****Browsing**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-26_10h20_53.png)To help avoid potential errors, if it is presently disabled, Enable Directory Browsing.  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-03-26_10h23_05.png) --- ## Create a Flow 1. In a Designer Project, click CREATE FLOW on the **Global****Action** **Bar**and select **Flow**. Enter a **Name**and click CREATE. 2. Attach an **External****Form**step from the DESIGNER ENTITIES > FORMS [INTERACTION] category of the **Toolbox**panel to the **Start**step. 3. On the **Properties**panel under the SERVICE DEFINITION category, click ADD under**Service Outcomes**. 4. From the **Add Service Outcomes** window, enter "Done" as input for the **Name**and click OK.The Outcome Name is important because the Form needs to know the Outcome path. If desired, parameters may be added in the form of Data by clicking ADD under the PARAMETERS category. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-25_12h36_04.png) 5. Under the INPUTS category, enter the Form's URL in the **URL**field. The URL should be formatted as http://[PortalBaseUrl]/[Name of virtual directory]/![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-25_12h37_38.png) 6. Connect the External Form to the **End**step. Click Save to save changes to the Flow. --- ## Debug 1. On the top action bar, click **Debug**. 2. Click START DEBUGGING. 3. Once the Flow opens the External Form, note that the Form received the flowTracking id, stepTracking id, and CallBackUrl. Provide the designated input for the Outcome Name, then click **Send to Decisions**.**** 4. After the Form submits, navigate back to the Debugger, then select **External Form 1 > Execution 1 > View Input/Output Data.**The resulting output displays the information received by the Form. --- ## How Saved Data Is Handled in External Forms When an End-User fills out an external Form, the submitted data is returned to Decisions and can be viewed in the workflow. To view Form submission details: - After the Form is submitted, navigate to the Debugger and select the External Form step execution. - Submitted details will be displayed in the Input/Output Data window. --- For further information on Forms, visit the [Decisions Forum](https://community.decisions.com/categories/Forms).