How to create an Enterprise layer application using Pega Blueprint.
Also how to create abstract data types ?
Are you talking about the Enterprise application? The Enterprise layer will be created as part of the blueprint while application import based on the Organization defined. If your question is related to Enterprise application, it has to be created manually.We can create EmbeddedData in Blueprint that is associated to the case level data model.
Question 1: how to create an enterprise application (assuming you mean an org layer app)
After doing your first import, the system will have created a ruleset that contains your org layer infrastructure. The easiest way to create an enterprise app layer is to:
- do a save as of the application you are in and
- associate it with the ruleset for the org layer,
- name it for the enterprise layer,
- remove the implementation layer ruleset
- update the application URL
- update the settings for the data and int classes to point to the org layer ones
- Save
- For your implementation layer application,
- set it to be built on the newly created org layer application
- save
- remove the org layer ruleset
- save
- if you want to make deployment easier:
- Do a save-as of your org layer class creating version 01
- Create a product rule that promotes Org App version 01
- When you create new versions of your org layer app, you can use the 01 version to promote all your new patch org app versions and you will not have to modify the product rule as you define new application versions unless there are rules that you need to promote that aren’t already picked up by association or ruleset.
Question 2: Abstract data classes
The short answer is that blueprint will not create abstract classes. The closest you can get is to add an embedded property to a case type (and name the property what you would want the class name to be - you can change the property name afterward). When the class gets created, it will be concrete, but no tables will be created for it, so you can change the class to be abstract post-import (or leave it alone).
As an example, lets say you need an address class and want to be able to use it in many places with names like a “mailing address”, “home address”, “business address”. You open the data tab of the first case you want to add an address to. Name the property “Address” and set it as an embedded type. Add some properties to address, like your line 1, line 2, etc. Save the property. Now you can edit the name of the property to be Business Address, but you will see the data type changed from Embedded to “Address”.
On import, address will be concrete, but it will be pointed to PR_Other. You can modify the class to be abstract at that point if you wish.
- Enterprise layer - you can create a layer with just your reusable data or case types. In Blueprint just select “do not build” for your implementation specific layers. There are some great videos out there, including Import: Creating a New Application Built on Existing Assets | Pega from @BraamSmithCLSA and other import scenarios, you may want to watch.
- Abstract class - In a modern architecture, you do not need abstract classes, in fact doing so will limit your options and functionality. See Abstract classes in Constellation are not a best practice.
- The key question, in your Blueprint is which items have records and which do not (what we would of called Concrete and Abstract in Traditional architecture).
- By creating embedded data, you are already instructing Blueprint not to create records.
- By added the data to the Data and Integrations tab, you are instructing the import to create a data object with records.
- Covered in this video (related to the earlier one shared) Import: Creating a New Application from Blueprint | Pega
- The key question, in your Blueprint is which items have records and which do not (what we would of called Concrete and Abstract in Traditional architecture).