Rollout

Rollout functionality allows your organization to determine whether or not your users are going to receive automatic updates to their devices. You can elect to ‘pin’ an app to a particular version. Electing to pin a version or use the latest version of an app is an easy process that takes just a couple of steps, outlined below.

IMPORTANT: Using the latest version is recommended to ensure your users receive the latest updates and patches, as they won’t be available on any versions other than the latest.

Click here to take it for a test drive.

This opens Solution Center straight to the Rollout configuration page.

For example, in a typical controlled rollout, here is what happens:

You set your Rollout Version Policy to pin to a specific version (or patch). All of your client machines on your tenant adhere to this pinned version.
If Schneider Electric releases a new version of the application, no updates are applied to any of your client machines on your tenant.
On your chosen date, change your Rollout Version Policy to the newer version (or patch) of the application. This unpins the old version and pins the new version.
Upon the next login on each of your client machines, the update for the new version occurs, and
- Users see a message stating an update is being applied.
- Once finished, users see a message instructing them to re-launch the application to use the new functionality.

Decoding the version string: The 1st number represents the major build, the 2nd number represents the minor build, the 3rd number represents the patch build, and any content after the “-” is the pre-release version number. The version string follows SemVer v1.0 (http://semver.org/spec/v1.0.0.html).

By default, Rollout is configured to use the latest version. Under the Rollout version policy field is information showing the specific version that matches your current selection for the rollout version policy. In the case below, for example, the latest version of the ArcFM Editor XI app is 11.1. The version plus the specific pre-release version number, in this case 1.2.0, is shown in parentheses.

The next 3 p tags are EXI

Click the Rollout version policy drop-down to view a list of available major and minor version choices. Select the desired version to pin. For example, selecting 3.17.* allows patches, but major and minor updates are not applied. Users are locked to the 3.17 version until such time as the policy is changed.

If you want to pin the version to a specific patch, click the Specify patch version checkbox. This affects the Rollout version policy drop-down list, displaying all available patch versions. When specifying a patch version, note that users receive no updates at all until the rollout version policy is changed to a later patch, a #.#.* version, or the latest version. When deselected, only major and minor versions are displayed in the drop-down.

EXI only

Click View release notes to view notes for all of the ArcFM EXI releases.