@Rakeshr7 Excellent question!
Our vision includes:
- Drastic reductions in development time
- An OOTB UX, optimized for efficiency and “guided workflow” – with Accessibility and front-end best practices built-in.
- Seamless UI upgrades
- Consistency across the application stack
- Extensibility
This enables designers, the business, and engineering to work shoulder-to-shoulder, focusing on the outcomes they want to achieve instead of heavy design and development of a highly customized UI.
Most of common patterns developers were building (often repeatedly) with UI controls and Action Sets are offered OOTB, configurable in App Studio.
When used in a View, Data Reference and Case Reference field types automatically render links to the preview panel or a case, so you don’t need to call open work or open assignment. The ability to expose Local Actions can be configured in App Studio.
Here’s a write-up on why you likely don’t need Action Sets in Pega Infinity Constellation UI:
https://community.pega.com/blog/goodbye-action-sets-cosmos-react-yes-good-reason
You might also be wondering how you achieve dynamic form behavior without manually specifying on change event handlers. That is described here:
https://support.pega.com/discussion/pega-infinity-%E2%80%9923-and-constellation-ui-offers-faster-and-easier-ways-configure-dynamic?
For the best value, we encourage clients to leverage our OOTB patterns where possible. Of course, for advanced, app-specific use cases, Constellation is also extensible where you can build a custom component using React and the web technologies, where you programatically assemble Constellation’s presentational components to build something new; in that scenario, you can define on click and other event logic.
Again, I urge caution. Only leverage custom components for advanced, app-specific use cases. My favorite example of when a custom component is reasonable is a Pega workflow app that interfaces with a finger print reader attached to the computer which captures a finger print and saves it into the case. Obviously, we do not ship a “finger print reader” component. For this advanced, app-specific use case, you’d build a custom component, programmatically assembling a Constellation Button (to initiate the scan) and a Constellation field to hold the image. In the click action on the Button, you’d use the JS api to the finger print reader, capture the image, and then set the image in the field.
Hope this helps.
Sam