A unique feature of the Dynamics Mobile applications is the ability for the administrators to configure the mobile functional modules by using”server-side settings”.

The server settings are key-value pairs setup by the system administrator for each device role. The server settings then are sent to each device and can be read from the developer to run specific code depending on the setting values.

The developers have to decide the settings, which they app will support and make them available in the documentation.

Reading settings

Dynamics Mobile provides a special API allowing the developer to read the settings:
They can be read by using the following “class”:

$ma.cfgManager

if we want to check the value of a specific setting for our current module, we can use the following code:

if($ma.cfgManager.get('myOption1',function(value){if(value=='true'){
...do something
}})

The developer does not have to take care of the server settings synchronization. The mobile app framework will make sure that the latest settings are retrieved from the server depending on the actual synchronization method used ( on-line, off-line ).

This way the mobile functional modules can allow for simple customization with the need of an experienced developer.

Note that actually the administrator will have to enter the setting for the device role pretended with the module’s unique code. if we have module with code SLA, the administrator will enter myOptions setting in the following manner:

SLA.myOptions1

However, the developer will still have to use only the settings name without the module code prepended ( as shown in the example )

Writing settings

The developer can write settings using the same cfgManager “class”

$ma.cfgManager.set('mysettings','value1',function(){alert('writing completed')});

The setting with name mysetting will be written locally on the device with value value1. Note that the setting and value is only stored locally on the device. It will be stored until the app is uninstalled or the user uses the “Clean Install” or “Wipe out” option from the mobile device.

Last Updated: Dec 1, 2015

Support lifecycle

We provide public releases of our products once a year or more and commit to 12 months support for all public releases. We also provide releases to support the new versions of Microsoft Dynamics NAV and Microsoft Dynamics AX within 12 months after a new version of the ERP is released.

Service Level Agreement

We envision the support as a major component of our effort to provide our customers with mission critical software solutions. We provide support services to customers in order to guarantee their business continuity. Our customer shall report issues or other cases, which requires support. The reporting is performed by authorized personnel from the Customer’s side via the standard support channels described below.

The support is provided in order to:

  • Solve current problems reported by authorized representatives of the Customer on occasion and in connection with Dynamics Mobile
  • Diagnose problems in connection with the standard system functionality
  • Diagnose problems in connection with the functionality customized by Dynamics Mobile team
  • Analyze and eliminate of any “defect” – a mistake in the program code of functionality, whcih affects the Client’s operations

The support services are only provided in response to a support request submitted by authorized personnel from the Customer’s side via any of the support channels:

  • -e-mail: support@dynamcsmobile.com
  • -phone: 00359 2 817 33 63

We provide different response times to support requests based on the request priority as follows:

Priority Reaction time Description
Critical to 2 hour Causes business process block.
Medium up to 8 hours Affects the business process as there are no work around actions.
Low up to 2 business days Low impact issues and requests, which does not affect the system.