Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
Important information about this release is available: Enhancements and resolved issues with update impact
As part of Pega's long-term security strategy, AI-assisted scanning has been implemented on a proactive basis. Pega strongly encourages all clients to stay current on the latest product versions, where security enhancements, patching, and hardening improvements are delivered.
Low-code Application Development
|
Ticket # |
Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| 711083-2 | Special Note | Cassandra version 5 has been set as the default in the local development environment. | System Administration |
Case Management
26.1 Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-D20018 |
1003564 | Improved security for Infinity Studio | Cross-site scripting protections have been updated for Infinity Studio. | Case Management |
| INC-B29899 | 953112 | "Enable Action Section" removed from available UI actions | The deprecated "Enable Action Section" function was incorrectly appearing in the action palette when adding actions to a control in the Traditional UI. This has been removed. | Case Management |
| INC-B32878 | 889594 | Assignment repair button functionality restored | After update, the "Repair this assignment" button was failing with the error "The flow this assignment corresponds to is no longer at this task". This was traced to additional conditional logic that was added to the FixBrokenAssignments activity which was not compatible with assignments which had validation messages on the last flow step. This has been resolved by modifying the conditional logic handling for the activity. | Case Management |
| INC-C10094 | 924852 | V1 upload API tracer compatibility restored | The V1 attachments upload API was failing when executed with tracer services events enabled, throwing property reference validation errors. Investigation showed the REST service was encountering property linking issues during trace execution. This has been resolved. | Case Management |
| INC-C13655 INC-C40010 |
952165 951536 |
Archived case search filtering corrected | Filter searches returned inconsistent results when applied to archived cases with decimal or datetime properties through report definitions. Investigation showed the indexing request was incorrectly sending property types as TEXT for archived cases instead of their actual data types (decimal, datetime), while regular cases had correct type mapping. This has been resolved by adding the property type of columns to the IndexArchivalDataModel class so the archived cases are filterable based on decimal and date. | Case Management |
| INC-C13699 | 957206 | FLAudit instance purge performance optimized | Field level audit instances could not be deleted due to SQL query timeouts (HY008 errors), causing purge operations to fail and instances to remain in Purge-Failure state. This has been resolved by optimizing the purge query logic to improve performance and prevent timeout failures when processing large FLAudit datasets. | Case Management |
| INC-C24316 | 931825 | Logic added to clear temporary files created by archive search | Logic added to clear temporary files created by archive search CSV files were being created in the temporary directory when archived cases were searched and opened, but these files were not being deleted after the case was closed. This was causing disk space exhaustion over time. This has been resolved by adding logic to clear the archival temp folder after opening the archived cases. |
Case Management |
| INC-C27150 | 942820 | File upload size tracking restored | File uploads using the pxFileUpload control failed to populate the pyFileSize property on the clipboard, preventing email file size validations against Pega and Gmail limits. Investigation showed this was caused by the prfUploaded.length() method returning zero after the pxUploadFile RUF invocation. This has been resolved by retrieving and storing the file size before the RUF call to ensure reliable pyFileSize population. | Case Management |
| INC-C29181 | 943821 | pyResolvedUserID property visible in list pages | The pyResolvedUserID property, defined in Work- class and exposed as a column at case type and work pool levels, could not be found or added to landing pages of type list page through the authoring interface. This was caused by the property not being properly exposed in the authoring records API endpoint, and has been resolved by modifying the pyResolvedUserID property table type to "Class key value" and adding validation class "Data-Admin-Operator-ID". | Case Management |
| INC-C31447 | 943422 | SLA context execution corrected | SLA escalation actions configured on split-foreach assignments executed in work page context instead of the expected pagelist context. Investigation showed the when rule always ran against pyWorkPage regardless of the split-foreach configuration. This has been resolved by ensuring SLA when rules execute in the proper pagelist context during split-foreach operations. | Case Management |
| INC-C33867 | 944924 | Corrected accessibility for notification gadget | Screen readers incorrectly announced navigation instructions for the notification gadget. This was caused by the dynamic layout role being configured as "ListBox" in the pyShowNotificationDefault section, which triggered arrow key navigation expectations. This has been resolved by removing role="listbox" from the dynamic layout of the pyShowNotificationDefault section. | Case Management |
| INC-C34187 | 947182 | CDLPEllipsis security updated | Cross-site scripting protections have been updated for text area properties using the pzCDLPEllipsis control. | Case Management |
| INC-C34810 | 948890 | Document details panel layout updated | Document details panels displayed distorted layouts when the "Available to" field contained lengthy titles or descriptions. This was caused by improper CSS styling in the pyDocumentVisibileTo section that did not account for text values over 64 characters, and has been resolved by adding the CSS text-ellipses in the pyDocumentVisibileTo section to indicate that the content is too lengthy to be fully displayed in the available "To" field. | Case Management |
| INC-C35762 | 951115 | Save button focus behavior corrected | Save buttons in TabbedScreenFlow case types caused focus to be lost and reset to the beginning of the form. This has been resolved by adding a check for event === 'string'. | Case Management |
| INC-C37564 | 953641 | Assignment skill validation implemented for Go button visibility | Assignment Go buttons were appearing in Constellation for users lacking required skills, only showing unauthorized access errors after clicking. This was a difference in behavior from previous versions, and was caused by the required skills not being loaded to the pxFlow page during assignment list formation. This has been resolved by ensuring required skills are properly copied to the pxFlow page and validated before displaying the Go button. | Case Management |
| INC-C38145 INC-C38268 |
954342 954004 |
Archived case accessibility and audit history restored following cloud migration | During cloud migration from Oracle to PostgreSQL databases, "Invalid clipboard stream detected" errors were generated when attempting to deserialize archived case data, preventing access to migrated archival files. This was caused by differences in how Oracle and PostgreSQL store BLOB data - PostgreSQL's BYTEA format included an extra 32 bytes compared to Oracle's 64-byte BLOB format, corrupting the stream header signature that Pega expected. This has been resolved by adding logic to detect hexadecimal strings and apply the appropriate database-specific BLOB processing logic. In addition, the audit history was missing due to a difference in the datetime format between the databases. This has been resolved by implementing logic to manage date conversion for various databases by deriving the database type based on the date format regular expressions carried from previous databases. | Case Management |
| INC-C38149 | 958656 | SMS attachment download functionality updated | SMS attachments were not downloading when accessed through the Constellation CS application. This was caused by the pzGetAttachment activity only checking for Email correspondence types while missing the necessary code to handle PhoneText correspondence, and has been resolved by extending the attachment handling logic to support SMS correspondence downloads in both the DX API and Constellation UI components. | Case Management |
| INC-C40245 | 950473 | Report property persistence fixed | Previously exposed properties in DataTableEditor reports were unexpectedly removed when adding new field properties. This was traced to improper handling of existing external mappings during field addition operations, and has been resolved by adding logic to not remove embedded references from report definition. | Case Management |
| INC-C40492 | 952549 | Embedded page attachment duplication eliminated | Multi-attachment fields configured within embedded page properties were creating duplicate empty attachment list pages alongside actual attachments. This has been resolved by updating pzApplyPageInstructions to prevent an empty page from being created when processing attachments within embedded page contexts. | Case Management |
| INC-C42045 | 959751 | DX API v1 validation processing corrected | DX API v1 services were failing with validation errors after upgrade. This was traced to modifications made to the handling of Declare OnChange triggers and changes in the pzApplyDataForPerformAction activity which applied mapInputJSON() logic designed for DX API v2 to v1 requests. This has been resolved. | Case Management |
| INC-C42220 INC-D2624 |
964842 976765 |
Case context passed to upload API | File uploads to external systems via REST API calls were missing the case context information needed for proper case tagging. This has been resolved by adding the necessary logic to pass ContextID in the Upload API to access the case context in pzSavetoRepository activities. | Case Management |
| INC-C43402 | 954416 | Case locking mechanism improved during creation process | When creating an interaction case through REST, a "lock not acquired" error was generated during case submission and proceeding to the next step. Investigation showed this was caused by a race condition in the locking mechanism during case initialization. This has been resolved by updating the svcAddWorkObject service to properly handle lock acquisition timing. | Case Management |
| INC-C43508 | 959091 | Case attachments widget report definition made available | Previously, the pzGetAttachmentsCountOfACase report definition was used to display the attachment count on the utility panel when collapsed. In order to support customization, this has been replaced with the available rule pyGetAttachmentsCountOfACase. | Case Management |
| INC-C43576 | 961265 | Child associations listed with parent associations in archive | After adding child case associations to the parent case settings, the association was not shown in the case settings even though the corresponding record was added to the d_archivalassociation table and the associated record was archived. This has been resolved by adding a pzListArchivalAssociation activity and updating D_pzListArchivalAssociation. | Case Management |
| INC-C44033 | 956772 | "Previous" button navigation behavior restored | After update, a behavior change was seen with the "Previous" local action. Originally, while sitting in the 1st assignment of the 2nd subflow in a flow with two back to back sub-flows, the "Previous" local action brought you back to the last step in the 1st subflow. After update, the "Previous" local action returned to the first assignment in the parent flow. This was caused by changes in the flow navigation logic that affected how the system determined the previous step in complex flow structures. This has been resolved by restoring the previous navigation behavior to match the expected flow traversal patterns. | Case Management |
| INC-C44509 | 957568 | Work object search correctly refreshes windows | When accessed through search functionality, work objects were opening in new windows instead of refreshing existing ones. This created multiple instances of the same work item. Investigation traced this to missing function definitions in the Navigation HTML fragment rule affecting the display_showImageErrors function, and this has been resolved by updating the navigation logic to properly detect and refresh existing work object windows rather than creating new instances. | Case Management |
| INC-C4509 | 948272 | Added handling for upload file parsing with special characters | File parsing during upload with the pzMultiFilePath control was failing if the file contained special characters. This was due to a mismatch in the file name which resulted in a "file not found" exception, and was caused by the pzMultiFilePath encoding the file name if it contained any special characters while the parsing function checked the file name without any encoding. To resolve this, the handling has been updated to ensure consistent encoding of file names during both upload and parsing processes. | Case Management |
| INC-C45742 | 962041 | PDF attachment accessibility retained after name changes | PDF attachments generated during case processing were becoming inaccessible after being renamed. This was caused by the pySaveFileContent activity creating new repository files without proper context when the pzSaveToRepository method was triggered during name update, and has been resolved by implementing logic to skip unnecessary repository calls during name changes while maintaining proper file context and accessibility. | Case Management |
| INC-C46167 | 969146 | Post value and refresh section functionality updated | Post Value actions were not reliably submitting /updating the intended values, and Refresh Section actions did not refresh the correct section or failed to reflect changes. This was traced to FlowActionHTML not using the correct page context for the local-case branch. Because the section/action was being rendered against an incorrect BASE_REF, UI actions like post value and refresh section did not resolve against the expected page. This has been corrected so those actions execute in the correct Primary context. | Case Management |
| INC-C46548 | 961847 | Wait shape error with duplicate stage names fixed | Parent-child case configurations were encountering Constellation errors displaying "An internal error occurred, Please contact administrator" when submitting parent cases. This was caused by wait shape configurations where child and parent stages had identical stage names and the parent next stage used a screen flow. This has been resolved by correcting the stage name conflict handling in wait shape processing. | Case Management |
| INC-C46918 | 961744 | Property max length display corrected | Properties were incorrectly displaying a maximum length value of 256 characters in the Advanced configuration section when no maximum length had been explicitly set. This has been resolved by correcting the Advanced configuration display to show empty values when no maximum length is configured, and documentation has been clarified to provide specific guidance on database column size limits rather than ambiguous references to multiple possible values. | Case Management |
| INC-C46937 INC-C49511 |
967415 967236 |
Multi-select dropdown values included in DX API responses | Multi-select dropdown controls were not returning complete option values when assignment views were being published to front-end mobile applications through DX APIs. Investigation showed this was caused by the API response only including key values while omitting additional field values configured in the data page source, preventing mobile applications from displaying proper dropdown options with both keys and descriptive values. This has been resolved by modifying the pzdxapifulljsonforvieworpage and pzdxapijsonformodes functions to provide additional option values in API responses. | Case Management |
| INC-C49224 | 960389 | File upload exception busy indicator handling updated | When file size validation messages appeared in modal dialogs, the screen was sometimes freezing with busy indicators remaining visible after clicking "OK" on size limit alerts. This was caused by the busy indicator not being properly dismissed, and has been resolved by adding a script to hide the busy indicator when the exception happens during file upload using pzMultiFilePath control. | Case Management |
| INC-C51780 | 961846 | Corrected DX API authorization handling for assignment urgency updates | DX API v1 calls were failing with 400 authorization errors when cases contained multiple open assignments including Wait (Case Dependency) assignments. This was traced to a missed use case of the pzSyncAssignmentUrgency declare trigger attempting to lock assignments without proper access privileges during urgency recalculation, and has been resolved by modifying the handling in the UpdateAssignmentUrgency activity to keep all assignment in sync with case urgency. | Case Management |
| INC-C52052 INC-D3152 |
963012 974832 |
Support added to include private pulse posts in email digest notifications | Private posts were not appearing in daily and weekly email digest notifications despite being properly created and mentioned recipients being configured for digest notifications. This was traced to the email digest report definition not including instance handle keys for private posts, causing them to be treated as deleted during digest processing. This has been resolved by creating a new report definition rule 'pzGetEmailDigestPvtNotifications' to fetch private notifications, and the 'pzRetrieveNotificationsData' activity has been updated to include those in the email digest.. | Case Management |
| INC-C52114 | 961727 | Document file removal behavior restored for reference deletion | After upgrade, document attachments were being permanently deleted from the repository instead of only removing the case association link. This was caused by modifications to the pzRemoveDocumentReference activity that were intended to avoid orphan records in the system without any association to a case, and has been addressed by restoring the original behavior to remove document associations while preserving the source documents. | Case Management |
| INC-C52257 | 965839 | Related case partial text search limited to 100 results | Related Cases widget searches in Constellation were hanging indefinitely when typing search characters in high-volume production environments. To address this, the auto-complete search for partial text in the Related Cases widget will be limited to 100 results. | Case Management |
| INC-C52381 | 965669 | API field validation error details restored | API responses were returning generic error messages instead of detailed field-level validation information when invalid data was submitted through the Case Creation API and other standard Pega APIs. Investigation showed this was caused by previous work that altered how validation errors were handled, and has been resolved by restoring the previous behavior of detailed field-level validation error responses that help with debugging and troubleshooting invalid API requests. | Case Management |
| INC-C52742 | 962297 | Documentation updated to address DX API case retrieval performance impact | Retrieving cases with pyWorkPage data sizes over 1.5MB through the DX API v1/cases/{id} endpoint can lead to performance degradation. To assist in avoiding this impact, the documentation for Traditional DX API -> Understanding the response page & Constellation DX API -> Understanding the response has been updated to recommend the use of Data References to avoid excessively large cases. | Case Management |
| INC-C54149 INC-D884 |
967141 972104 |
Field level auditing functionality restored for case creation | Field level auditing was not functioning properly during case creation, where the initial ADD operation for properties like pyStatusWork was not being captured in the audit trail. This was traced to previous work done to avoid duplicate field level auditing records which prevented the previousPage variable from being cleared properly during case creation, causing both previousPage and primaryPage to remain identical and blocking the audit capture mechanism. This has been resolved by updating the function in pxFieldlevelauditing to properly handle cases without create stage and ensuring the previousPage variable is correctly managed during the case creation process. | Case Management |
| INC-C54329 | 968462 | Child to parent case navigation corrected | Navigation from child cases to parent cases was automatically redirecting back to the child case after page loading completed. This occurred specifically when error dialogs were dismissed using the cancel button rather than the X button in edit details popups, and was caused by improper state management in the breadcrumb navigation logic following error dialog interactions. This has been resolved by adding "pega.desktop.infinity.clearCaseActionParams" to the cancel button action. | Case Management |
| INC-C54505 | 966456 | Database schema capacity expanded for instance identifiers | The system was rejecting or truncating longer instance identifier values during database operations, causing persistence failures when working with cases or rules exceeding the value capacity. This has been resolved by increasing the column sizes for pzInsKey from 512 to 900 characters and pxInsName from 255 to 768 characters in the pr_metadata table schema master. | Case Management |
| INC-C55523 INC-C56379 INC-C59726 |
969206 972908 969204 |
DSS added to support case archival process for SRS | After update, case archival processes were getting stuck at "index-failed" status. Investigation showed that data model changes had been implemented on the archival side to support date range search functionality, but these changes were not supported by the SRS (Search and Reporting Service) side, creating a compatibility mismatch that prevented successful archival operations. This has been resolved by implementing switching logic that allows toggling between old and new schema versions for the archival index data model, with the system defaulting to the old schema for archival indexing to maintain backward compatibility while providing the option to enable new schema features when SRS support becomes available. | Case Management |
| INC-C55752 | 971937 | Circumstanced flow action title display corrected | Flow actions using circumstanced variants were displaying incorrect titles from the base version instead of the appropriate circumstanced version, while the section content correctly loaded from the circumstanced rule. Investigation showed the title resolution logic was not properly following the same circumstance evaluation path as the section loading when flows are displayed in modal dialogs with default standard templates. This has been resolved by introducing a customizable 'when' rule to switch between doActivity and doAction APIs in the pzModalTitle control. | Case Management |
| INC-C56958 | 971441 | Embedded table data retention resolved | Deleted row data was being retained and incorrectly pre-populated when adding new entries to embedded tables and data grids within screenflows. Investigation showed this was caused by the Page-Validate method executing on a removed interest page, which created an empty page on the @baseclass instead of properly handling the deleted state. This has been resolved by adding a PageExistsWithClass check before executing the Page-Validate step in the pzFilterRefreshAPIFieldsInRequestBody activity, ensuring deleted row data is properly cleared from memory and new entries display with blank fields as expected. | Case Management |
| INC-C59657 | 978246 | Processing error screen flash resolved | A "processing error has occurred" screen was briefly appearing for 1-2 seconds when opening subsequent cases using the "Create Work" functionality with pega.desktop.infinity.createNewWorkInDialogContainer script, particularly in configurations with layout groups containing multiple dynamic layouts with deferred loading. This was caused by timing issues in the deferred loading mechanism for dynamic layout sections, and has been resolved. | Case Management |
| INC-D10624 | 984648 | Resolved field audit duplicate entries | Field level audit entries were displaying duplicate values for pyStatusWork and other properties, with UI controls appearing blank for these properties in user applications. This was caused by improper handling of field audit entries for properties without UI controls, and has been resolved by adding handling for empty conditions. | Case Management |
| INC-D12056 | 989162 | Archive policy duplication eliminated after migration | Applications migrated from Pega Platform 8 to Pega Infinity '25 were showing duplicate Archive Associated Classes entries in Archival Policy rules, with duplicates reappearing even after manual deletion. This was traced to redundant associations created by the migration script during the upgrade process, and has been corrected by updating the context handling for the pyClassName parameter. | Case Management |
| INC-D13958 | 994325 | Case note handling updated | Cross-site scripting protections have been updated for case notes. | Case Management |
| INC-D14282 | 996504 | Archived data display restored for migrated cases | Case Note and Activity data was not displaying for archived cases migrated from on-premises Pega 8.7 environments to PegaCloud, while locally archived cases displayed correctly. This was caused by compatibility issues with the database regex patterns for migrated archive data, and has been resolved by updating the MSSQL regex to properly handle migrated archive data formats. | Case Management |
| INC-D14606 | 987492 | Constellation form refresh pagelist synchronization improved | Inconsistent behavior was seen in Constellation when form refresh operations triggered data transforms that modified pagelist data during field change events, including stale rows persisting, deleted rows reappearing, or expected new rows failing to display after picklist selections. Investigation showed this was an issue in reconciling server-side pagelist mutations during form refresh operations, creating a disconnect between the server-side case state and the client-side view. This has been resolved by implementing enhanced page comparison logic and instruction formation capabilities that properly synchronize pagelist operations between server and client, including the addition of row identifiers for accurate change tracking and comprehensive page instruction generation for all refresh API endpoints. | Case Management |
| INC-D16719 | 989767 | Optimized Archival pipeline performance | Severe performance degradation was occurring in the archival pipeline (pzPerformArchiveUsingPipeline) where purge operations were limited to processing only one case every 15-50 seconds. This was due to inefficient DELETE queries on pc_FLAudit_ tables using LIKE conditions with leading wildcards on the pxHistoryReference column, forcing full table scans and generating PEGA0005 performance alerts. This has been resolved by updating the PurgeFLA query for Microsoft SQL Server to use more efficient query patterns that can utilize proper indexing, significantly improving archival throughput. | Case Management |
| INC-D17063 | 989077 | DX API preprocessing behavior made configurable | An intentional behavioral change in the DX API effective with Infinity '25 to execute pre-processing data transforms and activities during submission was creating issues with document processing in Angular page integrations where newly uploaded documents were being ignored due to repeated preprocessing. In order to improve backwards compatibility, this DX API behavior has now been made configurable by adding the DSS "DXAPIPreProcessOnce" to the pzApplyDataForPerformAction activity. Setting this to "true" will skip the preprocessing path. When the DSS is false, the system will follow the existing/default preprocessing path unless the request itself explicitly passes skipPreProcessing="true". | Case Management |
| INC-D17215 INC-D6574 INC-D7300 |
989539 984583 984218 |
Case archival indexing resolved | Case archival processes were failing during the Search and Reporting Service (SRS) indexing stage when attempting to archive cases containing null or empty date values in various date properties including Expecteddateofclosure, LatestWOUpdateDT, and DocumentationCompletionDate. ERR_INSTANCE_VALIDATION messages were seen with the sub-code ERR_MALFORMED_PROPERTY_VALUE, specifically reporting "failed to parse field [field_name] of type [date] in document with id 'XXX-XXX-XXX-XXX'. Preview of field's value: ". This has been resolved by adding logic to exclude properties with null or empty values from the indexing request. | Case Management |
| INC-D18151 | 993535 | Assignment page null pointer exception fixed | Assignment operations were intermittently failing with a NullPointerException in the OpenAndLockWork activity. Investigation showed the assignPage variable was unexpectedly null when the activity attempted to rename it, causing the "Cannot invoke rename(String) because assignPage is null" error. This has been resolved by updating the null checking and error handling in the assignment processing logic to prevent the null pointer exception. | Case Management |
| INC-D193 | 973360 | Pagelist UPDATE support added for embedded attachment properties | When working with attachment properties configured on an initial screen and transferring them to a page list property with Embed-Attach-File object class on a subsequent screen, an "Invalid page instruction" error message was generated when attempting to submit the second screen. Investigation showed this was caused by the system generating unsupported UPDATE instructions for page list properties with Embed-Attach-File object class. This has been resolved by modifying the pzapplypageinstructions activity to allow UPDATE page instructions in addition to DELETE and INSERT for page list properties that have a page definition as the embed-attach-file class. | Case Management |
| INC-D21011 | 996425 | User reference properties visibility restored in authoring | OOTB user reference properties like pxStatusStartOperator and pxStatusCompleteOperator were not appearing during List view authoring even after being marked as relevant. This has been resolved by updating the UI controls to pxDropdown or pxAutoComplete and creating proper association rules with Data-Admin-Operator-ID. | Case Management |
| INC-D2677 INC-D19353 |
980684 993804 |
External repository attachment cleanup improved | Attachments stored in external repositories were not being deleted during case archival when "Directly purge without copying to archival location" option was enabled, leaving orphaned files in external storage. This has been resolved by adding logic to delete attachments from external storage when cases are archived or purged with the direct purge option. | Case Management |
| INC-D2732 | 976444 | File attachment keyboard accessibility corrected | Attempting to attach files through the pyAttachContent control in overlays using keyboard navigation generated the error “There has been an issue, please consult your system administrator.” Mouse interactions worked correctly. This was caused by the pzMultiFilePath control lacking proper keyboard event handling when configured in an overlay, and has been corrected. | Case Management |
| INC-D3165 INC-D12319 INC-D14897 |
977070 986163 989166 |
Field level auditing inconsistencies resolved | Inconsistent results were seen for Field Level Auditing of temporary cases migrated from older versions and cases processed through parent-child relationships where FLA did not capture changes correctly for cases in their first assignment, causing expected audit entries to be missing. This has been resolved by refining previous work on duplicate FLA scenarios to include additional handling for temporary cases and cases with utility steps in create stage. The DSS "PreventDuplicateFLA" has been added to help prevent duplicate FLA records in edge cases while preserving prior behavior by default. | Case Management |
| INC-D3223 | 975039 | Drag and drop file size limit handling corrected | File uploads through drag and drop controls were incorrectly rejecting files when the pyMaxDragDropAttachSizeMB setting was configured to 2048MB or higher. This was caused by integer overflow in the byte conversion calculation within the pzMultiDragDropControlStandard control, and has been resolved by changing the variable data type from int to long to properly handle large file size limits. | Case Management |
| INC-D3317 INC-D17696 |
980219 989279 |
Previous button navigation functionality restored in case management workflows | Applications were experiencing infinite loading screens and NullPointerException errors when attempting to navigate backwards using the Previous button in multi-step case creation workflows, particularly in scenarios involving case spin-offs with reference field data copying. Investigation showed this was caused by a limitation in the handling of backward connections and inner loops in screen flows, and this has been resolved by adding an iterator to expand autopopulates in the pzJumpToStep method, ensuring proper backward navigation functionality is restored for case management workflows involving complex case reference patterns. | Case Management |
| INC-D3373 | 984094 | Attachment widget count refresh updated | PDF generation from eForm templates was not immediately updating attachment widget counters in Constellation applications. While PDFs were successfully generated and attached to cases, the attachment count continued displaying "0" until the widget was manually expanded. This was caused by the attachment widget not receiving proper refresh signals after eForm PDF generation, and has been resolved. | Case Management |
| INC-D3407 | 975497 | Pagination limit removed for App Studio subprocess selection | Applications with more than 50 flow rules were unable to access all available flows when configuring subprocesses in App Studio. This was due to a default pagination limit of 50 records in the pyGetCategoryItems report definition, and has been resolved by disabling paging so all flows are returned. | Case Management |
| INC-D4292 | 981914 | Database class definition exception resolved | UI Kit applications were generating EXCP0001-5409 BadClassDefinition errors in logs when dragging records from worklist widgets to team member widgets, though functionality remained intact. This was traced to missing or blank report-definition parameters in pyPopulateAssignedWork, and has been resolved by adding a check and handling for this scenario. | Case Management |
| INC-D4775 | 981241 | Pipeline archival functionality restored for direct purge configurations | After update, pipeline archival was failing when the direct purge option was configured without copying data. This was traced to an issue with the SQL query generation for audit table purges and , and has been resolved by updating the archival logic to properly handle SQL query generation for audit table purges along with adding defensive null checks to file name processing in attachment status updates to prevent failures during attachment processing. | Case Management |
| INC-D4916 INC-D6170 |
976152 981372 |
ase archival process corrected to prevent unintended data deletion | Systems were experiencing complete deletion of audit data tables when attempting to archive individual cases, including removal of audit records for unresolved cases that should have been preserved. Investigation showed this was caused by previous work on the field level audit (FLA) purge query logic. This has been resolved by updating the FLA purge query to target only the intended records. | Case Management |
| INC-D6004 | 982229 | Custom repository metadata context provided | Document uploads to custom repositories lacked necessary metadata context. This was caused by the upload API having no access to case or row contextand has been addressed by providing extension points with proper metadata access. | Case Management |
| INC-D6203 | 977484 | Question import in branches enabled | Question import functionality was failing with "Please correct flagged fields before submitting the form!" alerts when attempting to import questions in development branches without unlocked rulesets. This was traced to the "Run visibility condition on client" checkbox being checked on the pyRulesetVersion dropdown in the pzSurveyRecordContext section rule, and has been resolved by unchecking the box. | Case Management |
| INC-D7602 | 994067 | Ajax container tab behavior stabilized | Ajax container tabs in the pyCaseManager portal were exhibiting inconsistent behavior including tabs reappearing after closure, incorrect tab names displaying after browser reload, and SafeURL null pointer exceptions when closing tabs, particularly after upgrading from deprecated tab group layouts. This was caused by improper state management in the Ajax container implementation and race conditions in the tab lifecycle events, and has been resolved by updating the tab state management. | Case Management |
| INC-D7684 | 982565 | Added handling for resolved cases SLA processing race condition | Queue processor pyProcessSLA was accumulating broken items with "Unable to open an instance using the given inputs: ASSIGN-INTERNAL" errors for resolved cases where assignments no longer existed. Investigation showed this was caused by SLA processing attempting to access assignments that were removed during rapid case resolution cycles, and was due to cases/assignments being created and resolved without allowing enough time to process the SLA item. This has been resolved with an update to ensure the SLA queue processor item will not move to the broken queue if the corresponding assignment is not present, along with improved cleanup of queue items for resolved cases. | Case Management |
| INC-D7960 | 984263 | MaxFileSize added to file attachment handling | The file attachment functionality was missing the necessary configuration to set maximum file size limits for attachments. This has been corrected by adding the pymaxFileSize property to the Data-WorkAttach-File class to enable proper file size limit configuration and validation. | Case Management |
| INC-D7969 | 983490 | File upload replacement functionality restored | After update, multiple file uploads were not properly replacing previously attached files when using the standard configure user action attachment field. This was a missed use case for the pyGetAttachmentFieldInfo activity sorting the assignments in create date time ascending order, and has been resolved by restoring the expected file replacement functionality for attachment fields. | Case Management |
| INC-D8283 | 990484 | Remote case API authentication fixed | External automation tools were unable to create remote cases via the DX API, receiving "AAT cookie not found in the request" errors when providing the required remotesystemid header. Investigation showed the remote gateway validation required an AAT cookie even for API requests with proper authorization headers, and this has been resolved by updating the logic to read tokens from authorization headers when Pega-AAT cookies are not present and skipping CSRF validation checks for header-based authentication. | Case Management |
| INC-D8745 | 986207 | Bulk assignment transfer context handling updated | Bulk transfer of cases to worklists or workbaskets was not functioning when using the pxTransferAssignment activity in flow action post-processing. This was traced to an issue in the reassignment logic which could resolve the wrong work object page name during execution. This has been addressed by updating the Work- Reassign activity so it derives the work object name from the current step page instead of relying on the previous fallback expression so each assignment is processed in the right context. | Case Management |
| INC-D9141 | 992865 | Parent case lock release mechanism fixed | Parent case locks were not being properly released when child case assignments were canceled in Constellation applications with default locking configuration. This was occurring when child cases skipped the create stage and had "not lock parent case" option unchecked. This was caused by the pxLockHandle not being properly populated for parent case lock management, and has been resolved. | Case Management |
| INC-D9409 | 979600 | Case flow cleanup improved | Flow accumulation issues were seen when closing cases from within subflows using custom close activities followed by pxForceCaseClose. Embedded subflow instances were remaining present in pyWorkPage.pxFlow(), and upon reopening the same case multiple times, new flow instances were being appended while previous subflow instances were retained, eventually causing system errors when the pxMaxFlowAddCount safeguard was exceeded. This was caused by pxForceCaseClose not properly removing embedded pxFlow pages from cases during closure, and has been resolved by ensuring pxForceCaseClose properly cleans up all embedded flow instances when cases are closed. | Case Management |
Cloud Services
26.1 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B23561 |
950135 | Revalidate and Save updated for special/non-ASCII characters | Revalidate and Save operations were failing for rules containing special characters (ä, ö, ü) even when the system was configured to allow such characters. This was traced to a UTF-8 encoding mismatch bug in bulk update save/revalidate flows when IDs contained special/non-ASCII characters, and has been resolved with an update to ensure IDs are consistently encoded with encodeURIComponent() (UTF-8-safe). | Cloud Services |
| INC-B35793 | 951474 | File validation bypass for executable uploads prevented | Executable files were being stored in the serviceexport directory despite validation errors, with subsequent uploads showing "file already exists" messages. Investigation showed the import wizard was storing files before completing validation checks. This has been resolved by implementing proper validation sequencing to prevent file storage when validation fails. | Cloud Services |
| INC-B42656 INC-B31292 INC-C23421 INC-B30497 INC-C41068 INC-B40109 INC-B49213 |
953843 | Hotfix system scan file validation message updated | Hotfix system scans using Hotfix DL files were displaying incorrect error messages stating that files should be named CATALOG.ZIP, even though the scans completed successfully. Investigation showed that the file validation logic was checking for specific naming conventions while still processing the files correctly. To address this, the validation messaging has been updated to indicate that the catalog upload failed, but the process can continue with the scan using the existing catalog on the system if desired. | Cloud Services |
| INC-C27553 | 945955 | External database export table resolution fixed | When attempting to export applications containing data classes mapped to external databases, exceptions were generated indicating "ERROR: relation does not exist". Investigation showed this was caused by the export process failing to properly handle data classes residing in external databases separate from the main database schema, and has been resolved with an update to ensure the correct database is used for associated data collection when class mapped to an external database. | Cloud Services |
| INC-C37844 | 954082 | Column population data integrity preserved | Declare expressions executed unexpectedly during column population processes, potentially modifying instance data and compromising data integrity. This was caused by auto-chaining being enabled during property reads in the column population process, and has been resolved by disabling autochaining when reading properties from the blob during column population. | Cloud Services |
| INC-C37845 | 951489 | Database schema column display corrected | The column names displayed by the database schema modification wizard did not match the actual database column syntax and formatting. This was caused by improper column metadata retrieval and display formatting in the DBSchema_ListColumnsInTable HTML rule, and has been resolved by suppressing the Rule-HTML-Property formatting at render time. | Cloud Services |
| INC-C40496 | 951911 | Hotfix utility parameter handling corrected | The prpcUtils hotfix management utility was failing with invalid parameter errors when the hotfix.accessgroup property was configured. This was caused by incorrect parameter order validation in the utility that checked the access group value instead of the operation value, and has been resolved. | Cloud Services |
| INC-C47107 INC-C56898 |
963195 966054 |
Push notification service compatibility resolved | After upgrade, push notification execution was failing with the Publish-Notifications activity throwing PushServiceException errors and the pzIsPushServiceEnabled rule returning false, indicating the push engine had failed to start. Investigation showed this was caused by a Java version compatibility issue where the atmosphere-runtime JAR expected properties files to be located in different paths between Java versions - in the main directory for older Java versions but in the resources classpath for Java 17. This has been resolved by updating the atmosphere-runtime-3.0.13.jar file to relocate the properties file from the main path to the resources path, ensuring proper compatibility with Java 17 environments. | Cloud Services |
| INC-C48174 | 965389 | Updated handling for portal/thread context in URL mapping scenarios | Applications were experiencing failures where publish notifications were not reaching screens when using URL mapping functionality. This was traced to issues in the notification delivery mechanism for URL-mapped scenarios, and has been resolved by updating the logic in the Data-Portal.ShowSpaceHarness activity to better handle MTSP (multi-portal session) behavior and maintain the portal/thread context when an auto-generated thread (isAutoThread) is involved. | Cloud Services |
| INC-C56616 | 979503 | EdgeServer file extraction download handling improved | The Extract EdgeServer Files feature for deploying static content to AWS CloudFront was failing with duplicate rule errors, specifically encountering failures at RULE-FILE-TEXT STYLE PALSTYLESHEET CSS rules during extraction. This was an issue with logic for downloading the files after running the ExtractEdgeServer process, and has been resolved. | Cloud Services |
| INC-C57002 | 969354 | Requester pool size defaults to 1 for upgrade | Platform upgrades were experiencing blocking sessions during "Optimize Newly Exposed Columns" and "Generate Declarative Indexes" tasks. Investigation showed multiple concurrent threads were creating database contention between select and insert operations on rule tables due to the default thread pool size of 4 being used when the NumOfThreads property was not explicitly configured during expose operations. This has been resolved by setting the request pool size default to 1 for this scenario. | Cloud Services |
| INC-D12938 | 984689 | DDL generation script performance improved | The generateddl.sh script was requiring existing database schemas and taking an excessive amount of time to generate DDL for new installations. This was traced to the system performing excessive database queries, and has been resolved by updating the prdeploy version to one which eliminates that inefficiency. | Cloud Services |
| INC-D1366 | 972349 | Revalidate and save memo recording restored | Memos entered during Revalidate and Save operations were not appearing in the rule history. This was caused by the revalidation process not properly capturing and storing the memo text during rule processing, and has been corrected. | Cloud Services |
| INC-D14909 | 984779 | Oracle DDL upgrade handling updated | Database updates were failing with Oracle error ORA-30556 when attempting to modify the PYFOLDERNAME column in pr_log_service_email table. Investigation showed this was caused by functional or bitmap join indexes being defined on the column being modified, which is not supported by Oracle. This has been resolved by implementing the proper handling for indexes with descending columns during DDL generation. | Cloud Services |
| INC-D17999 | 992677 | Operator validation error persistence resolved | Operator ID records with custom property validation were experiencing persistent validation errors where subsequent save attempts continued to fail with "page is not valid" messages even after correcting the property values that initially caused validation failures. This was traced to validation errors not being properly cleared from the page history data after successful property corrections, and has been resolved by updating the operator save process to properly clear validation error history when property values are corrected and validation passes. | Cloud Services |
| INC-D4207 | 975189 | Handling added for post-migration Message rules visibility | Message rules were becoming invisible and unusable following platform update from Pega version 7 to Pega Infinity 24.1. Investigation showed this was caused by the loss of pxobjclass data during the migration process from pr4_rule to pr4_rule_message tables. This has been resolved with an update to ensure the pxobjclass data is preserved during the migration process for improved backwards compatibility. | Cloud Services |
| INC-D963 | 971772 | Upgrade performance improved for large Data-Content-Image environments | The in-place update process was taking an excessive amount of time to complete. Investigation showed this was caused by a query SELECT pzInsKey related to WHERE pxObjClass = 'Data-Content-Image' which returned the entire table content and consumed excessive processing time. This has been resolved by optimizing the upgrade process to handle environments with large numbers of Data-Content-Image instances more efficiently. | Cloud Services |
Conversational Channels
26.1 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C25989 | 942382 | Table column visibility restored in UIKIT | Optimized tables with show/hide field options were not displaying column values in UIKIT applications. Investigation showed CSS rules were incorrectly hiding column content in the personalization overlay. This has been resolved by updating the pypega-email-portal-styles CSS file to avoid targeting Customer Service (CS) grids. | Conversational Channels |
| INC-C31751 | 949752 | External email template integration added | In order to support enterprise clients with extensive template libraries, the Email AI composer has been extended to support integration with external template systems through new activity and data transform rules: pxGetEmailSuggestedReplyTemplates (Activity, Code-Pega-List, Pega-ProcessEngine) pyGetEmailSuggestedReplyTemplates_Ext (Data Transform, Code-Pega-List, Pega-ProcessEngine) |
Conversational Channels |
| INC-C33423 | 943765 | Email recipient display name corrected | When replying to or forwarding emails using MS Graph email accounts, the recipient name was being incorrectly updated to the operator ID instead of the actual email address. This was caused by the pxGetDisplayNameForEmailAddress activity not properly handling MS Graph account types where pyEmailAddress differs from the actual email address. This has been resolved by updating the email address resolution logic to properly handle MS Graph account configurations. | Conversational Channels |
| INC-C34859 | 947929 | Corrected email content display in cases | Incoming emails from Pega-based client systems appeared empty in case email panes despite containing content. This was caused by the pyGetHtmlMessage activity incorrectly removing email content enclosed in div tags with "pega-email-message-reply" IDs, treating legitimate content as previous conversation threads. This has been resolved by updating the email parsing logic to preserve original message content while properly handling conversation threading. | Conversational Channels |
| INC-C43147 | 955395 | Email draft attachments preserved correctly | Email draft attachments were being incorrectly retrieved when reopening cases, with attachments sometimes replaced or duplicated when multiple files were added to reply drafts. This was traced to pxSaveAttachmentstoDraft not updating the linkAttachment page with .pxAttachName property, and has been resolved. | Conversational Channels |
| INC-C45663 | 966555 | Migration guide provided for Digital Messaging Services | Documentation is now available for Pega Platform and Pega Customer Service applications with comprehensive guidance for successfully deploying Digital Messaging channels to higher environments. | Conversational Channels |
| INC-C45795 | 960027 | Email case timestamp made consistent | Email triage cases were displaying different create datetime values when accessed through class instances versus DISP case related views. This has been resolved by updating the the email manager portal display logic to standardize the timezone processing across all case access methods to ensure consistent timestamp display. | Conversational Channels |
| INC-C51533 | 975768 | Chat attachment and transcript delivery issues fixed | Customers were unable to download chat transcripts despite seeing "Transcript Requested" status, and agents could not deliver image attachments to customers when filenames contained hyphens in date formats like "screenshot 2025-12-19 2013". This has been addressed by updating the attachment processing logic to remove the unsupported character (the dash -) from the allowed set, to prevent creating invalid/unsupported keys that break delivery when encryption is applied. | Conversational Channels |
| INC-C51565 | 973505 | Entity mapping validation updated for assignment submissions | Assignment submissions were failing with "Invalid Request Data" errors when entities detected in channels were mapped to non-existent properties on the assignment UI. This was caused by the system attempting to submit unrelated data through the changeTracker when entity mappings referenced properties not available in the assignment context. To resolve this, the validation handling has been updated to ensure entity mappings only reference valid assignment properties before submission. | Conversational Channels |
| INC-C53198 | 973248 | Email bot triage lock management stabilized | Email bot triage was losing lock when clicking "All Case Types" in the pyTriageActionsPortal_Cases section, resulting in attachments not being transferred to newly created cases during manual triage. This has been resolved by correcting the lock management. | Conversational Channels |
| INC-C58483 | 977326 | Email thread timestamp handling updated for timezone differences | Email interaction threads were displaying incorrect timestamps with future dates and wrong day calculations, particularly affecting AEDT timezone (+11) environments where replies showed inconsistent timing. This has been resolved with an update to ensure the timestamp for 'email send' time is sent to client side based on user's timezone. | Conversational Channels |
| INC-D14219 | 985487 | Email case lock handling corrected for inflight cases | Lock errors were occurring for inflight email cases with inline images after upgrade, particularly affecting service level agent queues after wait shape continuation. Investigation showed this was caused by premature lock release during the pxLinkAttachmentToCase commit process in pzUpgradeOldInlineImages activity. This has been resolved by removing the commit parameter when calling pxLinkAttachmentToCase to maintain proper lock handling. | Conversational Channels |
| INC-D14690 | 989133 | GenAI attachment handling updated | After update, PDC alerts were generated for GenAI rule execution timeouts during case creation. This was caused by pySetAttachmentFiledsWrapper being invoked from pxCreateCase without checking if the GenAI toggle was enabled, causing unnecessary GenAI connect rule calls for attachment classification. This has been resolved by preventing the call of pySetAttachmentFiledsWrapper as it is no longer required due to attachment mapping now being performed using GenAI Agent. The attachment-linking activity and related logic has also been updated to use ServiceCaseForEmail.pzInsKey instead of ServiceCase.pzInsKey. | Conversational Channels |
| INC-D14757 | 993502 | Case creation lock management improved | After update, the pxCreateCase activity was generating lock gone exceptions at step 12. This has been resolved by updating the handling in the pxCreateCase activity to properly acquire and maintain locks throughout the entire case creation workflow. | Conversational Channels |
| INC-D15916 | 994064 | Error handling updated for email reply with inline images | After update, email replies to inflight cases containing inline images were failing to send. Investigation showed that when sending an email containing inline images, any failure during image processing (e.g. malformed base64, missing data-content reference, bad CID) would throw an unhandled exception in the `pzUploadRTEImageFromBase64Url` activity, causing the entire send operation to abort. This has been resolved by updating the error handling to make the send operation more robust. | Conversational Channels |
| INC-D16867 | 989614 | Email attachment filename property corrected | Email reply functionality was failing. This was due to missing pyFileName property references in Data-WorkAttach-File instances, causing attachment processing errors in the pzSendEmailReplyAPI activity. This has been resolved by updating the activity to use pxAttachName when populating the attachments page. | Conversational Channels |
| INC-D21058 | 993783 | Email triage reserved word handling corrected | Email triage processing was breaking when the word "Call" appeared in email subjects, causing the system to incorrectly interpret it as a rule invocation and throwing RuleNotFoundException errors like "Failed to find a RULE-DECLARE-DECISIONTABLE with the name FOR APRIL STATEMENT". This was caused by the pyGetTextToAnalyzeForEmail decision table treating "Call" as a reserved word and attempting to execute whatever text followed as a rule. This has been resolved by updating the logic to properly handle reserved words and prevent unintended rule execution attempts. | Conversational Channels |
| INC-D4559 | 985007 | Email body cross-contamination fixed | Outbound emails were being sent with incorrect email body content from different cases while maintaining correct recipients and subject lines. This was caused by conversation history being rebuilt from processed values rather than the original intended message in some reply/auto-reply flows, and has been resolved by updating the email body mapping logic to ensure proper case-to-email content association. | Conversational Channels |
| INC-D7576 | 981026 | Eliminated attachment audit trail duplication | Inbound email interactions containing attachments were generating duplicate audit trail entries. Investigation showed the pyPreProcessTriageWork activity was creating multiple audit notes when processing attachments through the pxLinkAttachmentToCase loop. This has been resolved by adding parameters to clear audit notes and prevent duplicate entries during attachment processing. | Conversational Channels |
| INC-D7776 | 977173 | Advanced URL override configuration enhanced for digital messaging channels | Organizations using Digital Messaging Service (DMS) with OAuth integration were experiencing difficulties navigating to application settings for URL overrides, and encountered issues with attachment names containing hyphens. To address this, an “advanced URL override” path has been added for Bot Agent integrations, allowing key endpoints (API endpoint, Integration Manager URL, Management API URL, webhook/auth notification URLs) to be sourced from Application Settings when the dedicated When rule "pyOverrideUrlsAdvanced" evaluates to true. This allows multiple Bot Agent activities to prefer parameter/app-setting driven URLs with fallback to existing override fields. | Conversational Channels |
Data Integration
26.1 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B1370 INC-B33414 INC-B52548 INC-C11118 INC-C32125 INC-C521 INC-C52115 INC-C54738 INC-C57452 INC-C8548 |
968833 | Application context and alert routing corrected | DX API calls were incorrectly routing PDC alerts to default access groups regardless of the actual application context, and Application.pyProductName properties were appearing empty after Cloud 2 to Cloud 3 migrations. Investigation showed that stateless REST services were no longer automatically loading Application context. This has been resolved by implementing automatic Application context loading for stateless REST services and ensuring PDC alerts are properly routed to the correct application context based on the API endpoint being accessed. | Data Integration |
| INC-259502 INC-B14827 INC-B32387 INC-C34516 |
946182 | Error handling improved for platform upgrade conclusion cache building | Platform updates could fail during class conclusion cache build due to ConclusionCachePreBuilder treating repeated ClassInfoConclusion initialization failures like generic build failures, triggering stop-building behavior. To address this, ClassInfoConclusion init failures are now treated with targeted handling, and those specific failures are captured and reported in a consolidated error. Non-ClassInfoConclusion failures still follow the original stop-building path. | Data Integration |
| INC-B27282 | 953311 | Corrected EForm rule saving in locked ruleset version | Creating an EForm rule in a branch resulted in the binary file being saved in the locked ruleset version instead of the branch. This has been corrected. | Data Integration |
| INC-B48689 | 959302 | Table instance deployment synchronization handling updated | Changes to properties such as adding new properties, adding new database columns mapped to existing properties, or exposing properties through property optimization were not being recognized on all nodes after deployment, causing only the importing node to have access to the updated information. This has been resolved by implementing forced mapping which will fetch the necessary information from the database and build the property mapping when a property change pulse or a DADT re-save method call is received. This information is built once and will be used in subsequent calls until there is a pod restart, DADT resave, class resave, or a new property change pulse not received. | Data Integration |
| INC-C10777 | 955985 | Logging enhanced for large email attachment issues | Outbound emails with attachments of 25MB or larger were failing to send through the pxReply activity. To assist with diagnosing these issues, error logging has been added for chunk upload failures. | Data Integration |
| INC-C17885 | 948943 | Eform generation updated for more robust font support | After update, the EForm function stopped working with domestic fonts. This was traced to limitations for embeddedFonts and UTF-8 based fonts in the pdfbox tool for EForm solutions, and has been resolved by adjusting the EForms API parameters. | Data Integration |
| INC-C19409 | 947577 | Configuration table validation messaging improved | Users were seeing duplicate error messages when working with configuration table primary keys, including both ".RecordsCode: Records Code cannot be blank" and ".pyRefToFocusKey: Records Code cannot be blank" appearing after the first validation attempt. This was traced to improper error message state management during field validation cycles, and has been resolved by updating the ValidateKeysContent activity. | Data Integration |
| INC-C21278 INC-D4788 |
943094 977272 |
Support added for .us endpoints for MSGraph | Microsoft Graph endpoints were hardcoded to use .com domains, preventing some systems from using required .us domains for Office 365 authentication. This has been resolved by adding support for configurable domain endpoints including .us domains for Office 365 deployments. | Data Integration |
| INC-C21857 | 948726 | Query runner export functionality restored | After update, the export functionality from the Query Runner history tab was not working properly. This was traced to an error in the parameter handling for the Microsoft Excel export, and has been resolved. | Data Integration |
| INC-C22184 | 930392 | Search landing page access control added | The Search Result Services (SRS) search landing page lacked privilege restrictions that were present in the embedded ElasticSearch version, allowing unrestricted operator access to re-indexing functionality. This has been addressed by updating the pzExtSearchLP class from Pega-Landing-System-Search to Pega-Landing along with creating the new wrapper section pzExtSearchLPWrapper which includes the existing pxAccessSearchLP privilege and warning text if the suitable privilege is not found. | Data Integration |
| INC-C24487 | 951880 | Diagnostic logging added for loggingEnabledClasses | Diagnostic loggers have been added to capture declarative index records for loggingEnabledClasses to assist with diagnosing issues related to duplicate entries being created in the pr_index. | Data Integration |
| INC-C25456 | 960937 | Property decryption enabled for association data | Encrypted properties were displaying in their encrypted form rather than being automatically decrypted when retrieved through report definitions using associations in Constellation interfaces. This was traced to the system not recognizing encrypted properties when accessed through this method, and has been resolved by adding the necessary decryption logic to support this use in the data_views API. | Data Integration |
| INC-C26129 INC-C58427 INC-C29220 INC-C33113 INC-C57821 INC-C34718 INC-C32103 INC-C17885 INC-C25880 INC-C32238 INC-C31541 INC-C56940 |
943190 | Field flattening enabled for GenerateEForm | PDF forms were experiencing issues where filled fields would disappear when opened in Adobe Reader. Investigation showed this was caused by the lack of field flattening in the GenerateEForm activity due to change in the dependency JAR from iText to PDFBox, and has been resolved by implementing functionality similar to the existing ConcatenateEForms activity, ensuring PDF fields remain properly populated and non-editable when viewed in external applications. | Data Integration |
| INC-C26290 | 945726 | Rule creation XML display issue resolved | Rule creation XML display issue resolved When attempting to create rules in certain locked ruleset scenarios, XML content was being displayed instead of the proper rule creation interface. This has been resolved by adding an Activity-Clear-Status step in the 'pzUpdateDataTypes' activity. |
Data Integration |
| INC-C26301 INC-C30575 |
944299 946529 |
JSON mapping corrected for nested pagelist structures | JSON Data Transform functionality failed to properly map nested pagelist structures, causing only the first pagelist to appear in the generated JSON output while subsequent pagelists remained empty or were skipped entirely. Investigation showed this occurred specifically when using the Append and Map feature to construct JSON structures with nested elements like page.page.pagelist configurations and was caused by a loss of context. This has been resolved. | Data Integration |
| INC-C27043 | 942887 | Heap dump DSS added for including unreachable objects | Memory alert heap dumps captured only live objects due to the Boolean parameter hardcoded to "true" in the dumpHeap invocation, preventing comprehensive root cause analysis of memory issues. This has been resolved by making the live parameter configurable by way of the prconfig setting "alerts/memory/onalert/excludeUnreachableObjects" to control the inclusion or exclusion of unreachable objects in heap dumps to allow full heap dumps when needed for analysis. | Data Integration |
| INC-C28380 | 955827 | Stack overflow tracing enhanced to assist with case loading issues | After updating to Cloud, cases were failing to load when accessed from the portal and pyWorkPage remained blank. This was traced to the pxCallObjOpen activity during D_CaseLookup operations, and the logs indicated "Error loading D_CaseLookup using activity {pxObjClass=Rule-Obj-Activity, pyClassName=BNS-FW-SCOBFW-Work, pyActivityName=pxCallObjOpen}". In order to assist with diagnosing this issue, detailed logging has been added to identify which property is causing the circular reference that leads to a StackOverflowError. | Data Integration |
| INC-C29786 | 951016 | DSS added to control RDA automation response mapping | JSON responses from RDA (Robotic Desktop Automation) were not being automatically mapped to the platform when automation status was not completed, causing integration failures. This was was a recent behavior change and has been resolved by introducing the ENABLEAUTOMATIONRESPONSEAUTOMAP DASS setting that allows modified fields to be copied from runtime responses even when automation completes with errors. | Data Integration |
| INC-C30214 | 945089 | Updated header handling for forwarded messages with attachments | Tracking codes were not being decoded properly for forwarded emails, causing new email triage cases to be created instead of appending to existing email threads. This has been resolved by updating content type handling during attachment processing. | Data Integration |
| INC-C31315 | 950532 | Data table search functionality updated to skip encrypted properties | Search functionality in data tables was failing when any property column had encryption enabled, affecting both elastic search and normal search scenarios across all columns. This has been resolved by modifying the filter logic to skip to skip the properties that are encrypted from the filters that are formed in pzFilterDataTableRecords data transform when forming search filters, allowing search to work on non-encrypted columns. | Data Integration |
| INC-C31368 | 946513 | Data class deletion prevented | Data classes were unexpectedly deleted when attempting to add the same class to Data Type Explorer twice through different methods. This was traced to the attempts triggering incorrect deletion logic, and has been resolved by updating pzAddDataType to prevent this issue. | Data Integration |
| INC-C32399 | 950079 | mAbortTimeout timeout handling updated | The mAbortTimeout value was not being picked up correctly by the HttpClient. This was caused by the use of the static keyword. Since static variables are shared across all instances, the mAbortTime outvalue was being overwritten when multiple HttpClient instances were in use. As a result, while one HttpClient was executing, another HttpClient could modify the timeout, leading to incorrect values being applied and ultimately causing request failures. This has been resolved by removing the static keyword. | Data Integration |
| INC-C33044 | 952774 | Service requestor initialization stabilized | Production system became completely non-responsive with severe latency and white screens during pod scaling operations. Investigation showed a null pointer exception occurred when access group values were null during service requestor initialization. This has been resolved by adding null value validation in the GlobalContextCache to prevent null pointer exceptions during service requestor setup. | Data Integration |
| INC-C34085 | 964631 | Application page initialization fixed for prediction notifications | Email notifications were not being triggered in Prediction Studio. Investigation showed this was caused by the application page not being initialized when attachment logic was invoked via batch requestor and queue activity, and has been resolved by initializing the application page to prevent null pointer exceptions. | Data Integration |
| INC-C34793 | 956662 | Server path sanitization updated | In some circumstances it was possible for the system to disclose the server path in a file upload failure error message. This has been resolved by sanitizing error messages and exceptions to display only file names instead of complete server paths. | Data Integration |
| INC-C34795 | 958630 | Invalid property persistence resolved | Cases were being created with an invalid pyReportDefinition property persisted on case instances, causing DX API validation failures. Investigation showed this was caused by the pxConvertResultsToCSV activity incorrectly creating classless properties under pyWorkPage when generating CSV downloads through UI links. This has been resolved. | Data Integration |
| INC-C34868 | 946518 | Improved ConvertResultsToCSV backwards compatibility | The pxConvertResultsToCSV activity was automatically appending dots to property names that already contained them, causing property retrieval failures. This was has been resolved by implementing conditional logic to check if property names already start with dots before appending them, ensuring backward compatibility. | Data Integration |
| INC-C35034 INC-C12148 |
947673 952880 |
Updated validation and null handling for MS Graph email integration | Email case creation failures were seen in the Microsoft Graph email integration, including emails failing to be processed and email attachments indicating "unknown attachment type". This was traced to null values in email address fields in the MSGraphRESTMessageConverter class, and has been resolved by updating the validation in the MSGraphRESTMessageConverter.getInternetAdresses() method before attempting to parse email addresses. The system has also been made more robust around handling null or malformed email address data to allow email processing to continue even when encountering problematic address fields. | Data Integration |
| INC-C35037 | 950573 | Data page security updated | Cross-site scripting protections have been updated for data page modal headers. | Data Integration |
| INC-C35583 | 956587 | Data view API behavior corrected for empty values | After update, custom components were failing to render when clicking Professional IDs from search results. Investigation showed the DX API endpoint /api/application/v2/data_views/{data_view_ID} response data transform behavior had changed, where the Default Automap Empty Behavior switched from Default value to Null, causing empty strings and arrays to be replaced with null values that were not expected by the custom components. This has been resolved by restoring the data view API Default Automap Empty Behavior to return default values instead of null for empty data. | Data Integration |
| INC-C36173 | 946384 | JMS listener GRS configuration enabled | JMS Listener instances could not be created when using Global Resource Settings (GRS) for connection factory and request queue configuration with data pages. This has been resolved by creating a new executable instance from PRThread if an active executable is not there. | Data Integration |
| INC-C36206 | 951130 | Null check added to MSGraphEmailClient message validation | Email processing failed with misleading null pointer exceptions instead of showing the actual underlying errors. This was caused by missing null checks in the MSGraphEmailClient message validation method, and has been resolved. | Data Integration |
| INC-C36555 | 950927 | Object opening stability improved | Object opening operations failed with null pointer exceptions when using handles with locking enabled. This has been resolved by adding null checks for aLockInfo. | Data Integration |
| INC-C36999 | 962612 | Rule sync pulse thread termination handling improved | Rule synchronization was failing due to pulse thread termination during handleTerminateRequestorRequest method execution, causing cache inconsistencies in distributed environments. Investigation showed this was caused by inadequate exception handling during requestor termination processes, and it has been addressed by adding a catch block to the handleTerminateRequestorRequest() method within NodeRequestorMgt to improve exception handling. This enhancement provides deeper insights into any errors that occur during requestor termination, facilitating easier debugging and more robust error tracking. | Data Integration |
| INC-C37078 | 949880 | File listener record processing restart corrected | File listeners skipped records during retry operations after transient errors. This was caused by not resetting one-time run segments during error recovery, and has been resolved. | Data Integration |
| INC-C37745 INC-C47734 INC-D7713 INC-D1333 INC-C55227 INC-C57952 INC-D13317 INC-D29548 INC-D31781 |
951075 959376 |
Engine class preloading enhanced for improved pod startup performance | Applications were experiencing increased response latency during inbound decisioning when new pods were being spun up, particularly under autoscaling conditions in CDH environments. This has been addressed by implementing an enhancement that preloads engine classes to prime new pods, with additional improvements to ensure the job scheduler runs on all tiers rather than specific ones, minimizing cold start delays and improving responsiveness for real-time inbound decisions. | Data Integration |
| INC-C37758 | 951766 | PropertyDataPageWrapper log message refactored | The Autopopulate loggers have been updated to create the necessary additional objects when debug mode is active. | Data Integration |
| INC-C40045 | 951278 | JSON data transform property reference corrected | Property references within JSON Data Transform update page actions were failing to set values correctly when the property and data transform existed in the same class. This was caused by improper property resolution during the update page action execution, and has been corrected with an update to explicitly set the Param.PageClass property from .pyPageClass to prevent null reference issues. | Data Integration |
| INC-C40236 | 960090 | Oracle database query limit handling improved | Database operations were failing with "ORA-01795: maximum number of expressions in a list is 1000" errors when retrieving property information for classes with large inheritance hierarchies. This was caused by Oracle's limitation on IN clause expressions when the ancestorAndClassGroupMemberList exceeded 1000 items during property lookups. To address this, an update has been made to detect the use of Oracle and modify the lookupPropertyQueryWithLimitedExpressions() function to build IN clauses with chunking to prevent reaching the restriction level. The original behavior is preserved for other databases. | Data Integration |
| INC-C40677 | 960731 | PDF form compatibility documented | The documentation for HTMLtoPDF parameters in Building custom UI capabilities has been updated to clarify that editable PDF files are not recommended and are a limitation of the Acroforms implementation. | Data Integration |
| INC-C42133 | 960369 | Authentication handling for service utilities improved | Export operations using prpcServiceUtils were failing with 401 Unauthorized errors when specific Dynamic System Settings for HTTP service response headers were configured, particularly those containing SET-COOKIE values. This has been resolved by modifying the authentication logic to properly handle custom response header configurations during service utility operations. | Data Integration |
| INC-C42223 INC-C49731 INC-C55559 INC-C55698 INC-C55701 |
965424 965307 964526 964523 964380 |
ConcurrentModificationException resolved for clipboard | CDH inbound container requests were experiencing authentication failures and service interruptions. Investigation showed this was caused by a ConcurrentModificationException occurring when Redux-based clipboard pages were shared across multiple requestors. In the Redux implementation, each read operation created new properties if they were not available on the page. If any of these properties were referenced in Declare Expressions, the system attempted to add or remove declarative metadata, which led to a ConcurrentModificationException. This has been resolved with an update to prevent the creation of a Redux-based clipboard for shared or system (application) pages across multiple requestors. | Data Integration |
| INC-C42476 INC-C51970 |
955090 961800 |
SOAP header handling improved for optional elements | ConnectSoap rules were failing when optional header elements had no runtime values, generating "Couldn't create OMElement from string value" errors. This has been resolved by adding empty string validation to skip processing of headers with no content values. | Data Integration |
| INC-C42700 INC-C50649 INC-C48247 INC-C55592 |
954389 961332 962389 965745 |
Session management and requestor lifecycle improved | Users were experiencing unexpected logouts and session disruptions during active work sessions. This was traced to requestor passivation and activation processes happening during requestor lifecycle management as part of infrastructure scaling events. To address this, the requestor activation sequencing has been updated and error handling during passivation processes has been improved. Additionally, unused properties have been removed from PAL pages during passivation, and the default retry attempts for on-demand passivation have been increased to 4 to provide better resilience during node scaling operations. | Data Integration |
| INC-C44025 | 963224 | Memory management improved for strategy execution | High-volume API testing was causing out-of-memory errors with PEGA0039 alerts indicating large pzpvstream references exceeding 499 MB and sometimes 1.8 GB during strategy execution. Investigation showed that GOSProgram2 blob objects were preserving excessive memory and creating orphan entries during Java object operations. This has been resolved by implementing proper memory cleanup to remove orphan entries whenever the orphan data exceeds 10% of the actual BLOB size. | Data Integration |
| INC-C45502 INC-D9882 |
974620 983331 |
Websocket connection stability improved during session passivation | Applications were experiencing websocket connection failures and requestor accumulation when browser sessions were being passivated during periods of inactivity. Investigation showed this was caused by Remote OnDemand Passivation jobs failing to properly clean up batch requestors when errors occurred during browser requestor passivation. This has been resolved by updating the batch requestor lock release and return to pool mechanisms., along with enhanced websocket resiliency features including heartbeat call integrity verification, selective cookie clearing only when requestors are not found, custom health check advice messages, and comprehensive websocket message debugging capabilities. | Data Integration |
| INC-C45726 | 980004 | Case update information persistence improved for optimistic locking | Applications using the CS Framework with optimistic locking were experiencing issues where the pyWorkPage.pyCaseUpdateInfo embedded page was appearing blank on second activation, causing end-users to lose their assignments during wrap-up actions on interaction cases. This was traced to a passivation issue where the logic did not sufficiently distinguish transient properties from ordinary empty properties. This has been addressed with an update to ensure transient properties are explicitly tracked and preserved correctly through encoding/passivation paths, along with a dedicated logger for transient-property encoding diagnostics. | Data Integration |
| INC-C46918 | 962193 | Property form documentation updated | The documentation for Property form - Completing the Advanced tab has been updated to clarify that if the max length field is left blank, the system will not limit the length of property values but other operational constraints and system performance considerations might apply. | Data Integration |
| INC-C47478 INC-C46353 INC-C56134 |
957251 956865 967022 |
Query runner display and performance enhanced | The query runner tool was displaying only 20 columns maximum, showing unformatted text data without word wrapping for XML/JSON content, and experiencing performance issues. This was caused by limitations in the query runner implementation, and has been resolved by implementing an HTML/JS/JSP/Java-based solution that increases the column display limit to 100, adds pagination functionality, enables dynamic table column generation, and improves text formatting with proper word wrapping. | Data Integration |
| INC-C47722 | 958821 | Resource management improved | Resource management handling has been updated for CMIS, REST, and HTTP connectors using try-with-resources blocks in the connector activities to ensure resources are properly closed. | Data Integration |
| INC-C48714 INC-C56859 INC-C57591 INC-C56824 |
958418 966301 970134 973386 |
Google cloud storage file operations issues resolved | ConcurrentModificationException and NullPointerException errors were generated indicating "There was an issue during checking if a file or directory exists" when connecting to Google Cloud Storage for hourly data updates and file retrieval operations. This was traced to the authentication page handling and synchronization of cached authentication profiles in the Google Cloud Storage connector, and has been been resolved by removing cached tools objects, eliminating the RetryCounter usage, implementing null checks on authentication pages, and ensuring synchronized copies of authentication profiles are passed throughout the connector. In addition, the global authPage variable has been replaced with AuthenticationPageHolder for improved thread safety. | Data Integration |
| INC-C49040 | 961619 | Box integration certificates updated with valid credentials | The BoxComTrust keystore has been updated with valid, current certificates to ensure proper Box integration functionality. | Data Integration |
| INC-C49446 | 966309 | SOAPAppender race condition resolved for node startup | Nodes and their events were not appearing in the Pega Diagnostic Center (PDC) across multiple environments, with only background nodes remaining visible in the event viewer. Investigation showed this was caused by a race condition between multiple threads (AlertThread, HealthThread, and BatchThread) during node startup that led to incomplete SOAP Appenders initialization, where the BatchThread would reset shared member variables to null while other threads were actively using them. This has been resolved by making the SOAPAppenderPega class thread-safe to prevent synchronization issues when multiple threads trigger appender initialization simultaneously. | Data Integration |
| INC-C49518 | 967619 | Auto-populate property logging added | Loggers have been added to identify which property is causing the error in order to assist with diagnosing issues where saving an auto-populated data page referenced in a property was throwing a null pointer exception with the error "Cannot invoke PropertyReferenceImpl.toString() because ref is null". | Data Integration |
| INC-C51032 INC-D8424 INC-C59744 |
960628 978634 970375 |
Database information visibility corrected for delegated data types | When delegated data types were accessed through the Web Portal, database and table information was unexpectedly being displayed to users on the landing page and through hover tooltips. Investigation showed this was caused by insufficient visibility controls that failed to distinguish between developer and business user contexts, and this has been resolved by adding proper visibility conditions and implementing appropriate access restrictions so the information is not displayed to a delegated user. | Data Integration |
| INC-C51402 | 967705 | Corrected XML literal mapping runtime exceptions | Parse XML rules using "Literal XML" mapping mode were generating runtime exceptions regardless of assembler configuration settings. This was caused by conflicts between the new and old XML assembler implementations when processing literal XML content, and has been resolved by correcting the assembler selection logic. | Data Integration |
| INC-C51507 | 966179 | Resolved memory leak in report data retrieval | Applications were experiencing out-of-memory errors when generating reports through the pxRetrieveReportData activity. Investigation showed that orphaned PageMetaDataImpl instances were accumulating in memory due to improper cleanup of temporary report pages during Page-Rename operations, with the Page-Remove calls not properly targeting the temporary report pages as configured. This has been resolved by correcting the page cleanup logic in pxRetrieveReportData to ensure temporary pages are properly removed from memory after report generation. | Data Integration |
| INC-C51762 | 967820 | Content-disposition header encoding corrected for international filenames | The Content-Disposition header was being omitted from DX API responses when downloading attachments with filenames containing national or special characters such as Polish diacritics. This was caused by character encoding issues in the header serialization logic within the servlet layer, and has been resolved. | Data Integration |
| INC-C52181 | 966222 | Filename truncation at comma resolved | File uploads were being truncated at comma characters, causing filenames like "abc,def,ghi.txt" to be stored as just "abc" without the file extension. Investigation showed this was caused by improper handling of special characters in the filename encoding process within the FileUploadHandler.java uploadFile() method. This has been resolved by updating the logic for the filename encoding. | Data Integration |
| INC-C53144 | 969915 | Database cache purge job improved | The pyPurgeAssemblyDatabaseCache job was failing consistently in production environments with a PEGA0099-197 exception. This was caused by query timeout and excessive cache table size, and has been resolved by optimizing the purge query to improve performance and reliability. | Data Integration |
| INC-C53460 | 972157 | Embedded property support added for BIX Kafka message keys | When configuring Kafka data sets with embedded properties as message keys, the keys appeared empty in the published messages even when using proper page context references like ".Payload.pzInsKey". Investigation showed this was caused by the message publishing logic not properly handling embedded properties from single pages when setting Kafka message keys. This has been resolved by updating the pzPublishMessage Java step logic to fetch DataSet keys and set them as top-level properties, improving how messages are published to external datasets. | Data Integration |
| INC-C53572 | 965043 | Table instance synchronization fixed across cluster nodes | Database commit errors were occurring when new columns were added to FDQuestions and CRQuestions tables, with changes not reflecting properly across all cluster nodes despite successful rule imports. Investigation showed this was caused by incomplete column-to-property mapping updates when table schemas changed. This has been resolved by implementing automatic column-to-property map updates after each column change to ensure consistency across all nodes. | Data Integration |
| INC-C54480 | 964920 | Job scheduler node type configuration corrected | The job scheduler pyAxis2ConnectionPoolCleanup was failing to with the error "Job Scheduler ConnectionPoolCleanup registration failed". This was due to invalid mapped node types "RTDG,DDS,RealTime" being included in the configuration when they were not available in the cluster, and has been resolved by updating the configuration to use only valid mapped node types. | Data Integration |
| INC-C55739 | 968689 | File listener parse segment retry corrected | File Listener was incorrectly re-reading records that were marked with the "once" checkbox during failure recovery scenarios, causing duplicate processing of clipboard parse segments that should have been processed only once. This was traced to a NullPointerException when evaluating lsf.isProccessingStatusError, and has been resolved by adding a null check so the "once" condition is properly evaluated and honored. | Data Integration |
| INC-C55924 | 968779 | Advanced search functionality corrected for data transform sourced pages | Advanced search and select controls configured with data pages sourced from data transforms were failing to return search results. This has been resolved by correcting the data page caching mechanism to ensure that searchable data pages receive the same implicit parameter treatment as queryable data pages for pagination support. | Data Integration |
| INC-C56335 | 972659 | Attachment migration updated for better locale handling | Duplicate attachment migration was failing to process all attachments when JVM was configured with non-English locales, causing only one of multiple duplicate attachments to be migrated. This was caused by a check which relied on a hardcoded English message in pzUploadAttachment activity that failed when framework messages were generated in other languages. This has been resolved by implementing locale-independent logic for duplicate attachment handling during migration. | Data Integration |
| INC-C56940 | 968703 | Handling updated for EForm generation with unmapped fields | PDF generation was failing when Map EForm rules had no properties or fields mapped, producing "cannot be null or blank" errors during post-processing activities. This has been resolved by adding validation checks and updating the handling for this scenario. | Data Integration |
| INC-C58064 INC-C54777 INC-C59664 INC-D24389 |
966808 970391 968855 999499 |
DSS added to support token refresh for non-RFC compliant identity providers | REST connector integrations were experiencing authentication failures when OAuth 2.0 access tokens expired. This was traced to the system not receiving the expected RFC-compliant invalid_token value/format (e.g., case/underscore/spacing differences), which caused the system to not detect the condition necessary to trigger the retry/token refresh flow. To resolve this, the DSS configuration option "allowTokenRefreshAndHttpRequestRetry" (Boolean) has been added which allows the REST connector to refresh tokens and retry requests on 401 errors regardless of WWW-Authenticate header content, providing backward compatibility for non-RFC compliant identity providers while maintaining the ability to prevent endless retries when needed. | Data Integration |
| INC-C59927 | 996935 | Logging added for DirectStreamEncoderV7 | Targeted logging has been added to the DirectStreamEncoderV7 class in order to assist with diagnosing BLOB/PageList corruption or indexing issues. | Data Integration |
| INC-C7132 | 948882 | WebSphere MQ authentication updated | Message Explorer failed to authenticate when connecting to WebSphere MQ 9 instances despite successful test connectivity. This has been resolved by adding code to fetch authentication details when JMS Listener and Connector configured with Resource Reference to ensure proper credential handling in Message Explorer connections. | Data Integration |
| INC-D10393 | 988101 | File repository API data page reloading issue corrected | Custom repository implementations were experiencing issues with the D_pxNewFile API where file paths were becoming blank during the save process. Investigation showed this was caused by improper data page caching and reloading logic in the repository API. With this update, if D_pxNewFile.pyPath is populated, behavior stays the same. If it is blank, the system now falls back to RepositoryFilePg.pyPath. | Data Integration |
| INC-D10608 INC-D13222 INC-D18003 |
984412 988674 990800 |
Real-time BIX extract restored for legacy case types and documentation updated | Real-time BIX extract was failing to capture and transmit case modifications to configured data destinations such as Kafka topics and GCP PubSub when working with case types that had been created in Pega versions prior to 8.8.5. This was caused by the pzProcessChangeDataCaptureCaseTypes activity exiting prematurely at step 7 for case types that lacked initialization stages, preventing the posting of messages to the designated topics. To resolve this, the pzDeriveEventType flow has been updated to properly handle both legacy case types created in earlier versions and single-stage case configurations. In addition, the documentation for real-time BIX extraction has been updated to specify that the Case from which data will be extracted must have its first stage completed before proceeding. | Data Integration |
| INC-D10625 | 981855 | NumberFormatException fixed in BIX extract execution status | The pzUpdateBIXExtractExecutionStatus activity was failing with NumberFormatException errors when executed on SQL Server databases. This was traced to column name resolution differences between database implementations, causing a type mismatch that resulted in a NumberFormatException when attempting to parse the retrieved value. This has been resolved with an update to ensure the column name references are consistent across all supported databases. | Data Integration |
| INC-D1091 | 979152 | JSON data transform property mapping corrected | JSON data transforms were not properly mapping properties to JSON keys with different names when inheritance support was enabled, causing incorrect data structure generation. This was due to initializing the inheritance tracker with the configured page class from the mapping model instead of the actual step page class at runtime. This has been resolved by correcting the class context used during mapping to restore the correct property-to-key mapping. | Data Integration |
| INC-D11117 | 998762 | Skin Preview diagnostic logging added | In order to assist with issues using Skin Preview in Dev Studio, diagnostic loggers have been added to capture ruleset and ruleset version details along with validation to check for null or blank values in both. | Data Integration |
| INC-D113 | 974826 | Improved backwards compatibility for date property parsing | After upgrade from Pega version 8.7, applications were unexpectedly storing full ISO datetime strings in date properties when previously only the date portion was extracted from service responses. This was due to modifications in the JSON data transformation logic. To improve backwards compatibility, the JSON-to-Property date handling has been adjusted to prevent Date properties from accepting date-time strings by default, with an opt-in DSS "parseDateTimeForDateProperty" to utilize the old behavior. | Data Integration |
| INC-D12711 | 992764 | Lock handling in modal workflows corrected | Users were receiving "You have lost the lock" errors when submitting local actions on work objects launched in modals from tables, despite holding valid locks. This was occurring due to erroneous LockInfo page creation when Obj-Open-By-Handle performed extra Delete and Insert operations on pr_sys_locks, and has been resolved by correcting the lock handling mechanism to prevent erroneous lock state modifications. | Data Integration |
| INC-D12769 INC-D6051 |
984371 985626 |
PDF form concatenation handling updated | Values were being removed during the PDF concatenation process and field flattening was not working properly, leaving fields editable when they should have been flattened. This was traced to the appearance generation for concatenateEform interfering with proper PDF concatenation, along with issues in checkbox and radio button mapping, null pointer exceptions in mapEForm, and flattening problems causing text to disappear. This has been resolved by disabling appearance generation for concatenateEform functionality and correcting checkbox and radio button mapping, addressing null pointer exceptions, and updating the flattening in the generateEForm activity to ensure forms are properly flattened and non-editable as intended. | Data Integration |
| INC-D12879 | 988533 | Infinity Studio datatype deletion accuracy improved | Deleting one datatype incorrectly removed additional datatypes from the interface. This was caused by incorrect selection logic affecting multiple items, and has been resolved by updating the logic around how the target data object is resolved along with adjusting the underlying report/filter behavior. | Data Integration |
| INC-D13098 | 989902 | Data page load timeout made configurable | Service timeouts were occurring intermittently during peak periods where GetDecision service calls exceeded expected response times (10-30+ seconds). This was due to a hardcoded 60-second wait window for asynchronous data page loading operations that was not configurable for scenarios requiring shorter timeouts. This has been made configurable by introducing a new DSS key (datapage/waitingTime/seconds) to control wait timeout. | Data Integration |
| INC-D14223 | 986587 | ABAC association-based access control corrected for search operations | Attribute-based access control (ABAC) with associations was not functioning properly when using global search in Constellation portals. Investigation showed this was caused by the search index not properly applying ABAC policies that relied on association rules for indirect permission checks. This has been resolved by ensuring lookup data pages pass the security parameter as true when calling database open APIs, so that read ABAC policies are properly applied during search operations. | Data Integration |
| INC-D15791 | 987829 | Business calendar error handling improved | Exceptions were being generated when dates used were not within the business calendar range, producing "FATAL (ed.pega_rules_businesscalendar) FATAL - null" errors. This has been resolved by implementing proper error handling for dates outside business calendar ranges. | Data Integration |
| INC-D19628 | 992148 | Swedish date format display updated | Applications were displaying incorrect date formats for Swedish (sv_SE) locale users, showing dates in yy-MM-dd format instead of the expected yyyy-MM-dd format when exporting to Excel or when date controls were set to "Control inherited from property". This has been resolved by updating the date patterns for sv_SE locale to to match ICU standard. | Data Integration |
| INC-D20120 | 1002010 | New DSS keys for JFrog/Artifactory repository resiliency | File operations to JFrog repositories were failing with ""java.io.IOException: Pipe closed"" errors during file uploads, causing data flow interruptions and preventing successful file storage. Investigation showed connection timeouts and network interruptions were not being properly handled during repository operations. This has been resolved by implementing improved exception handling and an enhanced retry strategy for JFrog repository clients with configurable maximum retries configured through new DSS entries added to the Pega-IntegrationEngine repository: repository/jfrogMaxAttempts repository/jfrogInitialRetryDelayInMillis repository/jfrogMaxRetryDelayInMillis repository/jfrogBufferMemoryThresholdBytes |
Data Integration |
| INC-D20267 | 1000229 | Data migration pipeline service availability improved | Data migration pipelines were failing when attempting to write to file datasets with ""503 Service Unavailable"" errors from Google Cloud Storage during resumable uploads. The failures occurred during POST operations to storage.googleapis.com/upload/storage/v1 endpoints, preventing completion of data migration workflows. This has been resolved by implementing improved error handling and retry mechanisms for cloud file repository operations. | Data Integration |
| INC-D21299 | 997159 | JSON transformation with namespaces restored | JSON data transform mapping and deserialization was failing when array lists contained namespace-qualified declarations. This has been resolved by updating the JSON transformation logic context parsing to avoid splitting namespace-qualified / URL-like keys. | Data Integration |
| INC-D22406 | 997483 | JSON string length constraints increased | REST connector operations were failing when processing JSON responses containing strings larger than 20MB, throwing StreamConstraintsException with the error "String value length (20000105) exceeds the maximum allowed (20000000)" during inbound JSON-to-clipboard mapping operations. This was due to Jackson library default constraints limiting string processing to 20MB. This has been resolved by increasing the StreamReadConstraints maximum string length limit to accommodate larger JSON payloads exceeding 20MB in ArrayList processing. | Data Integration |
| INC-D22638 | 998078 | Data page source validation enhanced | Data pages with missing pyLoadActivity or pySourceWhen values were causing sources to be ignored during runtime initialization and execution. This was caused by insufficient validation during data page configuration and missing default conditions. To resolve this, an activity has been provided to identify, revalidate, and save impacted Data Pages where one of the configured sources is missing the pyLoadActivity value. | Data Integration |
| INC-D23165 | 996473 | Connector wizard class naming compliance enforced | Dev Studio could not open integration classes created through the Connect REST wizard when class names exceeded 56 characters and the truncation process resulted in class segments beginning with digits. This was caused by the truncateByHashing method generating Java hashCode values that could create invalid class names which violated Pega's alphabetic character requirement for segment starts. This has been resolved by modifying the truncation logic to ensure all class segments begin with alphabetic characters. | Data Integration |
| INC-D2442 | 973715 | Savable data page connector error resolved | After update, savable data pages using connectors were failing with "aParameterPage is null" errors when no parameters were passed to the data page. This has been resolved with the addition of null checks in the DataPageSaverImpl.java callDataPageSaveForConnector method to guard to avoid errors when copying the IF_MATCH parameter into the activity parameter page during data page save for connectors. | Data Integration |
| INC-D26237 | 1000540 | S3 file upload connection stability improved | Data flows were failing during S3 file uploads with "PRRuntimeException: Failed to close some of the writers" and "WriterClosingException: Failed to close writer" errors, specifically showing "java.io.IOException: Pipe closed" messages during file operations. Investigation showed connection interruptions were occurring during large file transfers to S3 repositories. This has been resolved by implementing improved connection management and retry logic for S3 operations o address socket exception handling and broken pipe recovery mechanisms. | Data Integration |
| INC-D3981 | 978588 | REST connector Content-Type header automation implemented | Connect REST rules were not automatically including Content-Type and Content-Length headers in requests, causing API Gateway integrations to fail with 403 Forbidden errors when these headers were mandatory. The APIs would work correctly when headers were manually added to the Connect REST configuration, but this required additional manual configuration steps. This has been resolved by implementing automatic Content-Type and Content-Length header inclusion for Connect REST requests that will set the content type by parsing clipboard content. | Data Integration |
| INC-D4069 | 987461 | Data page rule validation consistency improved | In some cases, savable data pages with invalid or incomplete definitions could be silently ignored and left unresolved. This was caused by invalid or incomplete savable data page definitions/sources that were not being bulk-detected and revalidated. To address this, this update provides a structured way to identify all impacted savable data pages and bulk repair them by adding bulk validation/save support for savable data pages and tracking dirty data page definitions so invalid sources can be identified, revalidated, and saved correctly. | Data Integration |
| INC-D4073 | 973710 | Log level changed to debug for API call diagnostic messages | When making successful API calls using the PUT /data/{data_view_ID} endpoint, misleading error messages were appearing in Pega logs, specifically "Skip clearing default lookup data page as lookupDpName is empty" messages at error and info levels even though the API operations were completed successfully and no actual errors were occurring. Investigation showed this was caused by leftover debug messages in the datamgmt.dataapi.utilDataAPIUtilsImpl class that were incorrectly using error() and infoForced() logging methods instead of debug() methods in the clearDefaultLookupDataPage() function. This has been resolved by changing the log level for these diagnostic messages to ensure they only appear when debug logging is explicitly enabled. | Data Integration |
| INC-D522 | 981069 | Logging added for missing PageList element | In order to assist with diagnosing issues where a PageList element goes missing during clipboard/BLOB encoding, a dedicated DirectStreamEncoderV7DiagnosisPageListIssue logger has been added which will emit detailed debug messages in Page/PageList encoding paths. This includes a DSS-based filter "BLOBDebugPageListName" to only log for selected PageList/property references. | Data Integration |
| INC-D5683 | 977668 | REST connector PUT request payload issue resolved | PUT requests were failing and the payload appeared empty when using x-www-form-urlencoded configuration in REST connectors. This was caused by the request body not being populated due to a failure to set the reqMessageData variable in the mapping logic, and was traced to a conditional check in the MAP OUTBOUND DATA step that did not account for PUT method payload handling. This has been resolved with an additional check on method name so that list is being sent only if its post request and there is url_encoding in the mapping type. | Data Integration |
| INC-D6671 | 976387 | OAuth authentication support enabled for SMTP email communication | Microsoft has retired Basic authentication with SMTP protocol from March 2026, requiring applications to use OAuth authentication instead. With this update, OAuth support is provided for SMTP protocol to support using Microsoft as the email provider in the email account rule. |
Data Integration |
| INC-D6804 | 977473 | Null pointer exception handling added for SRS migration | Attempting to index regular class items during SRS migration data processing resulted in the error "java.lang.RuntimeException: Caught exception while expanding property null on page .pxFlow(Inbound).pyFlowParameters" . This was traced to a null PropertyName caused by data corruption in the blob storage stream processing, and has been resolved by adding handling for an empty property during deserialization. | Data Integration |
| INC-D6934 | 979428 | Doubled error message display corrected | Generic error messages were appearing alongside custom validation messages in Constellation UI components. This was caused by the DX API returning both generic and custom error messages simultaneously, and has been resolved by adding a new method for generic error message handling to prevent duplicate message rendering. | Data Integration |
| INC-D71 | 976269 | Data page functionality restored for embedded fields | After update, the error "Cannot invoke 'com.pega.pegarules.pub.clipboard.ClipboardPage.getString(String)' because 'dataPagesForClass' is null" appeared when trying to access data page D_testSavable. Additionally, attempting to update records containing embedded data fields through the DX Data API was not working. This was an unintended side effect traced to the introduction of the API mergeWithDBRecord(), and has been resolved by updating thread handling. | Data Integration |
| INC-D7199 | 981898 | Rate limit handling improved for data migration pipelines | Data migration pipelines were failing after processing only a few records with "429 Too Many Requests" errors from Google Cloud Storage, specifically encountering rate limit exceeded messages for object mutation operations. Investigation showed this was caused by excessive API calls during file dataset operations without proper rate limiting controls. This has been resolved by implementing intelligent retry mechanisms and request throttling to comply with Google Cloud Storage rate limits during data migration operations. | Data Integration |
| INC-D7424 | 982428 | Insight loading handling updated for embedded page configurations | Insights were showing only loading screens for data objects with embedded page properties configured using $any or @class, preventing proper metadata loading. This was caused by missing pyPageClass values for embedded fields being treated as valid input during metadata transformation, leading to the context class becoming null during metadata loading via pzGetClassDataModelFromDictionary. This has been addressed by adding warning messages and ensuring the system returns early when pyPageClass is blank to avoid processing failures. | Data Integration |
| INC-D7494 | 977571 | Windows file upload restored | File upload operations were failing on Windows environments with "Upload failed" errors and InvalidPathException messages showing "Illegal char ':' at index 4: file://web:/StaticContent/global/ServiceExport/". Investigation showed this was caused by the Web tier passing logical URI paths directly to java.nio.file.Paths.get() without proper URI-to-path resolution, which Windows file systems cannot process. This occurred when the configured upload directory was a Pega logical/VFS path instead of a native OS filesystem path, and was caused by FileUploadHandler passing that logical path directly into Apache Commons FileUpload. This has been corrected with an update which resolves the logical path first, normalizes it, and uses a safer bounded buffer size. | Data Integration |
| INC-D7948 | 998060 | Azure archival size limitations removed | Case archival operations to Azure repositories were failing with "maximum size for put Blob is 256MB" errors when archiving cases containing large numbers of attachments and dependencies, specifically when using OAuth authentication with Data Lake Gen2/Blob storage configurations. Investigation showed this was caused by OAuth authentication using different libraries that incorrectly enforced the 256MB limitation during blob uploads. This has been resolved by implementing size-based upload logic that uses putMultipartBlob method for files exceeding 256MB and putBlob method for smaller files. | Data Integration |
| INC-D8485 | 978103 | Improved Kafka topic partition error logging | In order to assist with diagnosing Kafka errors such as "UnknownTopicOrPartitionException: This server does not host this topic-partition" errors, logging has been updated to print the stream name if there is an issue while fetching stream partitions. | Data Integration |
| INC-D9183 | 987417 | SOAP namespace preservation implemented | SOAP services requiring SAML assertions were experiencing signature validation failures when duplicate namespaces were removed from SOAP request XML. To resolve this, the handling has been update to ensure SOAP RPC-encoded requests are constructed so the generated SOAP body includes the right namespace declarations and type metadata at the operation/body level. | Data Integration |
| INC-D9324 | 987234 | Data type integration details error resolved | The D_pzGetIntegrationSystemDetails data page was throwing StringIndexOutOfBoundsException errors when opening newly created data types without fields or records. Investigation showed the pzGetIntegrationSystemDetails activity was attempting substring operations on empty systemsCSV strings when no integration results were present. This was caused by missing conditional checks before performing substring operations on potentially empty strings, and has been resolved by adding proper conditional validation before string manipulation operations. | Data Integration |
| INC-D966 | 972574 | SOAP connector response parsing restored | Connect-SOAP invocations were failing during response parsing when processing MIME parts, and a MimeConfig$Builder exception at com.pega.apache.axiom.attachments.MIMEMessage.<init>(MIMEMessage.java:126) was generated. This has been resolved by updating the apache-mime4j-core library to the latest version. | Data Integration |
| PRB-B72 | 969378 | Database operation logging accuracy improved for report execution | System alert PEGA00167 was incorrectly identifying database operations from report execution as originating from Query-Runner, causing confusion in system monitoring and troubleshooting. This was caused by incorrect source identification logic in the database operation logging mechanism when reports were executed to populate data pages, and has been resolved by updating the logic for distinguishing between report execution and query runner activities. | Data Integration |
Decision Management
26.1 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-D18637 |
994902 | Cassandra read operations optimized for response monitoring | The MKTResponseHandler dataflow was experiencing significant performance degradation. Investigation revealed that each ADM response was triggering duplicate Cassandra read operations for the same subject/interaction pair - one from the newly introduced ResponseMonitoringHelper and another from the pre-existing ClientImpl. Investigation showed this was caused by the Response Monitoring feature adding an extra readByKeys() call to Cassandra that duplicated existing functionality. This has been resolved by eliminating the unnecessary duplicate Cassandra read operations while preserving the monitoring functionality. | Decision Management |
| INC-A23778 INC-C51864 |
879832 961977 |
Dataflow performance improved for Cassandra datasets | After upgrade, dataflows combining RDMS and DDS datasets were experiencing significant slowness when Cassandra datasets were included, while RDMS-only dataflows maintained high bandwidth performance. This was traced to multiple lookup keys in DDS Data Set browse by keys operation being processed sequentially, not in parallel, and this has been addressed by refactoring the dataset handling in dataflow operations to optimize Cassandra performance. | Decision Management |
| INC-B51876 | 962712 | Accessibility improved for question help icon | Smart Info help icons configured for questions in question pages were not accessible via keyboard navigation. This has been resolved by implementing proper keyboard navigation support for Smart Info help icons to ensure visible focus indications and activation with the enter key. The icon has the semantic role of button and a programmatic label. | Decision Management |
| INC-C22331 | 955192 | Improved DSMClipboardPage self-diagnostics | An update has been made to enforce periodic self-diagnostics for DSMClipboardPage which will check whether the current indexed property access matches the correspondent non-indexed property access, and reports an error if there is mismatch. | Decision Management |
| INC-C22614 | 936719 | Cosmos theme localization key mapping corrected | The text "Replies to my messages" was not being properly localized in Cosmos. This was traced to the getLocalisedText function in the pzRetrievePulseFeed activity not referencing the correct pyGenericFields key, and has been resolved by updating the activity to differentiate the handling of traditional and Constellation scenarios. | Decision Management |
| INC-C25530 INC-D8904 |
933736 978590 |
Performance metrics display accuracy improved | PDC was displaying nanosecond execution times incorrectly labeled as milliseconds, causing confusion during performance analysis. This was caused by improper unit conversion logic, and has been resolved by correcting time unit calculations and display formatting. | Decision Management |
| INC-C26186 | 943662 | Change request approval cover count fixed | Approving OpS change requests from Deployment Ready to Complete status failed with open cover count errors. This has been resolved by updating the Resolve activity to properly reset the pxCoveredCountOpen property during case resolution. | Decision Management |
| INC-C27000 | 945466 | Improved performance of DSMClipboardPage encryption | Data flow execution with DSMClipboardPage encryption was taking an excessive amount of time and significantly impacting ingestion performance. This was traced to performing excessive checks during data transform shape execution, and has been addressed by optimizing DSMClipboardPage encryption checks to reduce the frequency and duration of encryption validation operations. | Decision Management |
| INC-C27293 | 944061 | Dataflow service startup delays reduced | Dataflow services experienced significant delays when starting after node restarts, with partition assignments taking up to 15 minutes to complete. This has been resolved by optimizing service registry queries in CheckAssignmentsTask. | Decision Management |
| INC-C27835 | 948472 | Duplicate interaction history records prevented | Duplicate interaction history records with identical details were inserted during node shutdown scenarios when dataflow service threads were created just before shutdown. This has been resolved by implementing enhanced thread context detection and stopping mechanisms during shutdown sequences. | Decision Management |
| INC-C27915 | 952395 | Strategy action inlining diagnostics enhanced | In order to improve troubleshooting for missing actions issues in decisioning processes, comprehensive diagnostic logging has been added for all actions inlined and not inlined during GOS compilation. | Decision Management |
| INC-C29014 | 947831 | Updated handling for ResponseTimeout settings | Users were unable to save ResponseTimeout settings for Predictions when updating alternate labels in prediction rules. This was caused by a conflict in the rule saving mechanism when duplicate alternate labels were present, and has been resolved by adding the necessary validations to handle the duplicate alternate labels. | Decision Management |
| INC-C30676 | 944380 | File dataset preview functionality restored | After update, dataset preview operations were failing if the directory in which a file was generated had another sub directory or file that didn't match the pattern mentioned in the file path. This was caused by a system change to stricter pattern matching that had the unintended consequence of rejecting entire directories if they contained any non-matching content. This has been resolved by modifying the preview logic to focus only on files matching the specified pattern while ignoring non-matching directory contents. | Decision Management |
| INC-C31299 | 956421 | Strategy parsing performance optimized to eliminate redundant analysis | Globally Optimized Strategy (GOS) reports were timing out due to excessive processing times during strategy analysis. This was caused by the same strategy being analyzed multiple times when used in default criteria of proposition filters with large numbers of actions, and has been resolved by removing the second parsing pass when generation the GOS report, incorporating all the analysis into a single pass. | Decision Management |
| INC-C31299 | 953239 | Logging added for GOS strategy report generation | Globally Optimized Strategy reports failed to generate due to missing referenced WHEN rules, causing StrategyParserRuntimeException errors. To assist in diagnosing these errors, additional logging has been inserted for the Rule Scanner when getting the Rule report (inside the GOS report package), and the logger com.pega.decision.strategy.diagnostics.DiagnosticsReports has been set to DEBUG level. Some memory improvements have also been made for the Rule Report. | Decision Management |
| INC-C31864 | 946016 | Snowflake authentication resolved | Snowflake database connections failed with incorrect username/password errors despite using valid credentials when evaluated with HashiCorp encryption. This has been resolved by adding support for different types of encryption systems by updating the password decryption logic in Snowflake connectivity rules to use PRCrypto.decryp. | Decision Management |
| INC-C32205 | 945571 | GOS handling improved | Globally Optimized Strategy (GOS) revisions became stale and failed to refresh automatically after Next Best Action strategy changes, requiring manual invalidation. Investigation showed null pointer exceptions occurred during revision deserialization due to empty pyInlinedRules fields. This has been resolved by enhancing logging and error handling in GOSCentralCompilation for inlined rules processing and adding RuleDescriptor support for an optional name of DecisionParameters. | Decision Management |
| INC-C32564 INC-C50768 |
955302 961554 |
Data migration bucket assignment handling updated | Data migration processes were intermittently failing during the additional data export stages with the error "VBDException: api.core.service.cache.operations.BucketAssignedException: Bucket '5' is assigned but not yet active [operation='VBDBrowseOperation']". This was caused by timing issues in the Visual Business Director's bucket management system, and has been resolved by implementing Retry for broadcast release events, adding logging for bucket assignment events, and ensuring that missing assignment events are added when bucket is activated and that pulse message sending is delayed until subscription to the event stream is completed. | Decision Management |
| INC-C32691 | 959118 | Mobile browser case feed scrolling corrected | The pyCaseFeed section launched from pyCaseHeaderMobile action button was not scrollable in mobile browsers, preventing users from viewing overflow pulse messages. This has been resolved by updating the scroll handling CSS. | Decision Management |
| INC-C33467 | 953830 | Questionnaire file attachment support restored | Case creation was failing with "An internal error occurred. Please contact administrator" when using questionnaires with File type questions configured as "List of Records" in Constellation applications. Investigation showed this was caused by incorrect view metadata annotation where attachment properties were annotated with @p instead of @ATTACHMENT during questionnaire generation. This has been resolved by updating the questionnaire runtime generation logic to detect the underlying property mode for file questions and properly annotate attachment properties. | Decision Management |
| INC-C33586 | 945641 | Event catalog logging enhanced | Event catalog feature failures were not generating sufficient log messages to isolate problems, making troubleshooting difficult when incorrect Cassandra keyspace configurations were used. The logging framework has now been enhanced to provide more detailed diagnostic information for event catalog failures. | Decision Management |
| INC-C33809 | 944214 | Interaction history summary processing improved | Applications experienced out-of-memory errors when processing interaction history summaries due to excessive memory consumption during pre-aggregation runs. Investigation showed this was caused by overly specific keys in the Action Outcomes By Channel Summary Data Set combined with the presence of millions of interaction history records. This has been resolved by enhancing the Decision Data Store API to support backpressure, enabling iterative record loading from Cassandra instead of loading all records at once in order to reduce memory requirements during summary data processing. | Decision Management |
| INC-C34067 | 951363 | Strategy compilation performance optimized for large operations | Very long compilation times were occurring for Globally Optimized Strategy (GOS) operations. This occurred when the context manager contained duplicate context variables with the same name in a Deque structure. To resolve this, Collectors.toMap() has been replaced with a manual loop using putIfAbsent(). This preserves only the first occurrence of each variable name (representing the latest context variable in the Deque) and prevents duplicate key exceptions. In addition, several related areas have been refactored for improved performance and robustness. | Decision Management |
| INC-C35539 | 950062 | Avro schema URL modification enabled | After update it was not possible to modify the URLs of any existing Avro schemas due to the Schema Registry tab appearing greyed out. This was an unintended side effect of work done to introduce support for configuring the schema registry URLs using application settings, and has been corrected. | Decision Management |
| INC-C35650 INC-D5321 |
973120 984601 |
Parameterized predictors synchronized with adaptive models | Parameterized predictors were being populated in strategy results during testing but were not appearing as available options in Prediction Studio monitoring, displaying "No predictors available" instead. Investigation showed this was caused by a missing fail-safe auto-sync mechanism during rule save-as operations. This has been resolved by implementing an automatic synchronization process that ensures parameterized predictors are properly made accessible to adaptive models during save operations. | Decision Management |
| INC-C36291 | 948699 | Data flow initialization monitoring enhanced | Comprehensive logging has been added to track partition state transitions and identify initialization bottlenecks that can contribute to queue processors with high-volume data flows becoming stuck in initialization state during partition rebalancing events, particularly when CPU scaling occurs and Kafka isolation quotas caused throttling. | Decision Management |
| INC-C36371 | 957474 | Decision data invalidation mechanism corrected | Globally Optimized Strategy (GOS) containers were not reflecting updated decision data after changes were made to DDRC class rules. This was caused by GOS invalidation not occurring when decision data rules in the DDRC class were modified while related strategy rules existed in the DDRC-App class, and has been resolved by ensuring proper invalidation of affected GOSes when decision data, decision table, IH summary, and adaptive model rules are changed on parent classes. | Decision Management |
| INC-C38002 | 950774 | Inbound simulation channel property alignment corrected | Inbound simulations run against Call Center channel failed to yield results despite proper configuration. Investigation showed this was caused by mismatched channel property references between sample storage and simulation data flow browsing operations. This has been resolved by aligning the channel property usage across all simulation components. | Decision Management |
| INC-C38064 | 951675 | GOS rule deserialization error handling updated | Container API calls returned inconsistent results across different requestor contexts after action availability time changes, requiring multiple restarts to resolve. Investigation showed this was caused by null pointer exceptions during Globally Optimized Strategy rule deserialization when inlined rules could not be resolved during compilation. This has been resolved by introducing a checked exception RuleNotResolvedException that forces parsers to explicitly handle rule resolution failures and ensuring that unresolved rules are tracked in the inlined rules list for monitoring, enabling automatic recompilation when these rules become available. | Decision Management |
| INC-C38444 INC-C57391 |
956630 966775 |
Single action group end date enforcement restored | Actions within single-action groups were being offered to users even after their configured end dates had passed. This was traced to an incorrect optimization in the globally optimized strategies code which resulted in an action being always active if it had a begin date and an end date, was the only action in the group, and it was active at the moment of compilation. To resolve this, an update has been made to ensure the "Is Proposition Active" flag is correctly set to false when the proposition data reaches the end of its defined period. | Decision Management |
| INC-C38765 | 949791 | Real-time data flow status handling improved | Real-time data flows became stuck in failing state and could not transition to in-progress status even after restarts. Investigation showed this was caused by improper status transition logic when partition assignments were missing from the key-value store. This has been resolved with an update to still create an assignment in this case, which will allow unknown pods and terminated pods to be unassigned from the partitions properly. | Decision Management |
| INC-C39256 INC-D5143 |
958409 978324 |
Handling added for GOS rule deserialization null pointer exceptions | Globally Optimized Strategy (GOS) processing was experiencing null pointer exceptions during rule deserialization and rule name extraction operations. This has been resolved by updating the null validation handling, replacing StringMap usage with RuleDescriptor for rule definitions, and ensuring inlined rules collections are never null even for failed revisions. | Decision Management |
| INC-C40364 | 964638 | Support added for escaping double quotes in CSV dataset processing | CSV files containing escaped double quotes in the format "This is a ""Test"" data" were not being processed correctly when uploaded through data flows to data tables. This was traced to the parsing of escaped quote sequences in the CSV processing logic, and has been addressed with the addition of the DSS value "dnode/file/csv/enableEscapedQuotes". By default, the DSS is set to true and will use the new parser and serializer with support for escaped quotes. Setting the DSS to false will revert to the previous behavior of using the parser and serializer without support for escaped double quotes. | Decision Management |
| INC-C40466 | 963974 | Pulse gadget note persistence improved during refresh | Contact notes were disappearing from the Pulse gadget when users clicked refresh in the notes dialog during interaction wrap-up processes. This was caused by improper state management during the refresh operation in the notes dialog, and has been corrected. | Decision Management |
| INC-C40497 | 950788 | Decisioned record TTL customization enabled | In order to support applications requiring extended retention periods for decisioned records beyond the standard 1-day limit, support has been added for customizable TTL settings in pxDelayedLearningFlow based on specific request categories and conditions. | Decision Management |
| INC-C40955 INC-C43209 |
951899 962887 |
Data flow count accuracy corrected | Data loads from BigQuery to Pega showed count mismatches during high-volume processing with multiple nodes. Investigation showed scaling events resulted in incorrect metric calculations during the data transfer process. This has been resolved by improving the count calculation logic to handle node scaling events properly during data flow operations by only counting records in the primary source shape after they are picked up from the input queue. | Decision Management |
| INC-C41598 | 962939 | Handling updated for revision simulation empty segment failures | Revision simulations were failing and corrupting the revision case when configured with empty segment datasets.This was caused by the pyTriggerPerformanceTest activity completing assignments even after simulation failures, leaving error messages on the page without providing navigation options back to the pyViewRevision flow, and has been resolved by updating the handling for pyViewRevision so that if the simulation fails, the process remains in the viewRevision stage instead of progressing to simulateRevision. Validation has also been added to ensure the segment is verified before creating the simulation. | Decision Management |
| INC-C42350 | 954136 | Prediction model documentation updated | The documentation for Strategy design with multiple Predictions has been updated to explicitly warn against using identical alternative labels in the same strategy execution path to avoid the processing of duplicate responses for the underlying models. | Decision Management |
| INC-C42626 | 964984 | Screen refresh performance improved after artifact generation | Operation management cases were experiencing significant slowness due to large numbers of DDR records and database queries exceeding 5 second thresholds, with screens not refreshing properly after artifact generation. Investigation showed this was caused by inefficient DDR queries and circumstance value handling across rule versions. This has been resolved by optimizing database query performance and implementing proper screen refresh mechanisms post-artifact generation. | Decision Management |
| INC-C42945 | 954044 | Strategy expression null handling updated | After update, strategy expressions containing conditional date formatting operations were throwing null pointer exceptions. This has been resolved by updating the implementation to use Objects.toString() which safely handles null values by converting them to the string "null". | Decision Management |
| INC-C42986 INC-C46566 |
954054 956593 |
Adaptive analytics flow performance improved | After update, systems were experiencing significantly elevated busy thread counts and performance degradation during execution of the pxAdaptiveAnalyticsflow data flow. Investigation showed this was caused by excessive thread blocking in unsafe.park state when the system was attempting to retrieve prediction model configurations. This has been resolved with an update to only fetch the prediction configuration from the cache to avoid cache exception. Exception handling has also been improved. | Decision Management |
| INC-C43635 | 955266 | Group DDR section autogeneration corrected | Group-level decision data rules (DDR) sections were not being auto-generated for groups with spaces in their names, causing section rules to reference artifacts rules instead of proper group-specific sections. Investigation showed the pzSetAutoGenerateFlag Data Transform was incorrectly relying on the 'pzIsAutoGenerated' property instead of the 'pzIsAutoGeneratedForm' flag. This has been resolved by updating the data transform to use the correct property flag for auto-generation validation. | Decision Management |
| INC-C43714 | 955705 | DSS added to specify BigQuery connector quota limits | Applications were experiencing quota exceeded errors when using the BigQuery connector during data ingestion operations, with API calls hitting the tabledata.list limit of bytes per second per project. This has been addressed by implementing a MAX_PARTITIONS_COUNT DSS with the following default retry values: dnode/bigquery/max_attempts - 50 dnode/bigquery/initial_retry_delay_seconds - 1 dnode/bigquery/retry_delay_multiplier - 2.0 dnode/bigquery/max_retry_delay_seconds - 30 dnode/bigquery/total_timeout_seconds - 900 |
Decision Management |
| INC-C45466 | 956973 | Pulse message timestamp display corrected for ReplyDetailsHeader | Pulse messages posted in previous days were displaying incorrect date-time values in the pyReplyDetailsHeader, where the minutes portion was showing as months in the custom date format. This was caused by improper date formatting logic in the pulse message display component, and has been resolved by correcting the "Custom date-time format" field from "MMM dd, yyyy h:MM a" to "MMM dd, yyyy h:mm a" to display minutes correctly. | Decision Management |
| INC-C45511 | 961110 | Adaptive decision management commit log reads stabilized | Applications were experiencing continuous large amounts of responses being triggered to the ADM commit log when processing records with processing lag. Investigation showed this was caused by the system attempting to read from Cassandra commit log records that had already been deleted due to TTL expiration, resulting in tombstone reads that destabilized the commit log processing. This has been resolved by implementing logic to prevent reading from old partitions containing only TTL'ed records and making commit log reads more stable by avoiding tombstone reads entirely. | Decision Management |
| INC-C45773 INC-D3698 |
962497 974850 |
Customer Profile Viewer persona test data usage corrected | Failures were seen in Customer Profile Viewer persona tests where the system was incorrectly querying actual Cassandra data instead of using configured persona test data when running in test mode or single action mode. This was caused by the mxIHSummaryBrowseByKeys() function not properly propagating the IH summary cache parameters in test scenarios, and has been resolved. | Decision Management |
| INC-C45993 INC-C55321 |
960778 965967 |
Corrected GOS authentication during campaign execution | After update, outbound campaigns were failing with authentication errors during Globally Optimized Strategy (GOS) compilation, specifically when processing behavioral limits strategies. Investigation showed this was caused by GOS local compilation not properly switching to access group-only compilation for non-developer operators who are not allowed to check out rules, resulting in authentication failures when the system attempted to authenticate batch users with developer access groups. This has been resolved by implementing proper context switching during GOS local compilation that uses access group-only compilation for operators so changes in the operator and their private rules does not affect compilation for the access group-only context. | Decision Management |
| INC-C47266 INC-C53731 INC-D2781 |
960473 963154 973748 |
BigQuery data flow processing improved | BigQuery data jobs were intermittently getting stuck in "In Progress" status without processing any records, and attempts to stop these data flows were taking up to 10-12 hours to transition to "Stopped" status. Investigation showed this was caused by the system continuously attempting to recreate temporary tables even when they already existed, which exceeded BigQuery's rate limits for table update operations. This has been resolved by reducing the number of table.insert requests and fixing data flow handling in case of job failure. | Decision Management |
| INC-C49055 INC-C56266 |
960632 966370 |
Datetime formatting corrected in dataflow exports | After update, datetime columns were being exported via dataflows with 'GMT' appended to the values in output files, causing downstream import jobs to fail. Investigation showed this was caused by the convert step in dataflows modifying the pxObjClass property, preventing the system from properly identifying the property type and causing it to default to Pega's internal datetime format. This has been resolved by enhancing datetime properties parsing in CSV file datasets, and a related issue where duplicate double quotes were being created in exported files has also been resolved with this change. | Decision Management |
| INC-C50138 | 960118 | Real-time data grid proxy configuration updated | Actions were failing to load and sessions were hanging when proxy JVM settings were configured, particularly affecting development and test environments. This was caused by real-time data grid (RTDG) communications incorrectly using JVM proxy settings, and has been resolved with an update to use DefaultHttpRoutePlanner instead of ProxySelectorRoutePlanner. The DefaultHttpRoutePlanner will not make use of any Java system properties, nor of system or browser proxy settings. | Decision Management |
| INC-C51087 INC-D2112 |
962086 972435 |
Corrected missing Kafka response properties | After upgrade, applications were had missing pxStreamPartition and pxStreamPosition properties in Kafka responses. This was traced to incomplete property mapping in the Kafka dataset response by the DSMClipboardPage function, and has been resolved by updating the handling to not use DSMClipboardPage in DataSets. | Decision Management |
| INC-C51773 | 961370 | Handling added for Cassandra exceptions on platform-only deployments | Platform deployments without CDH services were experiencing CassandraConnectionManagerException errors when attempting to connect to non-existent Cassandra clusters for interaction summary datasets. This has been resolved by implementing proper service availability checks and providing configuration options under pzIsCassandraAvailable to disable Cassandra-dependent features when CDH services are not present. | Decision Management |
| INC-C51825 INC-C58870 |
967047 967993 |
Data flow service level configuration updated | Agent queues were experiencing failures when attempting to process data flows that were no longer available in the system. Investigation showed that the pxRunDDF and pxRunRTDataFlow flows were incorrectly configured to use service level settings, causing orphaned assignment instances to remain after data flow deletion and resulting in SLA agents attempting to reference deleted data flows. This has been corrected by removing the default SLA configuration from data flow run process flows. | Decision Management |
| INC-C52553 | 966162 | Predictors tab loading improved in Prediction Studio | The Predictors tab in some Prediction Studio models was not loading information, particularly affecting email and push models in the Monitor tab. Investigation showed that large amounts of data were causing loading failures in the predictors display. This has been resolved by adding modelId as a filter for optimized query reads to improve performance. | Decision Management |
| INC-C53234 | 963621 | Erroneous GenAI agent email error messages corrected | The GenAI agent was intermittently displaying failure messages to users when sending emails through the pySendEmailWithAttachments tool, even though emails were successfully sent in the background. This was caused by missing handling for an empty response parameter in the automation response processing, and has been resolved by adding the Response Parameter to pzSendEmailWithAttachmentsWrapper and Automation: pxSendEmailWithAttachment. | Decision Management |
| INC-C54551 | 965981 | Data flow batch mode processing corrected | Data flows were failing with "Cannot do this in batch mode error" during partition state updates, causing runtime exceptions and stuck data flow runs. Investigation showed the batch operations process did not reset the thread properly from batch mode to regular mode. This has been resolved by modifying the conditions in updatePartitionStates and ensuring batch mode is temporarily disabled during partition state commits and properly restored afterward. | Decision Management |
| INC-C56419 | 967015 | Dataflow initialization timeout handling improved | Multiple dataflows were failing to start when COUNT(*) queries against large datasets were timing out after 90 seconds, causing I/O errors and preventing dataflow initialization. This was caused by the system requiring successful completion of record count operations before allowing dataflow runs to proceed, and has been resolved by allowing dataflow runs to initialize even when the getNumberOfRecordsOperation fails, with warnings added to the dataflow run and exception details logged for troubleshooting purposes. | Decision Management |
| INC-C56713 | 969069 | ADM data migration status reporting corrected | Data migration export processes were incorrectly marking ADM (Adaptive Model) stages as failed despite successful completion. This occurred when repository persistence was enabled for Adaptive models, and was caused by incorrect status evaluation logic in the ADM migration factory component. This has been resolved. | Decision Management |
| INC-C56916 | 965845 | Decision table evaluation accuracy improved | Decision tables were producing incorrect results when evaluating When rules, particularly with isInPageListWhen and @CallWhen functions on Customer pages, and when using additional allowed results mapping. This was caused by named pages not being properly published to clipboard during platform rule execution in strategy and proposition filter contexts, and has been resolved by ensuring named pages are published to clipboard when non-strategy or non-proposition correspondent platform rules are executed. | Decision Management |
| INC-C57075 | 967570 | Kafka dataset class loading issues resolved | Dataflows utilizing Kafka datasets with AVRO data format were failing sporadically with NoClassDefFound errors. This was traced to the data flow overwrite functionality which allows source or destination shapes to be 'overwritten' by a different dataset / data flow implementation. In the process of using the rule class loader and the assembly of the data flow object, the Avro class is referenced. This leads to the failure as the rule class loader does not allow loading these classes in this context. To address this, a fallback class loader has been introduced in the context of data flows using overwrites. | Decision Management |
| INC-C57753 INC-C58277 |
966710 967391 |
Prediction model arithmetic exception resolved | Prediction Studio was experiencing failures when attempting to open prediction models that contained performance metrics with decimal values other than .00 (such as 92.56 or 72.02), generating a java.lang.ArithmeticException during the weighted average calculation of performance numbers. This was traced to an improper rounding mode configuration during the mathematical operations, and has been corrected. | Decision Management |
| INC-C58010 INC-C53850 INC-D1040 INC-D12601 |
968115 968354 970991 983881 |
Prediction model learning issue resolved | After update, prediction models were not learning properly and response timeout configurations were not functioning as expected. Investigation showed this was caused by the event-based response timeout mechanism not triggering independently for each prediction configured within the same decision flow, and unwanted information being persisted on the pxDR object during delayed learning processes. This has been resolved. | Decision Management |
| INC-C58606 | 975822 | Execution profile array bounds handling corrected | Decision execution profiling was encountering "Index -1 out of bounds for length 4096" ArrayIndexOutOfBoundsException errors during profile merging operations, particularly affecting globally optimized strategy (GOS) execution profiles and causing InstrumentedExecutionProfile$WrongProfileState exceptions with "Something corrupted" messages. This was traced to incorrect variable usage in Binary Search Chunks (BSC) iteration within the scanChildIndices method during AOP profile merge operations, and has been resolved by correcting the variable handling in the InstrumentedExecutionProfile class merge. | Decision Management |
| INC-C59087 | 968774 | Prediction Studio security updated | Cross-site scripting protections have been updated for Prediction Studio. | Decision Management |
| INC-C59941 | 971637 | Updated DX API swagger feed reference | The DX API swagger documentation contained empty $ref fields in the pzGetFeed.yaml file, preventing proper proxy API generation using Maven plugins. This has been corrected. | Decision Management |
| INC-C8270 | 935523 | Dataset repository documentation clarified | Documentation for content storage types has been updated to clarify that File Data Sets do not support custom repositories. Use one of the predefined repository types such as Amazon S3. | Decision Management |
| INC-C9933 INC-C41052 |
945497 952519 |
Updated migration handling for collection backed up by data sets | The PopulateSPA dataflow was not migrating single-page applications (SPAs) from Prod to Simulation as part of the data migration unless PopulateSPA was manually run. To resolve this, an update has been made to ensure collections backed up by a data set are now migrated using the dataset as the source of truth for any configuration property that was newly introduced. | Decision Management |
| INC-D10792 | 982261 | Improved backwards compatibility for Kafka legacy dataset validation | Kafka datasets created before consumer group functionality was introduced were failing application validation with "No enum constant com.pega.dsm.dnode.api.dataset.kafka.ConsumerGroupPrefixType" errors. Investigation showed this was caused by validation rules not accounting for legacy dataset configurations . This has been resolved by updating Kafka dataset validation artifacts to handle scenarios where the consumer group type is not set while maintaining compatibility with newer consumer group features. | Decision Management |
| INC-D11187 | 981563 | Connection resilience improved for GCP host migrations | Applications were experiencing connection resets during Google Cloud Platform (GCP) host migrations, causing service disruptions when the cloud infrastructure performed routine maintenance operations. This has been resolved by implementing enhanced connection reset timeout configurations and increased diagnostic logging to better measure connection drop timing. | Decision Management |
| INC-D12212 | 984603 | Adaptive model single-level-v1 pxDecisionResults format deprecated | The documentation for Pega Customer Decision Hub dynamic system settings - Adaptive Learning has been updated to note that the single-level-v1 value for the decision/adm/modelExecutions/format dynamic system setting (DSS) is deprecated. In an environment configured with single-level-v1, the system automatically uses multi-level-v1 for all new Decisions. Existing records created with the single-level pxDecisionResults format remain readable. To align with the supported pxDecisionResults format, update the value of the DSS to multi-level-v1 if it is currently set to single-level-v1. This information has also been updated in the documentation for Withdrawn and deprecated features in Pega Customer Decision Hub. | Decision Management |
| INC-D1273 | 971538 | Handling added for non-time-based UUIDs in ADM commit log processing | Predictive Decision Composer was experiencing UnsupportedOperationException errors during model updates when processing non-time-based UUIDs in the commit log system. This was caused by the TimeUUIDUtils attempting to extract timestamps from standard UUIDs rather than time-based UUIDs, and has been resolved by implementing proper UUID type detection and handling for non-time-based UUIDs. | Decision Management |
| INC-D12825 | 994695 | Added handling for null pages in metrics capture | Applications were experiencing InvalidReferenceException errors with NullMyStepPage messages during CDH and Decisioning metrics capture operations, specifically in CaptureInteractionHistoryStorageDetails and CaptureExplainabilityAuditStorageDetails activities. Investigation showed this was caused by activities attempting to reference null step page objects during metric collection processes. This has been resolved by updating the interaction history capture to add named step pages for activity invocations which will ensure the called activity handles/receives the step page context correctly instead of assuming it is always present. | Decision Management |
| INC-D12999 INC-D17309 |
983583 996753 |
Legacy component driver count mismatch resolved | ArrayIndexOutOfBoundsException errors were occurring when switch components in strategic filters fell back to legacy execution, particularly in "For each Strategy in StrategicFilter". Investigation showed this was caused by certain embedded legacy strategy components with hidden dependencies that introduced extra runtime references that were not counted up front, so the profiler allocated too-small ordered structures and overflowed. This has been resolved by forcing those legacy cases to use unordered iteration, which avoids the overflow. Additional diagnostic logging has also been added. | Decision Management |
| INC-D136 INC-D5368 INC-D2295 |
975749 976691 976769 |
Updated error handling for ADMDataSetSaveOperation | Data flow threads were becoming stuck in an unsafe park state after ADMDataSetSaveOperation encountered a ConcurrentModificationException during realtime data flow execution. This has been resolved by adding exception handling in SaveStageProcessor to properly release the latch. | Decision Management |
| INC-D14025 | 985935 | Data migration pipeline timeout handling improved | The data migration pipeline from Production was failing during Data Export with SocketException errors, with REST Service DataSync taking 300 seconds against a 30-second DMConnectorTimeout. Investigation showed this was caused by insufficient timeout handling and missing wait shapes in the Data Export flow compared to Data Import. This has been resolved by updating the pyInitializeDataExport flow to introduce a Wait assignment before continuing to repository-connection validation/export. | Decision Management |
| INC-D1441 INC-D1181 |
973010 973532 |
Repository based case attachments corrected for email notifications | Email digest notifications from Prediction Studio were being received but the attached CSV files were appearing as error files and could not be opened properly when repository-based attachments (pegacloudfilestorage) were being used. Investigation showed that the GenerateMailAttachment activity was only setting the pycategory field on the Link-attachment record while leaving the pxStorageType field blank, causing the content retrieval logic to fail in determining the correct handler for repository-stored files. This has been resolved by updating the pzGenerateMailAttachment activity to conditionally populate the pyStorageType field. |
Decision Management |
| INC-D14552 INC-D11367 |
984866 982583 |
Data ingestion timeout and count mismatch issues resolved | Data ingestion operations were experiencing DriverTimeoutException errors occurring after one minute timeouts during Cassandra upsert operations, accompanied by "Query timed out after PT1M" messages in the UpsertStatementExecutionException stack trace. Additionally, reconciliation processes were showing count mismatches between expected and actual record counts after data ingestion, with subsequent reconciliation runs sometimes displaying correct counts without requiring data copy operations. Investigation showed these issues were caused by timeout handling problems in the Cassandra driver and data consistency issues during high-volume ingestion operations. This has been resolved. | Decision Management |
| INC-D16104 | 987078 | Troubleshooting documentation added for partition count mismatch between pxResponsesStream and InteractionFiles datasets | When importing InteractionFiles from a lower environment with fewer partitions into a production environment where the Kafka topic has been created with more partitions, a partition count mismatch may be seen between the pxResponsesStream and InteractionFiles datasets. To address this, comprehensive troubleshooting documentation has been added to provide clear guidance on regenerating the InteractionFiles dataset to match the actual number of partitions in the pxResponsesStream topic and recreating affected summary datasets to restore proper backfill operations. Refer to "Inconsistent Number of Partitions in pxResponsesStream and interactionFiles Dataset" for more detailed information. | Decision Management |
| INC-D1645 INC-D3558 INC-D9444 |
973460 979730 979466 |
Deserialized JSON date field handling updated | Data flows processing JSON records with date fields were failing when attempting to save deserialized date properties to DDS datasets, resulting in NullPointerException errors. This was traced to null values during date field conversion in the JSON data transform process when using TimeOfDay properties in the Strategy Result class, and has been resolved with an update to enhance logging, null date handling, and exception messages. | Decision Management |
| INC-D16966 | 986571 | Dataflow configuration settings properly recognized from JVM arguments | Dataflows were continuing to execute despite setting JVM arguments to disable them, preventing database refresh operations that required all dataflows to be stopped. Investigation showed this was caused by the system not properly recognizing the configurable dynamic system settings for dataflow max_active_runs when specified as JVM arguments rather than DSS settings, and this has been resolved. | Decision Management |
| INC-D17007 | 987867 | IH summary partial key read performance optimized | Outbound decision runs were experiencing significantly longer execution times than expected. This was traced to Interaction History summary read operations which had redundant client-side CPU processing that scaled with the number of keys defined on the summary. This has been resolved by optimizing the BrowseByKeys processing logic to eliminate the redundant processing overhead. | Decision Management |
| INC-D17662 | 994825 | Work link email access authentication fixed | After update, work links received in emails were returning 403 Forbidden errors which prevented users from accessing cases directly from email notifications. The error message "Unauthorized request detected: pyActivity is outside Encrypted parameter" was generated. This was caused by changes in the URL encryption validation logic that incorrectly flagged legitimate work link requests as unauthorized. To address this, the pxWorkLink rule and associated encryption validation have been updated to properly handle encrypted URL parameters while maintaining security requirements. | Decision Management |
| INC-D18972 | 990458 | Action analysis service authentication header handling fixed | Action Analysis Service Client was receiving 401 unauthorized errors when accessing the configurations endpoint. This was caused by the client not passing the required authorization header for configuration requests due to a missing entry in gradle/engineProjects.gradle, and has been corrected. | Decision Management |
| INC-D20792 | 994584 | Data migration export process corrected for interval-enabled configurations | Data migration pipelines were getting stuck in the Monitor Progress stage during the Initiate Data Export phase. Investigation showed this was caused by a missing skip ADM check in the data migration path when intervals were enabled, which created an empty clipboard reference that led to status check failures in the pyExportDataFlowRunStatus flow. This h | Decision Management |
| INC-D21197 | 1002314 | Email processing restored after agent queue handling improved | Outbound emails were getting stuck in processing status without completing or failing, requiring manual intervention to restore normal operations. Investigation showed this was caused by a dataflow progress tracking mechanism that returned stale progress information when checking non-existent runs on the same thread. This has been resolved by ensuring the pxLoadProgress activity never returns stale progress for deleted runs, preventing the SendEmailChild agent from getting stuck in processing state. | Decision Management |
| INC-D21366 | 1001068 | Handling updated for value finder simulation date casting | Value Finder simulations were failing with "InvalidValueException: Cannot cast to date the value 2026-05-18 00:56:56" errors during data flow execution. This occurred when date properties were stored in App-SR class instead of the expected Data-PxStrategy class format, and has been addressed by saving pxObjClass to files in specific data sets to ensure properties are deserialized using correct context. | Decision Management |
| INC-D21427 | 997463 | Data migration thread handling updated for ADM factory | The ADM Migration Import DataFlow was running at only 1 record per second with single thread execution, causing excessively long migration durations. This was traced to the DataFlow not applying RunOptions configuration for thread count and batch size, and was due to the DSS values not being honored for the path when import ran with repository persistence enabled. This has been resolved with an update to ensure the system considers requestor and batch size DSS values when configured. | Decision Management |
| INC-D21731 | 997223 | PDF preview functionality restored in Pulse comments | PDF attachments in Pulse comments were not displaying image previews or thumbnails. This was caused by compatibility issues with the IcePDF API when running on Java 21 environments. This has been resolved by replacing the IcePDF API with the Apache PDFBox API, which provides full Java 21 compatibility and properly renders PDF poster images for preview display in Pulse comments | Decision Management |
| INC-D2189 | 973027 | Property chain access restored for platform pages in SSA mode | Strategy components were unable to retrieve property values from platform pages when using reference chains like Request.Payload.Customer.Subscriptions in SSA/GOS execution mode, causing an issue where an empty page list might be returned when the pages were actually present. This was traced to the nested property resolution handling for chained property access in the SSA execution environment, and has been corrected. | Decision Management |
| INC-D22143 | 997736 | Error handling updated for DataFlow resiliency | DataFlows with failureThreshold configured were remaining in In-Progress status when failures occurred within threshold limits, requiring node shutdown to recover. This was caused by the resiliency layer not checking completion status or posting terminal signals when failures were within threshold, leading to the in-flight request counter not being decremented. This has been resolved by ensuring count down latches do not leak when errors are encountered in secondary sources. | Decision Management |
| INC-D2309 | 974641 | Chart image export functionality restored | After update, the chart image export functionality was producing errors or generating blank PNG files when attempting to save charts as images. This was caused by the SVG→canvas conversion relying on an older synchronous call which could lead to the form being submitted before rendering completed. To resolve this, the FusionCharts export helper has been updated to work with the newer canvg API and the export flow has been made asynchronous so the image is rendered before form submit. | Decision Management |
| INC-D23714 | 998778 | Updated error handling in Globally Optimized Strategy execution | Campaign DataFlow execution was failing with NullPointerException "Cannot read field 'state' because 'v' is null" in ExecutionProfileRegistry during Globally Optimized Strategy (GOS) execution. This has been addressed by making profile-registry handling null-safe and initializing/guarding the registry access path. | Decision Management |
| INC-D23783 | 1000695 | Added handling to avoid data flow stuck threads | Data flows were experiencing NPE exceptions in pyProcessSLA operations and becoming stuck in inconsistent states when the PRPulseDispatcher class terminated the same requestor that the data flow was using for pyProcessSLA runs. This was traced to a race condition where two processes were borrowing the same requestor, leading to stale PRPC thread failures including StaleThreadError exceptions. This has been resolved by updating the handling for stale thread exceptions to mark the data flow as failed instead of ending in a stuck state. | Decision Management |
| INC-D2667 | 976321 | Job scheduler check added for archive folders before purge | Daily job scheduler RemoveImportJobFilesAndProcesses activities were failing due to missing ArchivedDataFiles folders when data jobs were created but no ingestion occurred. This was caused by the system attempting to purge archive folders that were never created, and has been resolved by implementing proper folder existence checks before attempting purge operations. | Decision Management |
| INC-D2893 | 975128 | Keyspace prefix configuration resolved for usage metrics | Applications were experiencing connectivity issues due to the system defaulting to connecting to an unprefixed usage_metrics keyspace even when a prefix was configured in the Cassandra settings. This has been corrected. | Decision Management |
| INC-D331 INC-D15984 |
978001 1002117 |
Adaptive model predictor display limit increased | Adaptive model reports were displaying only 500 predictors in the predictor importance tab despite having more than 500 predictors available in the model. This was caused by hardcoded limits in the pzgbpredictorinfo and pzpredictorinfo data retrieval queries, and has been resolved by increasing pyMaxRecords from 500 to 2000 for predictor reports. | Decision Management |
| INC-D3777 | 988605 | Real-time data flow event cleanup performance optimized | Cleanup operations for the pr_log_dataflow_events table were timing out due to large data volumes generated by dynamic scaling of real-time Data Flow nodes creating frequent lifecycle and partition rebalance events. This has been resolved by optimizing the cleanup query and implementing batch deletion of old lifecycle events and dataflow errors to prevent query timeouts. | Decision Management |
| INC-D3882 | 976060 | PMML mining model output field population corrected | Issues were seen with Predictive Model Markup Language (PMML) models generated via sklearn2pmml conversion where target fields and output fields were not being populated correctly during model execution. This was traced to improper field mapping during the PMML conversion process, and has been resolved by updating the field population logic. | Decision Management |
| INC-D3944 | 973901 | Kafka dataset migration compatibility updated | Publishing messages to Kafka Data Sets was failing consistently with the error "IllegalArgumentException: No enum constant com.pega.dsm.dnode.api.dataset.kafka.MessageHeaderDataFormat" after moving the Kafka topic from one data center to another. The error occurred during message configuration extraction when Pega attempted to validate the Message Header Data Format, with the system expecting values like KVLIST or Custom but encountering an unsupported enum constant at runtime. This was traced to a compatibility issue when Kafka data sets created in Pega 8.5 were imported into Pega 8.6+ environments, and has been resolved by addressing the enum validation logic to properly handle legacy data set configurations. | Decision Management |
| INC-D4587 | 976297 | NLP model name passed to resolve runtime exception | Manual testing of Text categorization Topic models in Prediction Studio was resulting in error pages and system hangs, while the same functionality worked correctly in Dev Studio. This was traced to the model class name not being passed properly during testing, resulting in a PRRuntimeException. To resolve this, the model class name will be passed as a parameter. |
Decision Management |
| INC-D5272 | 976234 | Google Pub/Sub dataset topic handling updated | Google Pub/Sub datasets were failing to function properly when topic configurations used application settings, with the system using outdated topic names even after application setting updates and node restarts. This was traced to the pyTopicName property being set during connection testing and not being updated when application settings changed. This has been resolved by ensuring topic names are dynamically resolved from current application settings rather than cached values, with a fallback to legacy topic name behavior. | Decision Management |
| INC-D6631 | 976646 | Proposition filter explanation values corrected for page collections | When evaluating proposition filters with conditions against page lists accessed through property reference chains, Engagement Policy explanations were displaying an accurate filter status, but the actual value was consistently displaying as "0" instead of showing the correct number of pages in the page list that satisfied the criteria. This has been resolved by correcting the explanation calculation logic so that actual values now properly reflect the number of qualifying pages in the collection when accessed through property reference chains. | Decision Management |
| INC-D7162 | 981387 | Bias check functionality restored for symbolic columns with mixed data types | Ethical bias simulation reports were returning empty results when analyzing symbolic columns that contained both numeric values and missing data. This was traced to the system incorrectly converting symbolic columns to numeric columns during data processing when missing values were filtered out, preventing the bias analysis from following the correct computational path for symbolic data types. This has been resolved by modifying the bias analysis logic to preserve the original column type of the bias field instead of inferring the type based on the content of the selected bias field after filtering. | Decision Management |
| INC-D7585 | 977428 | Monitoring message handling corrected | Messages were being lost during monitoring processes, causing discrepancies in response counts. This has been resolved with an update to ensure partitionOffsets are retained after truncation instead of being cleared. | Decision Management |
| INC-D7910 INC-D15985 INC-D7573 |
984113 986684 984110 |
Data flow validation logic updated for accurate record counting | Count mismatches were seen between processed record counts and input record counts, causing post-validation failures. Investigation showed this was caused by the PostValidation logic incorrectly relying on pySuccessfulRecords instead of pyProcessedRecords when validating data flow progress. This has been resolved with an update to rely on pyProcessedRecords so validation and reporting are aligned with the checkpointed partition progress to ensure accurate record counting. | Decision Management |
| INC-D8368 | 978543 | BigQuery WIF authentication flow completed | The authentication process was failing to complete properly when accessing BigQuery using Workload Identity Federation (WIF) configuration. This was traced to missing handling for the impersonation of the Foundry Application service account, and this has been resolved. | Decision Management |
| INC-D8370 INC-D16213 |
987146 993640 |
Explainability extract processing enhanced for embedded strategies | Explainability Extract operations were throwing exceptions when executed on top-level Globally Optimized Strategies (GOS) containing embedded strategies with data join components that reference other components for iteration. This was traced to embedded strategies being unable to process strategy result pages wrapped in execution audit-specific wrappers, and has been resolved by adding support for embedded strategies to handle strategy result pages with and without execution audit wrappers equally. | Decision Management |
| INC-D8475 INC-D9701 |
978261 982549 |
GOS always-on profiling execution errors resolved | After update, both scheduled outbound runs and real-time events were failing with ArrayIndexOutOfBoundsException errors indicating "com.pega.decision.compute.ssa.exception.DecisionRuntimeException: Message Caused by ArrayIndexOutOfBoundsException. Possible components or rules causing exception: [mzCheckPropositionFilteredForTestMode]" with detailed evaluation stack traces showing componentExitLog and trackInput operations failing during strategy execution. Investigation showed this was caused by incorrect always-on profiling metadata being assigned to non-inlined strategy components, which resulted in wrong processing when execution was being recorded into execution profiles. This has been resolved with an update to generate correct profiling metadata and add the DSS "decision/strategy/gos/enforceComponentBoundaries" that forces the GOS compiler to apply optimizations only within component boundaries, preventing cross-component optimization propagation when enabled. | Decision Management |
| INC-D8642 | 979102 | Data Decision Store interface behavior corrected | The Data Decision Store UI had unexpected table scrolling and display issues when navigating through the specified steps in the application. This was caused by Decisioning landing page table overflow and has been corrected by adjusting the CSS targeting/scroll container for the deployment view. | Decision Management |
| INC-D8721 | 990880 | File dataset browsing capability restored | Datasets were showing zero records when browsing despite having files available in storage, preventing access to existing data. Investigation showed this was caused by missing .directory metadata in the meta directory structure that shadows the original file structure for performance optimization. This has been resolved by implementing a directory meta structure update mechanism that ensures consistent and recoverable state, along with a recovery activity to fix issues in existing structures. | Decision Management |
| INC-D885 | 989515 | Data flow file creation reliability enhanced | A transient failure during WriteDataToInteractionFiles data flows file creation/write/flush could cause the whole batch to be treated as non-retryable and effectively dropped. To address this, the legacy eager empty file creation has been eliminated, failed records are now marked retryable so the batch can be retried, and empty files no longer produce stray .meta files. | Decision Management |
| INC-D9234 | 981154 | Customer Decision Hub (CDH) explainability and upgrade testing enhanced | An update has been made to SetProperty shape instrumentation to ensure full visibility and auditability in explainability operations, and the CDH update analyzer has been improved with preupgrade testing capabilities to proactively identify function issues during version transitions | Decision Management |
| INC-D9517 | 986194 | Data dictionary relevance scope refined | After update, searches were returning increased relevant record counts with relevance spanning across multiple classes instead of being restricted to intended classes. This has been addressed with updates in auto tagging to suppress the creation of relevancy for the properties of parent classes in the child class. | Decision Management |
| INC-D9522 INC-D13100 INC-D17995 |
985985 988816 988824 |
Impact analyzer data display restored | Impact Analyzer displays were empty in the Impact Analyzer interface despite having run the pxSyncActuals activity and verified results through data flows. Investigation showed this was caused by incorrect GroupedValue filtering when filter conditions were applied to empty fields for records. This has been resolved by updating the GroupedValue filtering logic to properly handle filter conditions on empty fields. | Decision Management |
Low-Code Application Development
26.1 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C21025 | 954104 | URL error message security updated | In order to improve security, the ShowMessage HTML rule in @baseclass and Code-Pega-List has been updated to remove requestor and operator details. | Low-code App Development |
| INC-C21097 | 949218 | Application version creation deployment error messaging improved | A failure occurred during the 'create application version' task of the revision deployment process despite successful deploy branch completion, resulting in empty output parameters. Investigation showed this occurred if the branch had checked out rules, and has been addressed by introducing a new Pega API error code which includes the message "You must check in all branch rules before merging" along with a fail code to better diagnose and remediate the issue. | Low-code App Development |
| INC-C21581 | 945948 | Performance statistics table bloat prevented | Application requestor metrics for Customer Decision Hub applications were generating excessive data in the pr_perf_stats table despite configured retention settings, requiring manual table growth management and causing failure events for ClusterAndDBCleaner. This has been addressed by improving the performance of the pyClusterAndDBCleaner which is responsible for purging data from the pr_perf_stats table. | Low-code App Development |
| INC-C22921 | 974197 | Resolved error for Ajax container tab deletion | Ajax container tabs were experiencing null pointer exceptions when attempting deletion operations. This was caused by data-record-key attributes not being generated for tab elements during page refresh operations, and has been resolved by setting recordKey for tabs on refresh. | Low-code App Development |
| INC-C24072 INC-C28803 |
948364 954857 |
Null handling updated for case creation | The create flow was not being automatically added when creating case types in workspaces, resulting in save errors. This was caused by incomplete workspace initialization logic during case type creation, and has been resolved by adding null checks for ThreadContainer.get() and a check whether the operator ID .pyuseridentifier is empty. An additional issue with null pointer errors being generated due to uninitialized requestor components when accessing developer preference data pages has been resolved by improving exception handling to prevent unnecessary logging of non-functional errors. | Low-code App Development |
| INC-C29204 | 947191 | Handling added for empty PreferenceOperatorID | Users encountered "Unable to load data page D_pzPreferenceStore. Required parameters: PreferenceOperatorID cannot be blank" errors when accessing the clipboard after updating operator locale settings. This has been resolved by adding handling for scenarios where OperatorID.pyUserIdentifier is empty. | Low-code App Development |
| INC-C31754 | 947143 | Copy/Merge RuleSet utility updated for conflicts | The Copy/Merge RuleSet utility was not displaying the list of conflicted rules during ruleset version operations. This has been resolved by updating the refactor utility's conflict detection mechanism. | Low-code App Development |
| INC-C33268 | 943753 | GetSiblings activity security improved | Cross-site scripting protections have been updated for the GetSiblings activity. | Low-code App Development |
| INC-C33901 | 945757 | Coverage report export functionality restored | Test coverage reports with names beginning with underscore characters failed to export, showing success messages without generating downloadable files. This has been resolved by updating the export logic so that report generation is skipped only if the pyLabel field is empty. | Low-code App Development |
| INC-C36061 | 958921 | Node data page preference loading access errors fixed | After update, access denied errors were generated for D_PZCACHEDPREFERENCE during portal launch and page load operations. This was caused by missing role context resolution for developer preferences, and has been resolved by updating the preference loading mechanism to properly resolve role contexts and access permissions for cached preference data pages. | Low-code App Development |
| INC-C41441 | 953244 | Empty values removed from Operator profile | Operator profiles were accepting and persisting empty skill entries, allowing invalid configuration data to be saved. To resolve this, empty skills will be removed from the operator page during validation. | Low-code App Development |
| INC-C42580 | 955077 | Decision table header rendering updated | Decision table headers were not rendering correctly when using specific function combinations in property headers. The issue manifested when switching between different function expressions like @startsWith with @substring versus @whatComesAfterFirst. Investigation showed this was caused by improper parsing of nested function expressions in the decision table header rendering logic, and has been resolved by modifying the function used in the decision table to ensure proper rendering. | Low-code App Development |
| INC-C42814 | 968420 | Lock and roll application instance association fixed | Lock and Roll processes were incorrectly associating new application instances with previously locked ruleset versions when attachments were added during the process. This was caused by the attachment handling interfering with the proper version association logic during ruleset locking and rolling operations, and has been resolved by updating the application instance association logic to remove ruleset version from rule page if the class is Rule-Application. | Low-code App Development |
| INC-C44532 | 956968 | Division name validation handling updated | Application creation was failing with ruleset validation errors when division names contained spaces while using the generate division layer option. This was caused by inconsistent space handling between different validation activities, where one removed spaces while another retained them. This has been resolved by standardizing the space handling logic across all division name validation processes. | Low-code App Development |
| INC-C45469 | 965346 | pyRelativePath property serialization issue resolved | Applications were experiencing PageCannotBeSerializedForPassivationException errors with the message "Property not serializable: pyCorrList.pxResults(1).pyRelativePath" when sending correspondence with the Tracer enabled, causing screens to hang and preventing rule access. Investigation showed this was caused by the pyRelativePath property being added to clipboard pages during rule checkout but not being present in the Rule-Obj-Corr class hierarchy or its parent classes, making the property non-serializable during passivation. This has been resolved by adding the pyRelativePath property to the @baseclass to ensure proper serialization support across all rule types. | Low-code App Development |
| INC-C45874 | 957281 | Multiple branch development ruleset save improved | While attempting to create multiple branches consecutively through the branch development preferences window, an error occurred after creating the second branch when trying to create the third. This was traced to application rules being saved to incorrect branch rulesets during the multi-branch creation process, leading to ruleset selection conflicts. To address this, pzAddBranchToApplication has been updated to use the standard Rule-!Save function and not call pxUpdateRecord. | Low-code App Development |
| INC-C47590 | 960215 | Skin rule preview functionality restored | After update, preview panels were displaying blank content when opening skin rules. This was traced to the cross-site scripting filters which passed the converted ascii value for the parenthesis and blocked the Preview from loading, and has been resolved by replacing this ascii value with parenthesis in the pzSelectivePreview activity. | Low-code App Development |
| INC-C50733 | 959368 | Date formatting error resolved | Email listener threads were encountering ParseException errors and remaining in running state, preventing processing of unread emails from the inbox. This was traced to incorrect date pattern formatting for elapsed time in the pyDeprecationDate processing within the GenAI Connect Rule, and has been corrected. | Low-code App Development |
| INC-C51112 | 963220 | Email validation rule enhanced to require domain names | The ValidEmailAddress rule was accepting email addresses without domain names (e.g., xxx@xxxx), which are not valid email formats for production use. This has been corrected by adding top level domain validation in the ValidEmailAddress edit validate rule. | Low-code App Development |
| INC-C51416 | 965510 | Font size scaling issue resolved in RTE-generated Word documents | When using Rich Text Editor (RTE) properties with custom font styling and sizes in Microsoft Word document templates, the generated documents were experiencing incorrect font size scaling where the configured font size was being reduced by a factor of 0.75. This was caused by improper handling of font size conversion between the RTE formatting and the Word document generation process which applied an unintended scaling factor during the conversion. This has been corrected by updating the logic to maintain the original formatting specifications from the Rich Text Editor. |
Low-code App Development |
| INC-C52261 | 966731 | Admin Studio requestor management error corrected | Users were encountering "Node id cannot be blank" runtime exceptions when accessing RequestorManagement and other functionality within Admin Studio. This was caused by the pzIsProfilingStarted activity expecting NodeID and RequestorID as required parameters that were not being passed from the pzRequestorDetailsGrid section, and has been resolved. | Low-code App Development |
| INC-C53140 | 965779 | Branch preferences auto-disable implemented | Applications were experiencing broken processes when merged branches were removed from the application stack while branch preferences remained enabled, causing "Branch development preferences are in an invalid state" errors during data record operations. This was caused by branch preferences not being automatically disabled when branches were removed from application definitions. This has been resolved by turning off branch preferences when branches are removed from the application stack. | Low-code App Development |
| INC-C53874 | 965858 | Corrected configuration settings access in system runtime context | Configuration settings were not returning valid values when accessed from System Runtime Context, particularly in job schedulers and queue processors. This was caused by improper context handling when accessing configuration settings from system-level processes, and has been corrected by updating ConfigurationHelper.java. |
Low-code App Development |
| INC-C55128 | 965125 | Workspace creation enabled for numeric-prefixed operator IDs | Operators with IDs starting with numbers received "Workspace ID cannot start with a number" errors when attempting to enable workspaces. This was caused by the pzGetUniqueWorkspaceID function creating invalid branch IDs that failed downstream validation, and has been resolved by prepending a "W" prefix to workspace IDs for numeric-starting operator IDs, ensuring proper validation compliance. | Low-code App Development |
| INC-C55854 | 967376 | Excel decimal value parsing precision corrected | Excel file parsing was altering decimal values by adding extra zeros, with values like 0.00001 becoming 0.000010 in the clipboard. This was caused by the internal clipboard API treating decimal values as doubles and converting them to BigDecimal during the parsing process, which added trailing zeros. This has been resolved by implementing proper decimal handling in the ExcelUtils.java parsing process to preserve original precision. | Low-code App Development |
| INC-C56696 | 970564 | Compliance score purge error handling improved | Systems were generating EXCP0001 exceptions regularly when the pzPurgeComplianceScore activity attempted to delete non-existing compliance score instances. This has been resolved with an update that enables mutual exclusion for agent queue execution, ensuring the agent runs on only one node at a time. | Low-code App Development |
| INC-C57070 | 967145 | Cross-site scripting protections updated for tracer settings | Cross-site scripting protections have been updated for the TraceOptionsDialog stream. | Low-code App Development |
| INC-C58030 | 969315 | Corrected currency control duplicate symbol display | After update, currency controls were displaying currency symbols twice after users entered values and clicked outside the field. This was seen when an alternate “other currency symbol” was configured from the Presentation tab. To resolve this, the alternate-symbol branch has been removed during display formatting and always renders using pyCurrencySymbol, which prevents duplicate symbol output for the affected scenario. | Low-code App Development |
| INC-C58048 | 970985 | Corrected portal data type editing freeze on operator icon click | Data type editing sessions were freezing when clicking the operator account menu without moving the cursor away, specifically affecting the top record on screen while subsequent records remained functional. This was caused by missing context setting in the grid action handler, and has been resolved by updating the pzPega_ui_grid JavaScript rule to properly set context on the grid div during pzdoGridAction execution. | Low-code App Development |
| INC-D10635 | 986082 | Warning logs and fallback added for lost or invalid production level | In order to assist with troubleshooting development environments where Production Level was sporadically being set as empty or 0 in the pxProcess page, a validation check has been added along with warning logging. If an invalid level is found during validation, it will fall back to the System rule value. | Low-code App Development |
| INC-D1150 | 971587 | Cross-site scripting updated in App Studio | Cross-site scripting (XSS) protections have been updated for App Studio. | Low-code App Development |
| INC-D12079 | 984548 | Application definition ruleset stabilized | When deleting branches while having a different branch selected, the application definition rule would change its ruleset from the base application name to the currently selected branch ruleset, potentially causing application access issues. Investigation showed this was caused by the pxChooseBestRuleSet function incorrectly selecting branch-specific rulesets during branch deletion operations. This has been resolved by ensuring application definition rules maintain their proper base ruleset assignments regardless of currently selected branch context during deletion operations. | Low-code App Development |
| INC-D13186 | 983338 | Improved LogViewer resource release | Resource closure has been updated for the LogViewer HTML rule to ensure file input streams are consistently released. | Low-code App Development |
| INC-D15016 | 988409 | Console error resolved for apostrophe handling | Applications were experiencing console errors when field values contained apostrophes. This has been resolved by updating the character encoding and escaping mechanisms in the UI controls to handle apostrophes and other special characters. | Low-code App Development |
| INC-D15512 | 986748 | Section refresh functionality restored for conditional local actions | After updating from Pega 7, clicking buttons configured with both "Refresh this section" and conditional local actions defined in separate classes resulted in the message "Error (Please contact system administrator)" . This was traced to a loss of base reference in the underlying JavaScript framework, and has been resolved by implementing a new configuration flag "pega.u.d.skipIECheck" in the webwb_pzpega_ui_doc_domutils.js rule's getBaseReference method, which can be explicitly set to true from UserWorkForm to bypass the problematic reference check and restore proper section refresh behavior. | Low-code App Development |
| INC-D16505 | 1005603 | Database table mapping errors resolved for Knowledge Buddy environment | Applications were experiencing database table mapping errors in the Knowledge Buddy environment, with usage data failing to save due to schema mismatches and too many properties being mapped to the Log-Usage table. Error messages indicated "Database-BadTableMapping-TooManyProperties". This has been resolved by updating the database table schema to accommodate the additional GenAI performance metrics properties | Low-code App Development |
| INC-D18113 | 989898 | Usage reporting data collection restored | The UVU Daily Usage report stopped collecting data after applying updates. This was caused by the sppr_aggregate_usage stored procedure containing unqualified table references that failed when executed by users with different default schemas. and has been resolved by updating the stored procedures to include proper schema qualification for all table references. | Low-code App Development |
| INC-D2165 INC-D9514 INC-D16973 |
979908 981276 988779 |
System information button function corrected | After update, the System Information button was failing to load and displaying the error message "No JMS Base Context Found on this Platform" along with JsonGenerationException errors when attempting to access system diagnostic information through Dev Studio. This was caused by conflicts between JMS and StAX XML processing implementations, particularly affecting JBoss EAP and WebSphere application server environments, and has been resolved by adjusting XML declaration stripping and XML serialization configuration, with an additional work applied for WebSphere environments paired with IBM JDK to ensure complete compatibility across all supported application server platforms. | Low-code App Development |
| INC-D2315 | 974400 | Application wizard division class validation improved | The New Application wizard was incorrectly validating class structures when divisional layers were included in the configuration, missing the divisional class from the validation sequence. Investigation showed this was caused by the validation logic not accounting for divisional layer classes in the class hierarchy check. This has been resolved by updating the validation sequence to properly account for Division and Unit class layers when checking for existence of a class. | Low-code App Development |
| INC-D24444 | 997750 | Proposition filter validation accuracy improved | Under certain circumstances, the proposition filters were being created with incorrect rule details, which caused the Revision Integrity check in Ops Manager to report deployment failures even though the change requests were completed correctly. This was most commonly seen if When rules and strategies shared the same name. To resolve this, the expected-results configuration was updated so a visibility check is no longer evaluated on the client side. This prevents the incorrect metadata from being generated and allows the integrity validation to pass as expected. | Low-code App Development |
| INC-D27517 | 1001615 | Queue processor maintenance updated for cross-database compatibility | After update, queue processor maintenance jobs were failing on non-PostgreSQL databases, including Microsoft SQL Server environments, during the execution of a new delayed item metrics calculation step that was introduced as part of internal queue processor monitoring enhancements. These were traced to database-specific datetime formatting in a SQL query within the pzQueueProcessorMaintenance activity that was incompatible with MSSQL's datetime conversion requirements , and which generated the error "There was a database problem when performing an RDBExecute: code: 241 SQLState: S0001 Message: An error occurred during the current command (Done status 0). Conversion failed when converting date and/or time from character string." This has been resolved by updating the SQL statement for queue processor metrics to use the ANSI CURRENT_TIMESTAMP keyword, ensuring cross-database compatibility for the delayed item metrics functionality. | Low-code App Development |
| INC-D5197 | 977916 | JSP tags fixed in table headers | Sections containing non-optimized tables were failing to save when JSP tags like "<pega:include name=\"pyLabel\" type=\"Rule-HTML-Property\"/>" were used in column header labels. This was traced to the GenerateCellContent Rule-Utility-Function not properly handling JSP tag processing in table header contexts, and has been corrected. | Low-code App Development |
| INC-D5425 | 979637 | Word content control functionality restored | Word content controls in document templates were not functioning properly after update. This was an unintended side effect of work done on the parseAndPopulate function of the docxGenerator API which resulted in compatibility issues with the updated docx4j library. This has been resolved by updating the code with a condition which will extract content if Word content control is used. | Low-code App Development |
| INC-D6811 | 987116 | Page validation error resolved in tracer viewer | Page validation was failing in the PZINITIALVALIDATIONFORPERFORMACTION activity with the error message "DeclarePageReference' does not match top of stack" appearing in the tracer viewer. Investigation showed this was caused by a validation mismatch issue that could occur with the tracer accidentally changing the runtime state while collecting page messages if AutoPopulate and Declare Expressions were involved. This has been resolved with an update which ensures the tracer collects primary-page messages in a guarded way that temporarily disables the state-changing behaviors around that read. | Low-code App Development |
| INC-D6854 | 986713 | Updated grammar for Expression Builder | After update, referring to a list/group property in AdditionalInfo from ContainerPayload generated an error in the Expression Builder. This was due to the introduction of stricter validation for the Expression Builder functionality in design time which prevented chaining property access after a function call within a single expression during design-time validation, even though the runtime engine could still evaluate these expressions correctly. This has been resolved by updating the grammar to support the <> operator, single-quoted strings '...', dot (.) in function examples / qualified usage, slash ( \ ) escape handling in strings, and function patterns such as whatComesAfterFirst(.pyFilterName,'.'). | Low-code App Development |
| INC-D7400 | 980891 | Application save-as data type copying corrected | Application save-as operations were failing with "URL Alias is already in use" errors and not copying data types to newly created applications. Investigation showed the PreSaveAs path did not correctly update pyProductAlias before the copy/save logic executed, causing the downstream logic used an incorrect/old alias context, so related data type rules were not associated and copied as expected. This has been resolved with an update to ensure Save As updates the alias context correctly. | Low-code App Development |
| INC-D8785 | 980365 | Handling updated for requestor exception | The RequestorHealthDaemon was throwing ConcurrentModificationException errors and failing with stack traces showing "Invalid value for Requestor parameter" errors. This has been resolved by expanding the exception handling to cover the broader RuntimeException class needed for ConcurrentModificationException. | Low-code App Development |
| INC-D9504 | 983458 | Tracer security updated | Cross-site scripting protections have been updated for the tracer. | Low-code App Development |
Mobile
26.1 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B25606 | 903759 | iOS location services configuration consistency restored | The iOS app configuration was incorrectly maintaining the "Enable constant tracking when app is offline-enabled" setting as true even after the parent "Enable geolocation tracking" option was disabled, leading to inconsistent location service behavior. Investigation showed the visibility condition was not properly clearing the dependent setting when the parent option was disabled, and this has been resolved by ensuring both location tracking properties are properly synchronized when geolocation tracking is disabled. | Mobile |
| INC-C21926 | 957694 | Mobile create menu positioning corrected | The create menu overlay was displaying in incorrect positions when accessed from mobile footer navigation, sometimes overlapping with the footer or extending beyond screen boundaries. This was caused by forced width styling conflicting with dynamic position calculations, and has been resolved by updating the CSS positioning logic. | Mobile |
| INC-C37214 | 962060 | JavaScript execution continues during SLA message display | JavaScript functionality was becoming unresponsive when SLA messages were displayed, preventing task completion in mobile applications used for field work. This has been resolved by modifying the SLA message display mechanism to allow continued JavaScript execution. | Mobile |
| INC-C42855 | 955890 | Mobile modal button alignment fixed | Modal dialog buttons were incorrectly aligned on mobile devices, with both Submit and Cancel buttons appearing on the left side instead of Submit on the right and Cancel on the left. This has been resolved by adding the necessary CSS code to align pyModalButtons properly on mobile devices. | Mobile |
| INC-C53708 | 971402 | Back button visible for notification-launched cases | The back button was not appearing on some mobile headers when cases were launched through push notifications. This was traced to an uncaught exception which prevented the web views from loading after a notification was clicked in certain scenarios, such as users being logged out during notification receipt. As a result, the mobile header navigation was not properly initialized and there were no previous navigation items were available to return to. This has been resolved. | Mobile |
| INC-C58580 | 968181 | Mashup modal dialog positioning corrected for mobile screens | Modal dialogs containing file upload controls were appearing at the top of mobile screens in mashup scenarios, making the loading indicator invisible to users during file uploads. This was caused by hardcoded vertical alignment and padding styles in the pega_ui_modaldialog component, and has been resolved. | Mobile |
| INC-C58641 | 974499 | Mobile overlay display corrected | Applications were experiencing modal popups that occupied the entire height of mashup screens on mobile browsers when using the overlay configuration for validation alerts. This has been corrected with a phone-specific override so local-action modal wrappers/content don’t force full height. | Mobile |
| INC-D14695 | 992584 | Offline data persistence improved for child page list operations | When working offline, clearing child page lists within parent page list rows and attempting to save changes resulted in the cleared child list data not being persisted despite the save operation appearing to complete successfully. This has been resolved by updating the serialization logic to prevent missing child-page placeholders when saving sparse pagelists offline, and ensuring the removal flows guard against missing/null resolved assignment or remove payloads. | Mobile |
| INC-D1531 | 975489 | Mobile app worklist updates correctly synchronized | Mobile applications were not displaying updated worklist items after modifications were made to the List Item Information configuration. This was traced to synchronization issues between the mobile app and the updated pyWorkList configuration, and has been resolved by updating the Pega Rule-Mobile-View-List activities to refresh/generate the mobile list view state after save. | Mobile |
| INC-D20470 | 997896 | Mobile modal dialog display corrected | Modal dialogs on mobile devices were experiencing issues with rendering and positioning of modal content on mobile screens. This was an inadvertent side effect of previous work which introduced conflicting CSS rules that interfered with mobile-specific modal styling. This has been resolved by adjusting the CSS implementation to ensure proper modal dialog behavior across all mobile device types. | Mobile |
| INC-D2050 | 988163 | Photo upload popup handling corrected for offline apps | Multiple attachment popups were appearing when uploading 2 or more photos/files using pxAttachContent control with action sets in offline-enabled applications. This has been resolved by adding a guard to prevent multiple attachment pickers from being launched during multi-file/photo uploads in the Hybrid Client attachment control. | Mobile |
Project Delivery
26.1 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C29597 | 950783 | OpenID Connect documentation enhanced for Azure integration | The documentation for configuring the identity provider for an OpenID Connect SSO authentication service has been updated with information about how claims are populated differently based on UserInfo endpoint configuration. | Project Delivery |
| INC-C30051 | 947213 | Documentation updated for SSO session management | The documentation for specifying preauthentication and postauthentication activities for an OpenID Connect SSO authentication service has been updated to clarify supported SSO configuration practices, specifically that it is possible to dynamically update the user’s role list by using a postauthentication activity, but it is not possible to change the Access group of an operator in an SSO postauthentication activity. | Project Delivery |
| INC-C30311 | 944292 | Case reference display documentation clarified for embedded data | The documentation for configuring common field settings has been updated to clarify that display-as-case-reference requires actual case reference properties rather than text properties with manual class configuration. If properties of types like Text, Integer, Decimal, etc., are configured to display as Case References, they will not function as true case references. This can lead to unexpected behavior in the UI. Only properties explicitly defined as Case Reference types should be used for this purpose to ensure proper functionality. | Project Delivery |
| INC-C30503 | 947344 | preventXSSInLabel documentation updated | The documentation for the preventXSSInLabel DSS setting has been updated to outline the use and security risks involved in the decision to prevent or allow HTML injection into a Label control. | Project Delivery |
| INC-C32328 | 945280 | Azure Entra integration documented | The documentation for creating a generation JSON web token profile has been updated to specify that if the identity provider is Microsoft Azure Entra, add x5t#S256 (the Base64url-encoded SHA-256 thumbprint of the X.509 certificate's DER encoding) to the header to prevent a 401 Unauthorized Error for OIDC from Microsoft Azure Entra. | Project Delivery |
| INC-C34811 | 958998 | Documentation clarified for expected UDF alert behavior | The UDF alert documentation has been updated to clarify that PEGA0167 alerts can occur as expected behavior following long idle periods, and represent normal system behavior rather than defects. | Project Delivery |
| INC-C35084 | 950945 | Data encryption documentation updated | The documentation for implementing and using the TextEncrypted property type has been updated with the information that the option to use a custom cipher for data encryption is deprecated as of the Pega Platform 24.2 release. In addition, an article with details to create a keystore for application data encryption has been made available to assist with choosing and applying a standard cipher. | Project Delivery |
| INC-C36265 | 953493 | Documentation clarity improved for Agile Studio integration | Documentation for integrating Agile Workbench with Pega Agile Studio has been updated to clarify that credentials may be obtained by contacting the administrator of the Agile Studio instance, and references an article with instructions for the administrator. | Project Delivery |
| INC-C41437 | 953180 | SSO best practices documentation updated | The SSO best practices documentation has been updated to note the importance of maintaining basic authentication for administrator accounts as a fallback in case of SSO failure. | Project Delivery |
| INC-C42022 | 955115 | Keystore URL documentation updated | The documentation for Configuring a keystore by using a URL reference has been updated to clarify that when a keystore is created by using a URL reference and the JSON Web Key keystore type, Pega Platform fetches the JSON web key set (JWKS) at runtime, and processes it depending on the content of the JWKS. | Project Delivery |
| INC-C42069 | 961303 | OAuth client registration documentation clarified | The OAuth 2.0 client registration documentation has been updated to explicitly clarify that Token Profile claim modifications affect UserInfo responses rather than access token content. | Project Delivery |
| INC-C42146 | 955777 | OAuth authentication profile documentation updated | The documentation for Configuring an OAuth 2.0 authentication profile has been updated to explicitly specify that scopes must be configured in identical order between the Authentication Profile and Authentication Service, and that all required scopes must be granted in the Identity Provider. | Project Delivery |
| INC-C47145 | 961912 | File listener documentation corrected for failed processing behavior | The documentation in Integration Types for using file listeners in has been updated to reflect the current system behavior of failed files being moved to the Completed directory when recovery is disabled, not the Work directory that was previously used. | Project Delivery |
| INC-C56117 | 968259 | Documentation updated for Rich Text Editor | The documentation for Configuring a Rich Text Editor control has been updated to specify that the Rich Text Editor supports Pega JSP tags only. All other JSP tags are removed. | Project Delivery |
Reporting
26.1 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C17807 | 926764 | Multiselect readonly display corrected | Optimized table multiselect controls configured as readonly were displaying as editable. This was caused by inconsistent handling in the renderControl function where multiselect controls did not follow the same readonly logic as other control types due to it being a a page-list type property. This has been resolved by implementing consistent readonly handling for multiselect controls in an optimized table. | Reporting |
| INC-C21667 | 959306 | BIX manifest count accuracy improved for nested structures | BIX extract manifest files were showing confusing and intermittently inconsistent values in pxTotalInsertsCount and pxTotalInstanceCount properties, with insert counts sometimes unexpectedly exceeding instance counts. Investigation showed this was caused by incorrect counting logic in the manifest generation process for chunked extracts with nested structures, and has been resolved by correcting the pxTotalInstanceCount manifest count calculation to accurately reflect the actual processed records when the extract includes a structure that has pagelist inside a pagelist. | Reporting |
| INC-C23231 | 949086 | Selection accuracy improved in engagement policy conditions | When searching for nested fields in Customer Decision Hub engagement policy conditions and selecting properties from search results, incorrect properties were displayed in the UI despite correct search results. This was caused by incorrect count handling in the searchResultMarkup function during deferred loading, and has been resolved by properly handling the count variable in the isDeferLoad condition of the searchResultMarkup function. | Reporting |
| INC-C25482 | 948109 | Percentage field export accuracy improved | Percentage field values displayed incorrectly when exported to Excel from insights, showing different values than what appeared in the original insight view. Investigation showed this was caused by incorrect handling of percentage formatting during the Excel export process in the Constellation framework, and this has been resolved with the addition of a toggle for saving percentages as decimals along with updating the handling for converting percentages to decimals. | Reporting |
| INC-C26363 | 941983 | Work queue count accuracy restored | Work queue counts displayed incorrect values in the Smart Dispute Portal dashboard. This has been resolved by updating the pyPopulateAssignmentStats activity with param.WorkGroup to properly handle empty work group parameters. | Reporting |
| INC-C29676 | 942673 | Dynamic property filter values display correctly | Filter values for dynamic properties, particularly those displaying current operator information, were not visible in the view filters interface. This was caused by the current operator ID value not being available on the client side for display purposes. This has been resolved by updating the filter display mechanism to properly retrieve and show dynamic property values in the TileHeader filter display. | Reporting |
| INC-C30200 | 945929 | Scheduled insights evaluate date filters correctly at runtime | Scheduled insight exports were producing identical data sets across multiple runs when relative date filters such as "Current day" were applied. Investigation showed this was caused by the system transforming relative dates into static values at the time of schedule creation rather than dynamically at each execution. This has been resolved by replacing the transformation of relative dates during the scheduling process with a new activity that dynamically converts relative date filters to appropriate static date literals using the current server datetime at the time of each scheduled export execution. | Reporting |
| INC-C31709 | 952832 | PDF margin settings corrected to allow zero values | PDF documents were not respecting explicitly set margin values of zero. Investigation showed the PDFUtilsImpl Java file contained a condition that applied default parameters when margin values were set to zero or less. This has been resolved by modifying the logic to properly honor explicitly set zero margin values in PDF generation. | Reporting |
| INC-C32126 INC-C25821 |
944269 959191 |
Table filter HTML tag display cleaned | HTML span tags appeared in optimized table filters when filtering integer columns with negative values. This has been corrected. | Reporting |
| INC-C32472 | 947607 | Caret symbol visibility restored in user views | The caret symbol was disappearing when specialists changed personalized views, preventing proper navigation between view options. This was caused by the parameter page not being properly forwarded during view transitions, and has been resolved. | Reporting |
| INC-C32508 | 945272 | Updated SearchResultsWorkOptions cloud environment status evaluation | The @Utilities.pzIsPegaCloud() function was returning false in non-production environments, causing controls like case search filters to not display the "Archive Items only" option. This has been resolved by updating the pzSearchResultsWorkOptions UI control condition. | Reporting |
| INC-C33003 | 948977 | KMAuthor access corrected | Users with KMAuthor access group could not use the "Summarize By" dropdown option in Knowledge Management Published Reports, while the same functionality worked for KMSysAdmin users. The access permissions for have been corrected to resolve this issue. | Reporting |
| INC-C34148 | 962670 | Cambria Math font rendering updated | PDF documents containing both Chinese and English characters were not properly displaying Cambria Math font content, resulting in missing or corrupted mathematical symbols and text. This was caused by ligature processing limitations in the PD4ML 4.0.19 library when handling complex font rendering, and has been addressed by introducing an enableLigatures parameter in the "pyPDFSettings" data transform that can be utilized to ensure proper Cambria Math font rendering in mixed-language documents. | Reporting |
| INC-C34367 | 947649 | Dashboard filter loading corrected | Dashboard landing page filters failed to populate with expected values after adding new data pages with "Allow querying any column" enabled. This was caused by incorrect data page rule resolution that invoked newly created data pages instead of the intended dashboard-specific data pages. This has been resolved. | Reporting |
| INC-C35444 | 947654 | Table result count refresh corrected | Table refresh actions updated table content but failed to update the displayed result count. This was caused by the refresh action on pyTableToolbar not updating the section containing the result count field, and has been resolved by adding a refresh to this section action on the refresh button. | Reporting |
| INC-C36386 | 955701 | Batch processor queue validation improved | Data was being pushed to the pySASBatchIndexClassesProcessor queue even when automatic updates were disabled. This was caused by DSS validation checks being applied at the processing end rather than when data was initially queued, and has been resolved by modifying the ModelChangeDispatcher to validate the automatic updates setting before queuing data. | Reporting |
| INC-C36544 | 951842 | Report data cleanup removes temporary data pages | The pxRetrieveReportData function accumulated temporary pages over time, leading to memory exhaustion and system instability. Investigation showed cleanup was not working as expected when a data page was involved, and this has been resolved by updating pxretrievereportdata to remove the temporary page in that scenario. | Reporting |
| INC-C37428 | 953323 | Report filtering performance optimized | Worklist item reports displayed missing filter values and experienced unusually long loading times in production environments. This was traced to redundant rule resolution calls when opening rules with available handles, and has been resolved by removing the unnecessary rule_resolve assignment and adding a resolution check for openRule action from pzGridOpenAction. | Reporting |
| INC-C38056 | 949848 | Table grid functionality restored after search operations | Table grids were becoming unresponsive after performing basic search operations, preventing hiding columns, accessing details, or performing other grid actions. This was caused by the pzDoGridPersonalize activity receiving invalid column numbers as NaN values during refresh operations after filtering, and has been resolved by updating the pyInitialOrder value retrieval from column objects in the templatizedgrid component to use the DOMParser API for safer HTML parsing. | Reporting |
| INC-C38289 | 949903 | Dashboard filter localization updated | Dashboard filter text including the "ALL" and "Clear All" options was not being localized. This has been corrected. | Reporting |
| INC-C38967 | 958664 | Handling updated for Azure BIX extract nested stream closures | BIX extract operations in CSV file mode were generating "Stream is already closed" errors in logs when run multiple times. This was caused by the Azure repository implementation closing the underlying fileOutputStream when the zipOutputStream was closed. To resolve this, the stream management logic has been updated to skip connection closure for an Azure repository as it’s handled by the zip output stream. | Reporting |
| INC-C39205 | 951259 | Database join functionality corrected with ABAC policies | Database queries failed with "invalid identifier" errors when joining classes that had ABAC policies applied. Investigation showed that the SQL generator incorrectly referenced column aliases from the wrong table context when ABAC policy conditions were applied to joined classes. This has been resolved by fixing alias resolution in report queries with right outer join when ABAC policy conditions are applied. | Reporting |
| INC-C40876 | 966069 | Table sorting functionality after filter changes restored | Table columns could not be sorted after saving a view with column filters and subsequently removing those filters. This was caused by gridObjJSON.gridTable.isDPEmpty incorrectly remaining true after filter removal, preventing sort operations. This has been resolved by properly updating the state parameter isDPEmpty based on the length of the filtered records. | Reporting |
| INC-C40950 | 963529 | PDF generation timeout handling updated | PDF generation processes were not terminating properly when exceeding configured timeout limits, with pd4ml processes continuing beyond the 1-minute timer threshold. This was caused by the timer starting after preprocessing rather than before, excluding preprocessing time from timeout calculations. This has been resolved by starting the timer before preprocessing to include all PDF generation time in timeout enforcement. | Reporting |
| INC-C41991 | 955907 | Lucene syntax support added for search | Lucene syntax search queries were failing due to conflicts with property level security mechanisms when property encryption was enabled. This has been resolved with an update to conditionally apply Lucene syntax with the pyLabel property for higher search scores only when the Data System Setting (DSS) EnableAttributeBasedSecurity is set to false. | Reporting |
| INC-C45896 | 960614 | Excel export consistency stabilized on Constellation for localized list | After creating a landing page in Constellation with a data page as the data source, configuring promote filters, and localizing column headers using field values, the Excel export functionality was producing inconsistent results when performed multiple times on the same list, with variations occurring in column order, column content, column name translations, and promote filter application. Investigation showed this was caused by the pyPageName not being properly maintained during the export process, and this has been resolved by copying the old pyPageName in the pzGetFiltersFromContent activity to ensure stable and consistent Excel export results. | Reporting |
| INC-C45919 | 955602 | Search configuration documentation corrected | The documentation has been updated to clarify that the "destructive_requires_name" setting is only required for Elasticsearch 8.x and later versions and does not apply to OpenSearch deployments. | Reporting |
| INC-C46150 INC-C43821 |
957460 959940 |
Chart drill-down functionality restored for date dimensions | Column chart drill-down operations were failing with HTTP 500 errors when date fields were used as chart dimensions. This was traced to the system incorrectly converting date values to epoch timestamps in the filter criteria during drill-down operations, and has been corrected. | Reporting |
| INC-C47259 | 965569 | Report definition grouping syntax error corrected | Constellation views with report definitions using "Include all descendant classes" were throwing SQL syntax errors when grouping by case type columns, displaying "syntax error at or near comma". This was caused by incorrect comma placement in generated SQL queries when multiple aggregate fields were present, and has been corrected. | Reporting |
| INC-C50968 | 960306 | commons-csv library updated | CSV file attachments were failing to index with NoSuchMethodError exceptions, preventing content-based search functionality. This has been resolved by upgrading the commons-csv library. | Reporting |
| INC-C51714 | 962405 | Work ID search functionality improved in Dev Studio | Work ID searches in Dev Studio were failing for certain formats like CC-C1903 because they did not match the hardcoded regex expression. Investigation showed that the regex pattern was not flexible enough to accommodate different customer work ID formats. To address this, the activity has been enhanced to read regex expressions from DSS to allow for customization. DSS : "Pega-SearchEngine", "indexing/workIdRegex" If no DSS provided, default "[a-zA-Z0-9-]+-[0-9]+" regex will be considered |
Reporting |
| INC-C52132 | 963024 | Optimized table date filter styling corrected | The "Filter by" section of an optimized table date column was displaying over the content above it. This was caused by incorrect CSS styling in the filter popup layout, and has been resolved by adding padding to correct the styling issue. | Reporting |
| INC-C52711 | 964719 | Filters cleared when changing tabs | Filters configured within specific tabs were incorrectly influencing other tabs in inline dashboard templates, causing unintended data filtering across multiple tab contexts. This was caused by shared filter state management across tabbed interfaces using the same data object source, and has been addressed with an update which will clear all dashboard filters so any promoted/active filters from the previous tab will not be carried over to the next tab. | Reporting |
| INC-C53463 INC-C60008 |
967647 970769 |
Aggregate function validation updated | After upgrade, reports and insights were failing with the error "You need to specify a property with the aggregate function: 'COUNTWITHNULL'" when attempting to execute report definitions or explore data functionality. Investigation showed this was caused by overly restrictive validation logic that incorrectly required a property specification for the COUNTWITHNULL aggregate function. To resolve this, the logic has been modified to allow COUNTWITHNULL aggregation without requiring any property specification. | Reporting |
| INC-C53493 | 962968 | BIX DDL generation permissions issue resolved | After update, BIX extract rules with Database Schema output format were failing during DDL generation with "Invalid output directory OR user doesn't have required permissions" errors. This was caused by incorrect S3 bucket validation during the DDL generation process, and has been resolved by bypassing S3 bucket validation during BIX database extraction operations. | Reporting |
| INC-C55301 | 965170 | Report format popup functionality restored | The Edit Report format option magnifying pop-up was not opening as expected. This was traced to a missing security validation in the popup invocation code, and has been corrected. | Reporting |
| INC-C57342 | 975241 | Corrected scheduled reports with timezone failure | After update, scheduled reports were failing with "unable to find instance" errors in multi-application environments. This occurred when the pyUpdateScheduledReportsWithCurrentTimezone activity was executed from one application context while the scheduled report shortcuts were created in a different application context, and has been resolved by modifying the timezone update activity to properly handle cross-application contexts so scheduled report shortcuts can be accessed regardless of which application context they were created in. | Reporting |
| INC-C57912 | 968110 | API errors resolved in experimental CWYD experience | The experimental Chat with Your Data (CWYD) experience was generating API errors when the EnableGenAIChatWidgetInExploreData feature toggle was enabled. Investigation showed that the pyGetExploreDataAIResponse activity was overriding the model configuration and always defaulting to the pega-default-fast model. As a result, updates made in the pySuggestAIInsight GenAI Connect rule were not being applied. This has been resolved by updating the pySuggestAIInsight connect rule to read the model properly and configuring it to use the pega-default-smart model. | Reporting |
| INC-C58002 | 966799 | Extract rule table name character limit corrected | Extract rules were preventing saves when table names reached exactly 30 characters, despite error messages indicating the limit should be 30 characters. This was caused by using a greater-than-or-equal-to comparison (>=30) instead of a greater-than comparison (>30) in the validation logic, and has been corrected to allow table names up to 30 characters in BIX database schema generation. | Reporting |
| INC-C58702 | 969715 | PDF export filename handling updated for special characters | PDF exports were displaying HTML entity codes in filenames when report names contained special characters such as parentheses, while Excel exports handled the same characters correctly. This was caused by improper HTML entity encoding during the PDF filename generation process, and has been resolved by modifying the handling for retrieving the report title for the PDF file name. | Reporting |
| INC-C58802 | 972622 | Screen reader accessibility improved for helper text overlays | Helper text configured as overlay local actions without the close icon was being read twice by screen readers. This was traced to duplicate accessibility markup in the overlay rendering logic, and has been corrected along with enabling "Disable clickaway" by default to improve the user experience. | Reporting |
| INC-C58957 | 969484 | Report sorting functionality corrected for top-ranked records | Reports were displaying incomplete results when sorting columns containing non-unique values while using the "top ranked" feature, causing records to disappear from the display unexpectedly. Investigation showed this was caused by changes made to the handling of sort parameters as part of disabling pagination, and has been resolved by adding an "if" condition in the pzGridSortPaginate activity to properly manage sort order and type parameters when pagination is not enabled. | Reporting |
| INC-C59359 | 974442 | Insight relative date filtering accuracy improved | Relative date filters in Insights were returning records outside the expected date range, such as including multiple days when "is equal to current day" was selected. Investigation showed this was caused by improper date range calculation in the filter payload generation for relative date comparisons. This has been resolved by correcting the timezone handling when transforming relative date filters into date/time ranges in the condition builder. | Reporting |
| INC-C59538 | 972778 | Filter interaction issues resolved | Dashboard filter interactions were experiencing an unexpected focus jump to the first element when entering values in promoted filters, and date range selections were clearing previously entered from dates when users selected to dates without first clicking outside the from date field. This has been resolved by updating the focus behavior and date selection logic in the Constellation UI filter components to ensure proper field retention and user interaction flow. | Reporting |
| INC-C936 | 946566 | Exception handling added for addreportdefinitiontodatapage | The pyReportDefinition page was missing from data pages despite enabling the 'datapages/addreportdefinitiontodatapage' DSS setting. Investigation showed this was caused by an exception in the report definition tracer post-successful execution, and handling has been added to resolve this issue. | Reporting |
| INC-D10340 | 982213 | Corrected batch index processor interference with case creation | Background case creation processes were being disrupted by SRS indexing operations related to pySASBatchIndexProcessor. The BatchEDIProcessor from Smart Claims Engine was unable to create work objects, and was receiving the error "Database-BadClassDef-BadObjectClass Trying to open rule PARSEX12!NM1 of class Rule-Parse-Delimited, but no defined-on class (pyClassName) was specified". Investigation showed this was caused by complex dependencies between claims processing and indexing caused by unnecessary thread-state cleanup calls for SRS Query Processors. This has been resolved by disabling calls to dictionaryReset and declarativeContextClear to prevent the thread state being cleaned more aggressively than needed, reducing interference between batch indexing and background case creation processes. | Reporting |
| INC-D1082 | 974025 | Personalized grid persistence fixed when localized | Personalized table views were not saving properly when the operator was set to a non-English locale, particularly when adding columns with localized field values or image controls. This has been resolved by correcting the localization handling in the personalized view save functionality to use a localized string instead of the headerLabel. If there is no localized value or field value, the plain label is returned. | Reporting |
| INC-D11306 | 985652 | BIX extract functionality for single-stage cases enabled | When creating a case type with a single stage and configuring real time BIX extract rules, running the case type resulted in empty data sets with no case data being extracted. Investigation showed this was caused by a limitation in the BIX real-time extraction feature where the pzDeriveEventType (Final, Internal) activity contained a When condition that evaluated whether the number of stages >=2, preventing single-stage cases from being processed. This has been resolved by modifying the BIX RTE logic to support single-stage cases and removing the stage count restriction. Logging has also been modified from INFO to DEBUG. | Reporting |
| INC-D12487 | 983054 | GenAI access controls implemented for Explore Data feature | Configurable access controls have been made available to allow administrators to restrict GenAI capabilities for specific users or based on business rules while maintaining system-wide toggle functionality. The new pyShowExploreDataAIInput 'when' rule in @baseclass is used to gate AI input visibility and updates pxPopulateDataExplorerInfo to reference pyShowExploreDataAIInput. | Reporting |
| INC-D12830 | 985816 | Context handling updated for scheduled reports | After update, scheduled reports were failing to execute in production. Investigation showed incorrect context validation during scheduled report execution could lead to tasks being handled under the wrong application context, causing some scheduled reports to be skipped or not refreshed correctly. This has been resolved with an update to the scheduled-task activity to explicitly open the target task, verify the current application matches the task’s application, and clean up temporary pages during processing. | Reporting |
| INC-D13258 | 985964 | Scheduled report end date handling updated | Scheduled reports with "EndBy" dates were continuing to schedule indefinitely because the pyRecurrenceDetails.pyUseEndDate property was always false. This was traced to incorrect end date flag handling in the scheduling logic, and has been corrected. | Reporting |
| INC-D14014 | 985946 | Data display corrected for report widget charts with ampersand | After update, dashboard charts were not displaying all data when the chart labels contained ampersand ("&") characters, though the same charts were rendering correctly when accessed directly through the report browser. This was caused by the ampersand character not being properly converted when passed as a query parameter in the chart rendering process, and has been resolved by updating the pzMultiSeriesData FusionCharts XML and pzComboData FusionCharts files to properly handle ampersand characters in chart labels. | Reporting |
| INC-D14250 | 987266 | Repeating view delete functionality restored | Delete icons were missing in Repeating View Panel when header property reference fields contained empty strings, preventing users from deleting corresponding views. This has been resolved by ensuring Field Group dynamic headers fall back to the default “Row N” label when the resolved header value is an empty string. | Reporting |
| INC-D14306 | 984390 | Database connection close during indexing improved | Batch indexing operations were causing database connection exhaustion and repeated node failures when encountering empty blob data, causing batch nodes to fail health checks and restart continuously until queue processors were manually disabled, particularly when processing items with null pzPVStream values. This was caused by the search indexing code not properly releasing database connections when encountering BadInstanceDataException errors from empty blob streams, and. has been resolved by updating the connection cleanup and error handling for empty blob scenarios during batch indexing operations. | Reporting |
| INC-D15390 | 986166 | Error message improved for search fuzziness parameter validation | Failed Fuzzy searches did not have helpful error messages when incorrect parameters were entered. This has been addressed by updating the description of the pyFuzziness parameter with the values allowed: AUTO, 0, 1 and 2. | Reporting |
| INC-D16855 | 992861 | Fallback handling added for search date filtering timezone alignment | Case search filters using the "Yesterday" selection were incorrectly displaying cases updated on the current day. This was caused by a null on the SRS dispatch thread which caused ZonedDateTime.now() to fall back back to the JVM default zone (UTC), and has been resolved by updating the handling for the search date filtering and including a timeForThread function that re-zones the current instant to the thread's timezone before computing interval boundaries. | Reporting |
| INC-D17635 | 997520 | Date calculation timezone handling standardized | After migration, the pxDifferenceInDays function was producing different results between on-premise and cloud environments. This was traced to the report calculations using pxDifferenceIn* functions which could return values based on the database or raw timezone rather than the operator’s effective timezone, causing users in non-database timezones to see off-by-one or otherwise skewed differences, especially around date boundaries. To address this, the timezone conversion logic has been updated and a new DSS "useOperatorTimeZone" setting has been added for configuration control so report difference values are aligned to their timezone context. When dateCalculations/OnPegaCloud/useOperatorTimezone is enabled, the functions convert timestamps using the operator timezone from pxRequestor.pyUseTimeZone, with a fallback to the default operator timezone. | Reporting |
| INC-D1802 | 972540 | doc, BUG-985217 | #resolvedissues note: BUGS for this issue: 25.1.3: BUG-972539, INC-D1802 (Resolved-NoAction) 26.1: BUG-972540, INC-D1802 (Resolved-NoAction) |
Reporting |
| INC-D18339 | 993113 | Added handling to avoid Oracle database query limit | After update, report definitions were failing with ORA-01795 error message "maximum number of expressions in a list is 1000". This was caused by Oracle database queries exceeding the 1000 expression limit when processing large datasets, and has been addressed by implementing query expression splitting logic that automatically divides large query expressions into smaller chunks when they exceed Oracle's 1000-item limit. | Reporting |
| INC-D19585 | 997951 | Localized table view record count display fixed | Constellation table views in some non-English locales were displaying incorrect record counts after saving personalized views or switching between views, with readonly DataPages showing unchanged counts when switching to default view and editable DataPages reverting to initial default counts after view operations. Investigation showed this was caused by locale-specific formatting issues in the view count calculation and display logic, and has been resolved by updating the localization for the generateCountText method. | Reporting |
| INC-D20438 | 996599 | Scheduled insights date filtering accuracy restored | Scheduled insight exports with relative date filters like "Current day" and "Last 1 day" were returning identical datasets based on the schedule creation date rather than the current execution date. This was caused by the system using static date references from schedule creation instead of dynamic date calculation at execution time, and has been corrected. | Reporting |
| INC-D21320 | 994937 | BIX file generation for complex data structures corrected | BIX extracts were failing to generate files when processing complex embedded data pages with rarely-populated referenced pages, throwing StringIndexOutOfBoundsException errors with "begin 0, end -1, length 19" during XML generation. This was caused by improper parsing logic in BIXXMLUtils.getKeyNameForTheProperty when handling wildcard properties in complex embedded data structures, and has been resolved by implementing enhanced parsing logic for deep structured embedded properties referenced through property-ref to external embedded properties. | Reporting |
| INC-D311 | 973422 | PDF filename extension duplication eliminated | The Create PDF functionality was generating files with duplicate .pdf extensions in Constellation applications, resulting in filenames like "document.pdf.pdf". The issue occurred because legacy attachment components displayed extensions as part of the filename, but Constellation separates extensions, causing the system to add .pdf twice when the extension was already included in the name. This has been resolved by updating the PDF creation logic to prevent the duplication. | Reporting |
| INC-D3168 INC-D14322 |
977868 990937 |
Report definition row key retrieval corrected | Report definitions configured with GetRowKey set to pzInsKey were experiencing inconsistent behavior where the pzInsKey column was appearing in query results in some environments but not others. Investigation showed this was caused by replica-mapped classes being incorrectly filtered out of internal table key resolution when using an alternate database, causing pzInsKey to be dropped from the generated SQL. This has been resolved by adjusting the internal table key resolution logic to always include keys for alternate-database replica tables. | Reporting |
| INC-D6108 | 977522 | Localization added for filtered date picker labels | Date picker "From" and "To" labels were displaying in English regardless of their configured locale when applying range filters to Date/DateTime fields in Inline Dashboards. This has been corrected. | Reporting |
| INC-D6592 | 988252 | Date picker year display corrected in dashboard filters | Year values were not displaying properly in DD-MM-YYYY format date range filters when multiple filters were added to Inline Dashboards. This was caused by CSS layout conflicts in the Insight template, and has been resolved by correcting the date picker layout handling for dashboard filters with multiple filter configurations. | Reporting |
| INC-D6593 | 984946 | Dashboard date range filtering corrected | Dashboard Insight date range picker was not displaying records when the same From and To dates were selected for filtering a specific day, instead showing no results. Investigation showed this was caused by the system using identical date and time values in the request, creating an impossible range condition. This has been resolved by adjusting the date range logic to properly handle same-day filtering by setting 23:59:59 for the end filter. | Reporting |
| INC-D7924 | 980546 | Table row count display corrected for large datasets with filters | Applications were displaying "NaN" instead of the actual selected row count in table toolbars when working with optimized tables containing more than 5000 rows and applying filters with select all functionality. Investigation showed this was caused by a grid selection count calculation error in the templates and layouts component when handling large dataset that contained undefined values. This has been resolved by initializing missing count values and updating the grid toolbar styling to ensure the count text is consistently targetable. | Reporting |
| INC-D8071 | 988119 | AI data exploration error handling improved | Explore data chat functionality was displaying "Unexpected output from the AI" errors when the dataObject was undefined. This has been addressed by updating the dataObject validation and error handling for AI-powered data exploration. | Reporting |
| INC-D8937 INC-D14471 |
980619 984333 |
BIX extract parsing improved for complex property structures | BIX extracts were failing with the error "InvalidReferenceException: The reference pxStageHistory().pxProcesses is not valid. Reason: unexpected character ')' at position 15, expected subscript (wildcards not allowed)" when attempting to extract data containing three-level pagelist property structures, particularly when XML extraction was selected with manifest generation. Investigation showed this was related to previous work that addressed incorrect pxTotalInstanceCount calculations but inadvertently introduced parsing issues for complex nested property structures involving multiple levels of embedded pagelists. This has been resolved by providing a solution for BIXXML Manifest XML parsing that correctly handles three-level pagelist structures, allowing extracts to complete successfully without the reference validation errors. | Reporting |
Security
26.1 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-C46073 |
958201 | Handling updated for proxy authentication password decryption | Email accounts configured to connect to Microsoft Graph API through corporate proxies requiring basic authentication were failing with "407 Proxy Authentication Required" errors. Investigation showed this was caused by the system sending encrypted password values directly to the proxy instead of decrypting them first, resulting in authentication failures. This has been resolved by ensuring proper password decryption occurs before sending credentials to proxy servers during OAuth 2.0 authentication flows. | Security |
| INC-B49938 | 946216 | Warning added for non-optimized properties in access control policies | In order to save an embedded property for the PropertyEncrypt access control policy, the property must be optimized. If this condition is not met, the error message "This embedded property is not optimized. Please optimize the property before using it in PropertyEncrypt access control policy. Exposed properties other than text type are not allowed." will be generated. This is applicable for both custom and standard properties. | Security |
| INC-C12804 | 988565 | SSO re-authentication flow corrected | OIDC single sign-on was working for initial authentication but failing during token expiration re-authentication scenarios, generating the error "Exception is thrown for OIDC flow java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "ssoAttrValues" is null "when accessing SSO attribute values. This has been resolved by updating the null checking and error handling in the OIDC re-authentication process. | Security |
| INC-C13496 | 952403 | OIDC scope selection control updated | Reviewing the viewXML rule of the OIDC Auth service showed discrepancies between the scope defined in the rule form and the indexes present in the OIDC XMLView. Investigation showed the multi-select control used for the Scope in Authentication Service rule was saving duplicate values for scopes. This has been resolved by updating the handling in the Data-Admin-AuthService class to avoid this behavior. |
Security |
| INC-C22611 | 953523 | Null check added to correct authentication validation error | After update, custom authentication services experienced unexpected system errors when processing incorrect PIN validation requests. Investigation showed this was caused by a NullPointerException that occurred if the PIN was invalid, and has been resolved by adding a null check. | Security |
| INC-C23867 | 943504 | SiteCipher decryption handling updated | Application creation from Blueprints was failing with "Decryption with SiteCipher is not supported" errors when site cipher encryption was enabled, causing the wizard to become stuck. This has been resolved by updating the siteCipher encrypted password validation. | Security |
| INC-C25152 | 942269 | Corrected special characters in multi-select email addresses | Email addresses had special characters displayed in multi-select fields. This was due to incorrect encoding by the cross-site scripting filter, and has been resolved by replacing the filter with DOMPurify in the "htmlForNewTokenCapsule" function within the multi-select control JavaScript. | Security |
| INC-C25230 | 953114 | File upload security validation enhanced | Security has been updated by improving the logic checks to prevent the upload of malicious files. | Security |
| INC-C25712 | 959687 | Mobile JWT authentication session handling corrected | JWT Bearer grant type authentication failed for mobile applications when configured to use JWT assertions from active SSO sessions. Investigation showed the pxRequestor page properties pointed to Mobile Token Credentials instead of the OIDC authentication service. This has been resolved by enhancing the design to properly identify OIDC authentication services for mobile users. | Security |
| INC-C25895 | 959691 | Date format pattern compatibility added for en_BE locale | After upgrade from Pega 8.8 to Pega Infinity 24.1 and from JDK 8 to JDK 17, applications encountered IllegalArgumentException with "Illegal pattern character" errors. Investigation showed date format patterns for the en_BE (English Belgium) locale were incompatible with the newer JDK version. This has been resolved by updating date format pattern handling to ensure JDK 17 compatibility. | Security |
| INC-C27076 | 943601 | Security checklist API names corrected | Security Checklist API response contained task names that did not match the corresponding names displayed in the studio interface, including several typographical errors. This has been corrected. | Security |
| INC-C29028 INC-C59122 |
945852 968791 |
Password security policy enforcement standardized across authentication methods | In some circumstances, inconsistent security controls were seen for SSO-authenticated administrators. This has been resolved by updating the password policy validation logic to consistently enforce security policies regardless of the administrator's authentication method. | Security |
| INC-C29398 INC-D1687 |
942413 971649 |
Corrected handling for TimeOfDay values in Redux-based data pages | TimeOfDay property values were being incorrectly modified when retrieved directly from Redux-based read-only data pages with report definitions as sources. This was traced to Java's binary floating-point representation (IEEE 754) returning incorrect precision values during arithmetic operations on double values in the format conversion APIs used by Redux clipboard implementation, causing 1 second to be lost during conversion. This has been resolved by updating the logic to use BigDecimal for accuracy. In addition, an issue with millisecond to date conversion has been corrected. | Security |
| INC-C29767 | 949815 | Security updated for DisplayAuthScreenSelector | Cross-site scripting protections have been updated for DisplayAuthScreenSelector. | Security |
| INC-C31671 | 945452 | Chinese timezone handling updated | Date formatting functions returned incorrect dates when converting between Asia/Shanghai and Asia/Chongqing timezones in Chinese locale after 4:00 PM local time. This has been resolved by adding proper support for Shanghai and Chongqing timezones in the zh_CN locale. | Security |
| INC-C32672 | 944372 | Security improved for WebLogic error messages | WebLogic servers were displaying detailed error messages in the browser when processing malformed requests. To improve security, error sanitization has been implemented to return generic HTTP 400 responses for malformed requests. | Security |
| INC-C32881 | 948707 | Extra logging added for File Listener | Some File Listener services were experiencing exceptions related to authentication profile configuration errors when accessing Google Cloud Storage repositories. Extra log statements have been added for debugging support to assist with diagnosing root causes for this issue. | Security |
| INC-C33074 | 944998 | Date time difference calculation corrected | After update, the @DateTimeDifference function was returning 1.0 instead of 0.0 for same-day time differences. This was an unintended consequence of work done on timezone conversion, and has been corrected. | Security |
| INC-C34123 | 947375 | Work item access security errors eliminated | Opening existing work items generated 403 errors with security alerts about unregistered requests for the showstream activity. This was caused by improper request validation in the Pega_Desktop_DocGadgets.JS file for whitelisted Action Launch Harness operations, and has been resolved by correcting the BAC validation logic for deprecated WorkList operations. | Security |
| INC-C35039 | 946692 | Security improved for drag and drop | Cross-site scripting protections have been updated for drag and drop operations for documents. | Security |
| INC-C35040 | 946696 | Application guide security updated | Cross-site scripting protections have been updated for drag and drop operations for guides. | Security |
| INC-C35485 | 952161 | Mitigation available for Notes protocol links blocked in Rich Text Editor | After upgrade, Rich Text Editor was not processing notes:// protocol links. This is due to the implementation of DOMPurifier, which restricts certain custom protocols, specifically the 'notes://' links due to security concerns. In order to support backwards compatibility, an update has been made which will support adding specific code in the UserWorkForm to permit the desired tags. This a mitigation mechanism for backward compatibility issues that might have been introduced by limiting tags. However, reintroducing the blocked tags carries the risk of creating security vulnerabilities for XSS and HTML injections. Please refer to the documentation for Security in Rich Text Editor for additional information. | Security |
| INC-C35686 | 948678 | Enhanced URL security | In some scenarios, there was a potential to execute unauthenticated activities by manipulating parameters. This has been addressed by introducing an attribute to identify tampered or malformed URL requests so they cannot bypass validation. | Security |
| INC-C36448 INC-C36734 INC-C36789 INC-C36801 INC-C36941 INC-C37168 INC-C37236 INC-C37237 INC-C37276 INC-C37353 INC-C37566 INC-C37624 INC-C37824 INC-C37994 INC-C38285 INC-C38376 INC-C39213 INC-C40100 INC-C41015 INC-C41020 INC-C41029 INC-C44165 INC-C45714 |
957415 | Live UI functionality restored for Chrome/Edge browsers | Live UI was failing to load when using the default Content Security Policy (CSP) configuration 'pxDefaultAllowAll' in Google Chrome and Microsoft Edge browsers version 139.X.X and later. This was caused by a Chrome 139 update which introduced a change that fires an error event when CSP blocks a Worker script, preventing Live UI from functioning properly. The issue may be addressed with a local workaound by adding "blob:" to the list of allowed websites in the Child Frame-Source section. This has been resolved by updating the platform to handle the new browser behavior and ensure Live UI compatibility with the latest Chrome/Edge versions. | Security |
| INC-C36482 | 946455 | Error logging corrected during successful operator creation | The CreateOperator activity logged error messages even when operator creation completed successfully. This was caused by missing conditional logic to skip error logging when no actual errors occurred, and has been resolved by adding the necessary conditional checks. | Security |
| INC-C36511 | 950562 | Authentication logout redirect corrected | Issues were seen with the redirect functionality after logout preventing proper return to the login screen. This was caused by incorrect parameter formatting in the SchemePRAuthBasicLogOff activity redirect URL construction, and has been resolved by including the redTo value in pzEncryptURLActionString(). | Security |
| INC-C36518 | 955861 | OIDC authentication flow corrected for multiple JWT authorization servers | OIDC authentication was failing with "Unable to execute OIDC flow: Caught exception while parsing the id token" errors when environments were using multiple OIDC authorization servers with JWT-based client authentication. This was traced to the handling for TokenProfileCacheImpl.java which incorrectly merged JWT profile details from different authorization servers when alternating between OIDC flows, resulting in invalid client assertions being sent with incorrect issuer claims. This has been corrected to ensure each OIDC flow maintains its proper JWT profile isolation. | Security |
| INC-C36852 | 954970 | Report definition class hierarchy handling updated for use with Access Control Policies | Report definitions were failing with pxObjclass exceptions when Access Control Policies (ACP) were defined on parent data classes in complex inheritance hierarchies. The issue occurred specifically when data classes served as parents to abstract platform classes that contained report definition subclasses, and was caused by improper class resolution when ACPs were present in the inheritance chain. This has been resolved by adding handling to prevent .pxObjClass exceptions in the subclass report definition when an ACP exists on the top Data-class. | Security |
| INC-C37512 | 957236 | Rule history access with security headers enabled | Rule history snapshots were not opening properly when the Cross-Origin-Opener-Policy (COOP) same-origin header was configured for security purposes. This was caused by the COOP header preventing the proper opening of modal windows containing rule history information, and has been resolved by updating the rule history display mechanism to work correctly with security headers while maintaining the required security posture. | Security |
| INC-C37533 | 949811 | Button alignment corrected in consent screen | Buttons in the authorization consent screen were misaligned. This was caused by incorrect CSS centering applied to the reject button, and has been corrected. | Security |
| INC-C37793 | 951000 | Platform security class logging expanded | Additional logging has been added to assist with diagnosing ClassCastException errors in platform security components. | Security |
| INC-C38031 | 958254 | Decision Tree rule execution CSRF validation corrected | Decision Tree rules were returning HTTP 403 errors with SECU0008/SECU0017 when attempting to run them from Dev Studio with CSRF settings enabled. This has been resolved by updating the Decision Tree rule execution flow to properly handle CSRF token validation. | Security |
| INC-C38451 INC-C46461 |
950656 960572 |
OIDC dynamic parameter processing supported | The dynamic parameters for the OIDC authorization endpoint were not getting passed. Investigation showed the dynamic parameters were treated as literal strings instead of being processed as parameter references, and this has been resolved by implementing proper dynamic parameter processing for OIDC authorization endpoints. | Security |
| INC-C39151 INC-C40806 |
953620 955870 |
Delegation security token handling corrected | Applications were experiencing SECU0019 "The mashup is not consistent with the latest security enhancements" alerts and blank screens when attempting to edit data type rules from delegated landing pages in blended UI environments. This was traced to the system incorrectly adding an active CSRF token (pzCTkn) to URLs when the signature token was already present, and has been resolved by modifying the UI logic to prevent duplicate token parameters from being sent. | Security |
| INC-C39326 | 955500 | History added for operators automatically disabled by security policies | When the Operator disablement policy was enabled with the "Number of days of inactivity," the DisableDormantOperators Agent would run at the appropriate time and invoke the pzDisableDormantOperators activity without any audit trail or history records being maintained. This was caused by the DisableDormantOperators agent's pzDisableDormantOperators activity lacking logic to update operator history records, and has been resolved by adding history tracking functionality to the operator disablement process. | Security |
| INC-C39526 | 953516 | Modified confusing URL error message | URL validation was incorrectly displaying error messages that indicated FTP protocol could be used when FTP was not supported. This has been resolved by removing the reference to FTP in the error message presented to the user if the URL is not valid. | Security |
| INC-C39718 | 963100 | Operator profile security updated | Cross-site scripting protections have been updated for operator name fields. | Security |
| INC-C41015 | 953482 | pxDefaultSecured updated to work with Chrome 139 | The Live UI tool failed to load due to Content Security Policy errors introduced by Chrome 139 browser updates which affected CSP-blocked worker error events. To address this, the Content Security Policy rule pxDefaultSecured has been updated. | Security |
| INC-C42978 | 974386 | JWT audience mapping processing corrected | JWT processing was failing when mapping audience (aud) claims through token profile rules, while other claims like sub and iss processed correctly. The error "InvalidParameterException — class "java.util.ArrayList" does not match mode "String" " was generated. This issue was caused by improper handling of audience claim deserialization in the pxProcessJWT activity where list-valued claims—especially the standard aud claim as returned by Nimbus—were being mapped into Pega clipboard properties as if they were simple scalar values. To resolve this, claim mapping has been made type-aware, so JWT processing no longer fails on valid tokens that contain multi-value claims, and safe handling has been added for non-string scalar claim types while skipping null/blank claims more safely. | Security |
| INC-C43863 INC-C55680 |
957864 964476 |
Identity Federation authentication refresh handling updated | Email listeners were experiencing authentication failures when using the newly developed Identity Federation feature with Azure Key Vault integration for external secret storage. The authentication profile would successfully retrieve client credentials from Azure Key Vault during initial startup, but subsequent access token renewal attempts were failing with 401 errors when the JWT tokens expired, causing email listeners to lose connectivity to Microsoft Graph services. Investigation showed this was caused by the system not properly handling batch and application requestors during token refresh operations for Identity Federation configurations. This has been resolved, and the issuer URL validation has also been updated to support configurations where the public link URL does not end with "prweb". | Security |
| INC-C47105 | 957066 | Date time difference calculation note | The @DateTimeDifference function expects the date input to be in a GMT format (YYYYMMDDTHHMMSS.mmm TZ) and might return incorrect results if the datetime property is used to provide input for this function instead of String property(GMT). This is due to the input values being parsed to the server timezone in milliseconds, and that difference in milliseconds is returned as an output of the function without considering decimal value. It is also recommended to use GMT variants for the timezone (TZ) value as functions comparing dates may interpret the Date string as GMT leading to incorrect results at run-time. For example, represent Hong Kong Time (HKT) as GMT+08:00. A simple date string (yyyyMMdd) does not provide a timezone. | Security |
| INC-C47134 | 962488 | Mashup page security updated | Cross-site scripting protections have been updated for the pzLoadMashupPage activity. | Security |
| INC-C47786 | 960137 | SAML authentication context database transaction handling improved | Applications were experiencing slow database performance and idle transactions remaining open for extended periods when processing SAML authentication requests, with some transactions staying idle for over 20 minutes on the pr_data_saml_authreqcontext and pr_data_saml_logininfo tables. Investigation showed this was caused by concurrent thread access in the SAMLRequestHandler attempting to save the same authentication context record simultaneously, leading to database contention and connection pool issues. This has been resolved by updating the thread synchronization and transaction management in the SAML authentication context handling logic to prevent concurrent database operations on the same record. | Security |
| INC-C50018 | 962226 | OAuth token refresh timing updated | OAuth token refresh timing optimized. REST connector applications making continuous API calls were intermittently receiving 401 authentication errors from external systems due to expired access tokens being sent in requests. This was caused by insufficient buffer time in the default token refresh timing configuration. This has been resolved by increasing the default value for the security/token/refreshEarlyBefore DSS to provide adequate refresh buffer time. | Security |
| INC-C52309 INC-C3699 |
961415 962443 |
CSRF token validation handling improved | Production environments were experiencing numerous CSRF alerts with blocked requests due to token mismatches even when client and server tokens appeared identical during inspection. This was caused by timing issues in CSRF token validation logic that created false positive security blocks, and has been resolved by improving the token validation process to handle edge cases and reduce false positive alerts. | Security |
| INC-C52805 | 962619 | SAML SSO session timeout corrected | This was caused by incorrect JWT token expiry handling when the "Set refresh token expiry from IDP session expiry" option was enabled in OAuth2 client registration. This has been resolved by correcting the token lifetime calculation to respect configured session timeout values along with setting a default minimum refresh token lifetime of 3600 seconds (1 hour) when using IDP session expiry and improving SAML assertion processing to use the more appropriate SessionNotOnOrAfter timestamp. | Security |
| INC-C5335 | 924667 | Security updated for Anypicker control | Cross-site scripting protections have been updated for the Anypicker control. | Security |
| INC-C53847 | 962935 | Enhanced logging for OAuth2 access token errors | Enhanced logging for blacklisted access token errors. Applications were receiving generic "AccessToken is Blacklisted" 401 errors without sufficient context for troubleshooting, particularly during production incidents with large error spikes. Investigation showed that the error logging lacked key identifiers needed for effective debugging. This has been resolved by enhancing the logging to include operator ID, jti value, and psyncID in error mode, and the full access token in debug mode. | Security |
| INC-C53879 | 968140 | Access security updated | An update has been made to improve security access controls to ensure authentication and proper authorization. | Security |
| INC-C54382 | 964316 | Access group timeout logout behavior fixed | After access group timeout occurred, users attempting to log off were being redirected to a success landing page instead of the login screen. This was caused by incorrect evaluation in the logoff activity step 5, which was returning true instead of false in post-timeout scenarios, and has been corrected. | Security |
| INC-C54667 | 970344 | Operator validation exception handling improved | The system was throwing null pointer exceptions during operator ID validation when processing PreDispute case creation flows, specifically when attempting to validate operator records with non-existent access groups. This has been resolved with the addition of a null check and updated error handling in the operator validation workflow to ensure cpAccessGroup is not null before accessing its properties. | Security |
| INC-C54725 | 964487 | Session handling and authentication security updated | Authentication sessions were experiencing synchronization issues and potential security vulnerabilities related to SSO handler management and operator integrity validation. This has been resolved by updating the synchronization mechanisms and introducing operator integrity validation to verify operator ID authenticity post-authentication. | Security |
| INC-C55147 | 967597 | Authentication error message display corrected | Authentication error screens were displaying rule names instead of proper error messages when expired requestor errors occurred, showing the message "key pyAuthenticationErrorForExpiredRequestor cannot be resolved in the html pyDisplayAuthErrorScreen" instead of user-friendly error text. This was caused by the pyDisplayAuthErrorScreen rule referencing an incorrect message key. To resolve this, the new message rule pyAuthenticationErrorForExpiredRequestor has been added to handle authentication failures when a requestor session expires due to inactivity. The message informs users that their session has expired and instructs them to close the popup and start again. | Security |
| INC-C56022 | 968394 | Documentation updated for embedded property references in policy conditions | The documentation for Creating an access control policy condition has been updated to clarify that embedded properties are not currently supported in Access Control Policy conditions. Attempting to save the condition with an embedded property in the Column source field will generate a "Property case mismatched" error. | Security |
| INC-C56202 | 968667 | Cosmos theme delegation and attachment loading issues corrected | After update, applications using the Cosmos theme were experiencing loading loops and stuck screens when accessing case attachments and rule delegation functionality. This was caused by a redirected encrypted action attribute in mMappeddata that interfered with proper screen rendering, and has been resolved. | Security |
| INC-C56768 | 979028 | Pega Desktop security updated | Cross-site scripting protections have been updated for Pega Desktop support. | Security |
| INC-C57934 INC-C57394 |
966818 970582 |
Bouncy Castle jar updated for improved memory performance | Outbound campaigns were running significantly slower than normal. This was traced to memory issues in the Bouncy Castle FIPS library version 2.1.1, and the jar has been upgraded to resolve this issue. | Security |
| INC-C58612 | 991698 | Security checklist verification handling updated in Deployment Manager | The verify security checklist task in Deployment Manager was failing with the error "Unable to fetch task status due to invalid configuration. Unable to derive access group for application" when the system was configured as Production-5 level. This was caused by case-sensitive application name comparison logic in the security task manager that failed to properly match application names with their corresponding access groups, and has been resolved by implementing case-insensitive application name comparison. | Security |
| INC-C58655 | 968074 | Corrected Jakarta servlet references for SSO compilation | After update, the pySAMLWebSSOAuthenticationActivity was encountering compilation errors when attempting to reference javax.servlet classes in custom pyEstablishOperatorContext code. This was traced to the platform migration from javax.servlet to Jakarta servlet APIs, and has been resolved by updating the servlet API references to use the appropriate Jakarta equivalents. | Security |
| INC-D10466 INC-D12499 |
980600 990790 |
AWS identity federation credential retrieval resolved | Identity federation rules were failing to fetch AWS temporary credentials when running in background jobs, with the error message "Cloud Identity Federation failure : Failed to fetch AWS temporary credentials for identity federation rule:GlobalIdentityFed" appearing in logs along with SECU0023 security alerts. Investigation showed that access group values were appearing as blank or null during credential retrieval operations, preventing proper authentication with AWS services. This has been resolved by refactoring the access group retrieval mechanism to properly handle null and empty cases, along with enhanced token caching logic to avoid unnecessary invalidation broadcasts and improved handling of the Hazelcast decommission latency issue. | Security |
| INC-D10747 | 990030 | Autoclose handling updated for secure URL configurations | HTTP 400 errors were generated when attempting to use the autoclose functionality in end-user portals after enabling the Dynamic System Settings prconfig/initialization/urlencryption/default (set to true) and prconfig/initialization/submitobfuscatedurl/default (set to required). Investigation showed this was caused by the autoclose feature sending plain text URLs that were incompatible with the URL encryption requirements, and this has been resolved by implementing URL encryption handling in the autoclose request mechanism. | Security |
| INC-D10774 | 986942 | Access policy condition results accuracy improved | The access policy condition results page was not reflecting validation results correctly when using the "Actions > View policy condition results" option, while the "Verify Policy" option worked as expected. This was caused by the ABAC policy-condition results page evaluating index- and association-backed conditions incorrectly at the per-condition level, effectively relying on the overall policy verdict instead of independently evaluating those conditions. This has been resolved with an update to ensure the ABAC policy-condition results page evaluates each condition independently. | Security |
| INC-D10948 INC-D13780 INC-D14227 |
983565 984014 984516 |
Forgot password functionality restored | After update, authentication failures were seen when attempting to use the forgot password functionality, with the system continuously looping back to the login screen and displaying "Please enter valid username" error messages even when valid operator IDs were entered. This was traced to the username/operator validation logic within the forgot password flow experiencing increased processing time for OAuth token lookups that failed with cache lock errors and retried multiple times, and has been resolved. | Security |
| INC-D11065 | 982464 | Token storage capacity increased for OAuth authentication | OAuth2 token decryption failures were seen while creating the OAuth2 client token. This was traced to token truncation, and was caused by the column length limitations of 4000 characters for pyaccesstoken and 512 characters for pzrefreshtoken columns being insufficient to store full token lengths. This has been resolved by increasing pyaccesstoken column capacity to 8000 characters and pzrefreshtoken to 4000 characters in the pr_data_token table. | Security |
| INC-D12665 | 994232 | Cross site scripting protections updated | Comprehensive URL parameter encryption has been added to maintain security throughout the entire user session lifecycle. | Security |
| INC-D1298 | 989556 | XSS prevention optimized for skin rules | The pyPreventXSSInLabel DSS setting was causing issues when applied to final skin rules, disrupting normal UI rendering and label display functionality. This has been resolved by implementing conditional XSS prevention that skips processing for final rules while maintaining security for editable content. | Security |
| INC-D13101 | 982544 | SAML authentication handling updated | In order to support site-specific needs for unsigned assertions, the DSS security/SAML/allowUnsignedAssertion (comma-separated list of auth service names, case-insensitive) has been made available. The default behavior is to enforce signature validation (DSS is set to false). | Security |
| INC-D14332 | 985472 | Multi-factor authentication handling improved for external authentication | A blank MFA page was displaying when logging in via SAML/OIDC/Platform Authentication with Multi Factor Authentication policies enabled but no associated email account configured. Investigation showed this was caused by insufficient validation of email account prerequisites for MFA policies. This has been resolved by ensuring MFA security policy handling behaves correctly even when an operator has no email account. | Security |
| INC-D15026 | 984654 | OAuth2 client registration deletion warnings added | Users were inadvertently deleting default OAuth2 Client Registration rules starting with "PegaApp_" without understanding their critical role, which prevented application login access. This has been addressed by implementing warning messages that inform developers when attempting to delete OAuth2 Client Registration rules that deletion will prevent user login to the application. | Security |
| INC-D15457 | 997635 | Access role read rules configuration corrected | Access Role Name configuration was failing when attempting to modify Read Rules settings, displaying errors when selecting or creating when rules, with the system incorrectly listing and creating rules in the ARO class instead of the proper Rule- class. This has been resolved by correcting the class determination logic to properly target Rule- classes for when rule operations. | Security |
| INC-D15773 | 986437 | Cookie reuse security updated | Handling has been updated to improve security for cookie reuse scenarios. | Security |
| INC-D17638 | 994676 | Token renewal updated | Token renewal handling has been updated with stricter token validation and improved handling of invalid tokens. | Security |
| INC-D18445 | 993615 | Report browser security updated | Cross-site scripting protections have been updated for Report Browser. | Security |
| INC-D20802 INC-D23353 INC-C25899 INC-D2915 INC-D18673 INC-D20802 |
999973 1001190 |
OAuth token authentication accuracy improved for duplicate client identifiers | After update or after decommissioning Hazelcast caching and clustering functionality, OAuth token authorization errors appeared. This was caused by the tokens being stored/looked up by mOperatorId instead of the resource owner's username, causing token collisions, and was due to centralized token caching changing from a shared global cache to a node-local cache. This led to issues when multiple users shared the same client ID, which is against best practices. To resolve this, for ROPC grant type only, the resolved resource owner username will use pyUserIdentifier instead of the Pega operator ID. | Security |
| INC-D21255 INC-C27956 INC-C31119 INC-C43410 INC-C45875 INC-C46305 INC-D5175 INC-D7285 INC-D7841 |
1001461 | Secured attachment access during virus scanning on Pega Cloud | Pega Platform now blocks access to attachments stored in Pega Cloud File storage (PCFS) until the antivirus scan returns a clean result. Pega Cloud clients using PCFS previously received a virus-scanning service by default, but access was not restricted during the scan. While a scan is in progress, the system displays an informational message explaining that the attachment is temporarily unavailable. If a scan identifies a file as malicious, users receive a clear unsafe-status message instead of a silent quarantine, and automated processes such as DocAI or DocuSign integrations receive an explicit error response. | Security |
| INC-D21743 | 999719 | URL tampering protections updated | The validation handling for URL parameters has been updated for improved security. | Security |
| INC-D2543 | 997856 | Kafka credential security enhanced with vault integration | HashiCorp Vault support has been integrated into the Stream Dataset feature to ensure sensitive authentication information remains encrypted throughout the deployment lifecycle. | Security |
| INC-D27916 INC-D19874 |
997275 1002685 |
Security improved for URLs | Cross-site scripting protections have been updated for hashed URLs. | Security |
| INC-D2915 | 983269 | Documentation clarified for OAuth authentication profile configuration | The OAuth 2.0 authentication profile documentation has been updated to clarify that multiple authentication profiles cannot use identical client ID, grant type, scope, and tenant ID combinations. | Security |
| INC-D390 INC-D465 |
979116 978791 |
Property encryption validation for page and pagelist properties resolved | After update, attempting to configure PropertyEncrypt actions in Access Control Policies for Page and Page List properties resulted in the error message "Property name - This embedded property is not optimized. Please optimize the property before using it in PropertyEncrypt access control policy. Exposed properties other than text type are not allowed", even when properties were properly optimized. This was traced to overly restrictive validation logic incorrectly blocking Page and Page List properties from being used in PropertyEncrypt configurations, and has been resolved by removing the validation restrictions for pagelist and page group properties, implementing proper detection of PageList/PageGroup mode to resolve item classes correctly, and adding appropriate warning messages for non-optimized properties while allowing text-type properties to be saved successfully. | Security |
| INC-D4523 | 980780 | OIDC authentication flow streamlined for expired requestor sessions | The error "Requestor session on the server expired due to long inactivity" was generated when users took longer than 2 minutes to authenticate with their identity provider during OIDC single sign-on, requiring users to manually close the window and restart the login process. This was traced to the handling for expired short-lived requestor sessions when receiving valid authentication responses, and has been resolved by implementing automatic redirection to the identity provider instead of showing the error screen, allowing seamless re-authentication without user intervention. | Security |
| INC-D4684 | 978319 | OIDC authentication service mapping error corrected | OIDC authentication was failing with NullPointerException errors when authentication services contained attributes in the mapping tab, specifically when dot notation variables were present. Investigation showed this was caused by realizeTheExpression prematurely fetching SSO attribute values from the clipboard before the request was generated, causing stale/empty data to be used during expression resolution. This has been resolved. | Security |
| INC-D5006 | 977590 | ABAC read policy access control restored | ABAC Read policies were not evaluating properly after update. This was traced to work done on PolicyConditionWhenAssembler.java, and has been corrected. | Security |
| INC-D5096 | 975410 | OAuth2 refresh token checkbox now defaults to disabled | Constellation applications were experiencing frequent "Login to Continue" prompts due to short-lived refresh tokens inherited from Identity Providers. This was caused by the "Set refresh token expiry from IDP session expiry" checkbox being enabled by default in automatically generated OAuth2 Client Registration rules. To address this, the OAuth2 client registration request template has been modified to set use_idp_session_expiry to false by default, allowing the standard 24-hour token expiry to apply unless explicitly overridden. | Security |
| INC-D5237 INC-D18832 INC-D2167 |
975551 993755 975009 |
API authentication performance improved | REST API calls using OAuth 2.0 token authentication were experiencing significant delays due to cache lock acquisition failures. This was caused by synchronization issues in the OAuth2 cache implementation following Hazelcast decommissioning, and has been resolved by updating the cache lock and node synchronization mechanisms. | Security |
| INC-D5346 | 974956 | HTTP 412 retry mechanism implemented for HashiCorp vault | Intermittent failures were seen when connecting to HashiCorp vault clusters, resulting in HTTP 412 errors. Investigation showed this was caused by token propagation delays within the HashiCorp vault cluster infrastructure. Automatic retry logic has been added to assist with request failures. | Security |
| INC-D6137 | 978593 | Hashicorp authentication connectivity corrected | After update, HashiCorp Vault authentication was failing with "Server returned HTTP response code: 400 for URL" errors. Investigation showed this was caused by changes in how HTTP request payloads were being formatted when communicating with HashiCorp Vault's authentication endpoints. This has been resolved by refactoring the VaultManagementService to use JsonObject for request payloads. Diagnostic logging has also been added. | Security |
| INC-D6662 | 976052 | Redirect encryption handling improved | Errors indicating "This action is not allowed as it is outside the current transaction" appeared during a workflow. This was traced to URL encryption and redirection handling not properly managing transaction boundaries during secure operations, and has been corrected. | Security |
| INC-D70 | 981027 | Security validation improved against improper access control | An update has been made to prevent unauthorized function execution. | Security |
| INC-D7107 | 980249 | JWT token expiration handling improved to reduce unnecessary alerts | Unnecessary runtime exceptions appeared in PDC monitoring when JWT tokens expired during validation, creating false alarms for developers investigating system issues. This has been resolved by modifying the error handling in the pxProcessJWT activity to log errors instead of runtime exceptions for expected token expiration events. | Security |
| INC-D7577 | 980861 | Azure identity federation connectivity restored | Azure identity federation rule testing was failing with authentication errors "MsalServiceException: AADSTS90061", "NoSuchMethodError related to io.netty.channel.SingleThreadEventLoop constructor", or "NoSuchMethodError: 'void io.netty.channel.SingleThreadEventLoop.(io.netty.channel.EventLoopGroup, java.util.concurrent.Executor, boolean, boolean)". Investigation showed this was caused by incompatible netty jar versions in the platform. This has been resolved by updating the jars. | Security |
| INC-D7744 | 984663 | OAuth 2.0 logging improved | In order to assist with diagnosing authentication issues, OAuth token endpoint failures will now log the provider’s actual error details (error / error_description) instead of only a generic HTTP status. | Security |
| INC-D8286 | 988107 | Open redirect security updated | Open redirect handling for OAuth2 authorize endpoints has been updated for improved security. | Security |
| INC-D9004 | 982532 | CIDR-based studio access implemented | CIDR-based access restrictions are now available to restrict studio access exclusively to IP addresses within client-defined CIDR blocks. | Security |
| INC-D9821 | 985260 | Security updated for cross-site scripting | Cross-site scripting protections have been updated for App Studio and rule set editing. | Security |
System Administration
26.1 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B23797 INC-D766 |
949446 980245 |
Added handling to avoid requestor destroyed error | The error "java.lang.InterruptedException: Requestor has been destroyed or recycled" was observed in the logs. A RequestorLockException occurs when the system tries to access or interact with a requestor object that is no longer available, either because it has been destroyed, recycled, or is otherwise locked due to concurrent access or timing conflicts, and generally occurs when deferred or queued events are triggered just milliseconds after a user logs off. This error is known to occur under certain timing conditions and does not have any functional impact on the system. To address the issue, an update has been made to manage exceptions more effectively by ensuring that all beforeunload event listeners are removed during logoff, preventing unexpected triggers after the requestor is recycled. | System Administration |
| INC-C14202 | 921316 | Agent selection functionality restored | When using node agnostic view in the admin studio "Agents" landing page, the checkbox for selecting all agents was not functioning. This was traced to the "Optimize code" checkbox being enabled for the table, and has been resolved by changing the optimized table to a non-optimized table. | System Administration |
| INC-C25875 | 946582 | Added check for file processing before removal | The queue processor was deleting repository files before successful processing completion when case locks were held during inbound email processing of attachments larger than 5MB. This has been resolved with an update to ensure that large message content is only removed from the repository upon successful processing, and the snapshot cleanup post handler has been removed. | System Administration |
| INC-C26775 | 942301 | Corrected pxSessionTimer popup handling | The pxSessionTimer popup was closing unexpectedly when focus moved away from it, and the close ("X") button was not displaying when modal dialogs were already open. This has been resolved by updating the handling of overlay interactions and focus management in the session timer popup component. | System Administration |
| INC-C31356 INC-C36685 |
946544 948649 |
Queue processor lag calculation corrected | Queue processor lag metrics displayed inaccurate values when processing high-volume Kafka messages. Investigation showed this was caused by a race condition where delays in committing queue processor offsets to the database table led the system to incorrectly use Kafka's end and start offsets instead of the correct queue processor offset for lag calculations. This has been addressed by correcting the lag calculation logic to properly handle timing delays in offset commits. | System Administration |
| INC-C32426 | 952929 | Configuration data page loading reduced | The D_pyConfiguration data page was being called excessively, causing increased response times during UI operations. The performance has been improved by removing the reload once per interaction action for D_pyConfiguration to reduce unnecessary reload operations. | System Administration |
| INC-C38015 | 948896 | Data flow query performance optimized | Scheduled record processing experienced significant performance degradation in DelayedItemsDataFlowService data flows. This has been resolved by implementing query optimization improvements to eliminate the performance bottleneck. | System Administration |
| INC-C41005 | 951294 | Made queue processor more robust when encountering corrupted items | Queue Processors were failing to process items after encountering corrupted messages in the queue. This has been resolved with an update that adds an isDebugEnabled check before logging values in the queue processor flow to allow the system to skip corrupted messages and continue processing. | System Administration |
| INC-C55525 INC-C15427 INC-D2445 |
965521 944601 972590 |
Job scheduler database compatibility improved | The pyCleanupExpiredRequestors job scheduler was failing with Oracle database error "ORA-00936: missing expression" when attempting to clean up expired requestor sessions. This was traced to an incompatible RDB-delete query in step 4 of the pzCleanupExpiredRequestors activity that utilized the DATE() function, which is not supported by Oracle databases. This has been resolved by updating the query to use database-compatible syntax with CAST(pxcreatedatetime AS DATE) to ensure proper compatibility across Oracle and PostgreSQL database environments. | System Administration |
| INC-C57958 | 973463 | Database query visibility corrected in tracer | Database operations were not displaying SQL queries and row update information in the tracer tool, particularly affecting queue processor activities where RDB-Open methods were being executed. Investigation showed this was caused by unique appender conflicts when fetching tracer sessions using requestor IDs for database query tracing. This has been resolved. | System Administration |
| INC-C57992 | 983873 | Debug logging added for queue processor | Additional logging has been added to help trace queue processor enqueue operations by surfacing the generated message. | System Administration |
| INC-C58146 | 973650 | Portal routing made more robust | The handling for portal routing has been updated to ensure users are directed to their Access Group’s default portal, with a fallback to the standard portal when no default is set. | System Administration |
| INC-C7526 | 961169 | Null pointer exception handling improved | Regular null pointer exceptions were occurring in production environments during list action processing. This has been resolved by adding safe null checks in the pzDolistAction activity to handle null grid metadata pages and prevent exceptions during list action execution. | System Administration |
| INC-D10643 | 981940 | Kafka client DNS lookup property enabled | Applications were not able to configure the client.dns.lookup property for Kafka connectivity. This was traced to the property being excluded from permitted configuration options, and has been resolved by adding the property to allowed client settings. | System Administration |
| INC-D17137 INC-C58823 INC-263727 INC-D2539 INC-D12773 INC-C10643 INC-D32429 INC-B11618 INC-C42152 INC-D13104 INC-D7255 INC-D6517 INC-D3377 INC-D5112 INC-D17394 INC-C16820 INC-B31469 |
991649 | Case locking functionality enhanced for multi-node deployments | Issues were seen with releasing case locks after node crashes when running cases in multi-node environments. Investigation showed that the WorkUnlock activity was returning false when attempting to release locks from a different node than where they were originally acquired, causing a wait for the default lock timeout period. This has been resolved by implementing enhanced case locking mechanisms with improved remote execution capabilities for cross-node lock management. | System Administration |
| INC-D17298 | 989475 | Axios updated | The Axios library has been updated to a newer supported version. | System Administration |
| INC-D1909 | 978107 | Queue processing stability improved for corrupted entries | Agent processing was stopping for 10 minutes when encountering queue entries with null pzpvStream values in pr_sys_queues or pr_sys_queue_sla tables, generating BadInstanceDataException errors. This was traced to corrupted queue items with null stream data that prevented proper page population from the database, and has been resolved by adding null checks to queries for the pzpvstream column and implementing table constraints to prevent insertion of null values, along with alert generation for handling such scenarios. | System Administration |
| INC-D20318 | 1000056 | Queue processor logging noise reduced | Queue processors were generating excessive error messages such as ""Threads mismatch null"" and ""Requestor thread is null. Recover from last usage"" that were flooding Splunk logs without causing functional impact. Investigation showed these messages occurred during normal queue processor operations but provided no actionable information. This has been resolved by updating the log statement to debug to suppress these non-functional error messages. | System Administration |
| INC-D21146 | 997005 | Handling updated for duplicate static content | In some scenarios, duplicate aggregate static content requests could be added multiple times during request extraction. In order to improve performance, an update has been made to ensure duplicates are removed while preserving original order. Skipped duplicate aggregate resources are logged when debug logging is enabled. | System Administration |
| INC-D24451 | 999281 | Real Time Extraction (RTE) BIX performance and scalability improvements | Writing events to Kafka was taking an excessive amount of time when handling a large number of events (100k). In order to address this, new alerting and context-building capabilities for extract event processing have been introduced, primarily focused on Kafka integration and message size monitoring. This reflects a change in implementation: instead of processing BIX extract events internally, changed events are now published directly to an external Kafka system. Outbound payload shaping for external Kafka consumers uses the more efficient metadata + data structure. New utility methods for raising event alerts, logging message size threshold violations, and constructing standardized alert context strings have been provided. To improve performance and scalability, the legacy single Job Scheduler flow has been replaced with a Queue Processor-based pipeline with three dedicated queue processors: pzRealTimeExtractionCaseQP pzRealTimeExtractionDataUpdateQP pzRealTimeExtractionDataDeleteQP The previous rule pzProcessBIXExtractEvents is disabled by default but remains available as an override option if there is a need to process in-flight data during migration to external Kafka. Please refer to the documentation for configuring real-time data extraction for further information. |
System Administration |
| INC-D2471 | 972973 | SRC cache optimization for improved server startup performance | Applications with large numbers of applications in the System Runtime Context were experiencing server startup times exceeding 20 minutes, causing Queue Processor nodes to be marked as unhealthy due to the 15-minute timeout threshold. Investigation showed this was caused by the Rule Application Flattener API being invoked with the entire application list during cache construction, creating a performance bottleneck. This has been resolved by implementing a cache-build-before-invalidation approach where the new cache is constructed first before invalidating the old cache, allowing ongoing tasks to continue using the existing cache until the new one is ready, and by optimizing the SRC invalidation flow to prevent duplicate pulses during application imports that were causing repeated cache invalidations. | System Administration |
| INC-D2958 | 977299 | Job scheduler alert diagnostics enhanced | In order to assist with diagnosing Job Scheduler execution failures, the alert configuration and job scheduler alert logging have been updated to include additional alert settings and richer exception details. These include an extended default granular alert configuration (pySetting) with additional alert codes and thresholds, and exception stack traces in the generated error text. | System Administration |
User Experience
26.1 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A29326 | 948850 | Focus corrected after modal dialog is closed on the utility pane | When users refreshed pages or launched cases and navigated to the utility pane gear icon, closing the “Followers" widget caused focus to be lost instead of returning to the gear icon. This was a missed use case and has been resolved by correctly setting the focus after section refresh. | User Experience |
| INC-B19295 | 869092 | Access role description corrected for clarity | Viewing the PegaRULES:TestID access role description in the history tab indicated "Role used by Pega developers which grants privilege to see all Threads in the clipboard viewer. May be used for other things later." This was a misleading description caused by outdated documentation and has been updated to display "Please refer pxTestID privilege for description". | User Experience |
| INC-B32013 | 980632 | Table filter accessibility labels improved | Screen reader users encountered difficulty identifying which columns table filters affected due to the use of the same generic 'Click to Filter' aria-label for each. This has been resolved by implementing dynamic aria-labels including column names. | User Experience |
| INC-B36054 | 949769 | Tab overflow navigation accessibility enhanced | Left and right scroll arrow buttons for tab overflow were creating navigation difficulties for keyboard and screen reader users in traditional UI layouts. This has been resolved by implementing semantic tab layout + Enable scroll as the new default setting for any new layout group (Default/Tab) introduced in a section rule. | User Experience |
| INC-B38285 | 970762 | Data-testid attributes made unique for navigation links | Navigation links in Constellation were displaying the same generic data-testid value (:link:) across all menu items. This has been corrected by implementing unique data-testid attributes in the format "menuitemname:link" for each navigation element based on the name on the pyRuleName of the page used as the source. | User Experience |
| INC-B53312 | 908228 | Case attachment upload progress visibility restored | File upload progress was disappearing when users collapsed and expanded the utilities panel during case attachment uploads. This was traced to the attachment widget not properly maintaining progress state during panel visibility changes, and has been resolved by implementing persistent progress tracking that maintains visibility across panel state changes. | User Experience |
| INC-C11202 | 956737 | Radio button tooltip displays multiline content | Radio button help text tooltips failed to display when field values contained multiple lines or line breaks. This has been corrected. | User Experience |
| INC-C11245 | 941894 | Follow and unfollow actions now provide user notifications | Users were not receiving any confirmation or notification when selecting follow or unfollow actions from the Actions menu in the Preview section. This has been resolved by implementing notifications to confirm when the actions have been completed successfully. | User Experience |
| INC-C11797 | 958979 | Skip links accessibility navigation corrected | Tab navigation was bypassing the skip links target element when initially loading the user portal. This was caused by improper focus handling during initial page load, and has been resolved by updating the handling for pyIsWindowStealFocusInIEAllowed to ensure skip links are properly accessible on first navigation attempt. | User Experience |
| INC-C12345 | 962618 | Report button icon accessibility corrected | To improve accessibility, the role of the expand/collapse icon for the Summary/Chart tables reports in Dev Studio has been updated from link to button. | User Experience |
| INC-C13096 | 956934 | Corrected change event actions for table operations | Editable table configurations with change events triggered system administrator consultation errors when clicking outside the work area after data entry. This has been resolved by updating the handling of change event action sequences in non-optimized table contexts. | User Experience |
| INC-C15899 | 961992 | Any Picker clear selection accessibility enhanced | Screen readers were not properly announcing the clear selection cross icon when hovering over selected values in Any Picker controls. This has been resolved with an update to ensure the clear icon is focusable and actionable with keyboard, with an aria-label reflecting the selected value. | User Experience |
| INC-C17545 | 953902 | Corrected AM/PM handling for Morocco | Date time controls were displaying AM/PM indicators in English instead of Arabic when using the Arabic Morocco locale (ar_MA), and subsequent refresh actions were throwing validation errors. This has been resolved by providing locale-specific AM/PM values for the ar-MA locale. | User Experience |
| INC-C18782 | 962504 | Dialog close button accessibility resolved | The dirty check popup close button was not accessible via keyboard after focus had moved to the Cancel or Submit button when working in the perform harness. This has been corrected with an update to ensure focus on the close icon when ModalDialogXIconFocus is true. | User Experience |
| INC-C19582 INC-C17018 |
949921 949923 |
Localization updates | Several localization issue have been addressed, including items on the duplicate case search screen such as assignment names, table headings, column headers, and status values not being properly translated, and the upload of localization Excel failing if it contained some bad entries. | User Experience |
| INC-C20915 | 937402 | CKEditor replaced with Tiptap for Rich Text Editing | To create consistency with newer editor architecture, the CKEditor-based Rich Text Editing implementation has been replaced with Tiptap-based implementation in Traditional UI for new applications. Existing applications will continue to use CKEditor. | User Experience |
| INC-C21062 | 958084 | Accessibility improved for field validation error announcement | JAWS screen reader failed to announce field-level validation error messages when client-side validation was triggered on required fields. This has been resolved by implementing proper focus management and accessibility attributes for validation error announcements. | User Experience |
| INC-C21617 | 954889 | Currency formatting in localized dynamic layouts corrected | Currency values were displaying incorrect formatting when entered in repeating dynamic layout rows, particularly affecting locales where the grouping is "." and the separator is ",". Investigation showed the readonly formatter was not properly handling locale-specific formatting rules in dynamic contexts, and this has been resolved with the addition of a check to verify if the value is already formatted. | User Experience |
| INC-C21855 | 942081 | Browser refresh assignment error resolved | An assignment error was generated on browser refresh while a Constellation case was displayed in a traditional portal. This error did not occur in a pure Constellation portal. This was traced to the state management during browser refresh in mixed portal environments, and has been resolved by updating the Rule-Utility-Function pzFindAndUpdate to better handle the blended UI. | User Experience |
| INC-C22028 | 945294 | Modal title styling corrected | Modal dialog titles were applying Heading 2 mixin styles instead of the specified custom styles when configured in the application skin. This has been corrected. | User Experience |
| INC-C23344 INC-C32243 INC-D10100 INC-D7451 |
994599 | Menu state management handling updated | The enableLabelBasedActiveMenuState DSS setting was causing JavaScript errors and UI freezes when navigating between cases and tabs, particularly affecting Case Preview panel functionality. This was caused by the active menu persistence logic storing tab label text instead of expected length values, causing validation failures during menu state restoration, and has been resolved. | User Experience |
| INC-C24143 | 932775 | Focus ring display issues resolved | Applications were displaying unwanted or incorrectly positioned focus indicators, including black borders appearing around focused elements and blue focus rings showing briefly on web embeds during page load. This was traced to focus ring styling and placement logic within the Constellation UI framework, and has been resolved by updating the CSS styling and focus management behavior for form elements and web embed components to ensure focus indicators only appear when appropriate and with the expected visual styling. | User Experience |
| INC-C24844 | 952283 | Modal dialog form submission with filepath control made more robust | Values entered in any control were not being submitted after the initial refresh if a FilePath control was used in the modal dialog to attach a file and the option "SetEncodingNow" was enabled for the FilePath control. This was traced to the form handling when filepath controls were embedded in modal contexts. This has been resolved by updating the handling for hasFile so the request correctly uses FormData and preserves the file-upload flow. | User Experience |
| INC-C25194 | 938771 | Validation error message ordering corrected | Validate Rule error messages were not displaying in the configured field order, appearing in random sequence instead of the expected sequential order. This was caused by the error display logic not preserving the original field configuration sequence, and has been resolved. | User Experience |
| INC-C25264 | 935512 | File selection dialog focus management improved | When touchscreen functionality was enabled, opening file selection dialogs incorrectly placed the initial focus on the close 'x' button instead of the primary "Select Files" action. This was caused by inconsistent modal focus management logic implemented in a previous fix that changed behavior based on input method detection. This has been resolved with the addition of the DSS setting "ModalDialogXIconFocus" to control the behavior, and will set the focus to the close icon when is set to true. | User Experience |
| INC-C25271 | 951495 | Email template security updated | Cross-site scripting protections have been updated for the Customer Decision Hub email correspondence rule template selection. | User Experience |
| INC-C25293 | 954403 | Launch harness file download behavior clarified | The documentation for Available UI actions has been updated to clarify that using the Harness action with target set to New document to download a file is no longer supported in Pega Platform versions 8.5 and later. Following this change, downloading a file is available only through the Open URL in window action. | User Experience |
| INC-C25296 | 933516 | Field group heading hierarchy corrected | Field groups in detail templates were displaying incorrect heading tags that did not properly reflect the nesting structure of views. This has been resolved by updating the logic for the heading tag calculation to consider the proper view hierarchy and improve accessibility. | User Experience |
| INC-C25702 | 942720 | Localization updated to handle line breaks in pega-reference tags | Instruction text with pega-reference tags scattered across multiple lines failed to resolve properties in translated content. This has been resolved by enhancing the translation bundle processing to localize paragraph content using DomParser to maintain property resolution across line breaks. | User Experience |
| INC-C25835 | 943519 | Autocomplete focus behavior updated | Autocomplete fields with "Set value" configuration caused focus to jump to the top of the screen after keyboard navigation and selection. This was traced to a missing blur handler on enter keypress events and has been resolved. | User Experience |
| INC-C26338 | 947763 | Browser tab title application name corrected | Browser tab titles were displaying the previous application name instead of the current application when navigating between multiple applications in a portal. This was traced to the GenerateLayout RUF file using a common title from the Theme-Cosmos application ruleset regardless of the active portal context, and has been resolved by implementing dynamic title updates that reflect the current application context during navigation. | User Experience |
| INC-C26731 | 951993 | Delegated data type label encoding corrected | Delegated data type labels containing special characters displayed encoded values instead of proper text. This was traced to the localization text processing double-encoding special characters, and has been resolved by updating the pzInitializeDataType function to properly handle special characters in data type labels. | User Experience |
| INC-C26736 | 948310 | Corrected scrollbar focus management | The scrollbar was not automatically returning to the top of the page after form submission, causing users to remain at their current scroll position instead of being repositioned to view the top of the updated content. This has been resolved with an update to ensure the assignment heading receives focus and the page scrolls to the top of the form when moving between steps. | User Experience |
| INC-C27085 | 949544 | Ellipsis hover shows localized field value | After update, the pzEllipsis control hover functionality was displaying raw property values instead of localized field values. This has been resolved by updating the localization logic in the hover display mechanism to add a "pyAddTitleForEllipse" condition set to true by default which will restore the title attribute to display localized field values in hover text. | User Experience |
| INC-C28351 | 942051 | Norwegian locale configuration updated | The Localization Wizard used the invalid Java locale no_NO instead of the correct nb_NO, potentially causing issues with date controls for Norwegian language configurations. This has been corrected. | User Experience |
| INC-C28719 | 953260 | Session timer dialog accessibility improved for screen readers | The session timer dialog was not being properly identified by NVDA screen reader software, reading as a normal dialog instead of a timer dialog. This has been resolved by adding the necessary accessible name attributes. | User Experience |
| INC-C28836 | 960987 | Modal close button accessibility behavior corrected | Modal dialog close buttons were unexpectedly activating on mouse down instead of mouse up when using pzModalTemplate, though it did not occur with the close icon in pyFlexModalTemplate.pzModalTemplate. The event handling inpzModalTemplate has been updated to correct this issue. | User Experience |
| INC-C2914 | 910001 | Server side validation handling corrected for stakeholder widget | Server-side validation errors were not being displayed when submitting stakeholder widgets, causing the widget to close despite validation failures. Investigation showed the stakeholder widget was not properly handling server error responses. This has been resolved by adding banner support to the Stakeholders widget, specifically to surface server-side validation errors (e.g., API failures from createParticipant/updateParticipant) as inline alert banners within the Add/Edit Stakeholder form dialogs. | User Experience |
| INC-C29528 | 943632 | Potential duplicate cases text localized for French | Localization has been added to the "Potential Duplicate Cases:" text in the create stage modal dialog. | User Experience |
| INC-C29805 | 938993 | Table virtualizer performance and stability improved | Tables with dynamic row heights were experiencing jarring visual shifts and rendering freezes during scroll operations. This was traced to incorrect height calculations and inefficient item reconciliation in the virtualizer implementation when handling rows with variable heights. This has been resolved by implementing a refactored virtualizer optimized for non-grouped tables that uses a more robust approach to handle dynamic row heights, eliminating content jumps and performance bottlenecks while providing smooth scrolling and stable rendering. Note this implementation currently only supports tables without grouping; gallery and grouped tables will be enhanced in future iterations | User Experience |
| INC-C29841 | 942495 | Declare trigger execution logic corrected | Declare triggers configured on page list properties were executing unexpectedly when screens were submitted without any property modifications. This was traced to the PageList processing handling, and has been resolved by correcting the trigger evaluation logic to only execute when actual property changes occur. | User Experience |
| INC-C30022 INC-C41013 |
953337 952522 |
Personalized view display corrected for image columns | Image columns configured as always visible disappeared from personalized views after removing unused columns from the interface, disrupting user customizations. Investigation showed this was caused by the system incorrectly associating image columns with common property references that were affected by column removal operations. This has been resolved by improving the column reference management to maintain always-visible image columns independently of other column changes. | User Experience |
| INC-C30656 | 947594 | Image upload controls properly enforced in Rich Text Editor | The Rich Text Editor was accepting drag-and-drop image uploads even when the image upload option was explicitly disabled in the toolbar configuration. This has been corrected. | User Experience |
| INC-C30672 | 943064 | Localization consistency improved for UI elements | Default UI elements including Yes/No field values and Next/Previous buttons were not correctly localized due to trailing spaces in button names and missing translation mappings for specific UI components. This has been corrected. | User Experience |
| INC-C30714 | 943796 | Added question mark handling for multiselect | Multiselect controls were throwing JavaScript errors when users entered a question mark as the first character, causing all page actions to hang. This was due to the character was not being properly escaped in the multiselect control's regex pattern, and has been corrected. | User Experience |
| INC-C30858 | 948249 | Combo box accessibility enhanced for keyboard navigation | Clear icons in autocomplete combo boxes were not accessible to keyboard users or screen readers. This has been resolved by adding proper keydown event handling and accessibility attributes. | User Experience |
| INC-C30897 | 947303 | Flow action localization corrected | Flow action names were appearing in their default language rather than the localized values when accessed through mobile applications. This was caused by the localization packaging process not automatically including flow action name translations for work item classes, and has been resolved. | User Experience |
| INC-C31047 | 943893 | Optimized grid focus retention fixed | After closing modal dialogs launched from optimized grid rows, the focus indicator was not returning to the originating row. This has been resolved by updating the handling for the display border on the focused grid cell when modal is launched and closed from that cell. | User Experience |
| INC-C31091 INC-C34223 |
940101 948719 |
Improved accessibility for radio button in high contrast mode | Radio buttons were not displaying properly when using Firefox in high contrast mode, affecting visual accessibility needs. This has been resolved by replacing background-color with border styling that is recognized by high contrast mode, ensuring proper visibility across all contrast scenarios. | User Experience |
| INC-C31140 | 943036 | Corrected error highlighting for calendar input | Property labels were incorrectly displaying in red (error state) after correct values were entered in calendar input fields with validation. Investigation showed the error message class was not being properly removed when the data-value matched the updated value after navigation from table configuration flows, and this has been resolved with an update which will remove the labelError class on the label when values are corrected. | User Experience |
| INC-C31176 INC-C43370 |
959874 959009 |
Autocomplete selection accuracy enhanced for multi-key data types | Autocomplete and combo box controls displayed incorrect selections when bound to data types with multiple class keys, causing wrong data persistence. Investigation showed this was caused by the system matching records based on only the first key, ignoring additional keys like RelationshipType. This has been resolved by adding support for composite keys in Autocomplete and Multiselect. | User Experience |
| INC-C31189 | 945230 | Tooltip functionality corrected for Constellation partial views | Tooltips were not functioning properly when implemented on partial views in Pega Constellation, specifically when using data reference fields displayed as dropdowns with additional information fields. This has been resolved by adding support for dynamic additional information in this configuration. | User Experience |
| INC-C31252 | 948856 | Pulse notes loading extended | Pulse sections in blended applications were limiting display to only 10 posts when Constellation cases were launched from UI Kit portals. Investigation showed pagination was not functioning correctly in the blended UI environment, and this has been resolved. | User Experience |
| INC-C31256 | 945360 | Corrected data update when grouping removed | When grouping was applied to an optimized table with a queryable data page, changing the option back to the "Select field" option in the dropdown returned "No results" instead of removing the grouping. This has been resolved by resetting the page index to 1 when select field option is selected. | User Experience |
| INC-C31332 | 942446 | Server validation error translation enabled | The field label in the server side error banner was not localized as expected. This has been corrected. | User Experience |
| INC-C31543 | 945512 | Autocomplete persistence corrected | Autocomplete values disappeared after page refresh in multiselect components. This was traced to PropertyValue being removed from submit payloads due to incorrect nonFormProperties classification, and has been resolved by updating the insertInstructions handling for Multiselect having display field in additional fields. | User Experience |
| INC-C31931 | 951274 | Updated class handling for embedded properties | SECU0001 security errors occurred when nested data reference objects were used in views with multiple keys. Investigation showed property information retrieval was limited to work class context, missing nested object properties. This has been resolved with an update to ensure the embedded properties resolve to the correct class to retrieve any further parameters when given a page. For the scalar properties, the flow remains the same. | User Experience |
| INC-C32058 | 947170 | Tooltip sizing corrected in modal | Tooltips expanded to excessive size on first interaction with case lifecycle stage elements. Investigation showed the Reveal with Animation feature on embedded sections was causing tooltip rendering issues. This has been resolved removing the animation checkbox in the local action for modal. | User Experience |
| INC-C32478 | 943981 | Updated banner component rendering | Banner components in confirmation templates were rendering multiple times when switching between tabs or performing actions, causing unnecessary data page calls and performance degradation. This was caused by redux state reference changes triggering unnecessary re-renders in the confirmation template component, and has been resolved by implementing useMemo optimization to prevent unnecessary re-rendering. | User Experience |
| INC-C32526 | 945192 | Table cell context menu keyboard accessibility implemented | To improve accessibility, the keyboard shortcut of Shift+Alt+F10 in Windows has been implemented to open and access context menus on focused cells. | User Experience |
| INC-C32528 | 945069 | Banner regions accessibility enhanced with unique labels | Multiple banner regions on pages were being announced generically as "banner" by screen readers, interfering with accessibility. This was traced to banner regions lacking individual descriptive labels required for proper accessibility navigation, and has been resolved by implementing unique and descriptive labels for each banner region to ensure clear identification when navigating with assistive technologies. | User Experience |
| INC-C32532 | 945062 | Improved accessibility for case lifecycle completion status | Completed steps in case lifecycles displayed green checkmarks in Constellation that were not accessible, preventing screen readers from identifying finished steps. This has been resolved adding a "Completed" announcement to the steps, including scenarios where a step can be passed as a link (react node). | User Experience |
| INC-C32603 | 946179 | Corrected accessibility for main page headings | Screen readers were incorrectly announcing non-interactive main page headings as "Clickable heading level" despite the elements being non-interactive. This has been resolved. | User Experience |
| INC-C32635 | 943003 | Case summary follow button focus behavior corrected | When clicking the star icon to follow or unfollow cases in the case summary header, keyboard focus was being lost, requiring users to press tab again to regain focus indication on the button. This has been resolved by updating the button state change event handling so focus consistently remains on the button when activated. The screen reader announcement also reflects the label changing upon follow/unfollow. | User Experience |
| INC-C32864 | 945364 | Corrected layout positioning for email notifications | Email notification settings were displaying outside the dynamic layout box in the Theme Cosmos User Portal notification preferences screen. This has been corrected. | User Experience |
| INC-C32979 | 942471 | Support added for Norwegian locale | The Norwegian (nb_NO) locale has been added to the Constellation Localization Wizard. | User Experience |
| INC-C33178 | 945080 | Date field digit visual clipping resolved for adjusted text spacing | Numeric values in date fields were becoming visually clipped or partially hidden when users adjusted text spacing through accessibility tools or user stylesheets, particularly affecting day and year values on the left and right sides. This has been resolved by updating the date field layout to properly support text spacing adjustments while maintaining full readability of all numeric values. | User Experience |
| INC-C33179 | 945076 | Keyboard navigation improved for case lifecycle dialog | Process lifecycle dialogs were displaying content that could not be scrolled using keyboard navigation, preventing keyboard users from accessing information beyond the initial view. This was caused by missing keyboard scroll functionality in the modal dialog implementation, and has been resolved. | User Experience |
| INC-C33310 | 944647 | Table filter clear behavior corrected | When users clicked the "Clear Filter" option in table columns, the page automatically scrolled to the top. This was caused by an additional href="#" attribute added to the clear filter link in the pzGridFilterPanel section, and has been resolved. | User Experience |
| INC-C33479 | 944945 | Calendar navigation behavior corrected | The calendar date picker was skipping months when users clicked the navigation arrows to move between months, jumping from October directly to August when going backward or to December when going forward. This was caused by timezone calculation issues in the calendar navigation logic when the timezone was set to GMT-4. This has been resolved by correcting the month navigation calculations to properly account for timezone differences. | User Experience |
| INC-C33676 | 947221 | Review harness heading structure updated | The "To do" heading in the Review harness was configured as an H3 element instead of H2, which is not correct for accessibility compliance. This has been resolved. | User Experience |
| INC-C33796 | 951168 | AnyPicker spinner behavior corrected | AnyPicker controls displayed unexpected loading spinners when clicking outside the picker icon in Ajax containers with default values set. This has been resolved by updating the event handling for the setSafeURL function. | User Experience |
| INC-C33991 | 950642 | Table record-level condition evaluation fixed | Record-level conditions in editable tables evaluated incorrectly on first load, applying the first row's condition to all subsequent rows until the assignment was reopened. This has been resolved by removing uniqueField handling used for older Edit in Modal embedded data views. | User Experience |
| INC-C33994 | 950357 | Web mashup login screen documentation updated | An article has been added to the documentation for troubleshooting mashup issues which covers that multiple tabs are not supported for mashups with anonymous authentication. The proper configuration should use only a single tab. If multiple tabs are used and each has session timer, the tab which times out first will see the expected log in screen with anonymous login, but additional tabs will display the login screen which asks for credentials. | User Experience |
| INC-C34202 | 945351 | Filters category based on ID instead of name | Attachment category dropdowns remained blank when editing attachments after customizing attachment category rule labels in Constellation applications. This was caused by improper label-to-value mapping when attachment category descriptions were modified from their default values, and has been resolved with an update to use the attachment category ID to uniquely identify a category because the name can be changed. | User Experience |
| INC-C34448 | 948694 | Added check to permit some local actions on offline mobile | After upgrade, local actions were not opening on mobile harnesses in offline mobile apps. This was due to work done to block local actions outside case context, and has been addressed by adding a null-check for pyWorkPage to allow execution of some specific scenarios for some local actions. | User Experience |
| INC-C34897 | 945029 | Promoted filters filter primary fields | Adding primary fields to promoted filters in list page authoring resulted in property panel errors and prevented filter management. This was caused by undefined values during filter configuration processing, and has been resolved by filtering primary fields from promoted filters. | User Experience |
| INC-C34938 | 947274 | Corrected accessibility for application names on switch | Screen readers announced application names as "unlabeled 0 button" during application switching. This has been corrected. | User Experience |
| INC-C350 | 967976 | Modal dialog accessibility labeling corrected | Some modal dialogs were unlabeled for screen readers due to aria-labelledby attributes pointing to non-existent DOM elements. This was caused by dialog templates inconsistently including the modaldialog_hd_title ID that the aria-labelledby attribute referenced, and has been resolved by implementing logic to verify the existence of the target ID before setting aria-labelledby attributes and to find the header element when the primary ID is not present. | User Experience |
| INC-C35183 | 949414 | Report table header focus accessibility corrected | Report table headers received focus but did not display visual focus indicators, creating confusion for keyboard navigation users. This has been corrected by adding the necessary focus border styling on table header elements with data-read attributes. | User Experience |
| INC-C35237 | 952333 | Cancel button infinite loading resolved | Cancel buttons on create stages in hybrid applications experienced infinite loading screens after clicking "Discard" in the confirmation popup, followed by "no assignment found" errors after hard refresh. This was traced to the security handling during cancel operations in blended UI environments, and has been resolved by registering the cancel action with basic access control (BAC). | User Experience |
| INC-C35239 | 949344 | Corrected radio button selection issue | Radio buttons marked as mandatory were not getting selected on the first attempt when they were the first field on a form. Users had to make a second selection for the radio button to register. This has been resolved by correcting the focus and blur behavior. | User Experience |
| INC-C35285 | 946443 | Currency field formatting corrected | Currency fields limited input to only 4 digits and displayed incorrect formatting when using mixed locale settings like "en-NL". This has been resolved by correcting currency field formatting logic for mixed locale configurations. | User Experience |
| INC-C35451 | 947561 | Dropdown selection in repeating layouts fixed | Dropdown values became unselectable after rapidly deleting multiple rows in repeating layouts without pausing between deletions. This was caused by improper state management during rapid row deletion operations, and has been resolved by correcting dropdown state handling in repeating layout deletion scenarios. | User Experience |
| INC-C35533 | 947358 | DateTime picker localized clock format accessible label corrected | DateTime picker aria-labels displayed incorrect time formats when using localization, showing 24-hour format in accessibility labels while the visible field used 12-hour format. This has been corrected. | User Experience |
| INC-C35895 | 950703 | Dynamic tabs re-render correctly | Dynamic tabs templates failed to re-render when underlying parameterized data page results changed. This has been resolved by subscribing to the datapage results update with registerAdditionalProps on pConnect. | User Experience |
| INC-C36108 | 951429 | Multi-select validation message clearing fixed | Inline error messages persisted on multi-select properties within embedded data repeating views even after selecting valid options. This has been resolved. | User Experience |
| INC-C36543 | 948688 | Accessibility improved for autocomplete controls | Screen readers could not properly identify autocomplete dropdown buttons due to missing aria-hidden attributes on the autocomplete caret button. This has been corrected. | User Experience |
| INC-C36764 | 950622 | Corrected embedded data property duplication | Adding items to embedded data properties created duplicate entries, particularly when adding attachments or list items. This has been resolved by reordering the instruction sequence to generate insert instructions before dispatching add container actions. | User Experience |
| INC-C36784 | 955338 | Cascading dropdown value persistence logic fixed | Applications were experiencing validation errors when using three-level cascading dropdowns, where changing the first dropdown would reset the second but incorrectly persist values in the third dropdown instead of clearing all dependent fields. This was caused by incomplete dependency chain handling in the cascading dropdown implementation, and has been resolved by ensuring all dependent fields at any level are properly cleared when parent dropdown values change. | User Experience |
| INC-C36809 | 947703 | Promoted filter display fixed for radio button picklists | Picklists configured to display as radio buttons appeared as normal text fields in promoted filters. This has been resolved by updating the type mappings for Picklist:pxRadioButton to set conditionFieldType to "PICKLIST". | User Experience |
| INC-C36899 | 954163 | Duplicate case search results refreshed properly after input changes | When users navigated back to modify search inputs in a duplicate case detection process, the duplicate case list was not updating to reflect the new search criteria and continued showing results from the previous search until a browser refresh was performed. Investigation showed the duplicate case view was not properly refreshing when input values changed during backward navigation in the process flow. This has been resolved by ensuring the duplicate case search results are properly refreshed when users modify input values and re-execute the search step. |
User Experience |
| INC-C36915 | 949429 | Work queue name localization handling updated | Work queue names were not displaying in localized languages as expected. Investigation showed that during runtime the datapage localization values created for the necessary datapage were not being used, causing the work queue to not be translated. To address this, the work queues have been added in the application context with the workbasket names. | User Experience |
| INC-C36919 | 949468 | Date field required message clearing behavior made consistent | Required validation messages for date fields were persisting when fields became readonly and no longer required, while text fields properly cleared their messages under the same conditions. This has been resolved by standardizing the validation message clearing behavior across all field types when requirement conditions change. | User Experience |
| INC-C36982 | 960540 | Constellation tab count refresh control added | Tab counts in landing pages were not refreshing when underlying table data changed, causing user confusion as displayed counts remained stale even after bulk actions modified record quantities. This was due to the behavior of thread-level data pages: when a data page is configured to reload once per interaction, it may not always refresh as expected during complex interactions or when navigating between different views. Additionally, if the UI is not set to refresh automatically upon returning to the tabbed view, the count will remain unchanged until a manual refresh of the browser is performed. In order to address this limitation, the setting "pyAutoUpdateLandingPageTabCounts (Boolean)" has been added which will cause the TabbedPage template to refresh the tabCount when case/process events have been triggered. | User Experience |
| INC-C37020 | 956351 | Hovering text color change supported for custom layout group | Hovering font color changes were not applying to custom layout group format headers when users moved their cursor over the elements. This has been resolved by adding the necessary CSS for hovering text color change for the tabs. | User Experience |
| INC-C37118 | 950083 | Currency field formatting corrected for maximum digits | Currency fields with maximum digit limits displayed unwanted trailing zeros when entering values at the maximum length. This has been resolved by adding a maxlength check before adding additional zeros. | User Experience |
| INC-C37240 | 954000 | Modal dialog submission behavior fixed | Modal dialogs launched via openLocalAction API were displaying blank screens after submission. Investigation showed this was caused by an overly broad clearView flag condition that was clearing screens inappropriately in modal contexts. This has been resolved by adding a condition to execute clearing the view only if activeContext has 'workarea' in it to ensure clearView only applies to appropriate review mode scenario | User Experience |
| INC-C37456 | 952087 | Corrected Rich Text Editor tools functionality in lightweight mode | Rich Text Editor dropdown tools such as font selection and color options were not working when in fullscreen lightweight mode. This was traced to a race condition happening in the resize event which resulted in an infinite loop when full screen was enabled, and has been resolved with the addition of setTimeout. | User Experience |
| INC-C37604 INC-C56603 |
959850 967784 |
Local actions functionality restored in Constellation portal | After update, local actions were not functioning properly from dashboards, causing the TransferInteraction flow action to display an unexpected summary screen instead of dismissing cases as expected, and Constellation portals were failing to load. This was traced to an issue with displaying confirm-view for local actions from list view in multi-document applications, and has been resolved. | User Experience |
| INC-C37628 | 949854 | Accessibility focus management updated for new rows | When using a screen reader and adding new rows to inline-editable tables in embedded data configurations, keyboard focus remained on the Add row button instead of moving to the first cell of the newly-added row. This has been resolved by updating the focus handling logic to automatically move focus to the first editable cell of newly added table rows. | User Experience |
| INC-C37775 INC-D1724 |
954548 975721 |
User saved views persistence in Theme Cosmos addressed | Applications were experiencing deletion of user-created personalized views when using the refresh action on worklists in Theme Cosmos, with views from different harness classes appearing instead. This has been addressed with an update to save the Table views in a single appropriate Harness class. | User Experience |
| INC-C38028 | 951865 | Date picker accessibility improved for labels with apostrophes | Date picker controls were displaying incomplete alt text when labels contained apostrophes. This has been resolved with an update to encode the apostrophe symbol as HTML Hexadecimal code in the date picker template so the full alt text is present. | User Experience |
| INC-C38047 | 954096 | Timezone conflict handling updated in datetime controls | When operators had specific regional timezone settings that differed from a datetime control timezone configured through a property, the control was showing time according to the operator's timezone rather than the specified property timezone. This has been resolved by updating the handling in the calendar JavaScript rule. | User Experience |
| INC-C38092 | 949727 | Dropdown behavior in table layouts standardized | Dropdown options failed to display when clicking directly in the field area within table layouts, only working when clicking the arrow. Investigation showed this was caused by inconsistent event handling between different click areas of autocomplete controls in embedded data tables, and has been resolved. | User Experience |
| INC-C38112 | 955108 | Table pagination accessibility enhanced | Accessibility issues were seen with unoptimized table pagination controls. This has been resolved by adding the necessary focus elements. | User Experience |
| INC-C38126 | 952186 | Date time field audit history display corrected | Date and time field values were displaying the date portion in field history audit trails without the time component. This was caused by the FieldHistory component not being able to match "DateTime" format when the data page property was "Date Time" with a space. This has been resolved with an update to convert property type strings to a consistent format. Property type values that contain spaces or hyphens (e.g., "True-False", "Date Time") will be given camelCase format (e.g., "TrueFalse", "DateTime"). | User Experience |
| INC-C38186 | 953443 | Modal button accessibility announcement corrected | Screen readers incorrectly announced "collapsed" when navigating to buttons configured to launch modal dialogs or overlays. This has been resolved by adding an aria-haspopup attribute for modal/overlay. | User Experience |
| INC-C38484 | 950222 | Dirty check alerts resolved for hybrid Constellation applications | Users were encountering persistent alert messages about unsaved changes when creating new Constellation cases in hybrid applications, with the page becoming unresponsive when canceling the alert. Investigation showed this was caused by improper dirty state management between theme-cosmos and Constellation applications during case creation workflows, and has been resolved. | User Experience |
| INC-C38771 | 951269 | Handling updated for Excel export functionality in search and select | The Export to Excel functionality was generating errors when used within Search and Select components in Constellation applications. Investigation showed the Export to Excel action could appear for a report definition even when its data sources were not fully compatible with export and export should be disabled. This has been addressed by adding a new allowExportToExcel metadata flag from list-view metadata into table initialization which only shows the Excel export option when the list is both queryable and explicitly allowed to export. | User Experience |
| INC-C39135 | 949611 | DSS added to control PegaReferenceTags for email treatments | Email treatment links did not work when clicking the source button in the Simple Rich Text Editor, specifically affecting Google Chrome browser users in Customer Decision Hub. Investigation showed this was caused by HTML parsing issues that corrupted pega:include tags during source view transitions. This has been resolved by introducing the DSS rteAllowPegaReferenceTags to control the use of pega:include syntax in email treatments. The default is false. | User Experience |
| INC-C39402 | 956474 | Embedded table row deletion restored | Row deletion was failing in embedded tables containing dropdown components when no placeholder text was configured, while working correctly when placeholders were present. Investigation showed this was caused by child dropdown components re-rendering and populating Redux state even when no page reference existed for the embedded data. This has been resolved by preventing child component re-rendering when page references do not exist for embedded data structures. | User Experience |
| INC-C39574 | 960838 | Form validation errors resolved during view refresh | Form submissions were failing with infinite loops and console errors when validation rules were triggered on fields that became invisible after unchecking form elements with refresh settings enabled. Investigation showed this was caused by the system attempting to validate invisible fields during the merge data action after view refresh. This has been resolved with an update to ensure there is validation on the field only when visible. | User Experience |
| INC-C39631 | 951284 | Coexistence page table resizing behavior corrected | Optimized tables in coexistence landing pages displayed excessive empty space below the table when pagination resulted in fewer records on the last page. This was caused by missing harness resize calls during pagination operations in mashup environments, and has been resolved. | User Experience |
| INC-C39725 | 950971 | Parameter handling updated for refreshAuthoringRecords | Additional detail views configured for list columns failed to appear in the selection dropdown despite being properly configured. This was traced to the template subtype reference handling during authoring record retrieval operations, and has been resolved. | User Experience |
| INC-C4038 | 953703 | Phone validation behavior improved | Phone field validation was not triggering on blur when the entered value matched the previous value, even though error messages were being cleared from the interface. Investigation showed this occurred because the validation logic incorrectly assumed no validation was needed when values appeared identical, despite intermediate changes that cleared error states. This has been resolved by ensuring validation triggers on blur events regardless of value comparison, maintaining proper error state management in the Redux store. | User Experience |
| INC-C40602 | 953432 | Nested view name length validation handling updated | Nested views could not be saved when the combined parent and child view names exceeded 64 characters due to automatic name generation. This was due to insufficient length validation during nested view name creation, and has been resolved by adding the pyLabel property to Rule-UI-View. | User Experience |
| INC-C40613 | 953922 | Country code SXM added | Support has been added for country code SXM (Saint Martin, Dutch part). | User Experience |
| INC-C40744 | 951731 | Page focus behavior improved | Page loading was automatically focusing on h3 table label elements instead of appropriate form controls. This has been resolved by updating the focus handling logic to target appropriate interactive elements on page load. | User Experience |
| INC-C40887 | 952503 | Rich Text Editor resizing constrained in multi-column layouts | Rich Text Editors in two-column layouts were expanding beyond their designated column boundaries when resized, overlapping adjacent fields and disrupting form layout. This was caused by insufficient boundary constraints in the resize functionality for scenarios with multiple Rich Text Editors, and has been resolved. | User Experience |
| INC-C41144 | 956425 | Optimized grid row focus resolved | Optimized grids were not consistently focusing on the first row by default. This was traced to a conditional check that was preventing focus from being applied in certain scenarios, and has been corrected. | User Experience |
| INC-C41181 | 951965 | Accessibility updated for report table expand/collapse | Keyboard users could not see focus indicators on expand and collapse icons in report tables within dashboard charts. This has been resolved by adding tabindex attributes in the HTML rendering for expandable table elements. | User Experience |
| INC-C41340 | 951569 | Hijri calendar support added | A comprehensive Hijri calendar control has been added to support Islamic calendar dates. | User Experience |
| INC-C41475 | 954826 | Promoted filter localization functionality corrected | Applications were displaying non-localized values in promoted filters even when the underlying table data was properly localized. This was caused by the promoted filter component not inheriting localization settings from the referenced picklist field, and has been corrected. | User Experience |
| INC-C41479 | 960824 | Dynamic questionnaire UI refresh corrected | When switching picklist options in dynamic questionnaires, the next question would load on the backend but the UI would continue displaying the previous question instead of refreshing to show the new content. This has been resolved. | User Experience |
| INC-C41827 | 953543 | Stale validation message corrected | Validation error messages in grid layouts were persisting after input corrections. This was traced to missing Redux clear message actions when validation states changed, and has been resolved by implementing proper message clearing logic. | User Experience |
| INC-C41858 | 954550 | Modal resize handle removed for improved accessibility | A modal dialog launched in the portal included a resize handle/button in the bottom right of the modal. The resize handle could be clicked and dragged to resize the modal using a mouse, but it could not be interacted with by keyboard or screen reader. This has been addressed by removing the resize button for consistent accessibility. | User Experience |
| INC-C42060 | 965187 | Constellation worklist grouping logic updated | Applications were experiencing errors when attempting to group columns in Constellation Worklist views, particularly when applying both grouping and sorting operations on date columns within pagelist configurations. Investigation showed this was caused by incorrect calculation ID preparation in the underlying query generation logic when processing date column operations in list view landing pages. This has been resolved by correcting the query calculation logic. | User Experience |
| INC-C42330 | 955292 | Profile image display corrected in parallel assignments | Parallel assignments were displaying incorrect profile images where all assignments showed the same user image despite being assigned to different users. This was caused by a stale derived value which only fetched the avatar URL on the initial mount and did not refetch when metaObj.image changed, and has been resolved. | User Experience |
| INC-C42801 | 954421 | Property data persistence corrected | Resolved Issue: Users were experiencing an issue where data that had been cleared from properties was reappearing in the Constellation interface after submitting a screen and returning to it. This has been resolved by updating the data persistence handling for the pzApplyPageInstructions activity. | User Experience |
| INC-C42884 | 953775 | User reference display names corrected in insight tables | User reference properties in Constellation insight tables were displaying operator IDs instead of readable display names when rendered in home widgets. This was traced to the insight table component not properly resolving user reference field display labels at runtime, and has been resolved. | User Experience |
| INC-C43151 | 959969 | Case search loading indicator fixed | Searching for restricted case IDs and pressing Enter resulted in infinite loading indicators despite proper security restrictions being applied. Investigation showed this was caused by improper handling of the busy indicator state when keyboard navigation triggered unauthorized access scenarios. This has been resolved by ensuring the loading indicator properly terminates after displaying security restriction messages. | User Experience |
| INC-C43329 | 956107 | Scroll position maintained during field editing autosave | When editing fields located at the bottom of assignment screens in Data Center, the autosave feature was triggering and automatically scrolling the view back to the top of the page. This was caused by the autosave mechanism not preserving the current scroll position during the save operation, and has been resolved. | User Experience |
| INC-C43395 | 957697 | Text wrapping improved for long content in text boxes | Long text content was overflowing beyond text box boundaries in Constellation. This has been resolved by updating the text wrapping mechanisms for FieldGroup text overflow. | User Experience |
| INC-C43413 | 954819 | Grid actions delete icon accessibility improved | Tooltip support has been added for the delete icon of the Sort Action in the Grid Actions. | User Experience |
| INC-C44604 INC-D6289 |
954539 980117 |
Constellation SLA deadline calculation corrected for assignment widgets |
Assignment SLA deadlines were displaying incorrect due dates in Constellation, showing 2-3 additional days beyond the configured deadline values. When assignment SLAs were configured with deadline intervals of 19 or more days, the system was adding extra days to the original SLA due dates - for example, a 24-day deadline would display as 27 days, and a 30-day deadline would show as 32 days. Investigation showed this was caused by incorrect relative time token calculations in the Constellation DateTimeDisplay component while the underlying pxGoalDateTime and pxDeadlineDateTime values remained accurate in the assignment XML. This has been resolved by modifying the way relative time tokens are calculated in the Constellation components, ensuring that displayed SLA due dates now match the configured deadline values in both Case Review and Perform modes. | User Experience |
| INC-C44746 | 955162 | Decimal field clearing behavior corrected | Applications were allowing form submission without required field validation in Constellation when decimal fields were cleared. This was traced to the system setting values to 0.00 instead of null when fields were emptied, and has been corrected. | User Experience |
| INC-C44913 | 959811 | Documentation updated for field validation behavior with conditional logic | The documentation for Common issues in Constellation has been updated to provide information about using When conditions to disable editable fields such as dropdowns. Given a field, such as “prop1,” which is editable but also has a “disable” attribute set based on a When condition, the field is not immediately disabled. Please refer to the section "Errors when disabling editable fields with a When Condition Rule" for guidance on using custom conditions as a workaround, which validate at runtime and immediately update field states on tabout or on blur events. | User Experience |
| INC-C45205 | 957532 | Scrolling in autocomplete combo box mode corrected | Autocomplete controls which were configured to display results as a list with combo box mode enabled were not showing scroll bars when more than the maximum configured results (5) were returned, and clicking the dropdown arrow was displaying all results instead of respecting the limit. This has been resolved by modifying the autocomplete control to enable scroll bars in combo box mode and properly limit results when the dropdown arrow is clicked. | User Experience |
| INC-C45450 | 957859 | 24-hour date format selection enabled for non-optimized grids | It was not possible to select 24-hour date format for calendar controls within non-optimized grids. This has been resolved by adding the necessary support to the editable date time picker controls for non-optimized grid configurations. | User Experience |
| INC-C45450 INC-C36335 |
955321 955840 |
24-hour date format added for localized calendar controls | Support has been added for a 24-hour date format in the editable date time picker controls when using localization. | User Experience |
| INC-C45461 | 955632 | Data reference table checkbox focus visibility enhanced | Users navigating with keyboards were unable to clearly see focus indicators when the keyboard focus was on the first checkbox inside the data reference property simple table layout. This was caused by insufficient visual styling for focus states on checkbox elements in table contexts, and has been corrected by adding padding to the row select checkbox to give space for an outline focus ring. | User Experience |
| INC-C45593 | 960601 | Screen reader accessibility improved for audit attachments | Screen readers were announcing and focusing on a hidden attachment data frame in the audit tab, causing confusion during navigation. This has been resolved by adding aria-hidden='true' and tabindex='-1' attributes to hide the frame from screen readers so that the iframe label and contents are not announced by screen reader when navigating case history dialog. | User Experience |
| INC-C45690 | 957810 | Checkbox validation error icon positioning fixed | Validation error icons were covering checkbox UI controls in UIKit applications. This has been resolved by adjusting the error icon positioning and margin calculations. | User Experience |
| INC-C45733 | 959522 | Modal dialog error message properly cleared | Error messages in flows running within modal dialogs were persisting even after screen refresh and control value changes. This has been resolved by ensuring error messages are properly cleared when control values change or screens refresh within modal dialog flows. | User Experience |
| INC-C45912 | 963323 | Query list preview rendering fixed in view editing | Query type fields containing scalar lists were not rendering in the preview pane when editing case view screens, despite appearing correctly in actual case views. This was caused by preview rendering logic not properly handling embedded scalar list fields within query lists, and has been resolved. | User Experience |
| INC-C45944 | 961401 | Screen reader error message announcements added for table validation | JAWS screen reader users were not receiving announcements of error messages when navigating to tables with validation errors. This has been resolved. | User Experience |
| INC-C46027 | 959790 | Table column width distribution corrected | The delete column in embedded tables was consuming all remaining width when entering full screen mode, disrupting the intended layout. This was caused by incorrect application of flex-grow properties to the last column instead of columns with fillAvailableSpace set to true, and has been resolved by updating the styledTableContainer to apply flex-grow only to designated columns and properly calculate auto-sizing for screen resizing. | User Experience |
| INC-C46701 | 960154 | Decimal formatting behavior standardized | Decimal properties were inconsistently appending zeros after entering integer values and then clicking outside the field. This has been resolved by updating the handling to ensure trailing zeroes are removed on blur for Decimal. | User Experience |
| INC-C46850 | 957548 | Landing page overlay display issues corrected | Landing pages created with the Tabbed template in Constellation-based setups were displaying overlay issues affecting table column headers. This was caused by CSS rendering conflicts in the Theme Cosmos environment when preview panels were opened alongside tabbed landing page content, and has been resolved. | User Experience |
| INC-C46933 | 958026 | SVG application logo rendering restored | SVG files uploaded as application logos from the Channels & Interfaces page were uploading successfully but were displaying as empty in the runtime portal. This has been resolved by adding the MIME type to image blobs for proper format identification. | User Experience |
| INC-C46979 | 957633 | Date-only field display corrected | Date-only fields in list view promoted filters were not displaying the default year when users selected just the date, with the year only appearing when selecting the To date. This has been corrected. | User Experience |
| INC-C47257 | 959028 | Apple Safari browser focus behavior for embedded data tables corrected | Embedded data table headers were not receiving proper focus when navigating with keyboard controls in Apple Safari browser environments. Investigation showed this was caused by Safari-specific focus handling differences in the data table header cell implementation. This has been resolved by adding outline-offset to show focus in embedded data table header elements. |
User Experience |
| INC-C47263 | 958708 | Helper text focus corrected | Focus was not working for the helper text if there there was a space or line break in the field value for "Help icon with overlay on focus". This has been resolved by adding a check for overlay on focus helper text. | User Experience |
| INC-C47390 | 959776 | Check added to update 'when' triggered for embedded table | The UI did not update correctly when a rule-based read only 'when' condition was triggered in an embedded table. This was traced to the 'when' condition calculation being done on the server and the cell not being re-rendered by the network call in a timely manner. To address this, a readOnly check has been added to update displayMode in react_pconnect instead of cellRenderers.js to ensure 'when' conditions are honored. Additional refinement to this work will be done in a future release. | User Experience |
| INC-C4770 | 960143 | Table focus navigation improved | Non-optimized tables with inline editing experienced focus issues where users could not tab back into the table after editing a row and moving away. This has been resolved with an update to ensure correct focus on the table row when "Click row to edit" is enabled. | User Experience |
| INC-C48743 | 959333 | Table delete column accessibility enhanced | Screen readers were unable to identify delete column headers in configurable tables due to missing accessibility labels. This has been corrected. |
User Experience |
| INC-C48771 | 961615 | Auto-fill behavior corrected | After Google Chrome updates, unsupported auto-fill was being allowed which resulted in unexpected behaviors. This was due to browser changes that were no longer honoring the previous settings, and has been resolved. | User Experience |
| INC-C48949 INC-C56393 |
962662 967165 |
BlendedUI navigation issues for landing pages and assignments corrected | Navigation functionality was experiencing problems where clicking menu icons failed to switch screens and URL and tab names were changing across all browser tabs in Constellation applications. This has been resolved by updating the traditionalGadgetId to ensure proper gadget reloading for landing pages and by adding support for launching assignments of traditional cases from the Constellation portal using assignmentURL. Additional work has been added to prevent URL and tab name synchronization across multiple browser tabs. | User Experience |
| INC-C49227 | 960861 | Picklist value persistence corrected | Picklist values were reverting to their original state after being updated and saved on certain screens. Investigation showed this was caused by custom expressions incorrectly evaluating string comparisons in the Constellation frontend. This has been addressed with by updating the expression evaluation logic to properly handle string value comparisons with equals and not equals operators for nullish values. | User Experience |
| INC-C49325 | 963719 | Custom DX component visibility consistency restored | Custom field-level DX components for bulk data onboarding were intermittently not appearing when users first accessed assignments, requiring cancel and reopen operations to display correctly. Investigation showed this was caused by timing issues in the component rendering lifecycle during initial assignment loading. To resolve this, an update has been made to the component initialization sequencing to ensure consistent visibility. | User Experience |
| INC-C49366 | 962917 | Focus navigation restored for form fields accessibility | Form fields were experiencing focus lock on the first field when page messages were displayed after validation errors, preventing navigation to other fields via keyboard or mouse. This has been resolved. | User Experience |
| INC-C50255 | 960759 | Corrected table reordering with RTE | Reordering tables containing embedded fields with Rich Text Editor (RTE) properties was causing content display failures or RTE disappearance. Investigation showed this was caused by improper handling of RTE components during table reordering operations in the Constellation UI, and has been corrected. | User Experience |
| INC-C50529 | 963440 | Unnecessary tracer failures eliminated during case creation | Case creation was generating false failure entries in the tracer due to attempts to access a non-existent CoexistenceCasesDT data transform in the pxGetCaseTypesForCoexistence activity. This was caused by hardcoded references to data transforms not supplied with the Pega product, and has been resolved by adding proper existence checks before attempting to access the coexistence data transform. | User Experience |
| INC-C50601 | 980145 | Chat functionality restored for real-time messaging and agent availability | Customer service representatives were not receiving new chat assignments for extended periods and were missing real-time customer messages during active conversations. Customer responses were visible after navigating away from the current chat screen and returning, and some messages showed as "Undeliverable". This was caused by capacity updates during chat wrap-up processes and CASE/DATAPAGE_UPDATED events not being properly handled, and has been resolved by adding an extra parameter to the closeContainer Item to allow Customer Service to differentiate between wrap-up and dismiss case actions, and by implementing proper unsubscribe functionality for CASE and DATAPAGE_UPDATED events to ensure real-time message delivery. | User Experience |
| INC-C50675 | 964411 | Date time spinner year restriction corrected | Date time controls with spinner navigation were displaying additional years beyond the current year even when configured to restrict both previous and future years to zero. This has been resolved by adding a "restrictToCurrentYear flag" to restrict the date range in spinner mode when 0 is set for both next and previous. | User Experience |
| INC-C50741 INC-D851 |
961537 970920 |
DX API payload handling corrected after upgrade | After upgrading from Pega 8.7 to Infinity 24.1, multi-select dropdown values in DX-API assignment/action/refresh calls were showing index values replaced with characters in the payload. This has been resolved. | User Experience |
| INC-C50833 | 960781 | Datatype edit view enabled | Previously, the pyEdit view could not be created directly in the Views tab for datatypes in Cosmos theme Constellation landing pages. With this update, pyEdit has been added to the Section rule in Data- so that it can be overridden into a data type's class and edited for List page table column editing purposes. | User Experience |
| INC-C51009 | 964347 | Embedded table focus behavior updated | Inline editable embedded tables were triggering validation errors when adding new rows due to focus shifting from mandatory fields back to the cell container. This was caused by conflicting autofocus attributes interfering with the accessibility-focused cell navigation system, and has been addressed by removing autofocus attributes when whole-cell focus is required for proper table navigation. | User Experience |
| INC-C51191 | 960672 | Rich Text Editor keyboard button localization added | Localization has been added for the "Keyboard" button and "Rich Text Editor toolbar keyboard shortcuts" text in the RTE control. | User Experience |
| INC-C51282 | 962168 | Notification timestamps corrected to local time | System notifications were displaying timestamps in GMT rather than respecting local time zone settings. This has been resolved by implementing proper time zone conversion in the notification display. | User Experience |
| INC-C51478 | 966170 | Summary panel refresh mechanism restored | Case summary panels were not properly refreshing field visibility when cases transitioned between stages, requiring manual expand/collapse actions to display all configured fields. Investigation showed the panel refresh logic was not properly re-evaluating visibility conditions after stage transitions. This has been resolved with an update which resets the truncation/display state and triggers a re-measure when the set of summary items changes. | User Experience |
| INC-C51543 | 961597 | Search functionality smart tip interaction resolved | Search functionality was malfunctioning when smart tips were enabled on search icons, preventing the search window popup from appearing during runtime. This was caused by conflicting interactions between smart tip overlays and search popup functionality, and has been resolved by removing the smart tip. | User Experience |
| INC-C51589 | 967586 | Date range control warning popup resolved | Warning popups were appearing incorrectly when navigating away from forms containing date range controls, even when no changes had been made to the form. This was traced to the date range control not properly tracking its initial state, leading the system to incorrectly detect unsaved changes. To resolve this, a data-initialvalue attribute has been added to the date range control to properly track the control's initial state and prevent false dirty form detection. | User Experience |
| INC-C51769 | 962272 | DateTime field value persistence fixed | Users were experiencing datetime property fields becoming blank when clicking on the field and submitting without making changes, particularly in meeting scheduling workflows. This was traced to the handling of unchanged datetime values during form submission processing, and has been resolved by correcting the datetime component logic to preserve existing values when no modifications are made. | User Experience |
| INC-C51822 | 965618 | Text truncation and icon overlap issue resolved | Stage labels with excessive characters were displaying ellipses truncation while check mark icons overlapped with chevron elements. This was caused by improper spacing calculations between text elements and styled icons with border-radius, and has been resolved by updating the CSS. | User Experience |
| INC-C52369 | 964293 | Constellation hidden mandatory field validation corrected | Applications were experiencing validation errors on mandatory fields that had been configured as hidden in Constellation UI due to the validateHiddenField configuration setting not being properly respected. This has been resolved by updating the field validation logic. | User Experience |
| INC-C52455 | 966490 | Custom action submission error resolved for operator preferences | A 500 error was occurring when submitting custom actions to update the pyUseLocale property from operator preference landing pages that were mapped to Operator ID data types. This was caused by improper handling of the view submit action API when processing locale updates, and has been corrected. |
User Experience |
| INC-C52533 | 966064 | Flow action work object close handling updated | When using the "Close the Work Object" option under "If an assignment is not being performed" for a flow action, the application displayed a gray screen on the first attempt instead of properly navigating or closing the work object. On subsequent attempts, the work object closed as expected and returned to the Home harness. This has been resolved with an update to close the Work Object after the flow action. | User Experience |
| INC-C52644 | 962094 | Corrected duplicate values shown in promoted filters | Duplicate work status values were appearing repeatedly when scrolling through promoted filter pick lists on landing pages. This was caused by the fetchPossibleValues function in ValueSelector duplicating the same list of values multiple times during load operations, and has been resolved. | User Experience |
| INC-C52779 INC-D5956 |
967081 975931 |
Military time format updated to resolve single digit hours | Applications working with 24-hour time formats were displaying single-digit hours (0-9) displayed without leading zeros, which conflicted with military time standards requiring double-digit hour formatting (00-09). This has been resolved by updating the date time calendar and input display logic with a new flag 'enable24HourFormatting' which is enabled by setting the pega.u.d.enable24HourFormatting value to true in userWorkForm. | User Experience |
| INC-C52811 | 961970 | Web embed errors properly displayed | Web embed implementations were displaying blank screens instead of error messages when case creation failed due to rate limiting or other validation errors. Investigation showed this was caused by the web embed framework not properly handling and displaying error responses from case creation failures. This has been corrected. | User Experience |
| INC-C53192 | 968601 | AnyPicker search handling corrected | When searching for a field in the Engagement Policy AnyPicker dropdown and selecting it, the displayed value differed from the one chosen. Additionally, if a value was selected from the dropdown, the system incorrectly selected the next value in the list instead of the intended one. This was an issue with the field search functionality not correctly handling the first row, and has been corrected. | User Experience |
| INC-C53523 | 965229 | Read-only number formatting consistent for all digit lengths | Read-only formatting for number controls was not being applied to 3-digit numbers and below, while working correctly for 4-digit numbers. This has been resolved by updating the data-changed attribute condition conditional logic in the pzpega_ui_events.js changeHandler function to properly handle formatting for numbers of all digit lengths. | User Experience |
| INC-C53585 | 973719 | Rich Text Editor spellchecker issue corrected | The spellchecker in the Rich Text Editor was not flagging any misspelt words starting with upper case 'R'. This was caused by a faulty regex pattern in the spellchecker_v2 file, and has been resolved. | User Experience |
| INC-C53759 | 963250 | Embedded data modal submission fixed | Auto-populated embedded data values in modal dialogs were not updating in corresponding table rows when forms were submitted, preventing new rows from being added. This was caused by missing page instructions in the second refresh of submit embedded modal payload, and has been resolved by ensuring proper page instruction handling during embedded modal submissions. | User Experience |
| INC-C53836 | 966393 | Date format display consistency improved | Date fields in case left panes were not displaying with configured formats on initial load, showing proper formatting only after refresh or case reopening. This was caused by improper dependency referencing in scalar list components within case summaries. This has been resolved by adding componentType to pxDependencies for ScalarList metadata. | User Experience |
| INC-C54056 | 964457 | Custom DX components loading fixed in Dev Studio | Custom DX components were failing to load when launching cases from Dev Studio, displaying 404 errors and preventing component functionality. This was caused by missing component loading logic specific to the Dev Studio environment, and has been resolved. | User Experience |
| INC-C54074 | 967998 | Corrected duplicate row creation during attachment upload | Adding attachments while editing new rows in repeating views was causing duplicate rows to appear in the grid. This was caused by improper state management during the attachment modal workflow in Constellation, and has been resolved by clearing saved properties from the context tree when the openLocalAction API is invoked. | User Experience |
| INC-C54097 | 965217 | Decimal field length validation restored | Decimal fields were accepting more than the expected 12-digit maximum length and displaying NaN values when exceeding 16 digits. Investigation showed this was an unintended side effect of previous work on decimal field validation logic, and has been resolved by implementing client-side validation to restrict the number of digits accepted and ensure proper input validation to prevent excessively large numbers from being entered. | User Experience |
| INC-C54122 | 970096 | Currency field display corrected for empty values | Currency fields in table views were incorrectly displaying "0.00" when the actual value was blank, particularly when data was populated through VRL responses or refresh calls. This has been resolved by ensuring currency fields maintain proper null values when no data is present, preventing the automatic conversion to zero. | User Experience |
| INC-C54311 | 966465 | Screen reader accessibility improved for table fields popup | Screen readers were reading the entire popup content after navigating past the last row in the Fields popup within optimized table configurations. This has been resolved by making the dialog body focusable when firstFocusableElement is not present in modal or popover. | User Experience |
| INC-C54427 | 968617 | Constellation case can be created from traditional case in Blended UI | Applications using Blended UI were experiencing issues when attempting to create Constellation cases from traditional cases, with new cases incorrectly opening in blended mode instead of the expected Constellation mode. This has been resolved with an update that implements UI mode detection and routing logic that ensures cases created from blended traditional cases correctly open in Constellation mode when the target case type is configured for Constellation, with flow parameters now properly converted to starting field properties to maintain compatibility with Constellation's architecture. | User Experience |
| INC-C54603 | 968649 | Corrected handling for parameterized checkbox inside repeating views | Checkbox groups backed by data reference properties with different parameters were experiencing option changes when users interacted with multiple checkbox groups on the same view. This has been resolved by updating the parameter handling logic to maintain distinct options for each checkbox group. | User Experience |
| INC-C54634 | 972485 | Theme preview display for migrated environments corrected | After update, migrated environments were showing blank previews instead of the configured colors in theme previews for mobile channels. This has been resolved by adding a check for pzLegacyTheming with getIfPresentMethod. | User Experience |
| INC-C54843 | 967722 | Anypicker control error accessibility updated | Screen readers were not announcing validation errors for anypicker controls. This has been resolved by adding the necessary aria-describedby attributes for the server side validations. | User Experience |
| INC-C54852 | 968605 | Button keyboard navigation restored for dirty forms | Buttons configured with both Click and Enter events were not responding to keyboard Enter presses when forms were dirty and only perform harness was present. This was caused by a missed use case in new feature implementation that prevented proper keyboard event handling on dirty forms, and has been resolved. | User Experience |
| INC-C54972 | 965949 | Modal keyboard navigation accessibility improved | Modal dialogs containing multiple tables with hidden default action buttons were not allowing proper keyboard tab navigation through all elements, with focus cycling back to the modal top instead of progressing through table elements. This was caused by the isSrcfromLastTable function incorrectly returning true even when the source was not from the last table, and has been resolved by correcting the table source detection logic. | User Experience |
| INC-C55204 | 965337 | Case preview corrected for hybrid applications | Case preview was not functioning for Constellation cases within hybrid application models that utilized both Cosmos and Constellation case types. Investigation showed this was caused by missing PreviewViewContainer components in the RootContainer and incorrect context handling that restricted preview loading in hybrid environments, and has been corrected. | User Experience |
| INC-C55318 | 968783 | Attachment field error clearance corrected | Error messages were persisting in attachment fields even after removing invalid files. This has been corrected. | User Experience |
| INC-C55697 INC-D54 |
970100 971885 |
Validation error labels fixed for pagelist properties | Validation error messages were not displaying field labels for pagelist properties even when the displayFieldNameInValidationMsg DSS was enabled. This was caused by the validation message system not properly handling pagelist property labels when the DSS setting was active, and has been resolved. |
User Experience |
| INC-C56147 | 966723 | Date picker correctly announces current date | Date picker controls were applying aria-current="date" to selected dates instead of today's date. This has been resolved by implementing proper aria-current="date" for today's date and aria-selected="true" for selected dates when appropriate in the pzpega_ui_calendar.js functions to improve accessibility. | User Experience |
| INC-C56309 | 965407 | Localization bundle creation corrected in Constellation applications | Applications were experiencing failures when attempting to create localization bundles in Constellation, particularly affecting Japanese language pack creation where users encountered "Failed generation" error messages during the localization process in App Studio. This was traced to the handling for type conflicts in bundles during bundle merges with an additional issue of limitations processing Excel imports exceeding 64K rows, and has been resolved. | User Experience |
| INC-C56366 | 968655 | Rich Text Editor resize toggle default updated | After upgrade, Rich Text Editor controls were missing the resizing capability which had been available by default. This was traced to the introduction of a resize toggle feature that changed the default behavior without maintaining backward compatibility, and has been resolved by restoring the default of pyRTEResizeToggle to true for better backwards compatibility. | User Experience |
| INC-C56469 | 968255 | File path control upload behavior corrected | When FilePath Control was added in the section and a file other than png or jpg was uploaded, it was not possible to locate the uploaded file. Investigation showed file path controls were adding incorrect values to pxRequestor.pyFileUpload after update due to the upload handler assuming every multipart file part represented a valid selected file. This has been resolved with an update to FileUploadHandler which will skip file parts when the uploaded size is 0 or the filename is blank, so empty/unselected file inputs are ignored instead of flowing into normal file-save logic. | User Experience |
| INC-C56722 | 967430 | Label display issue with dots resolved in Angular UI | Labels containing dots were not displaying properly in Angular UI applications. This has been resolved by modifying the RUF's pzdxapifulljsonforvieworpage and pzdxapijsonforfield to properly quote label values, ensuring labels with dots and other special characters display correctly in Angular UI applications. |
User Experience |
| INC-C56896 | 968975 | Grid view switching restored for parameterized data pages | Applications were experiencing null pointer exceptions when attempting to switch back to the default view from any other view of a table sourced from a parameter datapage. This was traced to the system deleting parameterized data page instances from the clipboard while they were still being referenced by the view switching API, and has been resolved with an update to necessary instances in the clipboard during view operations. | User Experience |
| INC-C56949 | 972771 | Data reference property navigation for data objects fixed | Data reference property links in data object details tabs were not displaying target data properly, showing blank screens instead of the expected data content. Investigation showed unique ID generation for the pyDetails view was only handled for case objects and not data objects, preventing proper component unmounting and refresh. This has been resolved with an update which uses caseId if present, otherwise a stable unique ID will be generated from dataInfo (dataContext + sorted dataContextParameters). | User Experience |
| INC-C56976 | 975658 | Screen flow attachment deletion behavior corrected | Screen flows were exhibiting incorrect attachment behavior where deleted attachments would reappear when navigating between steps, and attempting to delete them again would cause submission errors. This has been resolved by correcting the attachment lifecycle management in screen flow contexts to prevent deleted attachments from reappearing after cancel and reopen in multi-step forms. | User Experience |
| INC-C57109 | 968189 | Promoted filter null record display corrected | Applications were experiencing issues where promoted filters using True/False properties were not displaying records with null values when "False" was selected. This was traced to the cosmos Boolean Display component not properly handling null values in the filter logic, and has been resolved with an update which renders a display-only checkbox with null value as NoValue. | User Experience |
| INC-C57401 | 973265 | Page message display enhanced for search and select component | Messages set on pages through activities were not being cleared after correct values were entered in search and select components, and page-level messages were not displaying properly at the flow container level. This was caused by error classification issues and missing message propagation to the flow container, and has been corrected. | User Experience |
| INC-C57552 | 970899 | Complex embedded data structures persist for case reopening | Saved data including radio controls, dropdowns, and search results did not load correctly when cases with complex embedded structures were reopened from the flow after using the "Save for Later" functionality. This has been resolved by enhancing the data restoration logic to properly handle complex embedded structures during case reopening operations. | User Experience |
| INC-C57828 | 971911 | Column menu display labels corrected | Table view column menus were displaying property IDs instead of configured labels when adding Page or Page list properties, even when proper labels were configured in the record definition. Investigation showed the column menu was referencing internal identifiers rather than display labels for these property types, and this has been corrected. | User Experience |
| INC-C57985 | 976728 | Class rename wizard reference handling updated | The Rename Class and Search/Replace String wizards were not updating references in View rules when renaming classes, causing referenced rules to show error messages about being unable to open rules with the old class names. This was caused by incomplete reference updating logic specifically for View rule types during class renaming operations, and has been resolved by ensuring all rule references are properly updated during class rename operations by regenerating rule references on updating Views / Landing Pages. | User Experience |
| INC-C58029 | 967559 | Debug headers removed for web embed compatibility | Web Embed applications hosted in third-party environments were experiencing CORS policy violations when performing Cancel and Save for Later actions. Investigation showed this was caused by x-pega-app-debug-* headers being sent unconditionally to all client applications, including those not configured to accept these debugging headers in their CORS policies. This has been resolved by removing the debug headers for Cancel and Save for Later. | User Experience |
| INC-C58105 | 972473 | Date input validation corrected for promoted filters | Manual date range entry in Insights promoted filters was being rejected with the error message "Invalid date range". This has been resolved by updating the handling for focus-within detection when focus/mouse events occur inside the Shadow DOM and when using portals/iframes. | User Experience |
| INC-C58145 | 970159 | Screen reader accessibility enhanced for error messages | Error messages displayed through the NoID harness and pyIdNoHeader section were not being announced by screen readers like JAWS. This has been corrected by adding the necessary roles. | User Experience |
| INC-C58233 | 967542 | View designer data persistence improved in Constellation | JavaScript errors were occurring when closing the view designer in Constellation, resulting in incomplete saving of view changes. This has been resolved with an update avoid a NullType error by verifying contentDocument before rendering the content onto IFrame in Preview. | User Experience |
| INC-C58357 | 968585 | Nested page list data integrity maintained during refresh operations | Data was being lost in nested page lists when refresh operations occurred, specifically affecting QuestionGroups.Questions structures where EmbedUUID values were regenerated causing previously submitted values to become inaccessible. This was traced to differences in the path handling between pathPrefix and nestedPath in the cascade manager, and has been resolved by updating the replace logic for proper UUID matching. | User Experience |
| INC-C58416 | 974723 | Corrected unexpected date range calendar scrolling | Date range controls were causing unwanted page scrolling when opening the calendar, with the screen jumping to the top instead of maintaining the current scroll position. This was traced to the screen position adjustment logic in the calendar display mechanism, and has been resolved by adjusting the timing of focus setting in the date range picker component. The focus is now set after the container is fully displayed and positioned. | User Experience |
| INC-C59174 | 972090 | Menu item focus behavior improved for reports tab | The My Reports tab in traditional applications was retaining the Menu-item-active CSS class even after clicking elsewhere on the screen or focusing on other elements. This was determined to be style inconsistency caused by a reload being triggered through customizations, and has been resolved. The styling has also been modified to update the selected-item indicator color and add a background color for the selected menu item anchor, making the active menu item clearer and more consistent. | User Experience |
| INC-C59175 | 973521 | Console error when opening Constellation cases resolved | "Uncaught ReferenceError: PCore is not defined" console errors were generated when attempting to open Constellation cases in the Cosmos Portal, though no functional issues occurred. Investigation showed this was caused by the disconnectedCallback method being triggered for web components when the tertiary container div was removed, at a time when PCore was not yet initialized. This has been resolved by adding proper undefined checks to safely handle the PCore initialization timing. | User Experience |
| INC-C59187 INC-D24469 |
973515 1001377 |
Accessibility overlay dialog titles improved | Overlays launched in the application were displaying non-meaningful dialog titles containing camel case text, "py-" prefixes, or backend IDs, creating accessibility issues for screen reader users. This was traced to changes from previous accessibility work which automatically applied flow action short descriptions as aria-label attributes without validation. This has been resolved with an update to set overlays to use role="tooltip" if there are no interactive elements in the dialog. If there are interactive elements in the dialog, the overlay will have role="dialog" and aria-label value sourced from the flow action short description. | User Experience |
| INC-C59251 INC-C53488 |
972509 972990 |
Accordion accessibility state announcements restored for screen readers | Screen readers were not properly announcing the expanded state when accordion layout groups were opened. This was an unintended side effect of work done for focus indicator issues on expand/collapse headers, and has been resolved by updating the pzpega_ui_layoutgroup_js rule to restore proper ARIA state communication to screen readers while maintaining the focus indicator functionality, ensuring accordion expand/collapse states are correctly announced by NVDA and other assistive technologies. | User Experience |
| INC-C59383 | 969120 | Focus indicator corrected for collapsible dynamic layouts | Collapsible dynamic layout headings were not displaying focus indicators when the summary pane was collapsed. This has been resolved by adding appropriate CSS handling to ensure focus indicator styles appear correctly when navigating to collapsible headings in all states. | User Experience |
| INC-C59384 | 970031 | Decision table and paragraph editing access corrected for coexistence mode | Users were receiving 403 forbidden errors when attempting to edit decision tables or paragraphs in Blended UI coexistence environments. This was caused by the Pega-desktop-api openrule action missing required skin and portal name parameters for coexistence cases, and has been corrected. | User Experience |
| INC-C59531 | 974552 | Search modal tooltip interference eliminated | In Theme Cosmos, search modal dialogs were closing immediately after opening when the cursor remained on the search icon. This was caused by conflicting hover and focus actions configured on the search button in WorkSearchGadgetHeader , and has been resolved by removing the “Smart tooltip” behavior from the header search button. | User Experience |
| INC-C59544 | 968681 | Search and select controls handling updated for multiple entity configurations | Applications using repeating views with multiple Search and Select controls were experiencing issues where only the last control would return search results while earlier controls remained in a loading state, and searching in one control was causing all other Search and Select controls in the repeating view to refresh unexpectedly. This was traced to the same property reference being assigned to multiple controls, and has been resolved by updating the handling of multiple associated entities within the same repeating view context. | User Experience |
| INC-C59702 | 972288 | View property display fixed for matching page and property names | Views were not displaying property labels when the page name and property name were identical, such as when adding an embedded field named "Customer" to a page also named "Customer". This was traced to the pzAdjustContentClass activity evaluating where the condition !lastItem.equals(currentProperty) as false for matching names, causing the wrong class to be used for property evaluation. This has been resolved by updating the pzAdjustContentClass Activity logic to properly handle scenarios where page names and property names are identical. | User Experience |
| INC-C59988 | 979337 | Field group layout and conditional logic updated | 2-column layouts within field groups were rendering as stacked layouts instead of the configured column arrangement, and 'when' rules within field groups were not executing as intended. This was traced to logic that could incorrectly render the navigation template as a MultiStepForm instead of a normal StandardForm, and has been resolved by correcting the assignment component layout logic so that Standard navigation templates and single-step flows render with StandardForm, while only non-standard templates render MultiStepForm. | User Experience |
| INC-C60124 | 970790 | Date field year range configuration accuracy improved | After configuring a date field to be of precisely the current year range by configuring next and previous years in range as zero, it was not possible to select December 31 of the current year, the year drop down had the previous year entry available, and selecting January 1 of the current year enabled the previous year. This was traced to timezone-related calculations affecting year boundary determinations and dropdown population logic, and has been corrected. | User Experience |
| INC-C9516 | 919552 | Accessibility list structure corrected | Applications were displaying incorrect list structures for case ID text elements, affecting screen reader accessibility. This has been resolved by correcting the list structure generation MetaList configuration in the accessibility framework to ensure proper accessibility. | User Experience |
| INC-D10078 | 982264 | Date range picker accessibility improved | Date range picker modal dialogs were missing both accessible names and dialog roles. This has been resolved by adding proper dialog roles and localized aria-labels in pzpega_ui_daterangepicker and pzClientLocaleData. | User Experience |
| INC-D10116 | 980393 | Blended UI navigation and case creation issues addressed | When creating new cases from existing cases in the Blended UI (such as scheduling appointments), the parent case link was not updating to reflect the newly created case and the Recents list was not displaying new cases. Additionally, browser tabs were displaying Case Type names instead of Case IDs or Labels, and page loading was failing intermittently during navigation through landing pages despite correct URL updates. This was traced to case reference handling and tab management in the Blended UI framework, and has been resolved by updating case linking, Recents list refresh functionality, correct tab labeling with Case IDs, and improving page loading reliability in Blended UI navigation. | User Experience |
| INC-D10143 | 983137 | Case type localization fixed in browser tab titles | Case type names in browser tab titles were not displaying localized text in Constellation applications. This has been corrected. | User Experience |
| INC-D10282 | 982250 | Accessibility corrected for date control table markup | Date controls were generating inaccessible table markup in headers, including layout table semantics that were being read by screen readers during date picker interactions. This was caused by missing role="presentation" attributes on non-tabular table elements in the buildHeaderSpinners() function, and has been corrected. | User Experience |
| INC-D10515 | 985003 | Optimized table responsiveness checkbox behavior corrected | The Responsiveness checkbox was incorrectly remaining enabled and checked in optimized tables when users unchecked "Optimize code", selected responsiveness, then re-enabled "Optimize code", causing mobile-specific views to appear inappropriately. Investigation showed this was caused by the system retaining the last checkbox state before disabling rather than properly resetting it. This has been resolved by ensuring the Responsiveness checkbox is properly disabled and unchecked when Optimize code is enabled. | User Experience |
| INC-D10601 | 983142 | Corrected field flickering in summary UI views | Fields within summary sections of Interaction case full page views were flickering. This has been resolved by updating the styling to adapt more naturally when placed in different layouts, side panels, or constrained regions, especially around medium-width breakpoints. | User Experience |
| INC-D10676 | 981499 | Pulse search bar visibility corrected | The Search option for the search bar in Pulse was disappearing when the cursor moved over it. This was caused by conflicting Smart Tip configurations on the search icon and dropdown arrow elements, and has been resolved by removing the Smart Tip behavior from the Pulse search widget. | User Experience |
| INC-D10764 | 985184 | Left menu alignment corrected after update | After update, navigation panel menu items were displaying with misaligned child items. This has been resolved by updating the sub-menu alignment in left navigation by adding display: flex !important; to the .menu-item-anchor rule. | User Experience |
| INC-D10861 | 990060 | SIAA email composition data persistence restored | When proceeding through the "Send AdHoc Message" outbound email creation process in Smart Investigate Agentic Automation Framework, selecting an email template, navigating to the corresponding ORCH case, and then returning to the "Compose Email" assignment caused all previously selected data to be lost. Investigation showed this was due to openWorkByHandle failing to recognize and reuse an already-open item when encountering a multi-document-portal case for child-case assignments, instead treating it like it needed to be opened again. This has been resolved by adding a fallback check for an existing assignment item with child-case context (parentCaseInfo) and a semantic URL, then explicitly activating that container item instead of always re-fetching when activation details aren’t returned by the standard activation lookup. | User Experience |
| INC-D11037 | 985493 | Optional actions functionality restored for resolved interaction cases | Case-wide optional actions on resolved interaction cases were becoming unresponsive after submission, preventing further actions like case dismissal. This was caused by missing refresh calls on pyCaseSummary for closed interaction cases, and has been resolved by ensuring key population when finishing an assignment on a resolved case. | User Experience |
| INC-D11102 | 988082 | Busy status indicator corrected for embedded sections | The data-state-busy-status attribute remained "busy" after save completion when save operations occurred inside Repeating Dynamic Layout (RDL) with embedded pages containing dots in property paths. This was caused by selector failures in pzpega_ui_doc_focus.js when handling property paths with dots, and has been resolved by adding handling for dots and other special characters. | User Experience |
| INC-D11122 | 981822 | Localization corrected for browser and requestor locale settings | Localization was not being applied as expected when using browser locale or pxRequestor.pxReqLocale settings, even after importing language packs and following standard localization procedures. Investigation showed this was caused by Constellation portals not properly determining locale priority when operator locale was left empty and browser language was set to non-English languages. This has been resolved by implementing a proper locale determination hierarchy where Constellation portals now follow the priority order of Operator locale → Browser locale → Default locale, ensuring that language bundles are correctly loaded in environment info for browser locale scenarios. | User Experience |
| INC-D1137 INC-D2580 |
977710 978235 |
Redundant screen reader announcements removed | Unnecessary screen reader announcements of "Top panel", "Bottom Panel region", and similar labels were triggered during page navigation, and announcements of "Information on the content" were duplicated when contentinfo roles were added to footer elements. This was due to redundant ARIA label announcements on header, main, and footer landmarks, and has been resolved by removing the unnecessary attributes in the GenerateLayout rule file. | User Experience |
| INC-D11672 | 987347 | DX API readonly field evaluation accuracy improved | Angular starter pack applications were incorrectly rendering embedded sections as read-only when developers configured WHEN rules in DATA- class for readonly conditions in Repeating Dynamic Layout (RDL), regardless of the WHEN rule evaluation. Investigation showed this was caused by two issues: WHEN rules were not being resolved correctly, and readonly tables present in the same section were affecting the readonly condition evaluation. This has been resolved by modifying the pzdxapifulljsonforvieworpage function to properly handle readOnly conditions in cases where table grids and RDL exist in the same layout. | User Experience |
| INC-D11723 | 988600 | Date entity highlighting restored | After update, email processing applications were extracting date entities correctly but failing to highlight them in the user interface. This has been corrected. | User Experience |
| INC-D11767 | 982259 | Visibility when rules corrected for embedded data modals | After update, visibility when rules were not functioning properly in embedded data modal views, causing configured fields to remain hidden inappropriately. Investigation showed this was caused by incomplete data merging that only included caseInfo content data without the necessary context data containing summary_of_when_conditions. This has been resolved by modifying the handling around updating context_data when merging interest-path data so context metadata stays in sync with the primary data merge. | User Experience |
| INC-D11789 | 983103 | Promoted filters functionality restored for list views | User reference properties configured as promoted filters were not displaying properly in list view landing pages, showing blank screens when attempting to add promoted filters. This was traced to an issue with the handling of user reference property types in the promoted filter rendering logic, and has been resolved by correcting the promoted filter display mechanism to properly support user reference properties and other complex data types in list view configurations. | User Experience |
| INC-D11991 | 987419 | PDF image orientation support enhanced | iPhone JPEG images were not displaying with correct orientation in generated PDFs due to EXIF orientation data not being processed. This has been resolved by updating pd4ml to a version which includes EXIF orientation support for JPEG images. | User Experience |
| INC-D12233 | 984074 | Localized date pasting handling updated | Date input fields were rejecting date values containing January when they were pasted into date input controls, while other months worked correctly. This was traced to date parsing logic that incorrectly handled January month values during paste operations, and has been corrected with an update to better parse locale-formatted date/time strings. | User Experience |
| INC-D12317 | 988952 | Menu accessibility improved for disabled items | It was not possible to close menus containing only disabled items using the Escape key. This has been resolved by updating the menu component to properly handle keyboard navigation and closure events regardless of item states. | User Experience |
| INC-D12327 | 982908 | Localization migration fixed for short ruleset names | Applications with main ruleset names of five characters or fewer were experiencing failures during localization bundle generation when running the pxMigrationToLocalizationV2 activity. The activity was throwing a StringIndexOutOfBoundsException and only creating the base bundle in the unlocked ruleset version, while the localized ruleset and localized bundle were not being generated. Investigation showed this was caused by string length assumptions that led to an invalid substring operation, and has been resolved by correcting the string handling logic in the activity. | User Experience |
| INC-D12360 | 992072 | Excessive client-side refresh calls resolved after Constellation upgrade | Applications were experiencing a significant increase in PATCH .../refresh calls immediately following the Constellation runtime upgrade. This has been resolved by modifying the system to call refresh only on composite keys when onlyAllowRefreshOnCompositeKeys is true. | User Experience |
| INC-D12361 | 985634 | DateTime picker timezone handling standardized | The "Set now" button in DateTime picker was using browser local timezone instead of the configured server timezone, resulting in incorrect timestamps when timezones differed. This has been resolved by standardizing "Set now" to use operator timezone when provided, instead of browser timezone. | User Experience |
| INC-D12426 | 982254 | Modal popup display restored | The Create Workbasket form was rendering inline below the workbasket list table instead of opening in the expected modal popup when users clicked the '+' (Add) button in Manage Workbaskets. Investigation showed that the preview modal functionality was not working correctly for Add operations, and this has been resolved. | User Experience |
| INC-D12567 | 985243 | Delete handling updated to prevent conflicts with custom actions | After update, a custom case-wide action named "Delete" was triggering a browser confirmation dialog ("Are you sure you want to delete this record?") instead of invoking the configured flow action. This was caused by the standard delete handling intercepting actions with the "Delete" name. To support customizations, the action name resolution logic has been updated so the case-wide Delete action is opened via openLocalAction instead of being executed via deleteWork. | User Experience |
| INC-D12574 | 992759 | Corrected Rich Text Editor image source attribution loss | Images added to Rich Text Editor content were losing their src attributes when DOM purification was applied, resulting in broken image references where <img src="webwb/newimage.jpg"> became <img > after source editing. This was a missed use case in the updated DOM purification feature implementation, and has been corrected. | User Experience |
| INC-D12603 | 985827 | Table column sort announcements localized | Screen readers were announcing sorted table column status in English instead of the localized language. This was due to case sensitivity mismatch between sort strings and localization bundles, and has been resolved by correcting the case matching. | User Experience |
| INC-D13081 | 984978 | Table column correctly reordering with row selection | Column reordering functionality was not working properly in tables with row selection enabled, where header columns would move but the corresponding data columns remained in their original positions. Investigation showed this happened when row selection was enabled and categorization was disabled, and was caused by a mismatch in the 'expand-collapse' class handling between the header and data rows. This has been resolved. | User Experience |
| INC-D13229 | 984574 | Search and select component caching corrected | Search and select controls within page lists were displaying incorrect cached data after items were removed from the middle of page lists. This was caused by component caching using index-based keys that became misaligned when list items were deleted, and has been resolved by updating the caching mechanism to use stable identifiers that remain consistent when page list items are added or removed. | User Experience |
| INC-D13342 | 984661 | Constellation dynamic text localization restored | Dynamic text localization functionality was not working in Constellation applications after update. This has been resolved by updating the handling for the dynamic text localization functionality to replace localeUtils imports/usages with getLocaleUtils(). | User Experience |
| INC-D13778 | 984639 | Queue processor status transitions corrected | The pyProcessSLA Queue Processor was intermittently transitioning to a FAILED state and then returning to RUNNING approximately every 10-15 minutes, and null pointer exceptions were occurring from the pxIsAFollower function during FollowUnfollowHelperText operations. This was traced to a null pointer exception in the pzIsAFollower Rule-Utility-Function where the parameter defaulting logic was not properly handling null pages and values for Context/Follower parameters, and has been resolved. | User Experience |
| INC-D1391 INC-D9927 |
972679 981571 |
Looped assignment view rendering restored | Assignment views in case flows with loop conditions were not rendering and appeared blank, while the same assignments worked correctly when the loop was removed at runtime. Console errors were visible when attempting to display assignment views within looped flow steps, preventing users from completing their work. Investigation showed this was caused by the view rendering engine not properly handling assignment contexts within looped flow conditions, and has been resolved by correcting the MultiStepForm rendering for Standard navigation template. | User Experience |
| INC-D14132 | 985315 | Percentage field decimal validation corrected | Percentage fields were not properly detecting changes when users modified only the decimal point formatting, causing validation logic to evaluate previously submitted values instead of current input. This was caused by incomplete change detection for decimal-only edits in percentage field controls, and has been corrected. | User Experience |
| INC-D14161 | 983569 | Avatar status correctly localized | The avatar was showing "User status active" in English even when the application was configured for other languages. This has been corrected. | User Experience |
| INC-D14163 | 989311 | Screen reader accessibility updated for key-value pairs | Read-only key-value pair lists were using role="none" attributes that prevented screen readers from properly announcing content as definition lists. This was caused by overly restrictive semantic markup that removed necessary structural information, and has been resolved by adjusting the role attributes to maintain proper semantic meaning while preserving the intended visual presentation. | User Experience |
| INC-D14164 | 984320 | Empty list elements in navigation removed for improved accessibility | Empty <ul> elements in the Announcements area and left navigation bar were being generated by conditional rendering logic that created list containers regardless of whether content was available. This has been resolved with an update to prevent rendering of AppAnnouncement details and AppShell navigation components when their item arrays are empty. | User Experience |
| INC-D14169 | 988055 | File attachment field error messages corrected | Screen readers were announcing "invalid entry" when focusing on "Select attachment" input fields, with the error persisting even after successful file addition. This has been resolved by correcting the file status messaging handling for file attachment input fields. | User Experience |
| INC-D14191 | 987768 | Screen reader error messages improved for radio buttons | Screen readers were announcing compound error messages with technical terms like "undefined" when navigating radio button groups without selection. This was traced to non-localized state information being included in error announcements, and has been resolved by providing user-friendly error messages and removing technical state information from screen reader announcements. | User Experience |
| INC-D14195 | 984002 | High contrast mode focus indicators enhanced | Keyboard navigation was not providing visible focus indicators when using Windows 11 high-contrast mode. This has been resolved by implementing comprehensive visible focus indicators for all interactive elements when operating in Windows high-contrast mode. | User Experience |
| INC-D14196 | 991914 | Localization property filtering improved | Applications with identical properties across different ruleset versions were experiencing localization inconsistencies where the pzAllPropertiesForLocalizationByApp report definition returned duplicate properties from multiple ruleset versions instead of filtering to the latest version. Investigation showed the report definition lacked proper ruleset version filtering logic, causing older property versions to be selected during language pack generation. This has been resolved by updating the pzAllPropertiesForLocalizationByApp report definition to filter properties based on the latest ruleset version, ensuring consistent localization behavior. | User Experience |
| INC-D14211 | 986783 | Character limit feedback enhanced for message fields | Message fields were not providing adequate feedback when character limits were reached, only announcing character count without indicating limit exceeded. This has been resolved by adding appropriate user feedback when message character limits are exceeded. | User Experience |
| INC-D14225 | 990577 | Worklist button labeling improved for accessibility | Worklist Go buttons were displaying non-unique labels when multiple assignments of the same type appeared. This has been resolved by modifying the button labels to include case IDs in the format "Go - [Current assignment] [Case ID]", ensuring each button has a unique, descriptive label. | User Experience |
| INC-D14344 | 985168 | Document generation library updated to resolve Constellation localization | Localization was failing in Constellation applications. This was traced to the document generation library, which had an issue with generating documents when processing more than 64K records resulting in failed generation, incorrect output, or inability to process very large datasets. This has been resolved by updating the document-generation library to a recent version where the issue has been corrected. | User Experience |
| INC-D15487 | 986677 | DateTime seconds display supported in partial views | Seconds were not displaying in partial views for datetime properties formatted as DD/MM/YYYY HH:MM:SS, even when the "Display Seconds" option was enabled in Constellation applications. To support this use, a new "long numeric" format has been introduced in the datetime field authoring panel which allows seconds formatting in the field configuration options for partial views. | User Experience |
| INC-D15498 | 990509 | Portal metadata parsing stabilized | Custom landing pages placed at the top of portal channel lists were generating "Unable to parse view metadata" console errors during portal launch, though functionality remained intact. Investigation showed this was caused by metadata processing order issues when custom pages were prioritized in the channel configuration. This has been resolved by updating pzsetupviewpagetorender to check for the existence of a landing page using for Rule-UI-View-LandingPage. | User Experience |
| INC-D15899 | 990962 | Stage dropdown population restored | The pyChangeStage flow action was failing to populate stage name dropdown values when the Comments field was configured as Required (Always). Investigation showed this was caused by context metadata changes that disrupted the stage options retrieval process. This has been resolved by updating context metadata to add properties from the association. | User Experience |
| INC-D15930 INC-D18507 |
987325 989194 |
Constellation dropdown search functionality improved | Users were experiencing difficulty locating intended options from large dropdown lists when typing search text in multi-select combo box fields and single-select dropdown fields. This was due to the system applying 'Contains' search logic instead of the expected 'Begins with' logic, with the result that all values that contained the search string anywhere within them were presented rather than filtering to values that started with the search text. Additionally, in single-select dropdown fields with large option lists, the system was not displaying the full list of matched values when users entered search input, requiring users to scroll down to find all matched values. This has been resolved by implementing 'Begins with' search logic and ensuring complete display of filtered results. | User Experience |
| INC-D16093 | 990871 | Case summary panel refresh corrected | Interaction case summary panels were intermittently failing to refresh after status changes made through stage optional actions for creating child cases, requiring manual browser refresh to see updates. This was traced to the event propagation between parent and child case contexts in the Constellation engine, and has been addressed. | User Experience |
| INC-D16316 | 987012 | Account manager message visibility corrected | Account Manager screens were displaying blank message areas with visible borders while the same messages were visible to customers. Investigation showed this was caused by role-specific message markdown rendering issues affecting Account Manager visibility. This has been resolved by adjusting chat message bubble styling to keep markdown code blocks readable and visually consistent with the surrounding chat bubble theme. | User Experience |
| INC-D16597 | 994566 998111 |
Annotation functionality made backwards compatible | After update, attempting to add annotations to images attached to work cases resulted in the attached image not displaying and the Draw button not being clickable. This was related to updates made to the SignaturePad version, and has been resolved by adding compatibility support for older plugin API behavior/signatures so they work as expected with the new version. | User Experience |
| INC-D16657 | 991228 | Radio button deselection behavior corrected | Radio buttons configured as picklists were unexpectedly deselecting when clicked a second time, even when the clear selection option was not enabled. This was caused by incorrect click handling behavior that allowed radio buttons to toggle their selected state rather than maintaining the standard mutually exclusive behavior. This has been resolved by implementing the pyEnabledRadioOnclickDeselection feature toggle that restores proper radio button functionality where selections remain persistent until another option is chosen, with deselection only possible through an explicit "Clear selection" button when that configuration is enabled. | User Experience |
| INC-D16722 | 987803 | Attachment field display corrected for page lists | Attachment fields in page lists were incorrectly displaying in the UI when entering assignments, even though they were deleted from the clipboard. This was traced to UI synchronization with clipboard state for attachment fields, and has been resolved by correcting the attachment field display logic for page list properties to avoid overwriting propertiesToReplace when already set. | User Experience |
| INC-D1686 | 974046 | Screen reader accessibility improved | Screen reader accessibility for optimized table navigation was providing incorrect instructions, reading "Click to Filter" and "Click to Hide Field" instead of the required "Enter to Filter" and "Enter to Hide Field". This was caused by incorrect aria-label text in the pzTemplateGridMenuNavRule navigation rule, and has been corrected. | User Experience |
| INC-D17039 | 988992 | Instruction text display corrected in partial views | Form views included within partial views were not displaying instruction text for field groups. This was caused by incomplete context propagation when rendering nested view components, and has been corrected. | User Experience |
| INC-D1723 | 974056 | Horizontal scroll bar at 400% zoom eliminated | When increasing browser zoom to 400% on work object details pages, a horizontal scroll bar appeared that interfered with accessibility. This has been resolved by adjusting the CSS layout calculations to properly accommodate 400% zoom levels without generating horizontal scroll bars. | User Experience |
| INC-D17547 | 995167 | Table row reordering enabled with UI inspector active | Row reordering functionality was not working in Constellation UI when the UI inspector was enabled. This was caused by iframe compatibility issues in repeating structures, and has been resolved. | User Experience |
| INC-D17715 | 989400 | Asterisk positioning corrected for form controls | Radio button and checkbox controls with large captions were displaying required field asterisks in incorrect positions. This was caused by CSS positioning calculations that didn't account for multi-line caption text, and has been resolved by updating the component styling to properly position asterisks relative to caption content regardless of length. | User Experience |
| INC-D17848 | 994219 | Multiselect control duplicate values eliminated | Multiselect controls were displaying duplicate values in the options list when users removed items after initially selecting all options, particularly when the data source contained options with similar names like "Life" and "Childrens Life". This was caused by improper option list management when dynamically updating the available choices after user selections. This has been resolved by correcting the multiselect control logic to properly maintain unique option lists and prevent duplication when options are added or removed. | User Experience |
| INC-D18188 | 995984 | Improved error handling for Localization wizard | The Localization Wizard was incorrectly showing complete status on the first trigger and taking excessive time to reset the distributed map. This has been resolved by updating the exception handling. | User Experience |
| INC-D18549 | 997915 | Text input maxlength validation improved | Text input controls were allowing users to exceed the configured maxlength limit when typing quickly and pressing tab before composition events triggered. This was caused by maxlength validation only occurring on composition end or keyup events, missing edge cases with rapid input. This has been resolved by adding maxlength validation on blur events as a failsafe mechanism. | User Experience |
| INC-D1873 | 979076 | Screen reader accessibility for empty values improved | Screen readers were announcing "n dash n dash" instead of "no value" when navigating to text fields populated by declare expressions that returned empty or null values. This has been resolved by implementing proper "no value" text rendering for screen reader compatibility. | User Experience |
| INC-D18844 | 989839 | List view error message clearing behavior corrected | Error messages from failed delete actions in Constellation List Views were persisting after successful subsequent actions like add or edit operations. This was caused by error messages not being automatically cleared when new successful actions were performed, and has been resolved by displaying delete action error messages as part of modal dialogs to ensure proper message lifecycle management. | User Experience |
| INC-D18937 | 992516 | Date time control week localization corrected | Date time controls with "Display week numbers on the calendar" enabled were showing "Week" in English without proper localization support. This has been resolved by adding proper localization support for week number headers in the pzpega_ui_calendar.js buildDaysRow function calendar control and updating pzClientLocaleData with the necessary field values. | User Experience |
| INC-D19024 | 993095 | Filter column localization corrected | Filter dialog labels and column headers were not being properly localized. This has been resolved by implementing proper localization support for filter dialog labels and correcting aria-label generation to provide meaningful accessibility text for screen readers. | User Experience |
| INC-D19060 | 995991 | Attachment validation error messages restored | After update, custom attachment validation errors were not displaying to users in Constellation UI. This has been resolved with an update to ensure the rUpload failure state now fully clears progress flags for file errors in fileutility and clears cached progress entries for all files in the failed batch. | User Experience |
| INC-D19123 | 989815 | Rich Text Editor custom tag logic updated | Applications experienced blank screens after updating the rteCustomAllowedTags DSS value to include "a" and "svg" tags. Investigation showed the tag validation logic was failing when processing the updated allowed tags list. This has been resolved by correcting the tag parsing and validation mechanisms to properly handle custom tag configurations. | User Experience |
| INC-D19274 | 991340 | Dynamic text field labels in partial views corrected | Field labels using dynamic text with decisioning configuration in partial views were not updating correctly at runtime, displaying static text instead of the expected dynamic content based on decisioning rules. This has been resolved with an update to ensure Details components re-render as expected. | User Experience |
| INC-D1957 | 974505 | Busy indicator text localization added | Applications were displaying hardcoded, non-localized text in busy indicators that included a misspelled "inderminate, progress indicator" message. This has been resolved by correcting the spelling in English and by creating field value entries to enable proper localization of all busy indicator text elements. | User Experience |
| INC-D1973 | 984301 | Corrected handling for currency formatting with qualifiers | Currency fields were not displaying proper formatting in read-only mode when using specific currency qualifiers like XOF, XAF, JPY, or KRW. This has been resolved by updating the currency formatting algorithm to properly process and display currencies when qualifiers are specified. | User Experience |
| INC-D20526 | 993689 | Table navigation focus management restored | Table icons with menu actions that opened modal local actions were losing focus after modal submission, causing focus to jump to the first table element instead of returning to the original icon position. This was an issue where the keyboard focus behavior for navigation rules rendered in a table did not properly handle the complex navigation chain of icon → menu → modal → table refresh. To resolve this, the focus management logic has been modified to properly restore focus to the originating table icon after modal actions complete and table refreshes occur. | User Experience |
| INC-D20584 | 992849 | Summary set as default active tab in mobile view | Constellation case views in mobile browsers were defaulting to the first custom tab instead of the expected Summary tab, creating inconsistent user experience across different case types and custom configurations. This has been resolved by updating the mobile case tab initialization to default to the Summary tab when no explicit tab selection has been made by the user. | User Experience |
| INC-D20586 | 994060 | Table view font consistency improved | Table views were displaying inconsistent font sizes across columns within the same row. This has been resolved by standardizing font sizes across all column types in table views to ensure uniform display throughout. | User Experience |
| INC-D20646 INC-C47204 |
992572 960041 |
Axios library updated | The Axios library has been updated. | User Experience |
| INC-D20715 | 997880 | Navigation tree accessibility improved | Screen reader tools were announcing "Blank" when navigating through navigation tree items that contained person image icons. This was caused by missing aria-hidden attributes on decorative image elements, and has been resolved by adding aria-hidden="true" attributes to person image icons in the generateCellContent function. | User Experience |
| INC-D20896 | 997666 | Percentage control display calculation fixed | Percentage UI controls were incorrectly multiplying decimal values by 100 at the case level, showing 6.12 as 612% instead of 6.12%. Values displayed correctly at the data context level. This was caused by inconsistent percentage formatting logic between different UI contexts, and has been resolved by standardizing the percentage calculation across all display contexts in Constellation. | User Experience |
| INC-D20946 | 996352 | Case navigation fixed in blended portal appointments | Users were experiencing sporadic issues where clicking on a parent case from an appointment summary would reload the appointment case instead of opening the parent case. This was traced to an issue with case ID management in the Redux store when navigating between cases in the blended portal, and has been resolved by ensuring the caseID is populated for traditional UI (coexistence) cases during the SHOW_HISTORY flow, so the Redux store has the case identifier available across page refreshes and direct URL access. | User Experience |
| INC-D21163 | 993428 | Autocomplete clear button accessibility improved | Applications using autocomplete controls configured as combo boxes were experiencing accessibility issues where the clear button (X icon) was not properly accessible. This has been resolved by adding aria-label="Clear selection" and implementing proper keydown event listeners to enable keyboard navigation. | User Experience |
| INC-D2121 | 975857 | Restored autocomplete filtering in list views | After update, autocomplete filters in list views were not filtering results when the underlying data page was sourced by an activity rather than a report definition. Investigation showed this was caused by a gap in the handling of promoted filters for data sources that are searchable but not queryable. To resolve this, client-side filtering and pagination have been added for that case in PromotedFilters.jsx, while preserving server-side paging for queryable sources. | User Experience |
| INC-D21238 | 994322 | Textarea focus behavior improved during scrolling | Applications were experiencing focus loss in textarea components when scrolling through large amounts of text, even though the cursor remained visibly positioned within the textarea boundaries. This has been resolved by implementing proper focus retention logic that maintains textarea focus state during scroll operations, ensuring uninterrupted user interaction with text content regardless of scroll position. | User Experience |
| INC-D21353 | 997047 | Radio button aria-label attribute corrected | Radio button controls were displaying "pyCaption" as the aria-label value when no label was configured. This was caused by incorrect parameter passing in the getLocalizedValue function within pzpega_ui_template_radiogroup.js, where the mode was being sent instead of the field value, and has been corrected. | User Experience |
| INC-D21391 | 996766 | Multi-step form restart stage rendering corrected | Multi-step forms routed to work queues were displaying error banners and failing to show the first step when pyRestartStage was executed from non-first steps, particularly when routing was directed to specific users. This was caused by improper API calls triggering "low-action is not a valid action to use" errors during stage restart operations. This has been resolved by fixing the flow action validation and refresh mechanism to additionally validate that the stored actionID still exists on the matching assignment’s actions list before allowing PERFORM-mode updates. | User Experience |
| INC-D21488 | 996315 | Assignment instruction text display corrected | The Assignment instruction text was being truncated mid-sentence and followed by unwanted bullet points, such as "Select the track(s) to reserve for this trai•" instead of displaying the complete instruction text. This has been resolved by updating the CSS used by webwb to modify how the item-separator helper class injects the dot separator. | User Experience |
| INC-D21746 | 997956 | Multiple Google address API calls resolved | Applications were experiencing excessive Google Address API calls when using the LocationInput control in Constellation. Investigation showed this was caused by the LocationInput control triggering a separate Google API call for each character entered rather than implementing proper debouncing or throttling mechanisms. This has been resolved by implementing optimized API call patterns to reduce and better manage Google Maps Places API usage by introducing debounced autocomplete calls and reusing AutocompleteSessionTokens across a “typing session”, while also threading the active token into place-details lookups (including map clicks). | User Experience |
| INC-D22022 | 994127 | Promoted filter time range issue resolved | When specifying a time range of 7:00-7:30 in the Promoted Filter in Insights, the start time (7:00) was being excluded from the results, while the same filter worked correctly when applied directly on the column. Investigation showed this was caused by seconds being added from the current time when clicking the option in the select dropdown, which interfered with the time range filtering logic. This has been resolved by correcting the time handling mechanism in the Promoted Filter functionality to ensure consistent behavior with column-level filtering. | User Experience |
| INC-D22584 | 997638 | Firefox date picker keyboard navigation enabled | Date picker calendars were not displaying when accessed via keyboard navigation in Mozilla Firefox, while working correctly in Google Chrome. This was caused by Firefox-specific event handling differences that interfered with the keyboard navigation implementation, and has been resolved by adding Firefox-specific condition logic to prevent secondary key down events that were interfering with calendar display. | User Experience |
| INC-D23211 | 998869 | Arabic text overflow in multistep components resolved | Right-to-left (RTL) languages like Arabic were experiencing step label overflow issues in Constellation MultiStep components, causing display problems in the user interface. Investigation showed that the component library was not properly handling RTL text layout requirements. This has been resolved by implementing proper handling to correct the MultiStepForm horizontal progress step popover alignment when the app is in RTL mode, ensuring the first/last step popovers anchor to the correct edge. | User Experience |
| INC-D23369 | 997172 | Corrected non-template Calendar picker issue | After update, calendar picker controls were intermittently failing to open. This was traced to WEEKDAYS_LONG missing from the data-calendar locale array built in pzdatetimelocalescript, and has been resolved by updating the non-template calendar locale bootstrap so that the client-side calendar utilities receive a localized long weekday name list (WEEKDAYS_LONG) from the data-calendar payload, aligning non-template behavior with the DateTimeUtil-backed path. | User Experience |
| INC-D23481 | 996434 | Promoted filter infinite scroll duplication eliminated | Promoted filters using non-queryable, non-searchable DataPages were causing infinite refetch loops during scroll-based pagination, resulting in duplicate results. This was caused by the condition-builder continuously requesting more records even though the server returned the full dataset on every call. This has been resolved by implementing proper DataPage limitation handling to prevent multiple requests for the same data. | User Experience |
| INC-D23500 | 1000514 | Constellation form refresh performance improved | Applications were experiencing significant delays when dropdown controls and form refresh events were triggered in Constellation interfaces, particularly noticeable with large payloads where dropdown fields were briefly displaying cached values from previous sessions before updating to correct server values several seconds later. Investigation showed this was caused by a race condition between multiple refreshFor calls targeting the same component, creating performance bottlenecks during form refresh operations. This has been resolved by implementing logic to cancel redundant refreshFor calls when multiple pending calls target the same component. | User Experience |
| INC-D2373 | 974095 | Popup harness JavaScript error resolved | After update, custom close buttons on popup harnesses were failing with the error "window.opener.pega.u.d.getThreadName is not a function". This has been resolved by adding proper null validation before attempting to access parent window thread information. | User Experience |
| INC-D23860 | 997620 | AnyPicker apostrophe handling corrected | AnyPicker controls were truncating values at apostrophes and failing to load results properly when categorization was enabled, affecting department names like "Clie'nt support" which would display as "Clie". Investigation showed that the categorization feature was not properly escaping special characters in field values. This has been resolved by adding a function escapeMarkupValue in the anypicker.js to implement proper character escaping in the categorized search results functionality. | User Experience |
| INC-D24934 | 997517 | Language bundle reupload functionality corrected | Language pack reuploads were not updating existing bundles when branching was enabled, causing translation changes to be ignored. This was caused by the language bundle rule creation process not properly handling updates during the reupload workflow with branch configurations, and has been resolved by updating the Constellation UI localization bundle saving so that the save path avoids overwriting the rule’s ruleset/ruleset-version metadata when operating on a localization rule that already belongs to a branch ruleset. | User Experience |
| INC-D25044 | 1005541 | Digital messaging conversation closure synchronized with wrap-up actions | Customer service representative chat conversations were remaining active and allowing continued interaction even after wrap-up completion, despite having the "Update CSR capacity upon wrap-up" setting enabled. Investigation showed this was caused by a mismatch between wrap-up actions and conversation closure behavior in Digital Messaging. This has been resolved by preventing PubSub subscriber mutations during callback unsubscribe, ensuring conversations properly close when wrap-up is completed. | User Experience |
| INC-D2579 | 975872 | Advanced search error message clearing implemented | Error messages in Advanced Search components were persisting even after clicking the Search button, particularly for required field validations that should have been cleared when conditions changed. This was caused by required message clearing not functioning properly when requiredWhen expressions became false in modal contexts, and has been resolved by extending the error clearing mechanism to work properly in both work area and modal contexts by passing subType through the corejs messages API so reducers can differentiate message sub-types. | User Experience |
| INC-D2712 | 975565 | Search and select refresh functionality restored | The refresh functionality in search and select components was not properly retaining search parameters when using non-queryable data pages, causing filtered results to be lost and showing empty or unfiltered data instead. Investigation showed this was caused by search filter parameters not being preserved during the refresh operation, and has been resolved by ensuring search parameters are maintained when refreshing non-queryable data page results. | User Experience |
| INC-D2719 | 972846 | Accessibility improved for case icon | A role attribute/tag has been added to the case icon on the case details page to improve accessibility. | User Experience |
| INC-D2725 | 977382 | Date field validation made consistent | Date field validation messages were not being consistently retained when dates were entered manually through keyboard input, though validation worked correctly when using the calendar control. Investigation showed this was caused by the DateTime PartInput component incorrectly triggering onChange events during blur operations without actual value changes. This has been resolved by ensuring the onChange callback passed to PartInput is triggered when the value has changed. | User Experience |
| INC-D27868 | 1005507 | Promoted filters display behavior improved for dashboard insights | Dashboard chart insights were displaying promoted filters in collapsed mode at 100% screen zoom even when sufficient screen space was available to show them in full expanded view. The same filters displayed properly at 75% zoom. This was caused by incorrect rendering logic that failed to properly calculate available space for promoted filter display, particularly affecting single primitive-type filters, and has been resolved by updating the promoted filters rendering mechanism to prevent unnecessary collapsing into modal dialogs when adequate screen space exists. | User Experience |
| INC-D28666 | 1002922 | Discard unsaved changes functionality restored in pop-up screens | When working in pop-up screens and making changes, clicking cancel was presenting a "Discard unsaved changes?" dialog, but clicking "Discard" did not have any effect. This was seen in various scenarios including KMR (Knowledge Management Repository) case creation screens and other embedded data modals where users were unable to properly exit after making unsaved changes. This was caused by the discard changes functionality not working correctly on dirty dialogs for open embedded data modals, and has been resolved. | User Experience |
| INC-D2925 INC-D18906 |
976036 990736 |
Focus restored for embedded data table add operations | When adding records to embedded data field tables using the "Add" button configured as an action rather than a view, focus was incorrectly moving to the top of the screen instead of remaining on the modal. This was traced to incorrect focus handling in the "Action-based configuration for for adding rows to embedded data fields, and has been resolved by ensuring that the correct view is selected through the classID added to state, maintaining proper focus on the modal when adding table rows. | User Experience |
| INC-D2939 | 973238 | SDK link behavior standardized | External links in case instructions were behaving inconsistently between Pega portals and Angular SDK implementations, with links opening in new tabs in portals but replacing the current tab content in SDK applications. This was caused by the DOMPurifier logic in the SDK components not automatically adding target="_blank" attributes to external links, and has been resolved by implementing consistent link handling logic across all UI frameworks to ensure external links always open in new tabs. | User Experience |
| INC-D3156 | 983527 | Dev Studio context preserved on switch | After returning from the portal to Dev Studio, the Actions button in rules would only display "Get Help" instead of the full menu options, requiring logout and login to restore functionality. This was an inadvertent side effect of work done on context switching between different application interfaces, and has been resolved by ensuring proper context thread preservation when transitioning between Dev Studio and portal environments. | User Experience |
| INC-D3194 | 975715 | Corrected slider input synchronization with form refresh | Slider controls with numeric input enabled were displaying 0 instead of the actual slider value in the input box when auto-populated. This has been resolved by ensuring proper value synchronization between slider and input components during form refresh to ensure NumberInput does not display stale values. | User Experience |
| INC-D3261 | 977054 | Auto-save validation behavior corrected for tree navigation | Applications using TreeNavigation7 with auto-save functionality were triggering unexpected client-side validation popups when non-required fields were modified, even when required fields remained properly filled. This was traced to auto-save incorrectly running validation checks on the entire form rather than just modified sections, and has been resolved by adjusting autosave to save without running client validations when using TreeNavigation7. | User Experience |
| INC-D3276 | 974738 | Layout group tab focus borders corrected | Tab layout groups were displaying incomplete focus borders when "Semantic tab Layout" and "Allow scroll for tab headers" options were enabled together. This was caused by CSS conflicts that removed the top border during focus state rendering, and has been resolved by updating the focus styling rules to maintain complete border visibility across all tab layout configuration combinations. | User Experience |
| INC-D3328 | 981814 | Invalid flow action banner resolved during case creation | Invalid flow action banners were intermittently appearing during Demand Request case creation, particularly in staging environments, with messages stating "CollectMarketInformation is not a valid action to use". This was traced to a race condition between refresh and FinishAssignment actions, and has been resolved. | User Experience |
| INC-D3352 | 979079 | Screen reader accessibility improved for required fields | Screen readers were not announcing required field status for several UI controls including TextArea, Rich Text Editor, Radio buttons, AnyPicker, AutoComplete, and Dropdown when client-side validation was disabled. This was due to the aria-label attributes not being properly set for required field indication in these controls for this scenario, and has been resolved by updating the backend rendering logic to ensure all required field controls include proper aria-label attributes for screen reader accessibility. | User Experience |
| INC-D3470 | 973606 | Keyboard navigation flow restored for optimized tables | Keyboard navigation was becoming trapped in the first column of optimized tables with group by results. This an issue with the focus management in grouped table rows where the first column appeared empty beneath the group caret, and has been resolved by updating the keyboard navigation logic for a grouped table. | User Experience |
| INC-D3535 | 978679 | Corrected Multiselect dropdown save error | Multiselect combobox controls were throwing "Invalid Request Data" errors when attempting to save selections in Constellation. This was caused by data page parameter metadata not being processed correctly for page list properties, especially when the page list was empty or nested under a composite path. To address this, parameter resolution has been made path-aware and class-aware, so Constellation can still derive parameter property paths and metadata even when there are no page list rows yet. | User Experience |
| INC-D3541 | 975775 | Custom field label display corrected | After update, special characters were not correctly encoded and HTML tags were displayed in custom field labels. This has been corrected with an update to resolve the paragraph content as textContent if it is of 'simple' category. | User Experience |
| INC-D4493 | 978725 | Constellation case work area display improved | Cases with 50 or more assignments were displaying excessive blank space under the case work area when all assignments were expanded in Constellation. This has been resolved by optimizing the layout calculations to properly size the work area container regardless of assignment count. | User Experience |
| INC-D4505 | 974522 | Text area character counter persistence fixed | After enabling max length on a paragraph and using the same field in multi-step-form (screenflow) process, the counter remained as 0 on the next screen even though it included values typed in the prior screen. This was caused by the text area control always initializing the counter value to 0 when rendered, regardless of existing content, and has been resolved by initializing the character counter with the actual length of existing value or default value when present. | User Experience |
| INC-D455 | 971776 | View authoring configuration options restored | Search and Select date reference configurations were missing default value options in field settings, and case type Details tab content was losing view type specifications after specialization operations. Investigation showed that view authoring processes were not properly preserving configuration settings when a view was hoisted to a different class in the hierarchy due to the view type being removed when updating a view that has a class that did not match the current class. This has been resolved by updating the logic in ViewEditing.java to not remove the pxViewType when hoisting view. | User Experience |
| INC-D4570 | 976616 | Hover menu collapses as expected | Link controls configured with Hover Menu action sets were remaining expanded when focus moved elsewhere, causing multiple menus to stay open simultaneously and creating user interface confusion. This has been corrected by adding display:none inline style to implement proper menu collapse behavior when cursor focus moves away from hover menu controls. | User Experience |
| INC-D4579 | 979290 | Required field indication added for multiselect and RTE controls | Multiselect combobox controls and Rich Text Editor (RTE) fields were not indicating required field status to screen readers. This has been resolved by updating multiselect combobox controls to include required attributes and RTE controls to include required status in their aria-label values. | User Experience |
| INC-D492 | 976250 | Table cell text formatting preserved | Text and paragraph fields within table cells were not respecting user-defined formatting configurations, causing text to wrap incorrectly and ignore line breaks regardless of the intended display behavior. Investigation showed this was caused by table cell rendering overriding user-specified text formatting settings. This has been resolved by ensuring user-defined formatting configurations are properly applied to text fields within table cells. | User Experience |
| INC-D5058 | 981284 | View loading reliability improved after case submission | Applications were failing to load views after case submission due to messaging service subscriptions being unsubscribed prematurely without proper validation checks. This was caused by incorrect execution order where subscriptions were being unsubscribed before dependent operations completed, and has been resolved by improving AtomicSubscription message handling to safely handle cases where a subscriber is removed while iterating subscribers. | User Experience |
| INC-D5414 | 983330 | Remote case actions menu restored | The Actions button was not visible for remote cases launched from Process Fabric applications, preventing access to case-wide actions. This was traced to a missing Remote System ID parameter when calling actionsApi.openLocalAction and actionsApi.openProcessAction, and has been corrected. | User Experience |
| INC-D5674 | 981753 | Picklist behavior corrected during horizontal table scrolling | Search box picklists within horizontally scrollable tables were remaining open and moving with scroll position instead of closing, causing the open picklist to overlap and block UI elements during navigation. Investigation showed the ComboBox popover was not explicitly configured to hide when its anchor/target became hidden, even though the ComboBox’s open state could still indicate it should be shown. This allowed the popover to outlive the visible ComboBox target and remain rendered or visually inconsistent. To resolve this, the handling has been updated to ensure the popover now hides automatically when the ComboBox target is no longer visible. | User Experience |
| INC-D5931 | 978291 | Autocomplete pagination resolved for REST connector data sources | Applications using autocomplete controls with REST connector data sources were experiencing infinite loading when scrolling through results. This was traced to the autocomplete component not properly handling REST API responses that did not include pagination metadata (pageSize) in their response structure. This has been resolved by modifying the component logic so that for external data pages, if pageSize is not returned in the response, additional results are not loaded on scroll, preventing the infinite loading behavior and allowing proper display of all available autocomplete results. | User Experience |
| INC-D5954 | 977378 | Address control editing in modals corrected | Address controls in modal dialogs were allowing initial data entry but preventing subsequent editing of postal code values, and any changes were reverted after refresh. Investigation showed this was caused by conflicting Update and Replace instructions during address field modifications, where Replace instructions containing old values were overriding Update instructions with new values. This has been resolved by correcting the instruction merging logic for Address fields in embedded data scenarios to bypass the “merge with previous UPDATE instruction” behavior when replaying/merging page instructions. | User Experience |
| INC-D6093 | 979341 | Constellation partial view alignment corrected | Applications were experiencing inconsistent alignment between labels and values in Constellation partial views when displaying pxTextArea properties. This was traced to inconsistent rendering logic for different content types, and has been corrected. | User Experience |
| INC-D6154 | 978289 | Application name special character encoding corrected | Application names containing special characters like brackets (e.g., "App (Name)") were displaying with encoded special characters in the Switch Application menu within the End User portal. This was caused by improper HTML encoding of the pyApplications.pyLabel property, and has been corrected. | User Experience |
| INC-D6236 | 977445 | Corrected unexpected menu collapse | The Constellation portal expanded navigation menu was collapsing unexpectedly when closing cases. This has been resolved by updating the event propagation control for on-click case close actions in the navigation menu. | User Experience |
| INC-D6306 | 979879 | Global search functionality restored in Constellation applications | Applications were experiencing an issue where the global search box was disappearing after creating new cases while on the advanced search results page. This was caused by a rendering issue which affected the search component visibility during case creation workflows, and has been resolved. | User Experience |
| INC-D6514 | 979178 | Browser timezone handling fixed for empty operator settings | Date and time values were displaying in GMT instead of browser timezone when operator timezone settings were removed, and pulse feed functionality was generating errors. Investigation showed the environment timezone detection was not properly falling back to browser timezone when operator locale was empty, and this has been corrected by updating PCore.getEnvironmentInfo().getTimezone() to return undefined when user locale is empty, enabling proper browser timezone fallback. | User Experience |
| INC-D6634 | 978676 | Corrected validation trigger logic | Validations were not triggering properly after update. This was traced to an issue with the boolean-comparison in the corejs expression evaluator, which could mis-handle boolean fields when runtime field metadata was missing, causing expressions like .pyFlag == 'true' or comparisons against false to evaluate incorrectly. To address this, a RulesStore-based metadata fallback has been added to infer field type when _context.getFieldMetadata(...) is unavailable. | User Experience |
| INC-D6674 | 978716 | Coexistence case rendering behavior standardized | Traditional parent cases were incorrectly rendering as Constellation cases when accessed from child Constellation cases in coexistence environments while parent cases loaded correctly as traditional cases when accessed directly from the portal. Investigation showed the logic was not properly maintaining the parent case rendering context during navigation in the coexistence environment. This has been resolved by updating parent-case breadcrumb navigation in CaseView to correctly handle this scenario. | User Experience |
| INC-D6724 INC-D17290 |
980464 990080 |
Radio button placeholder selection issue resolved | Radio button controls with "Not Applicable" placeholder options were automatically selecting when there was a click anywhere on the control area, including white space or labels, even when existing values were already present. This was an issue with improper ID assignment logic in the template_radiogroup.js rule template that failed to distinguish between placeholder and regular value selections, and has has been resolved by implementing conditional ID assignment logic that properly differentiates placeholders. | User Experience |
| INC-D709 | 973363 | Case summary panel refresh implemented for local actions | The case summary panel was not updating when local actions created renewal cases, continuing to display resolved case details instead of the new case information even though assignments appeared correctly in the work area. This was caused by missing refresh logic for the summary panel during local action execution, and has been resolved by adding a check to dispatch mergeData when parent and child containers hold different contexts. | User Experience |
| INC-D7170 | 983535 | Skin rule handling updated to prevent out-of-memory errors | Skin rule operations were causing system unresponsiveness and Java heap out-of-memory errors during check-in, check-out, and save operations. This was caused by excessive memory consumption in the skin processing pipeline when certain formats within a Skin rule contained corrupted color styles without valid HEX values, typically originating from overridden or “Save As” formats. To resolve this, a server-side sanitizer has been added to repair corrupted RGBA values in skin data and the ColorPicker has been hardened so it only emits safe, valid CSS color formats. | User Experience |
| INC-D7325 | 977576 | Question page answer field borders restored | Answer input boxes in question pages were losing their visual borders when receiving focus, affecting the user interface appearance for editable text fields configured from page lists. Investigation showed that when an input or textarea received keyboard/mouse focus, its border color was being set to transparent, which could make the focused field lose its visible border. This has been corrected by updating the rule to border-color: inherit, so the field keeps its intended border color while focused. | User Experience |
| INC-D7397 | 984939 | Work portal favicon configuration fixed | Custom favicon configured in pyPortalIcon was being applied to the work portal while correctly appearing in the dev portal. Investigation showed this was caused by URL hash replacement with semantic URLs in src/initialiser/index.js, which broke relative URL resolution for icon fetching. This has been resolved with an update to prevent favicon and Apple touch icon URLs defined as relative paths from breaking after history.pushState updates the page URL. | User Experience |
| INC-D7408 | 979195 | Administrator landing page localization enabled | The pxAdministrator landing page and configuration sets were not translating properly when language packs were installed and operator locale was changed, with many values remaining in English despite other locale selection. This has been resolved by implementing the necessary translation framework to support universal localization across all Constellation administrator components. | User Experience |
| INC-D7507 | 980762 | Remote case types mapping error handling updated | Applications were showing step failures in tracer logs when attempting to open RemoteCaseTypesMapping. This has been resolved by adding a check to prevent an Obj-Open against RemoteCaseTypesMapping when the target rule instance does not exist. | User Experience |
| INC-D7657 | 983775 | Text area auto-resize behavior corrected | Text area controls were displaying unwanted scroll bars when populated with data from other controls while in hidden tab states. This was caused by the auto-resize logic attempting to determine dynamic height while the element was not visible, and has been resolved by updating the height calculation logic. | User Experience |
| INC-D7718 | 978711 | TODO operator name display adjusted | Operator names were not completely visible and urgency values were being cut off at certain zoom levels in the redesigned TODO component, requiring a hover over truncated names to see full assignment details despite available white space on the screen. Investigation showed the component layout was not properly utilizing available screen space for text display due to a hard width cap (max-width: 16ch) plus layout/padding choices. This has been addressed by widening the space available for assignee names in the HierarchicalAssignments UI so names truncate later, and adjusting padding, max-width, and flex behavior in the layout. | User Experience |
| INC-D7724 | 983000 | Identifier type handling made consistent in Nebula renderer | Simple tables in read-only mode were throwing errors when adding identifier type fields from runtime. Investigation showed this was caused by type identifier misalignment between the Nebula renderer getNebulaTypes method and the authoring UI type_mapping definitions. This has been resolved by correcting the type mapping logic to ensure Identifier fields render as TextInput and Double fields render as Decimal, which aligns runtime behavior with the expected UI component types. | User Experience |
| INC-D7756 | 985230 | Case-wide actions restored for split for each assignments | Case-wide actions were not appearing when Split For Each assignments were launched directly from the flow, though they displayed correctly when opened from the worklist. This has been resolved by ensuring case-wide actions aren’t inadvertently cleared when opening a “Split For Each” assignment (i.e., when parent/child contexts reference the same item). | User Experience |
| INC-D7907 | 977753 | Improved Date field year spinbox accessibility | The Date field spinboxes year field was starting at value "1" when using arrow keys, regardless of any configured date range restrictions. Investigation showed the year range restrictions were only being applied within the calendar dialog and not to the spinbox min attribute. This has been resolved by updating the year spinbox to reflect configured range restrictions in its minimum and maximum value attributes. | User Experience |
| INC-D7965 | 978109 | Constellation validation banner displayed as expected | Edit Validate rules configured on properties were only showing field-level errors without displaying the validation banner at the top of the screen in Constellation applications. This behavior differed from expected validation display patterns where both field-level and banner notifications should appear. Investigation showed the Assignment component only treated hasErrors or hasFormSubmissionErrors as failure conditions, so when a form refresh failed and surfaced errors only through bannerMessages, the error banner was not rendered or focused. This has been corrected. | User Experience |
| INC-D807 | 974595 | Focus functionality restored for Checkbox help text | Checkbox controls with "Help icon with overlay on focus" were not displaying help text when field values contained line breaks or spaces. This has been resolved by adding proper newline-to-HTML conversion in the pzpega_ui_template_checkbox.js rendering logic for tooltip display when using the focus-based help text feature. | User Experience |
| INC-D8318 | 978796 | Multi-step progress bar visibility enhanced for accessibility | Multi-step form progress bars were appearing as disconnected floating circles when Windows high contrast mode was enabled. This has been resolved by implementing proper high contrast CSS styling to ensure progress bar connectivity remains visible in all accessibility modes. | User Experience |
| INC-D8581 | 979293 | Data reference combobox 'required' attribute implemented | Data reference combobox controls were not indicating required field status. This has been resolved by adding proper required attribute support to data reference combobox controls. | User Experience |
| INC-D8597 | 981918 | Table column overlay positioning corrected | The show/hide column overlay in tables with many columns was appearing detached from its trigger button when positioned near page edges. This was caused by the overlay's top position calculation not accounting for scrollbar presence and overlay height, and has been resolved by updating the popover.js calculation. | User Experience |
| INC-D88 | 970521 | Promoted filters autocomplete search functionality updated | Autocomplete search in list view promoted filters was exhibiting inconsistent behavior, working correctly for 2 characters while ignoring case, but requiring exact case matching after 4 characters. This was caused by inconsistent application of "ignoreCase" in the filters, and has been resolved by standardizing the case-insensitive search behavior across all character length scenarios. | User Experience |
| INC-D8815 | 984258 | Web embed widget loading performance improved | Chat widgets embedded using the web embed feature were experiencing significantly slower load times after update. Investigation showed the pxGetEnvironmentInfo data transform was redundantly including pyHasCreateAccess alongside pyClassAccessList. This has been resolved by removing the duplicate pyHasCreateAccess property to restore previous loading performance. | User Experience |
| INC-D888 | 977021 | Preview action functionality works for hybrid UI environments | Preview actions were failing in Constellation landing pages embedded within UI-Kit portals, showing "Cannot read properties of undefined (reading 'showSlideInPanel')" errors. This was caused by missing panel functionality in hybrid UI setups, and has been corrected. | User Experience |
| INC-D8926 | 979770 | Date filtering updated for optimized tables | When applying a Date/Time filter on an optimized table and selecting “Tomorrow” with the checkbox “Also include today” enabled, the filter returns only records for today. This was an issue with an off-by-one-day boundary in symbolic date resolution, and has been resolved so that filtering with Tomorrow + Include Today correctly includes both today and tomorrow (especially for date-time end-of-period calculations). | User Experience |
| INC-D8930 | 981750 | Checkmark icon removed from hover | Autocomplete fields were displaying a checkmark icon on hover that was failing accessibility contrast requirements and was marked with role="presentation" making it invisible to screen readers. This decorative checkmark provided no meaningful information to users and has been removed. | User Experience |
| INC-D8966 INC-D8967 |
978813 978811 |
High contrast accessibility improvements | Dropdown and calendar control carets were invisible in Windows high contrast mode. This has been resolved by adding contrast-aware styling. | User Experience |
| INC-D8989 | 986224 | Corrected clearance of authorization error message | Authorization error messages were persisting in the PEGA Legal Group Advisory User Portal interface even after successfully accessing valid cases. This has been resolved by updating the context handling to ensure authorization messages are properly cleared from the interface once valid access is confirmed. | User Experience |
| INC-D9136 | 982506 | Bulk attachment download functionality enabled | The bulk download option for multiple attachment records in read-only mode was not functioning when users clicked the "download all" option in Constellation applications. This was a missed use case and has been resolved by implementing bulk download handling for read-only attachment categories. | User Experience |
| INC-D9181 | 980751 | Localization corrected for embedded fields | Single page properties with page definitions were displaying non-localized labels in runtime environments. This was traced to the system using the deprecated "@L Country" notation instead of the proper "@FL .Address.pyCountry" format for embedded single page fields, and has been resolved by updating the metadata generation to use the correct field localization notation format. | User Experience |
| INC-D9233 | 987522 | Corrected assignment due date display accuracy | Constellation assignments were incorrectly displaying due dates for assignments that had no due date configured, with the same due date appearing for multiple assignments until page refresh. The issue occurred when opening the second assignment in assignment lists, causing due date information to persist incorrectly across assignments. This was caused by a change in the dx API's response assignments array, and has been resolved by updating the date state management in the Constellation assignment display logic. | User Experience |
| INC-D9660 | 981794 | Session timer modal positioning corrected | Session timer warning windows were appearing in the top left corner when other popups were present on screen, with the close icon either missing or causing the browser window to close instead of the modal when clicked. This was caused by improper modal template selection when existing popups were detected, and has been resolved by ensuring the session timer uses the correct modal template regardless of existing popup states. | User Experience |
| INC-D9789 | 983024 | Multi-step form refresh timing corrected | Multi-step forms were experiencing errors when users changed fields with visible-when conditions and clicked next. The issue occurred due to a race condition between the setTimeout refresh handler and onClickHandler, resulting in finish assignment executing before refresh calls could register for blocking actions, and has been resolved by properly synchronizing refresh and click handler execution order. | User Experience |
| INC-D9950 | 990367 | Updated security handling for Localization migration | SSL handshake failures were seen during localization migration when using self-hosted CDNs with custom certificates, resulting in messages such as "Error while generating localization bundle for locale nb-NO" and JsonSyntaxException messages. Investigation showed the migration activity used an OkHttp client that did not honor the Pega Platform trust store, and this has been resolved by replacing the OkHttp client with a Pega REST Connector that properly uses the platform trust store for secure retrieval of component localizations from CDN endpoints with custom SSL certificates. | User Experience |