Question
Evoke Technologies
US
Last activity: 5 Jun 2024 6:34 EDT
Tabbed Layout-Form view based on a custom condition - Constellation
Hi everyone,
We have a screen wherein we allow users to select a type of Incident using a form view in the first screen. Based on the selected type the user must get a tab with the selected type and the corresponding input fields in the second screen and must be able to enter user information(Form View).
How can this functionality be implemented within Constellation?
Presently, the tabbed views are limited to displaying read-only data(Partial View) even when a form view is used.
Regards
Roshan Raj A K
Accepted Solution
Updated: 5 Jun 2024 6:34 EDT
Pegasystems Inc.
US
Hi!
Glad you wrote! I see that you have a UI in mind, and you're seeking to build that UI in Constellation. That UI-centric approach to development worked well with traditional section and harness rule technology.
For apps built with Constellation, you change mentality to focus on the business outcome you're trying to achieve. A business outcome might be "I need to search for and relate one or more customers to my service call case." Or, "I need to capture the a finger print from an attached finger print scanning device and attach it to the case." These are outcome-focused instead of UI-focused.
Hi!
Glad you wrote! I see that you have a UI in mind, and you're seeking to build that UI in Constellation. That UI-centric approach to development worked well with traditional section and harness rule technology.
For apps built with Constellation, you change mentality to focus on the business outcome you're trying to achieve. A business outcome might be "I need to search for and relate one or more customers to my service call case." Or, "I need to capture the a finger print from an attached finger print scanning device and attach it to the case." These are outcome-focused instead of UI-focused.
Once you've worked with the business to establish the critical business outcome, then you leverage simple configurations in App Studio to achieve that outcome, and you let Constellation generate the multi-channel UX for it (with built-in Accessibility and front-end best practices). In the above two examples, the first one is a simple configuration in App Studio (Data Reference field type, and when you configure it in a View, then you can "enable search". We will generate the entire end to end for searching for and relating customers to the case). Clearly, we cannot capture every conceivable pattern in the world as a simple configuration in App Studio, so the finger print reader would be built as an extension to Constellation called a DX Component: Professional front-end developer could programmatically assemble the Button and other components of the Constellation Design system and write JS to interface with the reader, then publish the extension back to Pega for low code developers to use in App studio,. Write once, share, use everywhere.
So, establish the business outcome and evaluate what Constellation offers as a simple configuration with app studio to achieve that outcome. That is the best value, b/c it's driven by the model, is upgrade-proof, and generates a UX that works across channels with front-end and Accessibility best practices built in.
I'm not entirely clear on what business outcome you're trying to achieve. Would be happy to explore options with you.
If it DOES turn out that some form of dynamic tabbed interface is critical to achieving a business outcome, then take a look at https://pegasystems.github.io/constellation-ui-gallery/?path=/docs/templates-dynamic-hierarchical-form--docs
Sam
Updated: 28 May 2024 4:46 EDT
Pegasystems Inc.
GB
@RoshanRajAK please review the answers provided in similar forum questions:
Tabbed layout/Accordion for Form views - Constellation
Issue working with Views in Constellation
How To Hide Assignment View In Constellation
@Sam Alexander @Marc Alderman @JeanK could someone from the Constellation team provide some input?
Evoke Technologies
US
@MarijeSchillern Thank you for these references but we have ideally checked all of these before putting in a request for this support question.
The functionality we are trying to achieve is different.
Thanks,
Roshan Raj A K
Accepted Solution
Updated: 5 Jun 2024 6:34 EDT
Pegasystems Inc.
US
Hi!
Glad you wrote! I see that you have a UI in mind, and you're seeking to build that UI in Constellation. That UI-centric approach to development worked well with traditional section and harness rule technology.
For apps built with Constellation, you change mentality to focus on the business outcome you're trying to achieve. A business outcome might be "I need to search for and relate one or more customers to my service call case." Or, "I need to capture the a finger print from an attached finger print scanning device and attach it to the case." These are outcome-focused instead of UI-focused.
Hi!
Glad you wrote! I see that you have a UI in mind, and you're seeking to build that UI in Constellation. That UI-centric approach to development worked well with traditional section and harness rule technology.
For apps built with Constellation, you change mentality to focus on the business outcome you're trying to achieve. A business outcome might be "I need to search for and relate one or more customers to my service call case." Or, "I need to capture the a finger print from an attached finger print scanning device and attach it to the case." These are outcome-focused instead of UI-focused.
Once you've worked with the business to establish the critical business outcome, then you leverage simple configurations in App Studio to achieve that outcome, and you let Constellation generate the multi-channel UX for it (with built-in Accessibility and front-end best practices). In the above two examples, the first one is a simple configuration in App Studio (Data Reference field type, and when you configure it in a View, then you can "enable search". We will generate the entire end to end for searching for and relating customers to the case). Clearly, we cannot capture every conceivable pattern in the world as a simple configuration in App Studio, so the finger print reader would be built as an extension to Constellation called a DX Component: Professional front-end developer could programmatically assemble the Button and other components of the Constellation Design system and write JS to interface with the reader, then publish the extension back to Pega for low code developers to use in App studio,. Write once, share, use everywhere.
So, establish the business outcome and evaluate what Constellation offers as a simple configuration with app studio to achieve that outcome. That is the best value, b/c it's driven by the model, is upgrade-proof, and generates a UX that works across channels with front-end and Accessibility best practices built in.
I'm not entirely clear on what business outcome you're trying to achieve. Would be happy to explore options with you.
If it DOES turn out that some form of dynamic tabbed interface is critical to achieving a business outcome, then take a look at https://pegasystems.github.io/constellation-ui-gallery/?path=/docs/templates-dynamic-hierarchical-form--docs
Sam