There have been several releases over the last few weeks - here's a summary!

Users with appropriate account roles and permissions can now upload resources (apps, connectors, process flows, scripts, and cross-reference lookups to a private marketplace.

Users associated with the same company profile - or users associated with any linked company profiles - can access this private marketplace and download items.

The typical use-case for private marketplaces is to allow agencies/partners to share resources between their linked 'child' companies much more efficiently. Agency/partner users can build resources within their own company profile, upload them to their private marketplaces, then switch into any of their 'child' companies to download those resources.

Accessing Private Marketplaces

Private marketplaces are accessed via the main marketplace. If applicable (i.e. if your user account is associated with 'upload' permissions or you are associated with a linked company profile, you'll see new public and private options on the far right of the options bar.

With the public options selected, you'll see the main Patchworks marketplace. With the private option selected, you'll see your private marketplace.

You can find out more in our product documentation!

It's now possible to add notes to shapes in a process flow. By default, notes are visible to your team, but can be marked as private if required. Notes are added/ edited in a markdown editor, with lots of formatting options such as tables, flow diagrams and so on.

• You can add a single note or multiple notes to each shape - there's no limit!
• Any single note cannot exceed 64kb.
• Notes are not encrypted - we strongly advise adding sensitive information such as API keys, login credentials, payload data, etc.
• Notes are associated with a shape, not the process flow version, so if you add notes to shapes in a draft process flow and then deploy that process flow, the notes remain in the deployed version.

You can find out more in our product documentation.

If a process flow runs and fails, a retry option is now available from the run logs page. Users can click this option to run the flow again.

You can find out more in our product documentation.

A manual input option has been added to route and filter shapes, so filters can be defined in cases where the schema can't be used for field selection (e.g. for incoming payloads via the API). Meta variables are supported for this input.

To speed up the process of creating endpoints for a new custom connector, a 'clone' button has been added to the endpoints list, so you can duplicate an existing endpoint and then make required changes to the new version.

You can find out more in our product documentation.

We have introduced a run queueing system to ensure that process flows are run equitably across all companies. Now when a job is triggered to run (either manually, or via a trigger/ webhook/ inbound API call), the run job is placed in a queue for processing. You can view your pending runs from a queue tab within run logs.

You can find out more in our product documentation.

Here are the new connectors added to the (public) marketplace since our last update: