Blueprint to create new application while reusing the data objects from existing applications

Hi can we please know if we are going to build a new application from the scratch whist we want to ensure to re-use our reusable data objects from other existing built-on applications? What will be the best practice to follow to create this new application via Blueprint?

Thanks.

Michael

@MichaelC16831869 -

  1. On Built From a Blueprint screen - choose your built on application.
  2. Click on Customize Build button
  3. On the Data Objects screen Select - From Blueprint with Inherited assets.
  4. New drop down will pop on the side - Inherit assets from - select your existing data object here to inherit from.

@MichaelC16831869

  1. On Built From a Blueprint screen - choose your built on application.
  2. Click on Customize Build button
  3. On the Data Objects screen Select - Use existing
  4. New drop down will pop on the side - Data references to link to - select your existing data object here.

@Atanu Sen Thanks Atanu, definitely will try this out. :slight_smile: Great guidance.

@MichaelC16831869

I’ll throw one more option out there. Lets say that you have multiple built-on apps that you want to leverage. You can first do an import and mark all your assets (case types, data objects and persona’s) as do not build. After generating your app and reviewing and potentially cleaning up what was generated, you could merge, build your dev and test apps, set up your org app and then add your reusable apps to your implementation app. Once that is done, you can do an extend with blueprint, using the same blueprint, but this time selecting a case type and its related data classes and setting up the inheritance at that point.

I just did an import this way last week: creating an empty app, doing all the set up stuff adding in component apps and then doing the next import (but doing it from the implementation app) and then moving the new branch to the dev app for review, cleanup and merge before we started refining the UI.

@ChrisBoone

Thank you so much Chris. I have been trying this methodology as well. One more question by using this methodology (which I found very interesting while playing with it), can we use your method to also actually manage the class hiearchy via this blueprint-multi-import process. E.g. I have data object in my blueprint which actually I want this data object to become a one level up sharable data object is my base application doesn’t have yet? Not sure if my question makes sense. But happy to share more about what I am thinking. Thanks in advanced.

Cheers.