Hello all,

Would like to ask some help in understanding a strange behaviour we've encountered during our proof of concept work using the community edition of Pega 24.2.2 as our sandbox. We've noticed that when starting a case type created in constellation in a UI kit portal it would not render using sections but would still use the view configured in the flow action.

The UI kit application is built on top of the constellation application and we have not enabled the "Use constellation UI to render landing pages" in its application definition. Attempts to override the flow action created in the constellation application to include a section would still choose to render the view at runtime. Creating the flow action from scratch using the same name and class in the UI kit ruleset to remove the view would result in the case displaying the message "View is not yet defined for this step." at runtime.

Additionally, we've noticed that when launching the case it would invoke a DXAPV2 call to create case which we find strange as there is no property or option where we can define if a case type is UI kit or constellation.

Refer to attached PDF for the series of screenshots of the configuration and demo of the behaviours described.