Question
Lventur
IN
Last activity: 26 Apr 2024 11:35 EDT
Tabbed View Fields Are In Read Only Format Always in Pega Constellation
Hello Team,
When we are embedding Tabbed Views inside other views, in perform mode also all the tabbed view fields are coming in read-only format. Is there any ways available to make tabbed view as editable in constellation.
Any alternative solution in constellation for tabbed view apart from screen flow?
We are currently using Pea Infinity 23.peg
Accepted Solution
Updated: 26 Apr 2024 11:35 EDT
Pegasystems Inc.
GB
The tabbed templates are used by Partial views (in Infinity 23 onward. If you are using 8.8 then you would see these called Case views). These are intended only for displaying / organizing read only data. Form views which use the Default form template are intended for user interaction.
There is some further information on the different view types in the below linked documentation.
What is the objective / requirement that you are trying to meet with a tabbed interactive view? Are you trying to break apart a single long / complex form for example? We would be interested to know more about the goal here.
As Ramesh mentioned, a multi step form might be an alternative if you are looking for a guided journey through entering data across multiple screens.
ING Nederland
NL
@Gunasekaran Baskaran had the same problem a few weeks ago, it seems field group is the only possible solution as of now within constellation - https://support.pega.com/question/tabbed-layoutaccordion-form-views-constellation
Pegasystems Inc.
CA
I'm curious to know, do you have a particular reason for avoiding screen-flow in your use case?
Screen flows are intended for Long, complex online forms that can make navigation difficult for users. A form is an interface for collecting data from users and processing the work
Accepted Solution
Updated: 26 Apr 2024 11:35 EDT
Pegasystems Inc.
GB
The tabbed templates are used by Partial views (in Infinity 23 onward. If you are using 8.8 then you would see these called Case views). These are intended only for displaying / organizing read only data. Form views which use the Default form template are intended for user interaction.
There is some further information on the different view types in the below linked documentation.
What is the objective / requirement that you are trying to meet with a tabbed interactive view? Are you trying to break apart a single long / complex form for example? We would be interested to know more about the goal here.
As Ramesh mentioned, a multi step form might be an alternative if you are looking for a guided journey through entering data across multiple screens.