1. Manufacturing
  2. Anywhere Mobility Studio
  3. Flows

Design control event procedure - Signature capture
Activity Flow

For a signature capture control, also define the control event procedure. A control event procedure has one or more actions that are done if the signature is captured and the resulting file is created. The signature capture file is stored in the file store.

Create an action to link the signature capture file to the related record in Microsoft Dynamics 365 for Operations. Add this action to the event procedure.

Designer Designer Developer Developer Start Start Is an action required, other than the  predefined actions? Is an action required, other than the  predefined actions? Inform the developer on the  action class to be developed Inform the developer on the  action class to be developed Develop action class Develop action class You can use an action on an event procedure. If the event occurs, the action is done. For an action, a class is required. To develop this class, extend the DAWActionRun class. A set of predefined action classes is available: Back (DAWActionRunReturnFrom) - Goes back to the previous form in the form stack of the user session. Note: This action can only be used for the On button clicked event procedure. Note: This action starts the On reactivate event procedure of the previous form, if defined.Form (DAWActionRunPage) - Opens a form as defined for the application in Mobility studio. Note: This action starts the On deactivate event procedure of the form that was open, if defined. Logout (DAWActionRunLogout) - Logs the user out of the current user session. This session is removed from the active sessions list. Note: This action can only be used for the On button clicked event procedure. Main menu (DAWActionRunMainMenu) - Opens the main menu for the application. Note: This action can only be used for the On button clicked event procedure. Prerequisite: Develop the extension of the DAWActionRun class in the AOT before you start the steps. Note: The steps are to have the developed action class uploaded as action to the related library. Procedure 1. Click Mobility design. 2. Click the Libraries tab. 3. In the list, find and select the desired record. 4. Click View. 5. Click the Actions tab. 6. Click Refresh. 7. Close the page. Notes If you deploy (export/import) an application as built in Mobility studio, make sure the related custom action classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project. Inform the designer that  the action is available  in the library Inform the designer that  the action is available  in the library Update application libraries Update application libraries In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.You link libraries to an application in several ways:Add manuallyYou manually add a library to an application to make it available for use in the application.Link automaticallyIf you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries. Procedure 1. Click Mobility design. 2. On the Applications tab, click Edit. 3. Click the Libraries tab. 4. Sub-task: Manually add library to application. 5. Click Add. 6. In the Library field, enter or select a value. 7. Click Save. Note: As a result, all current actions, functions, and data sets of the library are added to the application. 8. Sub-task: Link used libraries to application. 9. If you have imported an application, you must link the used libraries to the application. Click Link libraries. Note: You can also use this to clean up the list of linked application libraries. The libraries that are not used in the application, are removed from the linked libraries list. 10. Close the page. Is a condition required that uses a function  other than the  predefined functions? Is a condition required that uses a function  other than the  predefined functions? Inform the developer on the  function class to be developed Inform the developer on the  function class to be developed Develop function class Develop function class You can use a function to fill the related value of a condition.You can use function for a condition on:An event procedure action.A query range or a configurable grid query range. For a function, a class is required. To develop this class, extend the DAWFunctionRun class. Prerequisite: Develop the extension of the DAWFunctionRun class in the AOT before you start the steps.Note: The steps are to have the developed function class uploaded as function to the related library. Procedure 1. Click Mobility design. 2. Click the Libraries tab. 3. In the list, find and select the desired record. 4. Click View. 5. Click the Functions tab. 6. Click Refresh. 7. Close the page. Notes If you deploy (export/import) an application as built in Mobility studio, make sure the related custom function classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project. Inform the designer that  the function is available  in the library Inform the designer that  the function is available  in the library Update application libraries Update application libraries In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.You link libraries to an application in several ways:Add manuallyYou manually add a library to an application to make it available for use in the application.Link automaticallyIf you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries. Procedure 1. Click Mobility design. 2. On the Applications tab, click Edit. 3. Click the Libraries tab. 4. Sub-task: Manually add library to application. 5. Click Add. 6. In the Library field, enter or select a value. 7. Click Save. Note: As a result, all current actions, functions, and data sets of the library are added to the application. 8. Sub-task: Link used libraries to application. 9. If you have imported an application, you must link the used libraries to the application. Click Link libraries. Note: You can also use this to clean up the list of linked application libraries. The libraries that are not used in the application, are removed from the linked libraries list. 10. Close the page. Set up control event procedure Set up control event procedure 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. Procedure 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: 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. 8. On the Event procedure dialog, on the Actions pane, click Add to open the drop dialog. 9. In the list, find and select the desired actions. 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. 10. Click OK. 11. Sub-task: Fill in parameters. 12. On the Actions pane, in the list, select an action. 13. 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: If the parameter is of type enum, and you define a fixed value, you can only select an enum as defined for the parameter. 14. Sub-task: Define conditions. 15. Click the Conditions tab. 16. Click Add and fill in the fields. 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. 17. Click Close. End End Yes No Yes No

Activities

Name Responsible Description

Develop action class

Developer

 		You can use an action on an event procedure. If the event occurs, the action is done.
For an action, a class is required. To develop this class, extend the DAWActionRun class.
A set of predefined action classes is available:
  • Back (DAWActionRunReturnFrom) - Goes back to the previous form in the form stack of the user session.
    Note: This action can only be used for the On button clicked event procedure.
    Note: This action starts the On reactivate event procedure of the previous form, if defined.
  • Form (DAWActionRunPage) - Opens a form as defined for the application in Mobility studio.
    Note: This action starts the On deactivate event procedure of the form that was open, if defined.
  • Logout (DAWActionRunLogout) - Logs the user out of the current user session. This session is removed from the active sessions list.
    Note: This action can only be used for the On button clicked event procedure.
  • Main menu (DAWActionRunMainMenu) - Opens the main menu for the application.
    Note: This action can only be used for the On button clicked event procedure.
Prerequisite: Develop the extension of the DAWActionRun class in the AOT before you start the steps.
Note: The steps are to have the developed action class uploaded as action to the related library.

Update application libraries

Designer

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Develop function class

Developer
You can use a function to fill the related value of a condition.
You can use function for a condition on:
  • An event procedure action.
  • A query range or a configurable grid query range.
For a function, a class is required. To develop this class, extend the DAWFunctionRun class.
Prerequisite: Develop the extension of the DAWFunctionRun class in the AOT before you start the steps.
Note: The steps are to have the developed function class uploaded as function to the related library.

Update application libraries

Designer

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Set up control event procedure - Signature capture

Designer
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.

Activities

Name Responsible Description

Develop action class

Developer

 		You can use an action on an event procedure. If the event occurs, the action is done.
For an action, a class is required. To develop this class, extend the DAWActionRun class.
A set of predefined action classes is available:
  • Back (DAWActionRunReturnFrom) - Goes back to the previous form in the form stack of the user session.
    Note: This action can only be used for the On button clicked event procedure.
    Note: This action starts the On reactivate event procedure of the previous form, if defined.
  • Form (DAWActionRunPage) - Opens a form as defined for the application in Mobility studio.
    Note: This action starts the On deactivate event procedure of the form that was open, if defined.
  • Logout (DAWActionRunLogout) - Logs the user out of the current user session. This session is removed from the active sessions list.
    Note: This action can only be used for the On button clicked event procedure.
  • Main menu (DAWActionRunMainMenu) - Opens the main menu for the application.
    Note: This action can only be used for the On button clicked event procedure.
Prerequisite: Develop the extension of the DAWActionRun class in the AOT before you start the steps.
Note: The steps are to have the developed action class uploaded as action to the related library.

Update application libraries

Designer

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Develop function class

Developer
You can use a function to fill the related value of a condition.
You can use function for a condition on:
  • An event procedure action.
  • A query range or a configurable grid query range.
For a function, a class is required. To develop this class, extend the DAWFunctionRun class.
Prerequisite: Develop the extension of the DAWFunctionRun class in the AOT before you start the steps.
Note: The steps are to have the developed function class uploaded as function to the related library.

Update application libraries

Designer

 		In your application design, you can only use the libraries and library elements that are linked to the application. An application library defines which library elements can be used in the application design. Library elements are: actions, functions, and data sets.
You link libraries to an application in several ways:
  • Add manually
    You manually add a library to an application to make it available for use in the application.
  • Link automatically
    If you have imported an application, the used libraries are not linked automatically. To make the used libraries available for the application, you must link these. Only the libraries are linked of which at least one action, function, or data set is used in the application.
    Note: If you link libraries, and an already linked library is not used in the application, it is removed from the linked libraries.
If a linked library is updated, for example a new action class is created, you must refresh the libraries to have the updates available for the application. To do so refer to: Manage libraries.

Set up control event procedure - Signature capture

Designer
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.
Related to Notes

Design signature capture event procedure

 		 

Provide feedback