Design application configuration

Release notes

Design the configuration of a mobile application. The main elements in an application configuration are:

Application: The application is the base element for the mobile device applications that you can build with Mobility studio.
Processes: A process is a flow of actions on a mobile device to finish a task.
Forms: 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.
Form controls: A form control is a UI element of the form, for example, a field, a button, or a text.

Before you configure a mobile application, make sure the libraries are up-to-date.

Activities

Name	Responsible	Description
Manage libraries	Designer	Before you start the design of an application configuration, make sure the libraries are up-to-date. Each library is related to a model in D365 FO. A library can have these elements: Actions Test actions Functions Test functions Queries On Refresh, for each model with extensions of specific classes, a library is created or updated. The library name is the same as the model name. For each found extension of these specific classes, the related element is created or updated in the library. Extensions of these classes result in library elements: DAWActionRun - Actions DAWActionRunTestCase - Test actions DAWFunctionRun - Functions DAWFunctionRunTestCase - Test functions DAWQueryMethodRun - Queries A model can have a license defined. If you use a mobile app that uses a library, the related model is checked for a license. If a license is defined for the model the related license count is updated. You can refresh the libraries on the: Mobility design workspace, on the Libraries tab (explained in the steps). Anywhere mobility studio parameters, on the Automatic updates tab, in the Libraries section. If you do so, check the Update libraries and Add new libraries parameter settings. For more information, refer to Set automatic update parameters.
Design applications	Designer	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.
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.
Design forms	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. 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.
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.

Activities

Name	Responsible	Description
Manage libraries	Designer	Before you start the design of an application configuration, make sure the libraries are up-to-date. Each library is related to a model in D365 FO. A library can have these elements: Actions Test actions Functions Test functions Queries On Refresh, for each model with extensions of specific classes, a library is created or updated. The library name is the same as the model name. For each found extension of these specific classes, the related element is created or updated in the library. Extensions of these classes result in library elements: DAWActionRun - Actions DAWActionRunTestCase - Test actions DAWFunctionRun - Functions DAWFunctionRunTestCase - Test functions DAWQueryMethodRun - Queries A model can have a license defined. If you use a mobile app that uses a library, the related model is checked for a license. If a license is defined for the model the related license count is updated. You can refresh the libraries on the: Mobility design workspace, on the Libraries tab (explained in the steps). Anywhere mobility studio parameters, on the Automatic updates tab, in the Libraries section. If you do so, check the Update libraries and Add new libraries parameter settings. For more information, refer to Set automatic update parameters.
Design applications	Designer	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.
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.
Design forms	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. 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.
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.

Related to	Notes
Design application configuration

Provide feedback