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.
Application configurations and sample screenshots of behaviour.pdf (911 KB)
@AlyssaAshleyC this is expected. When you blend your architecture, the App that “owns” the casetype governs how this is rendered (Section or View based). So in your case, the Constellation Case is still using the Views defined - this is expected as you wouldn’t want to have to reauthor all your Views/Sections when you’re blending your architecture. The whole point of blending is using this as a stepping stone to incremental adoption.
For my part, as stated, this is expected - when you blend the UI’s you’re essentially using a WebEmbed to render the case from the other application.
Some resources on this:
Curious on your scenario and why you need to override the Constellation flow action to try and show a section?
Hello @MarcCheong,
We are working on creating a generic component built on Constellation that will be used by teams using UI kit applications and Constellation applications as a sub process and maybe in the future as a standalone case type.
@AlyssaAshleyC I have not seen this achieved. You could possibly go the other way, and render a View or React based component in both Architectures but not making a section visible in Constellation…
I should have also mentioned our GitHub of components, they are open license, you can see how they are built, maybe give you some clues in addition to the trainings I mentioned.
@MarcCheong
Thank you! You have been very helpful. Will reply to this conversation or create a new if we have more questions.