Skip to main content
Matrix42 Self-Service Help Center

Matrix42 Mobile configuration for iOS

Summary

The Matrix42 Mobile App for iOS can be pre-configured by using iOS Managed App Configurations on devices with iOS 7 and higher. The configuration is based on an XML and can be set in App Portal when editing the M42Mobile application. You can pre-config Service Store, Mobile Content Management, Branding options or security policies. You can place the XML keys + value in any order. All KEY values can be generally used optional - exceptions are mentioned in below sections. We added a sample XML file in the attachment area of this KB article.

 

Silverback EMM Management

This configuration points the M42Mobile App to a pre-defined Silverback server. By doing this, the M42Mobile App can retrieve various policies and configurations:

  • Content Management repositories like File Shares, OneDrive, ...
  • Policies configured in Silberback Admin not deploy by iOS App XML config feature  

We recommend to always define the following settings when managing the M42Mobile with Silverback: 

Key 'UDID'

This information is passed to the Silverback Server to identify the device.

<key>UDID</key>
<string>{DeviceUDID}</string>

Key 'EpicURL'

This is the external DNS name of the Silverback Server

<key>EpicUrl</key>
<string>https://external_dns.silverback_servername.com</string>

Customer Branding

You can change color of certain fields and texts where by default the Matrix42 orange color is used. This is also called the 'tint color'. Additionally you can exchange the Matrix42 logo with a customer logo.

Key 'TintColor'

Use the RGB code colors in decimal format separated by comma

<key>TintColor</key>
<string>40,133,60</string>

Key 'LogoURL'

Refer to a URL that is accessible for M42Mobile App. The logo will be download during M42Mobile Setup process

<key>LogoURL</key>
<string>https://dl.domain.com/u/47110815/logo.png</string>

Workspace Management (Service Store) Account

All accounts will be configured in the accounts dictionary starting with M42Mobile 3.3.6 for iOS. These accounts collection can contain multiple accounts of different types but currently never multiple accounts of the same time. This overrides manually created existing accounts in the app so that the IT can enforce account settings for their users. 

<key>Accounts</key>
<array>
    <dict>...</dict>
    <dict>...</dict>
</array>

These parameters can be used to create a Workspace Management account:

  • Type: Defines the type of the account and must be set to "ServiceStore"
<key>Type</key>
<string>ServiceStore</string>
  • ServerURL: The external DNS name of the Service Store server  
<key>ServerURL</key>
<string>external_dns.svs_servername.com</string>
  • Domain: This is the LDAP / Active Directory domain the Service Store Server user belongs to
<key>Domain</key>
<string>imagoverum</string>
  • Username: Configure the Service Store username. You can use Silverback lookup value to pre-populate.
<key>Username</key>
<string>{UserName}</string>
  • Password: You should use this field only for demo purposes
<key>Password</key>
<string>UseForDemos</string>
  • Port: The TCP Port used for HTTP(S) communication used to connect to the Service Store server
<key>Port</key>
<string>443</string>

The following full example shows how to configure a Service Store account as part of the accounts collection. In this example the password property is missing so that the end user will be enforced to enter the password:

<key>Accounts</key>
<array>
    <dict>
        <key>Type</key>
        <string>ServiceStore</string>
        <key>Server</key>
        <string>external_dns.svs_servername.com</string>
        <key>Port</key>
        <string>443</string>
        <key>Domain</key>
        <string>imagoverum</string>
        <key>Username</key>
        <string>{UserName}</string>
    </dict>
</array>

Mobile Content Management (MCM)

It is not required to pre-configure Content Locations like a File Share, Google Drive or SharePoint by using this iOS App XML Config feature. The Silverback Admin can easily configure the Content Locations in the Tag / Content area. This approach additionally has the benefit that the Silverback administrator can granularly assign the Content Locations on a per Tag basis compared to the  iOS App XML Config feature. 

If for some reason you need to use the iOS App XML Config feature, then please refer to the following KB article M42Mobile iOS Config XML for MCM Content

App Settings, Actions & Restrictions

Starting with version 3.3.6 of M42Mobile for iOS it's possible to configure every setting within the Silverback Server. This configuration is processed as policy enforce from the central server. After applying a settings via Silverback the end user can't change this setting anymore in the application. The following settings are supported: 

Passcode

Passcode settings are configured in the passcode dictionary

<key>Passcode</key>
<dict>** Add settings as described bellow here **</dict>
  • Enable: Enforces the user to authorize via passcode when opening the application
<key>Enable</key>
<true/>
  • Passcode Length: Defines the complexity level of the required passcode. Currently the values 4 or 6 are supported
<key>Length</key>
<integer>4</integer>
  • TouchID: Enforces the user to authorize via TouchID instead of a traditional passcode
<key>TouchID</key>
<true/>

This following full example enforces the user to authorize via TouchID or when this is not available on the hardware with a complex 6 digit long passcode: 

<key>Passcode</key>
<dict>
    <key>Enabled</key>
    <true/>
    <key>Length</key>
    <integer>6</integer>
    <key>TouchID</key>
    <true/>
</dict>

Privacy

Enabling the privacy setting ensures that all sensitive information will be blurred when switching out the app or when switching between the applications in the iOS task bar. In combination with the Passcode settings it prevents not permitted users from getting sensitive data via screenshots:

<key>EnablePrivacy</key>
<true/>  

Local Notifications

Local Notifications can be used to define the timeframe end users should be notified regarding pending tasks in the M42Mobile app. The Local Notification configuration is encapsulated in the LocalNotifications dictionary:

<key>LocalNotifications</key>
<dict>** Add settings as described bellow here **</dict>
  • Days: Time frame in days to be reminded in. Currently 0 - 7 is supported, 0 means notifications are disabled
<key>Days</key>
<integer>7</integer>
  • Time: Specific time of day to be reminded in 24 hour date format.
<key>Time</key>
<string>15:30</string>

This following full example notifies the end users every 7 days short after noon:

<key>LocalNotifications</key>
<dict>
    <key>Days</key>
    <integer>7</integer>
    <key>Time</key>
    <string>13:30</string>
</dict>

Start Tab

This configuration defines which section from the left menu should be used as the initial page when the application will be started from the end user.

<key>StartTabURL</key>
<string>m42mobile://news</string>

The following start tab url's are supported: 

Hide Tabs

This configuration defines which sections from the left menu should be hidden

<key>Menu</key>
<dict>
  <key>Hidden</key>
  <array>
    <string>m42mobile://dashboard</string>
    <string>m42mobile://news</string>
  </array>
</dict>

The following url's are supported: 

Actions

The M42Mobile application offers several actions which can be enabled or disabled from the Silverback Server. As soon an action is disabled it can't be used from the end user anymore. The following actions are supported: 

  • Add Account: Allows to disable the add account action in the application settings
<key>DisableUserAccounts</key>
<true/>
  • Add Datasource: Allows to disable the add datatsource action in the mobile content management viewer
<key>DisableDocumentSource</key>
<true/>
  • Was this article helpful?