1. Manufacturing
  2. Anywhere Mobility Studio
  3. Flows

Design forms
Activity Flow

For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.
For each form, define the applicable:

  • Variables - A variable is used to store data in mobile device sessions. You can also create application-specific variables.
  • Controls - A control defines an element on a form. For example, a button or a field.
  • Form event procedures - A form event procedure has one action or a series of actions that are done on one of the form events.

Designer Designer Developer Developer Start Start Is a handler  required for  the form? Is a handler  required for  the form? Create handler Create handler You can apply a handler to an application or a form, depending on the handler type. For a handler, a class is required. However, in your design, you can already use the handler definition without the class defined. Inform the developer on the requirements for the handler class to be developed. Procedure 1. Click Mobility design. 2. Click Handlers. 3. Click New. 4. In the Handler field, type a value. 5. In the Description field, type a value. 6. Close the page. 7. Close the page. Notes You can use a handler on any application. Inform developer on  handler class to be developed Inform developer on  handler class to be developed Develop handler class Develop handler class You can use a handler on an application or a form, depending on the handler type. For a handler, a class is required. To develop this class, extend one of these classes: DAWApplicationHandler - Extend this class to develop an application handler. DAWFormHandler - Extend this class to develop a form handler. Prerequisite: Develop the extension of the DAWApplicationHandler class or DAWFormHandler class in the AOT before you start the steps. Procedure 1. Click Mobility design. 2. Click Handlers. 3. In the list, find and select the desired record. 4. Click Edit. 5. In the Class name field, enter the name of the applicable class extension for the DAWApplicationHandler class or DAWFormHandler class. 6. In the Handler type field, select an option. 7. Close the page. Notes If you deploy (export/import) an application as built in Mobility studio, make sure the related handler classes are deployed as well. You can do so with a Microsoft Dynamics Lifecycle Services project. End End How to create a form? How to create a form? Create form with wizard Create form with wizard For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.You can create a form manually or with a wizard. This topic explains how to create a form with the wizard.Usually, if you use form control templates, you create a form with the wizard. Procedure 1. Click Mobility design. 2. Click Create form. 3. Sub-task: Define main settings for the form. 4. In the Process field, enter or select a value. 5. In the Form field, type a value. 6. In the Description field, type a value. 7. In the Label field, enter or select a value. 8. Sub-task: Add form control templates to the form. 9. Click Next. 10. Click Label. 11. In the list, find and select the desired record. Note: - If you select a control template, in the Template pane (middle pane), a preview of the control is shown. - You can select and add several control templates of a type in one go. 12. Click Add. 13. Sub-task: Change form control settings. 14. On the preview, click the control. 15. Click Details. 16. Close the page. 17. Click Refresh. 18. Sub-task: Review and finish form creation. 19. Click Next. 20. Click Finish. 21. Sub-task: If required, change form design. 22. Close the page. Notes Several toggle buttons are available on the Forms page to change what is shown on the page:Invisible controls:Show invisible controls: Form controls with the Visible property set to No are shown on the preview.Hide invisible controls: Form controls with the Visible property set to No are not shown on the preview.Preview:Show control list: The controls of the forms are shown in a grid.Show preview: The controls of the form are shown on a preview.Properties:Simple view: Technical properties are hidden.Advanced view: All properties are shown.The views you have chosen are stored in your usage data. Create form manually Create form manually For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.You can create a form manually or with a wizard. This topic explains how to create a form manually. Procedure 1. Click Mobility design. 2. Click the Forms tab. 3. Click Add. 4. In the Form field, type a value. 5. In the Description field, type a value. 6. In the Label field, enter or select a value. 7. In the Documentation section, write the form documentation. For example, describe the purpose and characteristics of the form. 8. Close the page. Notes Several toggle buttons are available on the Forms page to change what is shown on the page:Invisible controls:Show invisible controls: Form controls with the Visible property set to No are shown on the preview.Hide invisible controls: Form controls with the Visible property set to No are not shown on the preview.Preview:Show control list: The controls of the forms are shown in a grid.Show preview: The controls of the form are shown on a preview.Properties:Simple view: Technical properties are hidden.Advanced view: All properties are shown.The views you have chosen are stored in your usage data. Is a variable  required for  the form control? Is a variable  required for  the form control? Create form variables Create form variables You can define form-specific variables that can be linked to controls. For controls, you can also use the variables as defined for the current application. Variables are used to store data in mobile device sessions. Each session has its own set of variables, to which other sessions have no access. So, you can collect and store data throughout the process without the need to store the session data elsewhere. Procedure 1. Click Mobility design. 2. Click the Forms tab. 3. In the list, select a form. 4. Click Edit. 5. Click the Form variables tab. 6. Click Add. 7. Close the page. Design form controls

Design form controls

For each form, define the applicable controls. A control is a UI element of the form, for example, a field, a button, or a text.
For several types of form controls, you also need to define the control event procedure. A control event procedure has one or more actions that are done on a specific control event, like text changed or button clicked.
If your company uses different types of mobile devices, controls can require a different layout for each device.

 Use form control template to add form control Use form control template to add form control You can use form control templates to quicker design a form.You can add form control templates to a form:When you create a form with the Create form wizard.Manually.This topic explains how to manually add a form control template to a form.In general, if you add a form control template to a form, it is positioned after the last control on the form. Where the control is exactly positioned, depends on the Append new line property of the last control on the form:Yes: the template control is added below the last control.No: the template control is added to the right of the last control.An exception are button templates for which the Stick to footer property is set to Yes. These are always positioned at the footer of the 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. Click the Templates tab. 6. Click Label. 7. In the list, find and select the desired record. 8. Click Select. 9. On the preview, click the control that you have added. 10. Click the Properties tab. 11. Close the page. Notes You can use the Up and Down buttons on the Properties tab to move a form control to another position on the form. Is a  form event procedure  required? Is a  form event procedure  required? Design form event procedure

Design form event procedure

You can set up a form event procedure with actions that are done in a specific sequence. A form event procedure has one action or a series of actions that are done on a form event.

Optionally, you can run an action under specific conditions. For conditions, you can use variables or functions that are available for the application or form.

 End End Yes No Wizard Manually Yes No Yes No

Activities

Name Responsible Description

Create handler

Designer

 		You can apply a handler to an application or a form, depending on the handler type.

For a handler, a class is required. However, in your design, you can already use the handler definition without the class defined.

Inform the developer on the requirements for the handler class to be developed.

Develop handler class

Developer
You can use a handler on an application or a form, depending on the handler type.

For a handler, a class is required. To develop this class, extend one of these classes:
  • DAWApplicationHandler - Extend this class to develop an application handler.
  • DAWFormHandler - Extend this class to develop a form handler.

Prerequisite: Develop the extension of the DAWApplicationHandler class or DAWFormHandler class in the AOT before you start the steps.

Create form with wizard

Designer

 		For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.
You can create a form manually or with a wizard. This topic explains how to create a form with the wizard.
Usually, if you use form control templates, you create a form with the wizard.

Create form manually

Designer

 		For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.
You can create a form manually or with a wizard. This topic explains how to create a form manually.

Create form variables

Designer

 		You can define form-specific variables that can be linked to controls.
For controls, you can also use the variables as defined for the current application.
Variables are used to store data in mobile device sessions. Each session has its own set of variables, to which other sessions have no access. So, you can collect and store data throughout the process without the need to store the session data elsewhere.

Design form controls

Designer

 		For each form, define the applicable controls. A control is a UI element of the form, for example, a field, a button, or a text.
For several types of form controls, you also need to define the control event procedure. A control event procedure has one or more actions that are done on a specific control event, like text changed or button clicked.
If your company uses different types of mobile devices, controls can require a different layout for each device.

Use form control template to add form control

Designer

 		You can use form control templates to quicker design a form.
You can add form control templates to a form:
  • When you create a form with the Create form wizard.
  • Manually.
This topic explains how to manually add a form control template to a form.
In general, if you add a form control template to a form, it is positioned after the last control on the form. Where the control is exactly positioned, depends on the Append new line property of the last control on the form:
  • Yes: the template control is added below the last control.
  • No: the template control is added to the right of the last control.
An exception are button templates for which the Stick to footer property is set to Yes. These are always positioned at the footer of the form.

Design form event procedure

Designer

 		You can set up a form event procedure with actions that are done in a specific sequence. A form event procedure has one action or a series of actions that are done on a form event.

Optionally, you can run an action under specific conditions. For conditions, you can use variables or functions that are available for the application or form.

Activities

Name Responsible Description

Create handler

Designer

 		You can apply a handler to an application or a form, depending on the handler type.

For a handler, a class is required. However, in your design, you can already use the handler definition without the class defined.

Inform the developer on the requirements for the handler class to be developed.

Develop handler class

Developer
You can use a handler on an application or a form, depending on the handler type.

For a handler, a class is required. To develop this class, extend one of these classes:
  • DAWApplicationHandler - Extend this class to develop an application handler.
  • DAWFormHandler - Extend this class to develop a form handler.

Prerequisite: Develop the extension of the DAWApplicationHandler class or DAWFormHandler class in the AOT before you start the steps.

Create form with wizard

Designer

 		For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.
You can create a form manually or with a wizard. This topic explains how to create a form with the wizard.
Usually, if you use form control templates, you create a form with the wizard.

Create form manually

Designer

 		For each action to be done on a mobile device, create a form. Each form is part of a process of actions to do a task.
You can create a form manually or with a wizard. This topic explains how to create a form manually.

Create form variables

Designer

 		You can define form-specific variables that can be linked to controls.
For controls, you can also use the variables as defined for the current application.
Variables are used to store data in mobile device sessions. Each session has its own set of variables, to which other sessions have no access. So, you can collect and store data throughout the process without the need to store the session data elsewhere.

Design form controls

Designer

 		For each form, define the applicable controls. A control is a UI element of the form, for example, a field, a button, or a text.
For several types of form controls, you also need to define the control event procedure. A control event procedure has one or more actions that are done on a specific control event, like text changed or button clicked.
If your company uses different types of mobile devices, controls can require a different layout for each device.

Use form control template to add form control

Designer

 		You can use form control templates to quicker design a form.
You can add form control templates to a form:
  • When you create a form with the Create form wizard.
  • Manually.
This topic explains how to manually add a form control template to a form.
In general, if you add a form control template to a form, it is positioned after the last control on the form. Where the control is exactly positioned, depends on the Append new line property of the last control on the form:
  • Yes: the template control is added below the last control.
  • No: the template control is added to the right of the last control.
An exception are button templates for which the Stick to footer property is set to Yes. These are always positioned at the footer of the form.

Design form event procedure

Designer

 		You can set up a form event procedure with actions that are done in a specific sequence. A form event procedure has one action or a series of actions that are done on a form event.

Optionally, you can run an action under specific conditions. For conditions, you can use variables or functions that are available for the application or form.
Related to Notes

Design forms

 		 

Provide feedback