Support for advanced validation of embedded and referenced data
Valid from Pega Version 8.5
To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.
For more information, see Validating field values for stage entry.
Complete email and notification approval in App Studio
Valid from Pega Version 8.5
App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way.
For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.
Automatically update dependent applications to use the latest versions of built-on applications
Valid from Pega Version 8.5
You can now automatically update dependent applications to use the latest versions of built-on applications. When you import an archive that you created from a product rule, you can update all dependent applications to be built on the latest application versions in the archive.
For more information, see Updating dependent applications with the latest versions of built-on applications.
Business logic routing of approval steps
Valid from Pega Version 8.5
Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.
For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.
Business logic-based routing cards enhancements
Valid from Pega Version 8.5
To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.
For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.
Alerts for long-running queue processor and job scheduler activities
Valid from Pega Version 8.5
Pega Platform™ now saves an alert in the performance alert log when a queue processor activity or a scheduled job runs longer than the configured threshold value. Use the alerts to identify potential performance issues with long-running processes.
The alerts are enabled by default. You can change the alerts for dedicated queue processors and job schedulers at the rules level. For standard queue processors, you can also set the threshold value for the Queue-For-Processing command in an activity. You disable the alerts in dynamic system settings.
For more information, see:
- PEGA0117 alert: Long-running queue processor activity
- PEGA0118 alert: Long-running job scheduler activity
Default Create stage in a case life cycle
Valid from Pega Version 8.5
Pega Platform™ now adds a default Create stage to a case life cycle every time you create a new case type, both in App Studio and Dev Studio. The default Create stage includes a view that users interact with to provide initial data before case processing begins. Consequently, you can now easily locate the view to make any necessary changes. In the background, the Create stage makes a case type independent from the starting process, which removes relevant advanced configurations and makes application development faster.
For more information, see Capture initial data faster with the default Create stage (8.5), The Create stage.
New JWT access token format: Authorized Access Token
Valid from Pega Version 8.5
Pega Platform™ is changing from using opaque tokens to using JSON Web (JWT) tokens and the JWT access token format: Authorized Access Token (AAT). An AAT enables a client application to validate the server for user permissions and authorizes a specific application to access specific parts of a user’s data.
The major benefits to using the JWT format are:
- The JWT is a self-contained token that has authentication information, expire time information, and other user-defined claims digitally signed.
- A single token can be used with multiple applications.
- The tokens are short-lived and can minimize damage if transport security is compromised, as the token signature is verified.
- As the token is verified with the signature, there is no need to verify against a database, thus reducing latency (usually important for Web APIs).
For more information, see Understanding authorized access tokens.
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.
Enhanced refresh token strategy
Valid from Pega Version 8.5
You now have more precise control over your refresh token expiration strategy. When a refresh token is enabled, you can choose to set its initial expiration based on the value provided by the IDP. The refresh token expiry can be derived from IDP’s session timeout when SSO is used with external IDP for user authentication in the authorization code grant flow. You can also specify a separate refresh token expiration strategy based on your use-case.
These can be configured in the OAuth2 Client registration rule form.
For more information, see Enhanced refresh token strategy.