Dear Team,

In almost all applications, we design multiple case types that share a significant number of common attributes. From an architectural perspective, the cleanest and most maintainable approach is to define these shared attributes at the application (work-pool) level and let individual case types inherit them through the class hierarchy.

However, Blueprint currently only allows properties to be created at the case-type level, not at the application level. This forces teams to clean up the properties on case types to remove this redundancy before proceeding further.

As applications evolve, teams often need to manually re-save or relocate these shared properties into the work-pool class later ; an avoidable step that would not be needed if Blueprint supported defining shared properties at the application level from the start.

Given this, would Pega consider enhancing Blueprint to allow property creation at the work-pool / application level, so shared attributes can be defined once and reused cleanly across case types?

Such an enhancement would align Blueprint with real enterprise data-modelling practices, streamline Constellation development, and significantly improve long-term maintainability.

Cheers,

Midhun