Inside Pipelines: June Improvements from the Engineering Team
How one day a month turns small frustrations into smoother everyday workflows.
Most engineering teams spend a lot of time thinking about what's next.
We do too.
But over the past year we've also started protecting one day each month to improve what's already there. Around the team, we call it "Delightful Pipelines Day." It's a chance to focus on the smaller improvements that make building Pipelines just a little easier.
The search that doesn't stick. The extra click. The workflow that slows you down just enough to notice.
Most of the changes we make are small enough that you probably won't notice them in the release notes. But over time, they add up. We hope they make Pipelines a little easier to use every day.
We'll keep sharing these updates each month so you can see what we've been working on behind the scenes.
Naming Help
Naming things is hard.
We added a Suggest Name option that looks at your pipeline and proposes a name based on what it's doing.
Use it if it’s helpful, or Dismiss if you already have a better name.
Keeping your place when you're searching
You search the dashboard and several similar pipelines appear. You open the most promising one.
Wrong pipeline.
You go back to try another.
Previously, your search was gone. That meant entering it again and rebuilding your shortlist.
Now, your search and results stay with you when you return, so you can move on to the next candidate without starting over.
This works in both My Pipelines and Realm Admin.
Filters should remember what you already told them
We also noticed something while configuring filters.
If you switched from one field to another with the same data type, your filter selections disappeared and had to be re-enetered.
Now your filter selections stay with you when you switch between fields of the same data type. They'll only reset if you switch to a different type.
It's a small change, but if you're building more complex pipelines, it removes one more repetitive step.
A few other things we fixed
This month we also:
- Improved the loading state while a pipeline opens so you no longer briefly see internal IDs.
- Added descriptions to Pipeline Tags, making it easier to understand what a tag is meant to represent.
- Sorted Pipeline Tags alphabetically in the Tags view.
- Improved canvas panning when working in larger pipelines.
- Updated documentation links for AI Actions.
- Made filter names more consistent with Quickbase reports.
That’s June.
That's what we spent this month's “Delightful Pipelines Day” working on.
Some of these ideas came from customer feedback. Others came from things we noticed ourselves while building and testing Pipelines.
We'll do it again next month.
If there's something in Pipelines that makes you think, "There has to be a better way," let us know in the product Feedback, or add a comment below. Those are often the best kinds of improvements to work on.
See you next month.