Manage native apps

With Relution it is possible to distribute native iOS apps and to do release management. This means that different versions can be provided for different groups of people. For example, users can have version 1.0 of an app in productive use, while a group of key users tests version 1.1 without the other users noticing. To do this, version 1.0 must be uploaded to Relution at the beginning and set to the Release status.


Create a new app

Native apps are created in the menu under Apps → App Store. The Add button opens the Add a new app dialog. Under Source, the Native app option is selected.

After clicking Next, the app file (.ipa) is uploaded via Choose file. Add details then opens the app form.

In the app form, the Release status is specified and the app is created with Save. Except for the Archive status, each release status can only contain one version of the app.

By default, members of the Appstore User and Device Manager groups can see and install the app in the Relution Agent as soon as a version is in the Release status. Versions in the Development and Review status are not visible to these groups. If different permissions are enabled in the App Store settings under Default permissions for new apps, these apply instead. Without such a default, the permissions can be adjusted in the Permissions section of the app:

  • Owner: may apply any operation to the app in every status.
  • Reviewer: may edit the app and move versions to the Release or Development status.
  • Developer: may upload and edit versions in the Development status and move them to the Review status or to the Archive.
  • User: may download, rate and comment on versions in the Release status.

Regardless of these permissions, administrators can distribute the app to devices via the Relution portal:

  • with the Deploy Relution store app device action (App Installation →),
  • via the Required apps list of an App compliance → configuration,
  • via auto deployments in the app details, which automatically install the version in the Release status on the devices of the assigned users and groups (App Installation →).

Update app

If a new version is to be tested for the app, it can be set to the Development or Review status in advance. Before that, the new version must be selected and uploaded via the Add new version button.

A date can be set for the new version in the Go Live date field. The version is only moved to the Release status automatically on that date if an App Release Workflow → is active and the version in the Review status has passed all workflow steps. Without an active workflow, the date serves only as a preferred date and the version is moved to the Release status manually (see below).

Both versions can be viewed in the app properties.

Users with the appropriate permission can also view, install and test the app on devices.


Manual go-live of the new version

In the Relution portal, the respective versions can be viewed and configured. If the new version is in the Review status, clicking the Release button moves it to this status. If it is still in Development, the change is made via Move to → Release. If a version is already in the Release status, it is automatically moved to the Archive.

Top