Skip to main content

Manage versions of Here Core UI Components

When you deploy Here Core UI Components in a large organization, it is often a requirement to control the version that is available to certain categories of users.

Managing dependency versions​

Starting in Here Core UI Components v13, the Here Core package is a peer dependency of the Workspace and Notification Center packages. This means you must make sure you have the correct versions of all packages installed. You should also make sure you're running the same version of the Workspace and Workspace Platform packages. For details about which versions you need for all packages, see the release notes on the versions page.

Managing versions through desktop owner settings​

In the absence of a specific configuration, Here Core RVM launches the most recent stable version of Here Core UI Components. You can manage the version through an entry in desktop owner settings. This strategy enables you to determine what version of Here Core UI Components your end users receive and to control the rollout of new versions.

You can control the version of Here Core UI Components that runs on users' desktops with an entry like the following:

{
  "desktopSettings": {
    "systemApps": {
        "workspace": {
          "version": "8.1.7"
     }
    }
  }
}

If you're also running Notification Center, add an entry like:

{
  "desktopSettings": {
    "systemApps": {
        "notification-center": {
          "version": "1.20"
     }
    }
  }
}

The RVM uses this entry to find the appropriate version of Here Core UI Components or Notification Center to launch. That means that the desktop owner chooses when to update the Here Core UI software, not application owners.

If desktop owner settings aren't enough​

If desktop owner settings can't be applied, starting in Here Core UI Components version 11, you can specify fallback versions in your app manifest. This situation can occur if you have unmanaged desktops with untested versions you don't support, for example for external deployments. For details, see Fallback manifests for system applications.

Multiple desktop owner settings files​

Desktop owner settings can be as simple as a single static JSON file hosted somewhere on your network. However, to control what version different sets of users access, you might want to create multiple settings files.

Because desktop owner settings are configured through a registry key, you can have multiple static files, and direct an individual user to a specific one. For example, you can have a production version of Here Core UI Components for most of your users, a pre-production version for beta testers, and a third, developer version for your developers.

To deploy a new version of Here Core UI Components, change the version number in the settings file that a given set of users access. The new version is applied when the RVM is restarted. This can be accomplished by either rebooting or closing all OpenFin applications and restarting at least one of them.

Do the same to roll back to an earlier version of Here Core UI Components. In this case, it is a good idea to force users to close the Here Core UI platform, so that the older version is applied immediately.

Table of Contents