Automatic separation of date input
Valid from Pega Version 8.5
Date fields in Date Time controls now automatically divide strings of input into days, months, and years. In single fields, the system adds slashes (/) as the user types the value. For example, an input string of 10102020 becomes 10/10/2020. In separate day/month/year fields, the system automatically switches from one field to the next as the user types the value. This enhancement improves the user experience by helping to users provide input in a more convenient and time-efficient manner.
For more information, see Configuring a Date Time control.
Improvements to OAuth 2.0 Services with Token Introspection Service and Token Denylist Service
Valid from Pega Version 8.5
Increase the security of user sessions by using the newly supported Token Introspection and Denylist services for OAuth 2.0.
Token Introspection service
Use the Token Introspection service to validate JSON Web Tokens (JWT). The Token Introspection service requires authentication.
Pega now uses OAuth 2.0 access tokens called Authorized Access Tokens (AAT).
Token Introspection service endpoint
The Token Introspection service endpoint provides the information about the status of access token and refresh token. Token introspection can be used to validate if a given token is still active or inactive. The token introspection endpoint determines whether the token is valid. The status indicates whether an access token or refresh token is valid or invalid:
- Valid tokens have the
“active”:true
status - Invalid tokens have the
“active” :false
status.
The inactive status can also be due to revocation.
Token Denylist service
You can add tokens to the deny list in cases where suspicious activity might have occurred. The Token Denylist service provides a method for denying user access to the application by revoking the user's access token. This service can prevent a token from being used more than the specified number of times, which can be helpful in preventing replay attacks. Stolen tokens should be revoked using this service. A GET API is also available to get the list of denied tokens.
Keys endpoint
Pega Platform™ is changing from using opaque tokens to JSON Web (JWT) tokens. If this JWT is used by any other system, the public key is needed for signature verification. A new endpoint is exposed to provide these public keys in JWK format: https://host:port/prweb/api/oauth2/v1/token/keys.
For more information, see OAuth 2.0 Management Services.
Improvements to guided tour creation
Valid from Pega Version 7.2.2
Usability improvements to creating and managing guided tours enable you to more efficiently create tours that introduce the key features of your application. Now, you configure the Manage guided tour action on a control to start, continue, or dismiss a tour, instead of specifying an API script.
For more information, see Managing a guided tour.
Caching of common rules in offline mobile apps
Valid from Pega Version 7.2.2
To help start offline-enabled mobile apps more quickly from the time when the server was started, you can now cache common Pega 7 Platform rules, including node scope data pages. Optionally, you can also either cache all node scope data pages, with the exception of the selected ones, or cache only the node scope data pages that are explicitly specified. You set up the offline caching options for your custom mobile app in the Advanced tab of the Access Group rule form.
For more information, see the Offline Configuration section in Access Group form - Completing the Advanced tab.
Deploy in secured mode
Valid from Pega Version 7.2.2
Deploying the Pega 7 Platform in secured mode helps prevent unauthorized access to your system. By default, the Pega 7 Platform deploys in secured mode. For more information, see the Deployment Guide for your environment.
Create case and Wait smart shapes available in Case Designer
Valid from Pega Version 7.2.2
Two smart shapes have been added in Case Designer. Use the Create case smart shape in a case step to create another case, a child case, or multiple child cases. Use the Wait smart shape to pause the process of a case under specified conditions.
For more information, see Adding a preconfigured step to a process.
Search and Reporting does not index large items
Valid from Pega Version 8.5
When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.
Run advanced agents on only one node in a cluster
Valid from Pega Version 7.2.2
You can now configure an advanced agent to run on only one node in a cluster at a specified time. In addition, you can specify the time interval within which an advanced agent runs on only one node in the cluster, which avoids having two advanced agents starting to run on the same node at the same time.
For more information, see Improved control for running advanced agents and Agents rules – Completing the Schedule tab.
New PegaRULES:PegaAPISysAdmin role
Valid from Pega Version 7.2.2
The role PegaRULES:PegaAPISysAdmin has been added to the Pega 7 Platform. This required role gives system administrators access to the Pega API REST User Services and is not required for other services.
For more information, see Securing the Pega API.
Create case and Wait smart shapes are available for stage steps
Valid from Pega Version 7.2.2
You can design case types more efficiently by using smart shapes, which are steps with preconfigured functionality. Use the Create case step to create a case from an existing case type, or to create a new case type, and transfer information from the original case to the new one. Use the Wait step to pause case processing until another case reaches a specified status.
For more information, see Adding a preconfigured step to a process.