This week's updates focus on making stepbase easier to learn, more flexible to configure, and smoother to use day-to-day. Whether you're building your first Flow or managing dozens, there's something here for you.
Guided tours to get you started faster
If you've ever opened the Flow designer and wondered "where do I begin?" That's no longer a problem. stepbase now includes built-in guided tours that walk you through the designer canvas, the configuration panel, and the simulator, step by step.
The tours highlight key areas: where to drag in new Stages, how to configure assignments and actions, and how to test your Flow before publishing. They run automatically the first time you open each area, and you can replay them whenever you need a refresher. It's like having a colleague walk you through the tool, without needing to schedule the meeting.
Connectors that flex between admin and designer
When you set up a Connector to an external system, some parameters are fixed for the entire workspace (like an API key or base URL), while others change depending on the Flow (like which record ID to look up). Previously, that distinction wasn't explicit.
Now, each Connector parameter has a clear scope: either workspace (configured once by an admin when the Connector is enabled) or runtime (mapped by the flow designer for each invocation). This means admins lock down the credentials and endpoints, while designers get the flexibility to wire dynamic values into their Flows, without stepping on each other's toes.
A more polished design experience
Several small improvements add up to a noticeably smoother time in the designer:
Editable block labels. You can now click any Stage or block heading in the configuration panel to rename it inline. No more hunting for a "label" field buried in a form; just click the title and type.
Smarter expression editor. When you're writing conditions or templates that reference data from other Stages, the editor now shows you the human-readable Stage name alongside the internal ID. Hover over a Stage reference and you'll see exactly which Stage it points to. Less guesswork, fewer mistakes.
Initiator context made intuitive. You can now reference the person who started a Flow Instance using initiator. in your conditions and templates, a much friendlier alias than the old user. path. Plus, each Stage now tracks the name of who completed it, so downstream Stages and notifications can say "Approved by Sarah Chen" instead of showing an opaque ID.
Better output from comparison Stages. If you're using compare-and-select Stages (like vendor evaluations or bid comparisons), the results are now structured per respondent. This makes it straightforward to wire up downstream actions (like sending a notification or triggering an API call) for each winning respondent individually.
---
These updates are live now. If you haven't explored the guided tours yet, open your Flow designer; the first one starts automatically.