Skip to content

Create or edit an application update

Select Add Update or edit an existing release. The editor does not save until you select Save, and Cancel discards the current editor changes.

Release identity

Field Guidance
Application Code Required exact code used by the client application, such as ALLBOX. Matching is case-insensitive, but use one canonical spelling.
Channel Required stream. Stable, beta, and pilot are offered; custom values are allowed. Clients must request the same channel.
Version Required dotted numeric version advertised to the client.
MSI URL Required direct location from which clients can retrieve the installer.
SHA-256 Strongly recommended 64-character hexadecimal digest of the exact MSI bytes.
Minimum Current Version Optional lowest installed version eligible to receive this release.
Release Notes Concise user and support explanation of changes, prerequisites, restart, and known issues.

The editor checks that required fields are nonblank and that a supplied SHA-256 has 64 hexadecimal characters. It does not validate application-code ownership, duplicate releases, MSI URL syntax or reachability, TLS, package signature, version ordering, release-note content, or whether the hash matches the package.

Version format

Server-side comparison splits versions on periods and compares the numeric prefix of each segment. Missing segments are treated as zero. Examples:

  • 2.4.1 is newer than 2.4.0;
  • 2.4 compares equal to 2.4.0;
  • a suffix such as 2.4-beta is ignored after the numeric 4;
  • a segment beginning with a letter is treated as zero.

Use consistent dotted numeric versions such as 2.4.1.0. Avoid leading v, mixed build labels, dates with nonnumeric prefixes, or semantic prerelease suffixes for ordering. Channels should distinguish pilot, beta, and stable streams.

Integrity and package hosting

Compute SHA-256 after the final MSI is signed and copied to its immutable release location. If the file changes, its hash changes. Confirm:

  • HTTPS with a trusted certificate;
  • access from the target device network without interactive portal authentication;
  • correct MIME/content behavior and full-file download;
  • trusted MSI signing certificate and timestamp;
  • least-privilege storage permissions;
  • no reuse of the URL for different package bytes;
  • hash verification by the supported client.

The portal stores a URL; it does not upload the package.

Publication window

Published UTC controls when a release becomes eligible. Expires UTC is optional and excludes the release at and after that time.

Warning

Although the fields are labeled UTC, the current editor converts picker values through the application server's default time zone. Do not assume the typed clock time is stored as UTC unless the server runs in UTC. Verify the actual activation and expiration instants before enabling a production release.

A new release defaults Published to the current time. The editor does not validate that expiration follows publication. An invalid window can make an enabled release unavailable.

Mandatory and enabled

  • Mandatory sets the manifest update type to Mandatory. Enforcement still depends on the client implementation.
  • Enabled allows the release to participate in selection when its time and target conditions also match.

New releases default to Mandatory but Disabled. Keep a release disabled while validating metadata, package access, signature, hash, targeting, and rollback readiness.

Configure scope

Keep Global release selected only when every matching application and channel should be eligible. To target a rollout, clear Global release and add at least one SITE or DEVICE target.

Adding a target places it in the draft grid. Removing it from the grid is also a draft change. The target set is not persisted until Save.

When editing, Save writes the release first, then deletes all existing targets and recreates them from the current draft. Reopen the release and verify Scope after every save or error.