Low-code designer > Solution / Update a solution

Update a solution

The feature is used to import changes to an already installed solution. If you have edited components of the solution, you can update it in two ways:

  • Install the fully updated version without saving your customizations.
  • Select the soft update option. Then the components that have been changed will not be updated. Components whose settings you did not change will be updated.

 

To perform an update:

  1. Proceed in one of the two ways:
    • On the Administration > Manage Solutions page, in the solution page, click the three dots icon and select Update.
    • On any system page on the left menu, click clip0205, and in the opened window, click the Solutions tab. Then to the right of the solution name, click Manage and select Update.

update_solution01

  1. Select the .e365 file from your local computer or your system files and click Next.
    This will start the checking process for the components of the solution version from the downloaded file. If errors are found, for example, identical pages are found or dependencies from another solution are added to the version, you will not be able to complete the update.
    If the new solution version has apps, widgets, or business processes whose fields reference apps from licensed system solutions, you will see a notification about it. You can complete the solution update, but you will need to activate the license of the system solution you are using for it to work correctly.
  2. If the solution is successfully checked, click Next.

update_solution02

  1. The downloaded version is then compared to the existing solution in the system. If you have made changes to the solution components, for example, changing the app form or changing a business process, a list of conflicts is displayed. Select a further action:
    • Confirm the solution update. Then the new version of the solution will completely replace the existing one. Your changes will not be saved.
    • Perform a soft update.
    • Cancel the update.

update_solution03

Soft update of the solution

You can use this update option if there are conflicts between the installed and the new version of the solution. The option allows you to save the changes you have made to components such as business processes, apps, forms, pages, and widgets. During the soft update process:

    • Components with conflicts will not be updated, your changes will be saved.
    • Other solution components will be updated if they are not in the conflict list and they do not contain references to components with conflicts.
    • New solution components will be added if they do not contain references to components with conflicts.

Let’s look at some examples.

Case 1. Conflict in the solution component

You have added property A to the app context that is part of the solution. In the new version of the solution:

  • Property B is added to the context of this app.
  • Widget C is placed on the app creation form.

The result of the soft update:

  1. There will be a conflict in the app, it will not be updated. Property B will not be added to its context, property A will remain.
  2. The app creation form will be updated, it will not have a conflict. Widget C will be added.

Рисунок 1

Case 2: Reference to a component with a conflict

The initial solution contains:

  • The app in the context of which you added property A.
  • A business process that has a variable that refers to this app.

The new version of the solution adds property B to the app context and adds a task to the process diagram.

The result of the soft update:

  1. There will be a conflict in the app, it will be not updated. Property B will not be added to its context, property A will remain.
  2. The business process will not be updated because it refers to the app in which the conflict occurred.

Рисунок 2

Case 3. A new solution component contains a reference to a component with a conflict

You have added property A to the app context that is part of the solution.

In the new version of the solution:

  • Property B is added to the app context.
  • A new process is added that references this app.

The result of the soft update:

  1. There will be a conflict in the app, it will be not updated. Property B will not be added to its context, property A will remain.
  2. A new business process will not be added because it refers to the app with the conflict.

Рисунок 3

Soft update of a locked workspace

If the solution contains a locked workspace, the soft update ignores dependencies between this workspace and the unlocked workspace where conflicts are found. In this case, the components of the locked workspace (apps, processes, widgets) will be updated.

Let’s consider the specifics of such an update. Components of a locked workspace:

    • Will be updated if they refer to components of an unlocked workspace in which conflicts are found.
    • Will be updated if they are referenced by components of an unlocked workspace in which conflicts are found.
    • Will NOT be updated if they contain conflicts.
    • Will NOT be updated if there are dependencies between them and components of another locked workspace where conflicts are found.

Let’s analyze the case on the example of the HR solution that contains a locked HR workspace and an HR Settings workspace available for changes:

  1. In the installed version of the solution, at the HR Settings workspace level, add a task to the process that references the locked HR workspace app.
  2. Let’s assume that in the new version of the solution:
  • At the level of the HR workspace, property A is added to the context of the app that is associated with the changed process.
  • At the level of the HR Settings workspace, property B is added to the context of the process we have changed.
  1. Let’s run the solution update.
  2. During its checking phase, it will show conflicts in the process that is changed at the level of the HR Settings workspace. In this conflict, we will see dependencies with the app in the locked HR workspace.
  3. Let’s apply a soft update to the solution and get the following result:
  • The app at the level of the locked HR workspace will be updated, and property A will be added to the app context. Dependencies found in the conflict will be ignored.
  • The process at the level of the unblocked HR Settings workspace will not be updated. The task in it will be saved, property B will not be added to the process context.

Рисунок 4

Found a typo? Highlight the text, press ctrl + enter and notify us