Creating configuration files

When you deploy iManage Work Mobility for iOS as a Managed App through MDM, the first step is to upload the XML configuration file. This file contains the same data as the Managed App Configuration key-value pairs.

iManage Control Center enables you to create your own configuration file or edit an existing .immconfig file, which are deployed through email or MDM. For more information, see Deploying configuration files.

  1. From the iManage Control Center, select iOS under Client Setup.
    CREATE CONFIG FILE is displayed as shown in the following figure:
    Figure: CREATE CONFIG FILE
    images/download/attachments/39977778/Screen_Shot_2018-04-25_at_11.36.40_am.png
    Type the name of the file in File Name at the top.

    NOTE:

    The configuration files are saved as .immconfig. You may also upload an existing .immconfig file and edit the policies. For more information, see Editing an existing .immconfig file.

    IMPORTANT:

    The inter-dependencies must be examined carefully in Managed App Configuration Policies. For more information on the configurable policies, see Managed App Configuration Policies.

    The following table lists the available policies under iManage Control Center and a very brief description of their use in iManage Work Mobility:
    Table: Policies

    Option

    Description

    Enable Downloading

    Is enabled by default, and allows the users to download document(s) copy on their iOS mobile device.

    Enable Printing

    Is enabled by default, and allows the users to print the iManage Work documents through iOS AirPrint.

    Enable AirDrop

    Is enabled by default, and allows the users to share the iManage Work documents using iOS AirDrop feature.

    Enable touch ID for passcode

    Is enabled by default, and enables the Touch ID authentication for users on the Passcode screen.

    Enable Native Mail

    Is enabled by default, and allows the users to send documents as attachments from the native email app. This feature does not affect the Document NRLs.

    Open in send

    Is enabled by default, and allows the users to send a copy of a document to other applications through the Open In feature of iOS.

    Open in receive

    Is enabled by default, and allows the users to receive copies of documents from other apps through the Open In feature.

    Enable App Extensions

    Is enabled by default, and restricts the users from using the Storage Provider Extension to save or access content on their iOS mobile device.

    Enable privacy curtain

    The Privacy Curtain feature is enabled by default, and is displayed when the application is not active.

    Show demo connection

    Is disabled by default, and Demo is not listed on the Sign In screen of the iManage Work Mobility application.

    NOTE:

    Demo server connection that connects to a public iManage demo server, can be used to test the iManage Work Mobility application before it is deployed in your environment.

    It is recommended that you disable Demo for any production environments.

    Number of password retries

    Is used to set the number of times a user enters the app passcode, before all locally stored data is erased from the iOS mobile device (data on the server is not impacted).
    By default, the Number of password retries is set to a Minimum of 3 and a Maximum of 20.

    CAUTION:

    Users may also lose any local document modifications.

    Passcode grace period in seconds

    Is the time delay that is enforced when switching away from the iManage Work Mobility app, before the App Lock is enforced, and the user is required to enter the app passcode (or use Touch ID if configured).
    By default, the Passcode grace period in seconds is set to a Minimum of 10 seconds and a Maximum of 999999999 seconds.

    NOTE:

    Additionally, you may use the User ID Pre-fill (auth=0 Only) feature, that enables the MDM system to record the user ID after a successful authentication, and populate the User ID field during the next login. If the field is not updated, the User ID value does not auto-fill.

  2. Select Add Server at the bottom to update the server configurations.
    Server Details is displayed as shown in the following figure:
    Figure: Server Details
    images/download/attachments/39977778/Screen_Shot_2018-04-25_at_12.21.55_pm.png

  3. Enter Server Name, and select Generate to get the Server UUID.

    IMPORTANT:

    If you must use special characters in the .immconfig file, ensure you use the corresponding encoded value instead of string literal, as shown in the following table:

    Table: Special Characters

    String Literal

    Encoded Value

    "

    &quot

    '

    &apos

    <

    &lt

    >

    &gt

    &

    &amp

    NOTE:

    After a UUID is assigned to a server, mapping between the UUID and server cannot be altered, as this can cause connectivity issues to the clients.

    IMPORTANT:

    UUID cannot be blank or duplicated. If any of the servers have a duplicate or blank UUID, then that .immconfig file is rejected, and an error message is displayed.

  4. Provide the URL link to the Server.

  5. Select Server Authentication Type from the list:

    1. Standard: Supports both Work credentials and domain/username & password for explicit network authentication.

    2. ADFS: Displays an embedded web view where the user must follow whatever authentication procedures the company has defined for the ADFS implementation.

    3. iManage Cloud (ADFS): Can be used for customers connecting through cloud.
      For more information, refer to the Server Configuration section of the table, in Managed App Configuration Policies.

  6. Select Add.
    The .immconfig file is generated and the configurations are captured.

  7. Select Download File at the bottom to save the file.
    You can use this to deploy the configurations. For more information, see Deploying configuration files.

For more information on setting up ADFS and SAML, refer to iManage Work Server Administration Guide.