hide building blocks in from marketplace that used as a helper buildingblock or pre-run buildingblock
Janny the AI Product Manager
New use case: hiding composition dependency Building Blocks
We are using a Composition Building Block to expose a unified service to end users. The composition depends on several individual Building Blocks, which need to be published so the composition can use them.
The problem: all those individual dependency BBs also appear in the marketplace. End users see a long list of single BBs alongside the composition, which is confusing. Worse, those individual BBs don't actually work when applied directly — the composition is responsible for filling in their required input values automatically. So users who pick them directly will get a failed run.
Proposed solution:
Add a "hide from marketplace" flag on a Building Block Definition that:- Keeps the BB published (so compositions can reference and use it)
- Removes it from the marketplace listing visible to end users
- Forces users to go through the composition instead