Add and manage landing pages in App Studio application menus
Valid from Pega Version 8.1
When working in App Studio, you can now create landing pages that are not directly associated with a case flow to make your application more informative. The landing pages are a good place to display the resources that are related to a case, images as well as text. Configure them to provide an overview of the work, workers, teams, reports, or any information that is available.
For more information, see Creating a landing page.
Mobile apps now use custom-generated skeletons for page transitions
Valid from Pega Version 8.1
Mobile harnesses are now configured with custom-generated skeletons. Used during page transitions, skeletons render a temporary placeholder UI that closely matches the actual UI while data is being loaded from the data store. The use of skeletons enhances the user experience by providing a smooth transition while data is being loaded.
Skeleton transitions work with both dynamic and Ajax containers on the mobile client but work only with the Ajax container on tablets and desktops.
For more information, see Transition effects on actions.
For Microsoft SQL Server deployments, change settings to create data types in Integration Designer
Valid from Pega Version 8.1
For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:
- Owning ruleset: Pega-Reporting
- Setting purpose: reporting/useMergeHintForRRquery
- Value: true
For more information about configuring dynamic system settings, see Creating a dynamic system setting.