Activities

Activity	Area	Description
Add existing form control to templates	Configuration	You can use form control templates to quicker design a form. If you have designed a form control that you want to use on other forms as well, you can save it as a form control template. All settings of the form control are copied to the template: Control properties Device-specific control layout Documentation Control-type-specific setup. For example, if the control type is Configurable grid, the grid configuration is also copied to the template. A form control is application specific and a form control template is generic. These application-specific elements, if used on the original form control, are copied to the form control template: Labels: Template labels are shown on the Labels tab. Variables: Template variables are shown on the Variables tab. Queries: To view a template query, in the Query field click the link. Additionally, for each form control template, you define the: Name and description Default styling: the default styling is used for the template preview. For form controls with an event procedure, you can indicate if the event procedure also must be copied to the template.
Add processes to roles	Setup	For each role, define the applicable processes. If a user logs on to a mobile app as built in Mobility studio, the user roles define which processes are applicable to the user.
Analyze test runs	Testing	Each time you run a test, a test run is created. You can run tests for these entities: Test scenario Test case Test suite Test plan All elements of the test entity that you run are added to the test run. For example, if you run a test suite, each of its test cases is run. And for each test case in the test suite also the test scenarios are run. So, the resulting test run has all test cases and all the related test scenarios covered. Use the test runs to analyze the results of the tests.
Change steps for test case	Testing	If a test case has recorded steps, it can be required to make changes to these steps. For example, if the related process is changed as well. You can add, remove, or change steps to align the test case with changes in the related process. So, all settings for the existing steps are kept, which would be overwritten if you do a re-recording.
Check cache	Setup	To run an app from a cached configuration, you must publish a menu or a process to cache. You can check if a cached menu or process is still up-to-date. This topic explains how to check if a cached menu is up-to-date.
Check for errors	Configuration	You can automatically check Mobility studio applications for errors and inconsistencies. Which checks are done? Generally, the checks are done that are also done when you manually enter a record and save it to the database. So, the checks are done that control the data consistency in the database. For example, does a used reference still exist in the database? What is checked? If you check for errors, these Mobility studio elements are checked: The selected application. The application elements. For example, its forms, actions, and event procedures.
Clean up transaction history	Deployment	If required, you can clean up the transaction history. You can define the number of days for which you want to keep the transactions.
Configure configurable grid	Configuration	Configure the columns of the configurable grid and the data that is shown in the configurable grid. The related query defines which columns are available for the grid.
Configure data grid	Configuration	Configure the columns of the data grid. You can only add columns that are also defined as fields in the data set. Ask the developer of the data set class for the exact names.
Create and record test case	Testing	Use a test case to test a process. For each test case, you can define a specific sequence of steps through the process to be tested. You can define several test cases for a process, as the steps done in a process can vary. You can create a test case and directly record the related steps.
Create application variables	Configuration	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.
Create form control - Literal HTML	Configuration	You can add a control of type Literal HTML to a form. With this control type, you can use literal XHTML tags to add controls to a form. For example: <hr /> adds a horizontal line to the form.
Create form control - Button	Configuration	You can add a control of type Button to a form. For the button, also define the control event procedure. A control event procedure has one or more actions that are done when the button is clicked.
Create form control - Camera	Configuration	You can add a control of type Camera to a form. As a result, you can use the mobile device to take a picture or record a video. If it is OK, you can save it to Anywhere mobility studio. Both pictures and videos are saved to the Images tab on the Mobility sharing workspace. The files are saved in a fixed format: Pictures: PNG Videos: MP4 If a form with a camera control is shown on a mobile device with several cameras, you can choose which camera to use.
Create form control - Check box	Configuration	You can add a control of type Check box to a form.
Create form control - Configurable grid	Configuration	You can add a control of type Configurable grid to a form. Compared to the data grid, a configurable grid uses a configurable query to query the data.
Create form control - Data grid	Configuration	You can add a control of type Data grid to a form. Compared to the configurable grid, a data grid uses a developed data set to query the data.
Create form control - Image	Configuration	You can add a control of type Image to a form. As a result, the specified image is shown on the form.
Create form control - Label	Configuration	You can add a control of type Label to a form. A label is piece of text or a variable value to appear on the application as shown on the mobile device.
Create form control - Report output link	Configuration	You can add a control of type Report output link to a form. As a result, a button is added to the form. If clicked, a file is opened and shown on the mobile device. To be able to open the file, a class method is required that gets the file from a location that is both accessible from the mobile device and from the AOS. Ask a developer to develop this class method. In the onLoad method of the form, the report output control must be activated. The path to the file must be defined with the reportFilePath method, which is available from the user control class.
Create form control - Signature capture	Configuration	You can add a control of type Signature capture to a form. Use this control to capture a signature on a mobile device and get it saved as a file. The resulting signature capture file is stored in the file store.
Create form control - Text box	Configuration	You can add a control of type Text box to a form.
Create form manually	Configuration	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	Configuration	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.
Create form with wizard	Configuration	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 handler	Configuration	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.
Create labels	Configuration	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 process	Configuration	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.
Create query	Configuration	You can use a query to get the relevant data: To be shown in a configurable grid. For the predefined 'Query' action that is used on an event procedure. For a counter. To configure a query, you can use the Create query wizard.
Create test case	Testing	Use a test case to test a process. For each test case, you can define a specific sequence of steps through the process to be tested. You can define several test cases for a process, as the steps done in a process can vary. You can create a test case and record the related steps later.
Define application preview style sheets	Configuration	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".
Define test variables	Testing	For each test case, you can set up test variables to be used as input during test execution. For each test variable, you can define the default value. You can use test variables: To define the Field value for a test case step of type Set field. In asserts, parameters, and conditions of an action on an event procedure for pre-actions or post-actions for a test case or for a test for a test case step. To define the values to be used in a test scenario.
Delete expired sessions	Deployment	Once in use in real life, each time a user logs on to Mobility studio on a mobile device, a session is created. If required, you can delete sessions that are expired.
Deploy translated label file	Configuration	You can make a translated label file available on any Dynamics 365 for Finance and Operations environment. This topic explains how to download the label file. When it is downloaded, add the label file to the relevant Visual Studio project.
Develop action class	Configuration	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.
Develop action class for test action	Testing	You can use a test action for any test case on a: Test case event procedure. If the test case event occurs, the action is done. Test event procedure for a test case step that concerns a button. If the button is clicked, the action is done. For a test action, a class is required. To develop this class, extend the DAWActionRunTestCase class, which is an extension of the DAWActionRun class. Prerequisite: Develop the extension of the DAWActionRunTestCase class in the AOT before you start the steps. Note: The steps are to have the developed test action class uploaded as test action to the related library.
Develop class method for a Report output link form control	Configuration	For a form control of type Report output link, a class method is required. A Report output link form control adds a button to the form. If clicked, a file is opened and shown on the mobile device. To be able to open the file, a class method is required that gets the file from a location that is both accessible from the mobile device and from the AOS. To develop this class method, in the onLoad method of the form, the report output control must be activated. The path to the file must be defined with the reportFilePath method, which is available from the user control class.
Develop data set class	Configuration	Use a data set on a form control of type Data grid. The data set gets the data to be shown in the data grid. For a data set, a class is required. To develop this class, extend the DAWQueryMethodRun class. Prerequisite: Develop the extension of the DAWQueryMethodRun class in the AOT before you start the steps. Note: The steps are to have the developed data set class uploaded as data set to the related library.
Develop function class	Configuration	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.
Develop function class for test function	Testing	You can use a test function for a condition on a test case event procedure action. The test function fills the related value of the condition. For a test function, a class is required. To develop this class, extend the DAWFunctionRunTestCase class. Prerequisite: Develop the extension of the DAWFunctionRunTestCase class in the AOT before you start the steps. Note: The steps are to have the developed test function class uploaded as test function to the related library.
Develop handler class	Configuration	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.
Develop literal XHTML tag	Configuration	Develop the requested literal XHTML tag to be added to a form control of type Literal HTM. For example: <hr /> adds a horizontal line to the form.
Export configuration	Setup	You can export a configuration to an XML file. So, you can import it in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. If you export a configuration, all related content is included in the file. You can export these configurations: Application Device Menu Process Style sheet Form control template As an example, the steps explain how to export an application.
Export test case	Testing	You can export a test case to an XML file. So, you can import the test case in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. What is included in the export depends on the export type: Only test case For all selected test cases, this is included in the export: General test case settings Steps Test variables Events Only test scenario For all selected test cases, only the test scenarios are included in the export. Test case & test scenario For all selected test cases, everything is included in the export. If you export a test case, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import. A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.
Export test plan	Testing	You can export a test plan to an XML file. So, you can import the test plan in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. If you export a test plan, this setup is always included: General test plan settings Related test suites General test suite settings of related test suites The related test cases Which parts of the related test cases are included in the export depends on the export type: Only test case For all related test cases, this is included in the export: General test case settings Steps Test variables Events Only test scenario For all selected test cases, only the test scenarios are included in the export. Test case & test scenario For all selected test cases, everything is included in the export. If you export test cases, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import. A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.
Export test scenario	Testing
Export test suite	Testing	You can export a test suite to an XML file. So, you can import the test suite in another Microsoft Dynamics 365 for Operations environment. You can find and download the created file on the Mobility sharing workspace, on the Data files tab. If you export a test suite, this setup is always included: General test suite settings The related test cases Which parts of the related test cases are included in the export depends on the export type: Only test case For all related test cases, this is included in the export: General test case settings Steps Test variables Events Only test scenario For all selected test cases, only the test scenarios are included in the export. Test case & test scenario For all selected test cases, everything is included in the export. If you export test cases, consider this: The default values for the test variables are included in the export of a test case. Possibly, this data is not available in the environment where you import the test case. To be able to run a default test, you must check and, if required, change the default values of the test variables after import. A test scenario is set up based on specific data (variable values) which possibly is not available in another environment. So, a test scenario cannot be run in another environment if the same data is not available in that environment. You can, of course, change the variable values after you have imported the test scenarios. An export of only test scenarios, only makes sense if the related test cases already exist in the environment where you import the test scenarios.
Fix errors	Configuration	Fix the found errors. You can do so from the Check page. For each check operation, the result is logged in the operations history. It can, for example, be that you didn't yet fix all errors immediately after doing the check. A next time, you can open the logged check operation results to continue fixing errors.
Generate documentation	Configuration	For each Anywhere mobility studio application, you can generate several types of documents. The type of information and detail level, that you can add to a document, depend on the document type. The types of documents are: Default: You can include all available information in the document. Technical design: You can include all available information in the document for the application, processes, forms, and controls. Functional design: You can only include functional information in the document for the application, processes, forms, and controls. Test case: You can include functional application information and test case information in the document. The template for each document type is defined in the Anywhere mobility studio parameters. For several elements, you can write documentation. For these elements, you can include the available documentation in the generated document: Application: As you generate a document for a specific application, the application documentation is automatically included. Processes: The process documentation is included if you select Yes in the Processes field and Process details field. Forms: The form documentation is included if you select Yes in the Forms field and Form details field. Form controls: The form control documentation is included if you select Yes in the Control details field. Test cases: The test case documentation is included if you select Yes in the Test case details field.
Import configuration	Setup	You can import a configuration from an XML file. This XML file must be the result of a configuration export from Mobility studio on another or the current Microsoft Dynamics 365 for Operations environment. The steps in this topic show how to import a configuration file that is stored on the file share. Make sure the file is already uploaded as type Data file to the Mobility sharing workspace. You can also import a configuration file from: A file location on your computer. To do so, in the File location field, select File on file share. Browse for the file on your computer. On selection, the file is automatically uploaded as type Data file to the Mobility sharing workspace. A file location on the server on which Microsoft Dynamics 365 for Operations is running. Only use this option for big configuration files.
Maintain form control template	Configuration	You can use form control templates to quicker design a form. Usually, a form control template is created from an existing form control or it is imported from another environment. You can check these form control templates and make changes, if required.
Make control layout device-specific	Configuration	If your company uses different types of mobile devices, controls can require a different layout. For example, longer labels do not fit properly on a smaller screen. So, you can define a smaller version of such a label for these small-screen mobile devices.
Manage libraries	Configuration	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.
Monitor active users	Deployment	Once in use in real life, each time a user logs on to Mobility studio on a mobile device, a session is created. Each session is created based on the related application. A session represents the running instance of an application. The data, as stored in the controls and related variables, is unique for this session and is separated from other sessions of other users that can run simultaneously. The session data is stored in tables in Microsoft Dynamics 365 for Operations to make the session state persistent. As a result, for example, if a device is reset or the web session is lost, the application state is preserved. If the user logs in again, the application continues where it is left off. You can monitor these active sessions in the active users log.
Monitor export history	Setup	You can review the configuration exports you have done from Mobility studio.
Monitor import history	Setup	You can review the configuration imports you have done to Mobility studio.
Monitor license count	Setup	You can monitor the actual license usage of a library compared to the available number of licenses. On the License users versus active user chart, this is shown: Active users - For each library, the number of currently active mobile app users is shown. For each active mobile app that uses a library, an active user is counted for the library. A mobile app can use several libraries. So, the use of one mobile app can result in an active user count for several libraries at the same time. License count - The license count is only shown for a library if a user count license is defined for the related model. So, if a perpetual license or no license is defined for a model, no license count is shown for the related library. As a library can be used in several applications, the license count is not application specific. The chart shows the overall license count and active users. If for a library the full license count is used, an additional user cannot use the library. Example: The AnywhereFoundation library has a license count of 10. 10 users are currently active on this library. Another, eleventh, user tries to open a mobile app that uses this library. This is not allowed as the full license count for the library is already in use. If the license count of a library is fully or almost fully used, it can occur that users cannot use the related mobile apps for that reason. To solve this, you can take actions like cleanup the active sessions and, if that does not help, increase the number of user licenses for the applicable libraries.
Monitor operations history	Configuration	You can monitor the history of operations. For the check-and-fix operations, the results are logged in the operations history.
Monitor transaction history	Deployment	All events during a session on a mobile device, are logged in the transaction history. All transactions that are sent from the mobile device to Mobility studio and the response from Mobility studio to the mobile device are stored. Also, the contents of the infolog at the end of the event handling is stored. If an application gives errors, you often can find an answer in the transaction history. For example, you can find error messages in a response.
Publish to cache	Setup	Running an app on the real-time configuration in Anywhere mobility studio can be slow in a Tier 2 environment. In this case, you can choose to run an app on a cached configuration. This is faster, but the app can be outdated. You can publish a menu or a process to cache for the first time or to update the cache. You can publish to cache or update cache on the: Mobility management workspace, on the Menus tab (explained in the steps). Mobility design workspace, on the Processes tab. Anywhere mobility studio parameters, on the Automatic updates tab, in the Cache section. Note: Cache is only published or updated for the menus for which the Update check box is selected.
Record additional steps for test case	Testing	Use a test case to test a process. For each test case, you can define a specific sequence of steps through the process to be tested. You can define several test cases for a process, as the steps done in a process can vary. Use this procedure to record additional steps for a test case if it already has steps. The additionally recorded steps are added after the last existing step. If you have finished the recording, you can remove the newly added steps that are not needed, for example the logon step. You can use the Up and Down buttons to position the needed additional steps in the right position in the sequence of steps.
Record steps for test case	Testing	Use a test case to test a process. For each test case, you can define a specific sequence of steps through the process to be tested. You can define several test cases for a process, as the steps done in a process can vary. Use this procedure to record the steps for the test case if no recording is yet done.
Register for Google Maps API	Setup	In Anywhere mobility studio, you can embed Google Maps in your applications. To be able to embed a map, you must register for it and get an API key from Google. Google may charge you for this.
Register for Google Translate	Setup	In Anywhere mobility studio, you can translate labels from these sources: Anywhere mobility studio application. Dynamics 356 for Finance and Operations label file. You can translate labels with Google Translate. To use the Google Translate services, you need an API key. Google may charge you for this.
Register for Microsoft Translate	Setup	In Anywhere mobility studio, you can translate labels from these sources: Anywhere mobility studio application. Dynamics 356 for Finance and Operations label file. You can translate labels with Microsoft Translate. To use the Microsoft Translate services, you need an API key. Microsoft can charge you for this.
Re-record steps for test case	Testing	Use a test case to test a process. For each test case, you can define a specific sequence of steps through the process to be tested. You can define several test cases for a process, as the steps done in a process can vary. Use this procedure to re-record steps for a test case if it already has steps. Note that a re-recording overwrites all existing steps. So, all settings on the existing steps will be lost as well.
Run default test	Testing	You can test the default test case to check if it runs properly. The default test case is the test case with the steps as defined. If you have used test variables in the test case, the related default values are used.
Run test case	Testing	You can test a full test case to check if it runs properly. As a result, all active test scenarios are run. If no test scenarios are defined, only the default test case is run. The default test case is the test case with the steps as defined. If you have used test variables in the test case, the related default values are used.
Run test plan	Testing	Usually, you run tests according to a test plan. A test plan can have test suites from several applications. So, these test suites can be run in one go. You can run a test plan according to a schedule. Set up this schedule as a batch recurrence. Each time you run a test plan, a test run is created. All elements of the test plan that you run are added to the test run. Example You run a test plan. As a result: Each of its test suites is run. For each of these test suites, also the defined test cases are run. For each of these test cases, also the defined test scenarios are run. For each test step, the preview is saved if, on the Anywhere mobility studio parameters, the Log test run preview parameters is set to Yes.
Run test suite	Testing	You can run a test suite to test a group of test cases. So, these test cases can be run in one go. A test suite can have test cases from but one application. Each time you run a test suite, a test run is created. All elements of the test suite that you run are added to the test run. Example You run a test suite. As a result: Each of its test cases are run. For each of these test cases, also the defined test scenarios are run. For each test step, the preview is saved if, on the Anywhere mobility studio parameters, the Log test run preview parameters is set to Yes.
Scan configuration	Setup	If you have installed a deployable package to upgrade an Anywhere app in your D365 FO environment, you can scan for changes on these elements: Libraries Applications Style sheets Cache It can be useful to scan before you do an update. To see if changes are made and an update is required. The scan checks all currently available records. It does not consider the automatic update parameters and the value of the Update check box for a record. When the scan is completed, and for a currently available record, the current version is: Different from the new version, an update is required, and the record is marked with the icon. The same as the new version, no update is required, and the record is marked with the icon.
Set automatic update parameters	Setup	Set the parameters for automatic updates. These parameters are applied when a full update is done. The applicable parameters are also applied when you only: Refresh libraries Update applications Update style sheets Update cache
Set document template parameters	Setup	You can define document templates for several types of documents to be generated from Anywhere mobility studio. You can set a default document template for these types of documents: Default Technical design Functional design Test case The type of information and detail level, that you can add to a document, depend on the template type.
Set map API provider parameters	Setup	In Anywhere mobility studio, you can embed Google Maps in your applications. To be able to embed a map, you must register for it and get an API key from Google and enter it in the Anywhere mobility studio parameters.
Set number sequences	Setup	Before you can use Anywhere mobility studio, set up the related number sequences. Define the number sequences that are used for: Applications (Application instance) Forms (Form instance) Controls (Control instance) Sessions on mobile devices (Application session) Test cases Test runs Test suites Test plans For more information on number sequences and how to generate number sequences, refer to Number sequences.
Set security parameters	Setup	Set the security parameters for Anywhere mobility sessions.
Set test manager parameters	Setup	Set the parameters that apply to the Anywhere mobility studio Test manager.
Set translator API provider parameters	Setup	In Anywhere mobility studio, you can translate labels with Google Translate or Microsoft Translate. To these translation services, you must register for it and get an API key from the translation service provider.
Set up application	Setup	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
Set up application event procedure	Configuration	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 one of these application events: On load - An application is loaded to a mobile device. On logoff - A user logs off from the application. The user session is stopped and removed from the active sessions list. Note: On logoff does not take place if a user session expires. On menu select - A menu is opened on the mobile device. 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 that are available for the application.
Set up before and after actions for test case	Testing	You can set up a test case event procedure with test actions that are done in a specific sequence. These actions can be done before or after the test case is run. A test case event procedure has one action or a series of actions that are done on one of these test case events: Initializing - The test actions are done before the test case is run After execution - The test actions are done after the test case has been run. For an application event procedure, you can use: The pre-defined test actions. Self-defined test actions - For each of these actions, a self-developed class is required. 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 that are available for the application.
Set up control event procedure - Button	Configuration	For a control of type Button, 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 button clicked control event. So, the procedure is started if the button is clicked. 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 and variables that are available for the application or form.
Set up control event procedure - Check box	Configuration	For a control of type Checkbox, 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 checked changed control event. So, the procedure is started if the check box is selected or cleared. 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 and variables that are available for the application or form.
Set up control event procedure - Signature capture	Configuration	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.
Set up control event procedure - Text box	Configuration	For a control of type Textbox, 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 text changed control event. So, the procedure is started if the value in the text box is changed. 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.
Set up counter for process	Configuration	For each process, you can set up a counter that is shown on the process tile on a menu. A counter can give information on, for example, the workload or the escalation level of the process. To set up a counter, you need a: Query to get the relevant data. CSS class to define the appearance of the counter on the process tile on the menu. These predefined counter CSS classes are available: CounterLeftBottom (UI_Anywhere_Counter-leftBottom) CounterLeftTop (UI_Anywhere_Counter-leftTop) CounterRightBottom (UI_Anywhere_Counter-rightBottom) CounterRightTop (UI_Anywhere_Counter-rightTop) These CSS classes show a small counter number on the process tile. The counter number is shown in one of the corners of the tile. Example CounterLeftTop: CounterLargeCentre (UI_Anywhere_Counter-large) Shows a big counter number centered on the process tile. Example: CounterAnalog(UI_Anywhere_Counter-analog) Shows both a counter number and a gauge on the process tile. The gauge shows the counted number expressed in a percentage. The percentage is calculated based on the counter range. For the gauge to work properly, you must enter this in the Custom style attributes field: counterRangeColors(#56d134, #eae43a, #d62828) counterRange(0, 100) By default, the counter range is set to 0, 100. You can change these range numbers. In the example, the colors to be shown on the gauge are green, yellow, and red. You can change these colors to any color (in HEX code). Example:
Set up CSS class references	Setup	You can define a device-specific layout for a menu or form-control. For example, to apply a different design for a button or to apply a different font. For such a layout, a specific CSS class is required in the relevant style sheet file. To be able to use such a specific CSS class, in Mobility studio, set up a reference to the CSS class in the style sheet. You can link this CSS class reference to the relevant form control to get the required layout. For several application components, a default CSS class reference is pre-defined. These CSS class references are automatically added when you add a component of the related type to an application: Button CheckBox GridView Label TextBox Caption MenuButton FormTitle DropDown
Set up default printers	Setup	Set up the default printer for each warehouse, user, and printer type combination. Based on this setup, it is determined which printer is used when a user prints from an app.
Set up devices	Setup	Set up devices to define the screen sizes for the mobile devices that you use. This ensures that the pages are properly displayed on your mobile devices.
Set up form event procedure	Configuration	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 one of these form events: On init - A form is created in the form stack of the user session. Usually, this is done once for a user session. On load - A form is opened on the mobile device. On submit - The user submits data on the mobile device. For example, scans a barcode or enters a number. On deactivate - Another form is opened with an event action of type Form. On reactivate - The previous form is opened with an event action of type Return from. 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 variables or functions that are available for the application or form.
Set up general parameters	Setup	Set the general parameters that define the: Session behavior. Transaction logging during sessions. Document types to be used for notes and images. Run time mode, and if it is Cache, also the cache limits.
Set up main menu	Setup	In the menu structure to be used on a mobile device, you need a main menu. In the menu structure, the main menu is the top one and the first a user sees on a mobile device. For each main menu, you can define the: Submenus that can be opened from the main menu. Processes that can be started from the menu. Style sheet to be used for each applicable device type.
Set up printer types	Setup	Set up the different types of printers that can be used by the apps as designed in the Mobility studio. For example: packing slip printer or label printer.
Set up printers	Setup	Before you can set up printers for Mobility studio, install the Document Routing Agent to enable network printer devices. You can use the registered network printers to set up the Mobility studio printers.
Set up roles	Setup	Set up the roles for the users in Mobility studio. Use roles to define which processes apply to which users: For each user, you can define the applicable roles. For each role, you can define the applicable processes.
Set up style sheets	Setup	Style sheets are used to define the appearance of: Menus and processes on mobile devices. Applications in the design previews. Set up a reference to these style sheets in Mobility studio.
Set up submenu	Setup	In the menu structure to be used on a mobile device, you can use submenus. In the menu structure, the submenu can be linked to a main menu and to another submenu. For each submenu, you can define the: Submenus that can be opened from the submenu. Processes that can be started from the submenu. If you create a submenu, automatically a line is added to navigate back to the previous menu.
Set up test plan	Testing	Use test plans to group test suites. You can add test suites from several applications to one test plan. So, these test suites can be run in one go.
Set up test scenarios	Testing	You can add test scenarios to a test case to do several tests with a different data set. Depending on the data, you can run the test under different conditions. You can only use scenarios, if you also use test variables.
Set up test suite	Testing	Use test suites to group test cases for an application. So, these test cases can be run in one go.
Set up tests for test case steps	Testing	For a test case step that concerns a button, 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 button clicked control event. So, the procedure is started if the button is clicked. For a test case step event procedure, you can use: The predefined test actions. Self-defined test actions - For each of these actions, a self-developed class is required. 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 that are available for the application.
Set up user configuration	Setup	You can view and edit the current configuration for you as a user. You can change the: Application - The current application you are working on. If you change it, also the application filter on the workspaces is changed accordingly. Level - The level on which you currently can create, edit, or remove Mobility studio elements. For example, if you as a user have configuration level Base: All elements that you create get level Base. You can only edit elements with level Base. If you try to edit an element with, for example, level User, you get error messages. You can only remove elements with level Base. If you try to remove an element with, for example, level Company, you get error messages.
Set up users	Setup	Set up the users for the mobile apps that are built with Mobility studio. For each user, define: The main menu that is shown if the user logs on to the mobile device. Note: if no menu is available yet, you must define the user menu later on. The login settings to log in to the mobile app on a mobile device. The app run time mode. Does the app run from cache or on the configuration? For each applicable company, the roles of the user in the company. The roles define which processes are applicable to the user. If the user menu has processes that are not applicable to the user, these are not shown to the user on the mobile device.
Translate application labels	Configuration	In Anywhere mobility studio, you can translate labels from an Anywhere mobility studio application. By default, all labels of the application with the same source language are translated. You can use several settings to limit the set of labels to be translated. When the labels are translated, the label translations for the target language are saved to the Labels table.
Translate label file	Configuration	In Anywhere mobility studio, you can translate the labels of a Dynamics 356 for Finance and Operations label file. Before you translate a label file, get the to-be-translated label file from Visual Studio and store it in a folder.
Update application libraries	Configuration	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.
Update applications	Setup	If you have installed a deployable package to upgrade an Anywhere app in your D365 FO environment, you can update the applications in your D365 FO environment to make the changes available. It can be useful to scan before you do an update. To see if changes are made and an update is required. For more information refer to: Scan configuration. On update of applications, only the applications with the Update check box selected, are updated, applying the Attach libraries to applications parameter setting. New applications are always added.
Update configuration	Setup	If you have installed a deployable package to upgrade an Anywhere app in your D365 FO environment, several elements must be refreshed or updated in your D365 FO environment to make the changes available: Libraries Applications Style sheets If you run the app from cache, also the cache must be updated with the changes. It can be useful to scan before you do an update. To see if changes are made and an update is required. For more information refer to: Scan configuration. You can update all elements in one go. On update: All libraries are updated, applying the parameter settings. Only the applications, style sheets, and cache records with the Update check box selected, are updated, applying the parameter settings. New records are always added.
Update style sheets	Setup	If you have installed a deployable package to upgrade an Anywhere app in your D365 FO environment, you can update the style sheets in your D365 FO environment to make the changes available. It can be useful to scan before you do an update. To see if changes are made and an update is required. For more information refer to: Scan configuration. On update of style sheets, only the style sheets with the Update check box selected, are updated. New style sheets are always added.
Use form control template to add form control	Configuration	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.