Updating blocks from the library#

For Sherpa Orchestrator version 5.10.0.

Preparation and preview#

Updating replaces the selected block’s definition with the current definition of that block in the library. Multiple selected blocks can be updated. Selecting a group includes its member blocks. Saving the result to the server requires permission to create Processes and access to the selected Process.

An update can be performed as follows:

  1. Select a block on the canvas or select multiple blocks with a rectangle.
  2. Right-click the selection and choose "Update block".
  3. The "Update block" popup opens. The diagram remains unchanged until confirmation.
  4. Review changes and warnings about lost properties and connections. "Cancel" closes the preview without applying it.
Block update preview and warnings

Block update preview and warnings

Possible changes#

The preview displays these changes:

  • Block version, when different from the library version.
  • Added and removed properties and changes to their types.
  • Added, removed or changed inputs and outputs.
  • Updated library metadata, including tooltips and service data.
  • Connections removed because an output is absent or connection limits changed.

The block name, canvas position and current values of matching properties are preserved. The service property RobotData is regenerated. Removed property values are not retained. When a property’s type changes, its value remains but must be checked against the new type and constraints.

Applying and limitations#

"Apply" updates the current diagram. Then save a new Process version. Undo and redo on the designer toolbar can reverse or repeat the local change.

If any selected block lacks a library template, none of the selected blocks are updated. An update cannot be applied when no differences exist. If the project changes while the preview is open, reopen it.

"Update block" uses the current template in the active library. Pinning another block version and rolling back are separate operations described in individual block version management. Check the updated workflow’s compatibility on the Robot used.