Scalar Properties at the case level in Blueprint

[IVANIARIVAS]

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?

[ChrisBoone]

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:

Much Rejoicing for Multi Tier Embedded Data!

This week’s release of Blueprint has delivered the much anticipated ability to take a multi level class and be able to use fields from that class, regardless of level, to create views in blueprint. Imagine that you have a service that is going to return you an account structure like this: Account AccountNumber AccountID AccountType PrimaryContact LastName First Name Phone Address Address Line 1 Address LIne 2 City, State, Zip Additional Contacts (list with the same structure as contact…