Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Ignacio Arriscado (IgnacioA4578)
Capgemini Espana SA

Capgemini Espana SA
ES
IgnacioA4578 Member since 2017 4 posts
Capgemini Espana SA
Posted: Jan 8, 2018
Last activity: Jan 24, 2018
Posted: 8 Jan 2018 9:13 EST
Last activity: 24 Jan 2018 8:10 EST
Closed
Solved

Limited number of fields

Hello:

I´m new on PEGA, I´m completing right now the UI Specialist Course, and i have one doubt: when designing a harness/section, is there any limit in the number of fields you can drag in? In addition , regardless there is a limit or not, does the number of fields in a harness affect the compliance score?

To see attachments, please log in.
User Experience

Accepted Solution

Posted: 6 years ago
Posted: 8 Jan 2018 15:44 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES
Absolutely not, though obviously it's trade-off between performance and user experience. Long and messy UI isn't helpful for end-user. Pega discourages to have excessive fields in UI. And suggests to break down the UI in multiple components as collapsible/tabbed layouts etc. Pega also suggests screen-flow to break the long contented UI. Hope it clarifies your query, kindly notify by marking this post as answered.
To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jan 2018 9:37 EST
Sudhakar Reddy Yaparla (YSudhakarReddy)
JPMorgan Chase & Company

JPMorgan Chase & Company
US

Hi,

As of my understanding there is no such limit, too many fields will lead to performance alerts.

To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jan 2018 9:43 EST
Mounika Thatikonda (MounikaThatikonda) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hello,

There is no limit in the number of fields you can use for a particular layout/section.

Compliance score is generally calculated based on the warnings in you application. Using large amount of fields will not generate a warning.

Hope this answers your query.

Best Regards,
Mounika

To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jan 2018 12:43 EST
Gurpreet Kaur (Gurpreet_GCS)
PEGA
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

Hello,

Pega follows same UI standards as defined by W3C. The benefit you get with PRPC is,  you can create your UI without knowledge of any front end technology, even HTML knowledge is also not required. 

When it comes to limiting the number of fields, you should follow user readability standards. When ever your fields are more, you can divide and group them in logical way. Pega doesn't limit for any number of fields, you can add as many you like.

Hope this resolve your query.

Thanks:

Gurpreet

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 8 Jan 2018 15:44 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES
Absolutely not, though obviously it's trade-off between performance and user experience. Long and messy UI isn't helpful for end-user. Pega discourages to have excessive fields in UI. And suggests to break down the UI in multiple components as collapsible/tabbed layouts etc. Pega also suggests screen-flow to break the long contented UI. Hope it clarifies your query, kindly notify by marking this post as answered.
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice