Deployment of the Roam Mobile Application

Use of Mobile Application Management (MAM) or Mobile Device Management (MDM)

Roam can be deployed to mobile devices by clients using their Mobile Application Management of choice.

One of the main advantages of these systems is that, in case of lost or stolen devices, these devices can be accessed remotely to either block access, and/or delete information from these devices.

Use of AppConfig Option in an MAM/MDM

Roam supports the use of AppConfig. In short, in enables businesses to push the Roam app onto managed mobile devices, while also providing some parameters which control the behavior of the app on initial startup, as well as during use of the Roam app.

Currently, the following variables can be applied.

• Variable Name: ServerURL
  • Content: the URL of the SAI360 web application
    For example: https://SAI360:8080/NetForms
  • If provided, upon first start of Roam after install the Server Address is defaulted to this value.
• Variable Name: AllowChangeServer
  • Content: True or False
  • If set to True:
    Roam users can change the Server URL during the login process, or at any stage later.
  • If set to False:
    Roam users will not be able to access the Server settings at any stage. They will only be able to connect to the server URL which was provided by the MAM/MDM

Accessing (opening and logging in to) Roam via URL

If you intend to launch the Roam application via a hyperlink (for example from an Application Center), you can use this URI:

• Basic: cint-roam://?url=<SAI360_url>
  For example: cint-roam://?url=http://myserver/NetForms
• Including the username: cint-roam://?url=<SAI360_url>&username=<username>
  For example: cint-roam://?url=http://myserver/NetForms&username=joe blogs

If your URL includes any blanks, the string needs to be encoded (for example to escape ' ' with '%20'). This can be done using freely available online tools, like: http://pressbin.com/tools/urlencode_urldecode/.