Improved identification and handling of code assembly errors
Valid from Pega Version 8.5
Code assembly error logs are now more meaningful and help you identify root causes with better accuracy. Pega Platform™ now also invalidates erroneous assembly to facilitate successful reassembly when the code is accessed again. For example, if a section is not correctly assembled when a user first signs in to the system, the application attempts to reassemble that section the next time a user signs in. In this way, you can avoid lingering issues and improve stability.
Enhanced tables in Cosmos React UI
Valid from Pega Version 8.5
The Pega Platform™ Cosmos React UI environment now includes improved tables. The updated tables use a revamped graphic design and support a number of new run-time behaviors, including column freezing and advanced filtering. The added features improve the user experience by giving case workers more control over data in tables, while the revised architecture enhances efficiency and reliability.
Response timeout configuration for predictions
Valid from Pega Version 8.5
You can now set a response timeout for your predictions in Prediction Studio. By setting a response timeout, you control how Prediction Studio registers customer responses that later serve as feedback data for your predictions.
For more information, see Customizing predictions.
FTP server records enhanced for SSH FTP
Valid from Pega Version 7.1.9
When using SSH FTP (SFTP) in an FTP Server record, you can securely transfer files by using SSH keys. You can enable and configure SFTP by opening the FTP server record and completing the fields in the Protocol section.
For more information, see SSH FTP for FTP server records.
Data APIs support data exploration in React UI tables
Valid from Pega Version 8.5
Data APIs have been enhanced to support filtering, sorting, paging, and aggregation in React UI tables. You can use that functionality to access your data quickly and intuitively. For example, by using paging, you can query a data page to retrieve the second page of an employee contact list and specify the number of results that are displayed on the page.
For more information, see Data API performance and limitations.
Enhancements to token lifetime limits
Valid from Pega Version 8.5
Pega Platform™ uses OAuth 2.0 authorization codes, access tokens, and refresh tokens to provide flexible token-based security for applications. Expiration settings for these codes and tokens now adhere to certain strict value range based on industry leading practices. For example, the lifetime specified for the authorization code must be in the range 1-600 seconds.
These can be configured in the OAuth2 Client registration rule form.
For more information, see OAuth 2.0 Management Services.
Improved view authoring
Valid from Pega Version 8.5
Case authoring in Cosmos React UI now features updated view authoring tools. The redesigned view tab and overlay provide a more intuitive interface for creating views, applying design templates, and adding fields and controls. This enhanced work environment improves the user experience and reduces context switching, which contributes to a lower development effort.
For more information, see Editing views in a case type.
Context-specific documentation is not available in express mode
Valid from Pega Version 7.1.9
Help topics that are opened from express mode display content that is specific to Designer Studio.
If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.
Designer Studio
Valid from Pega Version 7.1.3
Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.
- Treegrid controls work more quickly in IE9 and IE10.
- On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
- Message error handling has been improved.
- Log messages have been cleaned up.
- Connectors may now be used in Data Pages.
- Move Rules wizard has been enhanced to work in Version 7.1.
End of support for form-based rule forms in Pega 7.1.9
Valid from Pega Version 7.1.9
Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.
Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.
- Open the class form.
- Click the Advanced tab.
- Select
Harness
from the menu. - Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.
Migrating custom rule forms to harnesses and sections offers the following benefits:
- User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
- User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
- Rendering performance on modern browsers is dramatically improved.
- User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.