25.1 adds Dev Studio Support for Editing Constellation Views

User Experience Knowledge Share
1

While, Dev Studio now supports the creation and editing of Constellation Views, making it possible to work with Views without having to use the Case Designer, it also now allows you to save the views to your existing class structure. This allows Constellation to better fit into your existing enterprise class structures.

2

Hello @cantg Welcome to the community :slight_smile:

Can’t agree more on your point.

Having said that, a developer has to follow certain practices which can speed up their development while doing this.

  1. Mark the view as relevant record when they save as from an exisitng view.
  2. Its not advised to modify the view from dev studio and stick to app studio. Its advised and much comforting in app studio.
  3. If the newly saved view does not appear in the UX tab, they can do a browser refresh or logoff and login. It should show up.
  4. To have a clear vision, reasoning, and understanding of existing class structure when they are creating/editing the view into a specific class to avoid redundancy.

Any more best practices others can think of..

Regards

JC

2 Likes
3

@cantg I’ve changed this to a knowledge share category, so it can be found with others of it type :slight_smile:

I’d also add to @JayachandraSiddipeta’s good practices that this should not be a starting point for those new to Constellation.

Constellation knowledge

  • Without knowing the difference between case tabs, form views, partial views, list views AND
  • where views get saved for top level views, data views, portal/landing pages etc.

Those new to Constellation can very easily get this wrong - the native Case Designer / UX Tab are much better at handling this.

Unfortunately, I see time and time again people trying to build rules manually in Dev Studio for Constellation and continually getting it wrong, having to refactor, troubleshoot and raise tickets to fix. Save yourself the pain and let the Pega Wizards handle it :mage: :man_mage: :woman_mage: .

Exception not the rule

This adds some great flexibility to approaching implementation. However, for my opinion, this should be the exception, not the rule. Only dip into doing this manually for specific use cases (e.g. moving, copying, specialisation etc.).