Updates from your partner

If a partner manages your organization, they can push workflows and components to it. This page explains how to recognize them, what happens when the partner sends an update, and how to undo an update you do not want.

Your copy is yours

Each workflow or component a partner pushes is an ordinary item in your organization, owned by you. Your people can open, run, edit, duplicate, or delete it with their usual permissions, and the files it needs are copied into your Storage.

When the partner sends an update, it lands on top of your copy. If you changed your copy, the partner sees that and decides whether to replace your changes or leave your organization out of that update. Nothing is merged. Values you filled in for step parameters are kept when an update arrives, for steps and parameters that still exist.

How to recognize partner items

In the Workflow Library and the Task Library, pushed items carry a From label followed by the partner's name, in both grid and table views. Everyone who can see the item sees the label.

Files that came with a push sit in Storage in a folder named From followed by the partner's name.

Checking an item

Select the From label on an item, or select Partner updates in its menu. The menu option only appears on items a partner pushed.

The Partner updates dialog shows:

  • Which partner the item came from, and when it was last updated.
  • Whether your copy still matches: Matches the partner's version or Changed locally since the last update. The dialog checks this when it opens, showing Checking for local changes... while it does.
  • When the last update replaced changes you had made, a notice that reads Updated by the partner on the date over your local changes.

How updates arrive

Components are updated in place with the partner's version. The version you had before is recorded first, so you can revert to it.

Workflows arrive as a draft by default. A new workflow starts unpublished. If your copy is already published, the update becomes its unpublished changes, and your devices keep running the published version until you publish. See Versions and publishing.

A partner can also choose to publish the workflow in your organization as part of the update. That is a normal publish of your workflow, so it also publishes any unpublished edits you had made to it.

If your organization already has an item with the same name, the pushed copy is named with "from" and the partner's name in parentheses, for example "Install Agent (from Northwind IT)". A push never overwrites one of your own items.

Reverting an update

You can undo the partner's last update to an item and go back to the version you had before it. This is available after every update, not only one that replaced your changes, so you can also undo an update that does not work for you.

  1. 1

    Open the item's partner updates

    Select the From label on the item, or Partner updates in its menu.

  2. 2

    Revert

    Select Revert to your version, then Confirm.

When it finishes, the dialog reads Reverted. This copy now shows as changed locally.

What revert restores:

  • A component goes back to the version it had before the update, saved as a new version. For a task group, its steps are restored too.
  • A workflow gets its steps, description, and tags from before the update back as its draft. Its name and whether it is published are left as they are. A published workflow keeps running its published version until you publish, and nothing you published after the update is undone.

Revert is one step. It undoes the most recent update only, and once used, it is gone until the partner sends another update. After a revert, your copy no longer matches the partner's version, so their next push shows your copy as changed, and they choose whether to replace it.

When revert is not available

  • You need edit access. Reverting a workflow needs permission to edit workflows, and reverting a component needs permission to edit components. Without it, the dialog reads You need edit access to revert.
  • There is nothing to go back to. An item the partner created in your organization has no earlier version. The dialog reads There is no earlier version to revert to. The same applies after you have already reverted the last update.
  • Files and marketplace components cannot be reverted. Marketplace components the partner sends are installed from the marketplace at the partner's version.

If something changed while the dialog was open, revert is refused with one of these messages:

  • This update was already reverted, when someone else reverted it first.
  • A newer update arrived from the partner. Reopen to see it. Close the dialog and open it again to see the newer update before deciding.

Partner Activity

Each update that changes something in your organization is recorded in your Partner Activity history as Received a workflow or Received a component, under the name of the person who pushed it and the partner organization. An update that found your copy already matching the partner's version changes nothing and is not recorded.

Owners, Admins, and Client Admins can review this history under Settings, then This Organization, then the Partner Activity tab. See Roles and permissions.

Deleting a pushed item

You can delete a pushed workflow or component like any other. If the partner pushes it again later, you get a new copy.

When the partnership ends

If the partner stops billing for your organization or releases it, the copies you have stay with you as your own, and the partner can no longer push to your organization.

Related