Manage Blueprints in Agentforce Operations

Why Blueprint Management Matters

Blueprints aren't static templates. They evolve as your business processes change, as you discover improvements, or as new requirements emerge. With effective blueprint management, you can make changes without disrupting running workflows, collaborate with teammates during development, and maintain a clear history of what changed and when.

The key to successful blueprint management is understanding when to create a new version and knowing which changes affect running workflows.

Blueprint Versions

Every time you publish a blueprint, Agentforce Operations creates a new version. Versioning protects running workflows from changes that you make to the blueprint. When you edit and republish a blueprint, existing workflows continue using the old version while new workflows use the updated version automatically.

Use versions to track the evolution of your process over time. Add version notes when you publish to explain what changed and why. If you discover an issue with a new version, you can restore a previous version and republish. There's no limit on the number of versions a blueprint can have.

To learn more, see Manage Blueprint Versions in Agentforce Operations.

Collaborative Editing

Multiple people can edit the same draft blueprint at the same time. With collaborative editing, teams can work together on complex blueprints without interfering each other's changes. You see who else is editing the blueprint in real time, and changes appear immediately for everyone.

Use collaborative editing during initial blueprint development when multiple people must contribute different sections, or when you're making coordinated changes across stages and tasks. Collaborative editing only works on draft blueprints.

To learn more, see Collaborative Blueprint Editing in Agentforce Operations.

Deleting Blueprints

Delete blueprints that you no longer need, to keep your workspace organized. When you delete a blueprint, Agentforce Operations deletes all versions permanently. Running workflows created from the blueprint continue to run normally. Deleting a blueprint doesn't affect workflows that are in progress.

Consider whether you might need the blueprint again before deleting it. If there's a chance you might want to reuse the process structure, keep the blueprint and mark it as inactive or archive it by using tags instead of deleting it. Deletion is permanent and you can't undo it.

To learn more, see Delete a Blueprint in Agentforce Operations.

Locking Workflows

Lock a blueprint's workflows to prevent run-time owners from modifying stages or approval criteria after the workflow starts. Use locking when your process requires strict adherence to the defined structure. To learn more, see Lock a Blueprint’s Workflows to Prevent Run-Time Changes in Agentforce Operations.

Understand which actions are permitted and which are restricted in locked workflows, so workflow owners know what they can and can't change at run time. To learn more, see What You Can and Can't Do in Locked Workflows in Agentforce Operations.

To learn more, explore these links.