Dear Team,
The current version of Blueprint structures the process around a sequential flow from Case Data Model to Data Types and Integrations. Blueprint does offer the flexibility to navigate back and forth. However, it doesn’t yet capitalize on that flexibility when it comes to context-aware suggestions.
For instance, in integration-heavy applications, once complex data types with internal associations are defined, going back to the Case Data Model tab doesn’t prompt users to relate those data types to the case/ to regenerate the case data model based on the context provided through the next step in the process(Data/Integration) . Technically, users can still create properties on the case and manually reference or query those data types based on specific needs;but a contextual prompt would make this significantly more intuitive.
Recognizing defined data objects and prompting users to establish meaningful case-to-data relationships( auto-recognition) could streamline the experience and provide considerable value!Of course, the user should be able to skip it if its not needed.
Just sharing a train of thought that might inspire ideas.
Best , MK