Ask the Expert - Front-end User Interface with Richard Marsot
Join Richard Marsot for this exciting session November 5 - November 16 to learn how to build components and interactions to match the UX design.
Meet Richard: Richard joined Pegasystems in 2010 and is leading several front end development teams working on the Pega Platform. He’s worked on different part of the core UI platform as well as on the mobile and reporting capabilities. He provides regular training sessions to the Pega development teams on UI Best practices including accessibility and localization.
Message from Richard: Hello! I am looking forward to answering all your questions on how you can leverage the capabilities of the Pega Platform to build some very advanced user interactions and components. The flex-based layouts and the 100+ helper classes are the foundation layer for wiring all your components on your page. I’d love to hear your questions/feedback around the challenges and difficulties that you have when building UI screens!
Hi Richard, Thanks for posting the best practices document !!!
I was going through the section ruleform document and have a question on "Consolidate actions in the action set" topic. Is there any OOTB action set using this model?
Reducing the number of HTTP requests looks promising. We have using multiple actions for an event in many instances and looking forward to use the consolidate actions. So I would like know to if there are any limitations to using this.
often, the primary page when you run an activity / DT might be different if you run a refresh section with a pre-activity / pre-DT since your control that has the action set might be in a sub-page or a completely different context has the section.
the recommendation is that chaining actions like run activity / run DT is very expensive and it is better to create a wrapper activity/DT that run all of them at once and handle errors. If you can also use the wrapper in the reload section, you can get down to a single HTTP request which is very atomic and can improve the user experience. In this case, you need to handle the page context difference manually.
Are there any best practices or additional resources for using flex based layouts?
I feel like a lot of times, when building out UI, I always end up nesting more dynamic layouts then I need to. I have played around with the various property panel settings (like Right flex-end) and that has helped to improve things to a certain extent. I noticed there are a lot of flex based helper classes, is it recommended to just play around with those, get familiar with them and try to leverage them as much as possible?