I have a small tool that generates Constellation View & Context Metadata JSONs from a simplified CSV input. The goal is to automate parts of UI configuration as part of a legacy transformation initiative. I’m wondering if this approach may be feasible as it involves updating Rule-UI-View instances, so I’m curious to hear any thoughts.
This approach assume the data model already exists (either properties on my work class, or a referenced data object).
Hi, Wolfgang. Very interesting idea, definitely worth exploring. If it comes to generating JSON this is one part to be done, second part is to be explored if there is anything more on Rule-UI-View that needs to be set. I don’t have this info readily, but I suspect there is not much more (assuming it is plain View without paragraph rules, localization).
Rule-UI-View is like any other rule, so with some skills you can craft an Activity that will be creating those rules.
Taking this idea further you can as Gen AI to created the input json for you basing on available data model and use case description.
@mrwolf2 there is a lot more to a View than just properties. My biggest concern would be the expertise required to get this right would probably outweigh the time taken to manually create the Views you need. If this could be done reliably, I’m sure we’d already have it in our Modernization Assistant. I’ve seen a fair number of Pega Support issues where people have modified the JSON of the Views, I’d really want to avoid opening myself up to maintenance issues here.
Off the top of my head, some issue:
@Kamil Janeczek and I were talking to a client 2 weeks ago, they were manually create view rules directly in Dev Studio (App Explorer). They were still using the OOTB View editor, but the creation came from the rule up, instead of the UX Tab of the Data/Case. Even that small change in approach did lead to some issues for them getting production ready. Always best to stick to the OOTB wizards for configuration.
Have not seen it done, but if anyone could do it I know it would be you! Please share your learnings 
If you do crack it, might be something we can look to get into the Modernization Assistant.
@MarcCheong appreciate your response - and that’s fair. Yet, creating hundreds of views manually isn’t scalable. We’re exploring alternatives for migrating a legacy app that’s not yet on Pega. While we recognize the importance of reimagining processes rather than simply replicating them, we want to try a pragmatic approach: migrate first, then prioritize optimization where it delivers the most value.
@mrwolf2 “We’re exploring alternatives for migrating a legacy app that’s not yet on Pega” good point! I should of thought of this even when I though legacy was Pega. Why not use Blueprint? If you import what you have into Blueprint, once you eventually import that Blueprint into Pega it will create Views for you, for every step! So actually, you’re work is done for you, and you don’t have to worry about settings and configurations - Pega’s Blueprint Import tool will handle that for you.
