Following best practices, scalar properties should not all be defined at the case level; instead, data should be structured using embedded data objects. Pega Blueprint currently generates most UI elements based on scalar properties at the work level, and there is no capability to select individual properties from an embedded data object. Are there any plans to better support embedded data objects in UI generation with Blueprint?
This changed in March. You can now define a property in your case as Embedded which will create a class for that property. You can define additional properties on the embedded property as embedded to create a nested class structure. Any embedded property can now be referenced on a view and you can select individual properties from it. See the following post for more details:
@ChrisBoone But, I feel still there are space for improvements!! Defining embedded property is fine but why should be always creating a new class? Why cannot we create embedded property with the existing data objects created?! Lot of times, we may need that to capture and persist at a later stage!!
Also some logical LSA reasoning could help right? As per design we know scalar properties should not be created on case level, Why can’t blueprint by default incorporate it, instead every time expecting the LSA or the Pega professional to update!!
Agreed. I just ran an new blueprint to see if our embedded data classes were getting put on the data tab (something I thought was going to happen), but it is not doing that as of yet. I, personally, would prefer being able to see embedded classes there so I can better control the naming of the classes. I’ll follow up with the team on this.