Installation

Provides orchestrator server-based updates. You can update libraries/DLLs such as pre-built templates and custom libraries deployed on the server through the update manager.
In addition, you can install a recent version of the 'client install' package.

1. After log-in in the designer click on Menu > Help > Update Manager.

2. You can check the list of packages deployed to the server in the Update Manager.

Click the 'View Client Install Packages' button at the top of the screen; you can see a list of packages that can install all updates for the client. Only updated packages with a newer version than the version of the currently installed client will appear in the list.

Click the 'View General Update Packages' button; you will return to the screen where you can see the list of packages, such as add-in libraries, custom libraries, and template libraries.

3. Click on one of the lists of package. Details of the DLLs included in the update package will be displayed.
4. Click on the checkbox to activate the install button.

5. Click the Install button. A confirmation message will be displayed.

If the installation of the 'client install' package proceeds, the user will also be warned that the operation cannot be undone.

6. Click OK . The selected package will start downloading.

7. When the download is complete, the designer will exit and start updating.

8. When the update is finished, the designer will restart.

Restoring the Installation

You can view the histories of installed packages and restore the installation status.

1. After log-in in the designer click on Menu > Help > Update Manager.

2. Click the 'Already Installed' tab in the Update Manager pop-up to check the history of previously installed update packages.

3. Click on the row. Details of the DLLs included in the update package are displayed at the bottom of the row.
4. Select the 'Restore to Previous' combo box at the top to select the date and time you want to restore before a specific time.

5. The package histories to be removed are displayed in gray font, and a restoration target icon is displayed when the restoration is in progress.
6. The most recently installed packages will be restored, including the point in time specified in the 'Restore to Previous' combo box.

7. Click the Restore button. A confirmation message is displayed below.

8. Click the OK button. Programs such as Designer are closed, and restoration of the installation begins.
9. During the restoration process, only the installation history of packages whose 'Type' is '3rd-party installation file' is removed and does not restore the installation of external installation files.

10.  When the restore is completed, the designer will restart.

Real-Time Bot Engine Updates

When a bot is requested to perform a process from the server, it can automatically select the best bot engine to execute. The first-installed bot in the role of an agent in charge of communication with the server and basic bot control operations is a function that executes the process with only the optimal bot execution engine for the process requested to be executed without any change.

You will go through the process of preparing a bot execution engine on your local PC environment that is optimal for performing the version of the designer who wrote the process. At this time, the bot execution engines must be pre-registered on the server by the administrator as update packages in the form of execution engines.

Optimal Execution Engine Version Selection Criteria

To use the real-time bot engine update function, multiple versions of execution engines must be registered as update packages on the server through the administrator in advance. Execution engine update packages contain the following additional information, which can be used to select which execution engines can run a particular process automatically.

A process to be performed can contain multiple work tasks. Therefore, for the bot to select the optimal engine to perform the process, it is necessary to determine the representative version of the process. The most recent version of the process and nested tasks are selected as the representative version of the process. This is because if an older version is selected as the representative version, the possibility of errors occurring in the execution of tasks, etc., of the newer version may significantly increase.

Optimal Execution Engine Execution Flow

When a bot is requested to perform a process, it selects the bot engine that will finally perform the process in the following order of priority.

1. If an execution engine of the same version as the process representative version already exists on the local PC, select it.

   1. If an update exists on the server, such as a hotfix for that Execution Engine, select it.

2. Ensure the server has an execution engine capable of running a representative process version.

   1. If an execution engine with the same version as the process representative version exists on the server, it is selected.

   2. Choose the most recent execution engine capable of performing the representative version of the process.

3. If the optimal execution engine cannot be identified locally and on the server, the process is performed by the bot first installed on the local PC.