Portal Community

The Pipelines Screen

Selecting Pipelines from the left menu shows a searchable, filterable grid of every Pipeline in your tenant:

Column What It Shows
NameThe Pipeline's name, as set in Add Pipeline.
DescriptionThe free-text notes entered when the Pipeline was created.
Poll TimeoutThe "how long to wait per step" value in seconds — the failure-detection window from Creating a Pipeline.
Last ExecutedWhen this Pipeline last ran, from any trigger.
Execution CountHow many times this Pipeline has been run in total.
EnabledWhether the Pipeline is currently allowed to run.

Your Search Is Remembered

Whatever you type into the search box, and whichever filters you set, are remembered for you personally. Come back to the Pipelines screen later — even after navigating away entirely — and it picks up right where you left off instead of showing a blank search every time. This is the same "remembered search" behavior already used on the Templates screen; both work identically.

Row Actions

Execute

Starts a new run of that Pipeline immediately, no navigation required. Since a Pipeline run is more than a single execution, the confirmation links you straight to that run's entry in the run-history view (see Executing & Run History) rather than just a plain "started" message.

Edit

Opens the Pipeline builder screen for that Pipeline — the same master-detail screen you used when first adding steps (see Adding Items & Template Lookup), now pre-loaded with its existing steps.

Delete

Asks for confirmation, then removes the Pipeline. Past run history for it is retained, not wiped out — deleting a Pipeline stops you from running it again, it doesn't erase what already happened.

The Templates Menu, Right Alongside It

The left menu has a second item — Templates — sitting next to Pipelines. It's not a lookalike or a cut-down copy: it's the exact same Templates Search screen used everywhere else Templates are managed, unchanged. This means you never have to leave this app to review, configure, or spot-check a Template before adding it to a Pipeline through the Template Lookup picker.

Why two menu items? Templates are the more heavily used, primary building block — you'll open that menu far more often. Pipelines is for the specific case where several Templates need to run together as one repeatable chain. Having both one click apart keeps that workflow fast without duplicating any screens.