There is a ton of information on how to build an application or workflow in blueprint, and bring it into a live environment where the blueprint can be combined with existing assets.
But what if you wanted to do the opposite, and bring in a reusable component or application into Blueprint to combine it with a new workflow, so that you can sketch out what it would look like with actual assets like data, names, channels that doesn’t need to rely on Blueprint’s AI design agents to fill in the blanks.
How would one approach this?
Export a Blueprint from the original app? Maintain a library of component blueprints? Run the AST?
this is a trickier one. If you have built out reusable flows that can be plugged into a case, I would just drop in a utility shape and replace it post-import.
When there is a data structure that you are wanting to reuse, then it gets a little messier because you likely want to use that data structure to create views or perform lookups (search and select). In those cases, I would start in your implementation application and have your ai agent generate an extract of the classes and properties you need to get into blueprint for preview purposes. I would then go into blueprint and ask the ai agent to add the class (as embedded) to a case that you need it for, or to add it to the data tab if you are trying to use it for selecting records.
If you need the same class for both selecting and data display, you will need to prioritize which purpose to proceed with. During import you would then identify those embedded classes you created as “Use Existing” so that the existing classes get referenced instead of new ones.