Version

Configuring Mobile Workspaces as Site Homes

In SharePlus, Portals can present a pre-configured mobile workspace that can be shared with its sites. In this scenario, you use the same ZIP package but different content is displayed to the user depending on the site’s context.

You can configure a Site Home with a SharePlus Mobile Workspace to be used by default for a portal and all its sites. To achieve this, Site Homes for Portals need to be pre-configured using Pages and Sites in the Configuration File instead of using the MobileNavigation list.

Steps Overview

  1. Creating a Page that includes a SharePlus Mobile Workspace.

  2. (Optional) Enabling the default list view for the Portal.

  3. Configuring the Portal’s Home.

  4. Defining the Site Home by default (DefaultSitePageName).

  5. Adjusting inheritance settings (InheritParentPage).

Steps

  1. Create a Page that includes a SharePlus Mobile Workspace.

    Define a new page in the Configuration File or use an existing one. You need a View Part for ZIP packages to be specified for the page. For details on how to specify a Page and a View Part including a SharePlus Mobile Workspaces see the Application Home scenario in this section.

  2. (Optional) Enable the default list view for the Portal.

    When pre-configuring home content as the Portal Home, the default content is replaced.

    A View Part with SharePlus default list view needs to be added, so you can switch between content (default list view and the new home content) by using the selector.

    Note

    Note: SharePlus default list view shows all the sub-sites, libraries, and lists for portals or sub-sites. The bottom bar also includes the site´s Favorites.

    In the Configuration File, the Page with the SharePlus Mobile Workspace should include the following View Part:

    <key>ViewParts</key>
<array>
    <dict>
        ...
        <key>Settings</key>
        <dict/>
        <key>ViewControllerID</key>
        <integer>2</integer>
        <key>Title</key>
        <string> </string>
        ...
    </dict>
</array>

    The elements to configure are:

    • ViewControllerID – Specifies the ID defined in the app.plist for the View Controller to be used. For the default list view, the integer value specified must be 2.

    • Title – Specifies the title to be displayed on the top toolbar for this View Part.

  3. Configure the Portal’s Home

    1. Open the Configuration File.

      Search your Portal configuration in the Sites section.

    2. Reference the Page in the pre-configured Portal

      You need to reference the page you created by name (PageName key value).

      The Configuration File should be similar to:

      <key>Sites</key>
<array>
    <dict>
        ...
        <key>PageName</key>
        <string>yourCustomPage</string>
        ...
    </dict>
</array>

  4. Define the Site Home by default (DefaultSitePageName)

    1. Navigate to the HomeManagement feature in the Features.

    2. Reference an existing page by name (PageName key value).

    A sample Configuration File snippet illustrating this step is included on the next step.

  5. Adjust inheritance settings (InheritParentPage).

    In, HomeManagement, enable inheritance between a pre-configured parent site and its sub-sites.

    The HomeManagement feature in the Configuration File should be similar to:

    <key>HomeManagement</key>
<dict>
    <key>Enabled</key>
    <true/>
    <key>Settings</key>
    <dict>
        ...
        <key>DefaultSitePageName</key>
        <string>yourCustomPage</string>
        <key>InheritParentPage</key>
        <true/>
        ...
    </dict>
</dict>

    The existing elements are:

    • DefaultSitePageName – References the page to be used as Site Home by default. The page name must match the name of an existing page in the Pages section.

    • InheritParentPage – When true, sub-sites inherit pre-configured pages from their parent site.