Multiple Blueprints on different fields at the same time.

Multiple Blueprints on different fields at the same time.

It looks only 1 Blueprint can run at the same time, it makes sense for many Blueprints on the same field (Eg. Stage). But what about multiple Blueprints on "different" fields? the multiple options must be available. (Eg. Stage, Documents Status, Contract Signed, etc). We have multiple roles having to change different fields on the Deals. Let say we have these Blueprints:

Stage, Sales agent (record owner) goes moving the stages during the sale until closed.
Documents Status, Analyst (another role) goes moving the Documents Status states until done.
Contract Signed, Comercial Support (another role) goes moving the Contract Signed states until it's signed.

Here you have 3 different roles moving 3 different List fields each at a different pace. In this case there are 3 Blueprints running on 3 different fields and transitions for all Blueprints must be available.



Info
Workaround suggestions:
1. Marketplace extension
      Our developers have built an extension as a workaround to support multiple blueprints on different fields within the same record simultaneously. You can install it directly from our Marketplace.
2. Separate module for entities associated with Blueprint
      To manage tracking for Deals, Document status, and Contract status effectively, we recommend creating separate modules for each—Deals, Documents, and Contracts—with individual Blueprints tailored to each process.
      When a Deal record is created, you can use the Create Record action in a Workflow to automatically generate associated Document and Contract records. Each module will then have its own independent Blueprint to manage status updates.
      You can synchronize the status from the Document and Contract records back to the Deal record, and display these related records within the Deal’s related list for easy reference. This approach allows for better process management and clear tracking across all three entities.