New capabilities of the rich text editor
Valid from Pega Version 8.3
The enhanced rich text editor has a new plug-in that helps the users skip a few configuration screens by uploading image files directly from the file system. When they copy and paste content from a word processor or a spreadsheet, the text retains the original formatting. The developers can now configure all toolbar options, such as bulleting or font formatting, so the users can focus only on the tools that they need and work more efficiently.
For more information, see Selecting the property for a Rich text editor control.
Streamlined user interface for designing case life cycles
Valid from Pega Version 8.3
Case life cycle design now supports reorganizing stages by dragging them to a different position and renaming stages by selecting their text field. The user interface for designing a case life cycle is now more intuitive and provides a better user experience.
Web mashups preview
Valid from Pega Version 8.3
App Studio now has a preview mode that shows how an integrated Pega application is displayed on a chosen website. You can try different host sites, as well as window sizing types and skins, to find the best presentation options.
For more information, see Creating a mashup demo.
Numbered accordion for layout groups
Valid from Pega Version 8.3
Layout groups and dynamic layout groups with the accordion layout now support automatic numbering of collapsible headers. You can now build better user forms, as the numbers show the steps that users need to follow to fill out a form so that they know the process stage at every moment. Automatic numbering accommodates when conditions that are used in accordion sections.
For more information, see Creating a layout group.
Improved performance for work ID generation
Valid from Pega Version 8.3
Work IDs are now generated in batches and managed with dynamic system settings. Batch-based ID generation improves performance and scalability, which reduces the time that it takes to migrate data to a Pega Platform™ application.
For more information, see Default dynamic system settings data instances.
Upgrade impact
In a multi-node environment, the new ID generation method can assign IDs that are not as sequential as in the previous method.
For example, in a 2-node cluster, the IDs could come in from each node in batches of 1000, resulting in successive Work objects having IDs that differ by 1000 (such as 1, 1001, 2,1002, 3, 1003). As more Work objects are created the gaps can get filled. However, there might still be gaps left in the generated IDs. For example, if a node crashes or shuts down, some IDs would be missing, or if a node has given out 600 IDs from a batch of 1000 IDs, then 400 IDs would remain unused. In most situations, this should not be an issue.
What steps are required to update the application to be compatible with this change?
If you must have nearly sequential IDs or cannot accept gaps in IDs (and do not need the performance improvement), then you can change the dynamic system setting to disable the new ID generation method.
The dynamic system setting for this feature is idGenerator/defaultBatchSize. The feature is enabled by default with a defaultBatchSize of 1000. To disable the feature, set the value to 1.
Improved control of case locking and retry mechanisms
Valid from Pega Version 8.3
The Delay factor, Initial delay in minutes, and Max retry attempts fields have been added to queue processors, and the Timeout to acquire lock field has been added to the Queue-For-Processing method. Using these fields, you can quickly configure background processes that require you to lock cases or retry case processing.
For more information, see Creating a Queue Processor rule.
Upgrade impact
After a successful upgrade, the new fields contain their default values.
What steps are required to update the application to be compatible with this change?
To customize the functionality of this feature (and the new fields), open the Queue-For-Processing definition and modify the values for the new properties or fields.
Automatic management of run-time context for background processing
Valid from Pega Version 8.3
Management of system run-time context is now automatic. You no longer need to manually modify the AsyncProcessor requestor type context to make a queue processor or job scheduler work after importing or upgrading an application. Additionally, you do not need to manually modify the AsyncProcessor requestor type context to make new queue processors and job schedulers work.
For more information, see System general landing page and Automating the runtime context management of background processes.
Upgrade impact
After upgrade, you manage the runtime context of your background processing in System Runtime Context instead of in the deprecated AsyncProcessor requestor type.
What steps are required to update the application to be compatible with this change?
Select the Include in background processing option in the Advanced section of the application rule form for all applications that use background processing (such as Job Schedulers and Queue Processing). When this option is enabled, the system automatically includes the rulesets (for the application and its components) in System Runtime Context used for resolving and running Queue Processors and Job Schedulers. Also, when the option is enabled, the application is placed on the System Runtime Context list during application rule saves (such as during application import and migration).
Define a default reporting database
Valid from Pega Version 8.3
You can now easily define a reporting database for all classes that are assigned to a primary database. You can also assign this reporting database as the default reporting database. This provides support for reporting against Amazon Aurora read replicas. AWS Aurora increases the performance and stability of your database management system.
For more information about reporting, see Report Definition data access tab.