1. Manufacturing
  2. Anywhere Mobility Studio
  3. Flows

Design applications
Activity Flow

Set up and manage the required applications. The application is the base element for the mobile device applications that you can build with Mobility studio.
For each application, you can define the applicable:
  • Labels - A label defines a piece of text to appear on the application as shown on the mobile device.
  • Variables - A variable is used to store data in mobile device sessions. You can also create form-specific variables.
  • Event procedures - An application event procedure has one action or a series of actions that are done on one of the application events.
  • Processes - A process is a flow of actions on a mobile device to finish a task.
  • Preview style sheets - These style sheets define the appearance of forms on the application previews.
  • Libraries - An application library defines which library elements can be used in the application design. Library elements are: actions, test actions, functions, test functions, and data sets.

Designer Designer Developer Developer Start Start Is a handler  required for  the application? Is a handler  required for  the application? 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 Set up application Set up application Set up and design applications for mobile devices. An application consists of a set of related processes. For example, you can add all warehousing processes to one warehouse application. For each application, you can set up application-specific: Variables Labels Menus Procedure 1. Click Mobility management. 2. On the Applications tab, click Add. 3. In the Application field, type a value. 4. In the Default preview style sheet field, enter or select a value. 5. In the Default device field, enter or select a value. 6. In the Documentation section, write the application documentation. For example, describe the purpose and characteristics of the application. 7. Close the page. Notes You can also import an existing application from another environment with a special XML file. Create labels Create labels Create a label for each piece of text to appear on the application as shown on the mobile device.  You can: Define own labels. Use system labels as already available in Microsoft Dynamics 365 for Operations. Labels are application-specific. So, you cannot use labels across applications. Within an application, you can use the labels on the: Application Forms Form controls Menus Procedure 1. Click Mobility design. 2. Click the Labels tab. 3. Click Add. 4. In the Label ID field, type a value. 5. In the Device type field, type a value. 6. In the Language field, type a value. 7. In the Text property field, type a value. Note: You can: - Enter your own label as text. - Enter a system label as already available in Microsoft Dynamics 365 for Operations. For example: @SYS66152. Notes For own labels, if you operate the application in several languages, provide a translation of the label for each language. For system labels, no translation is required. Create application variables Create application variables You can define application-specific variables that can be linked to form controls. You can use these application variables for all forms of the 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. On the Applications tab, click Edit. 3. Click the Application variables tab. 4. Click Add and fill in the fields. 5. Close the page. 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. Define application preview style sheets Define application preview style sheets For each application, you can set up preview style sheets. These style sheets define the appearance of the forms on the application previews.You can define:The default preview style sheet. This style sheet is used for the application previews, unless defined otherwise.Device-specific preview style sheets. For each applicable device type, you can define a specific preview style sheet for the application.For more information on style sheets, refer to "Set up style sheets". Procedure 1. Click Mobility design. 2. On the Applications tab, click Edit. 3. Sub-task: Define default application preview style sheet. 4. On the General tab, in the Preview style sheet field, enter or select a value. 5. Sub-task: Define device-specific preview style sheets for the application. 6. Click the Preview stylesheet tab. 7. Click Add and fill in the fields. 8. Close the page. Is an  application event procedure  required? Is an  application event procedure  required? Design application event procedure

Design application event procedure

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

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

 Design processes

Design processes

To each application, add the applicable processes. A process is a flow of actions on a mobile device to finish a task. For each of the process actions you set up a specific form.

Assign each process to the applicable roles.

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

Set up application

Designer

 		Set up and design applications for mobile devices. An application consists of a set of related processes. For example, you can add all warehousing processes to one warehouse application.
For each application, you can set up application-specific:
  • Variables
  • Labels
  • Menus

Create labels

Designer

 		Create a label for each piece of text to appear on the application as shown on the mobile device. 
You can:
  • Define own labels.
  • Use system labels as already available in Microsoft Dynamics 365 for Operations.
Labels are application-specific. So, you cannot use labels across applications. Within an application, you can use the labels on the:
  • Application
  • Forms
  • Form controls
  • Menus

Create application variables

Designer

 		You can define application-specific variables that can be linked to form controls. You can use these application variables for all forms of the 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.

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.

Define application preview style sheets

Designer
For each application, you can set up preview style sheets. These style sheets define the appearance of the forms on the application previews.
You can define:
  • The default preview style sheet. This style sheet is used for the application previews, unless defined otherwise.
  • Device-specific preview style sheets. For each applicable device type, you can define a specific preview style sheet for the application.
For more information on style sheets, refer to "Set up style sheets".

Design application event procedure

Designer

 		You can set up an application event procedure with actions that are done in a specific sequence. An application event procedure has one action or a series of actions that are done on an application event.
Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application.

Design processes

Designer

 		To each application, add the applicable processes. A process is a flow of actions on a mobile device to finish a task. For each of the process actions you set up a specific form.
Assign each process to the applicable roles.

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.

Set up application

Designer

 		Set up and design applications for mobile devices. An application consists of a set of related processes. For example, you can add all warehousing processes to one warehouse application.
For each application, you can set up application-specific:
  • Variables
  • Labels
  • Menus

Create labels

Designer

 		Create a label for each piece of text to appear on the application as shown on the mobile device. 
You can:
  • Define own labels.
  • Use system labels as already available in Microsoft Dynamics 365 for Operations.
Labels are application-specific. So, you cannot use labels across applications. Within an application, you can use the labels on the:
  • Application
  • Forms
  • Form controls
  • Menus

Create application variables

Designer

 		You can define application-specific variables that can be linked to form controls. You can use these application variables for all forms of the 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.

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.

Define application preview style sheets

Designer
For each application, you can set up preview style sheets. These style sheets define the appearance of the forms on the application previews.
You can define:
  • The default preview style sheet. This style sheet is used for the application previews, unless defined otherwise.
  • Device-specific preview style sheets. For each applicable device type, you can define a specific preview style sheet for the application.
For more information on style sheets, refer to "Set up style sheets".

Design application event procedure

Designer

 		You can set up an application event procedure with actions that are done in a specific sequence. An application event procedure has one action or a series of actions that are done on an application event.
Optionally, you can run an action under specific conditions. For conditions, you can use functions that are available for the application.

Design processes

Designer

 		To each application, add the applicable processes. A process is a flow of actions on a mobile device to finish a task. For each of the process actions you set up a specific form.
Assign each process to the applicable roles.
Related to Notes

Design applications

 		 

Provide feedback