--- title: "Set up control event procedure - Signature capture" slug: "set-up-control-event-procedure-signature-capture" description: "Set up signature capture controls in D365 F&SCM, linking files to records with customizable action sequences and conditions for efficient document management." tags: ["Task", "Anywhere Mobility Studio"] updated: 2026-03-20T12:49:06Z published: 2026-03-20T17:46:51Z canonical: "docs.staedean.com/set-up-control-event-procedure-signature-capture" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up control event procedure - Signature capture For a control of type **Signature capture**, you can set up a control event procedure with actions that are done in a specific sequence. A control event procedure has one action or a series of actions that are done on the **On document captured** control event. So, the procedure is started if the signature is captured and the resulting file is created. The signature capture file is stored in the file store. To link the signature capture file to the related record in Microsoft Dynamics 365 for Operations, an action is required that takes care of this. Use the **Up** and **Down** buttons to define the action sequence. Optionally, you can run an action under specific conditions. For conditions, you can use functions or variables that are available for the application or form. ### Steps 1. Click **Mobility design**. 2. Click the **Forms** tab. 3. In the list, find and select the desired record. 4. Click **Edit**. 5. On the preview, click the **desired signature capture control**. > [!NOTE] > **Note** > > If the control list is shown instead of the preview, in the list, find and select the desired signature capture control. 6. On the **Properties** tab, next to the **On document captured procedure** field, click the **Edit 'On document captured' procedure (+)** button. 7. Sub-task: Add actions. 1. On the **Event procedure** dialog, on the **Actions pane**, click **Add** to open the drop dialog. 2. In the list, find and select the desired actions. > [!NOTE] > **Note** > > At least, add an action that links the signature capture file to the related record in Microsoft Dynamics 365 for Operations. For example, the predefined 'Capture Signature' action. 3. Click **OK**. 8. Sub-task: Fill in parameters. 1. On the **Actions pane**, in the list, select an action. 2. For each action, the relevant parameters are defined in the action class. Each action can have a different set of parameters. Usually, these are input or output parameters. For these parameters, you can define the value. Only define a value for the parameters that are applicable to the event procedure. Sometimes, an action has a different type of parameters or no parameters. In the **Value** field, you can use a variable, a function, or a fixed value. In this step, as an example, you enter a fixed value. On the **Parameters** tab, in the **Value** field, enter or select a value. > [!NOTE] > **Note** > > If the parameter is of type enum, and you define a fixed value, you can only select an enum as defined for the parameter. 9. Sub-task: Define conditions. 1. Optionally, you can run an action under specific conditions. Click the **Conditions** tab. 2. Click **Add** and fill in the fields. > [!NOTE] > **Note** > > In the first **Value** field, you can use a variable or a function. In the second **Value** field, you can use a variable, a function, or a fixed value. 10. Click **Close**.