Ready-Made Solution Update Steps

When update steps are needed

Update steps are for projects where the ready-made solution is already installed. They are shown when moving to a specific new version and help complete actions that cannot safely run in the background: entering new variables, selecting a channel, reassigning an agent, or confirming an important change.

These steps are not shown when the latest version is installed for the first time. Use installation steps for initial setup.

How to add steps

1. Open the draft of a new ready-made solution version.
2. Select After Confirmation update mode. An automatic version cannot contain update steps because it must apply without user action.
3. In Update Steps, click Add Step.
4. Select a type, enter Russian and English text, and set the order and requirement.
5. Configure the selected type's fields and save the step.

The builder and available types are the same for both phases. Agent, variable, and subscription-link fields are described in Installation Steps.

How the two step groups differ

• Installation steps are part of initial ready-made solution setup and are copied from the latest published version into a new draft.
• Update steps apply only when moving to a specific version. They are not copied into the next draft: add only genuinely new actions for each release.
• Installation steps do not run again during an upgrade.

Upgrading across several versions

The user upgrades the ready-made solution to the latest published version. If several releases lie between the installed and target versions, Senler applies them in order. When it reaches a release with update steps, the system synchronizes that release's resources, shows its steps, and continues after they are completed.

A required step cannot be skipped. An optional step can be completed or skipped. Mark only actions without which the version's resources cannot work correctly as required.

If a step cannot be added

• make sure the version is a draft;
• switch update mode from Automatically to After Confirmation;
• for an agent step, first include the agent in the current version's resources;
• check permission to manage ready-made solution versions;
• see If the step cannot be saved for the remaining field and step-type requirements.