Bosch IoT Rollouts

Rollout view

Table of contents:


Software rollout in large scale, rollout status overview and rollout management.

Features explained

  • Create, update, start, copy and delete rollouts.

  • Pause and resume rollouts.

  • Progress monitoring for the entire rollout and the individual groups.

  • Drill down to see the groups in a rollout and targets in each group.

  • Rollout attributes:

    • Selection of targets as input for the rollout based on target filter.

    • Selection of distribution set.

    • Auto-splitting of the input target list based on group number defined.

    • Splitting of the input target list based on a list of defined groups.

    • Trigger threshold to define the percentage of installations to be completed to trigger the start of the next group.

    • Error threshold defines the percentage of error tolerance of a group before calling for an emergency shutdown of the rollout.

Deletion of targets which are in a rollout, changes the rollout’s statistics.

Tips and hints

  • Click on Action buttons to start, pause, resume, edit, copy or delete a rollout.

  • Click on Rollout name to see the rollout groups.

  • Click on Rollout group name to see the targets of that group.


You need the following permissions to see the Rollout view in…

  • read-only access mode: READ_ROLLOUT


The cloud user has full access by default for all available service plans except Starter.

See the Authentication and authorization for further information about available roles and their included permissions.

Rollout list view


Rollout group view


Rollout creation dialog


Clicking on the add icon above the rollout list or on the copy icon of a rollout, opens the rollout creation dialog. In this dialog a new rollout can be defined either with Number of Groups or with an Advanced Group definition.

In the Advanced Group definition tab groups can be added and defined with a Target filter query and Target percentage. The Number of Groups tab defines a fixed amount of groups onto which the targets are distributed in equal parts. The Trigger threshold is the percentage of targets in the group, that must be successful before the next group is started. The Error threshold is the percentage of targets in the group that must fail before the rollout is paused.

In the Action Type field, you can select the type of action the rollout should be running as, see Action state machine > Defined Action Types.

Up to 500 groups can be defined per rollout.

The pie chart shows the distribution of the total targets count onto the different groups.

Depending on the Start type the rollout will be started automatically or only when the user triggers the start. If the scheduled date lies in the past or the Auto start option is selected, the rollout will start as soon as it is ready. Depending on the size of the rollout, the rollout can be ready within a few moments or within several minutes. Very large rollouts (> 100000 targets) might take longer.

Once saved, the Targets will be filled into the defined groups.

Rollout approval workflow

When enabled in the System configuration view, the approval workflow demands an approver to accept or deny a rollout before it can be started.

After a rollout is created, as described in the previous section, it is waiting for an approval. This is indicated by the hourglass icon images/confluence/download/thumbnails/1695525472/hourglass-gray.png . A user, with the role APPROVE_ROLLOUT, can now approve or deny the rollout by clicking on the handshake icon images/confluence/download/thumbnails/1695525472/handshake-gray.png . In the opened dialogue window the approver can review the created rollout, make a decision, and can provide a remark. If the rollout is approved, it is ready to start. If the rollout is denied, it can not be edited or approved anymore, but only be copied or deleted.



Deletion of a rollout

It is possible to delete a rollout using the trash icon, even when it is already started.

After confirm the delete action, the deletion is performed.

When a rollout is not started yet, it will be hard deleted. This means that it is removed completely out of the Bosch IoT Rollouts repository.

If a rollout is already started, all scheduled actions will be deleted and all running actions will be continued.

In the action history you only see the already running actions while the scheduled actions are deleted and are not shown in the UI. Already started rollouts are soft deleted which means that they are still available in the repository but are not presented on the UI.

The Rollout View only shows rollouts which are not deleted. To delete a rollout you need the permission DELETE_ROLLOUT.