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.)
As part of Pega's long-term security strategy, AI-assisted scanning has been implemented on a proactive basis. Pega strongly recommends that clients stay current with the latest product versions to receive current security enhancements, patches, and hardening improvements, and promptly install all critical hotfixes.
Low-code Application Development
Case Management
26.1.1 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B45609 INC-B51964 INC-B52132 INC-C14591 INC-C29756 INC-C37540 INC-B45676 INC-D29531 INC-D13970 INC-D12758 INC-D12334 INC-D13135 INC-D13696 INC-D17620 INC-D20987 |
1008790 | File attachment handling improved in repository operations | The error message "Couldn't upload file. The specified file/folder already exists in the target repository. Please specify a different file/folder" was generated when trying to attach files with names that had been previously used, even after removing the original attachments from forms or case records. This issue was particularly problematic in scenarios where process flows encountered exceptions during file creation, as the attachment would persist in the S3 repository while the database transaction rolled back, creating an inconsistent state between the repository and database records. Investigation showed this was caused by insufficient cleanup of repository artifacts when attachment operations failed or were reversed, leaving orphaned files that blocked subsequent uploads with identical filenames. This has been resolved by implementing proper synchronization between repository and database operations to ensure complete cleanup of attachment artifacts during rollback scenarios and improved handling of duplicate filename conflicts. | Case Management |
| INC-D15718 | 1001012 | Dynamic audit history text localized | Audit history was displaying raw field values instead of executing dynamic localized text expressions, causing flow action names and field labels to appear as literal text rather than their intended localized values. This was caused by the @getLocalizedText function not being properly added for local action labels in the audit trail processing, and has been resolved. | Case Management |
| INC-D16465 | 1005799 | Case resolution status synchronization corrected | Cases configured with optional cancel actions were experiencing inconsistent resolution behavior where the assignment was properly removed and work history was correctly updated, but the work status remained as "New" instead of "Resolved-Cancelled" with missing resolution details. Investigation showed this was caused by improper page handling in the findPageByHandle method. This has been resolved by fixing the page synchronization logic to ensure work status properly reflects the resolution state. | Case Management |
| INC-D18613 | 996646 | Security updated for Infinity Studio | Server side input validation in Infinity Studio has been updated for improved security. | Case Management |
| INC-D18672 | 996976 | Flow error display accuracy improved | Flow error displays were showing incorrect assignment labels when routing failures occurred, displaying the preceding step's label instead of the actual failed assignment label. This was caused by improper error context tracking in the flow error reporting mechanism, and has been resolved by correcting the error display logic along with updating the label from "Step" to "Problem occurred at" for better clarity. | Case Management |
| INC-D19571 | 995922 | Archived case navigation restored between parent and child cases | Cases were experiencing navigation failures when attempting to open archived parent cases from child cases through breadcrumb links. This was traced to the system attempting to locate cases using pzInsKey references while the cases resided in secondary storage. To resolve this, conditional logic has been added to a dynamic layout that checks if a parent case is archived and applies special handling using the pzOpenArchivedWorkObject activity. | Case Management |
| INC-D22247 | 1005219 | Email approval flow processing restored | Email approval flows were getting stuck at approval stages and not resuming after email processing. This was caused by a mismatch in action name comparison logic between UI-Kit applications using "pyApproveInternal" and Constellation applications using "pzApproveInternal" in the pyProcessEmailRequest activity. This has been resolved by correcting the action name matching logic to handle both UI-Kit and Constellation approval actions. | Case Management |
| INC-D23418 INC-D36526 |
1009418 1011808 |
Case archival optimized for complex hierarchies | Pipeline archival jobs were not completing the archival process when encountering extremely complex case hierarchies. Investigation showed that when a case type class had no sub-cases in its hierarchy, the archival pipeline built an invalid CTE and silently returned empty results, causing jobs to run to completion without archiving any data. This has been resolved with an update to resolve silent archival failures by introducing a configurable fallback strategy: DSS-configured case types skip traditional hierarchy construction and use native SQL recursive (START WITH / CONNECT BY) queries on single tables, while all other case types continue using the existing multi-table union-CTE approach. Additionally, when any case type has an empty sub-case list at runtime, a fallback recursive query is automatically triggered to prevent failed archival operations. | Case Management |
| INC-D23653 | 1003859 | Screenflow navigation state accuracy restored | Screenflow progress indicators were displaying incorrect states in embedded subprocess scenarios, showing navigation elements as both completed and current simultaneously with partially colored progress bars. This was a missed use case caused by the pyTabbedScreenFlow7Nav rule not correctly handling navigation state for nested screenflows containing subflow navigation, and has been resolved by updating the screenflow navigation logic to properly manage state transitions in embedded subprocess scenarios. | Case Management |
| INC-D24248 | 1006137 | Set value event action functionality corrected for hidden tabs | After update, dropdown controls were failing to update other properties when their values changed, especially when one tab was hidden and submit logic was triggered from the active tab. Investigation showed this was caused by field validation logic not correctly accounting for tab visibility/active context during submit-time checks on hidden tabs, affecting OnSubmit processing in active tabs. This has been resolved by correcting the field validation logic to properly handle event actions across tab configurations. | Case Management |
| INC-D28560 | 1013857 | Assignment label length validation updated for work actions populate activity | Work object action menus were generating string length errors when usernames exceeded 64 characters, causing the pyWorkActionsPopulate activity to fail during label extraction from workflow assignments. This was caused by the activity concatenating flow names and usernames into the pyLabel property without considering the 64-character database field limit, and has been resolved by implementing proper string truncation and length validation in the pyWorkActionsPopulate activity for pzGetAssignmentLabel to print the first 64 characters. | Case Management |
| INC-D29311 | 1006802 | File upload size validation precision corrected for drag-drop controls | File upload operations were exhibiting inconsistent size validation behavior across versions, with the drag-drop control accepting files that exceeded configured limits due to precision errors during megabyte-to-byte conversion calculations. This has been resolved by ensuring file size validation accurately enforces the configured pyMaxDragDropAttachSizeMB limits by updating the validateMaxSize function in AttachmentUtils.ts to check if the file size (in MB) is less than or equal to the maximum allowed size, and no longer round the file size before comparison. | Case Management |
| INC-D29605 | 1008609 | Restricted Pulse message security enhanced | To improve security for Pulse messages, an updated access verification mechanism has been introduced in the Constellation API endpoint to ensure authorization checks are properly enforced on the messageID path parameter before allowing users to view, like, or interact with messages. | Case Management |
| INC-D297 INC-D8250 |
1006705 1010083 |
Pega archiver pipeline execution stabilized | The pyPegaArchiverUsingPipeline job scheduler was running endlessly without performing any archival actions, requiring manual environment restarts to resolve the issue. Investigation showed this was caused by missing end time conditions in the copier logic that prevented the archival process from stopping when the job scheduler duration was completed. This has been resolved by adding proper fail-safe cleanup and predictable termination. | Case Management |
| INC-D29702 | 1008970 | Archival settings retained after update | During system update, archival configurations were being automatically changed from archive-only to purge mode with a default 1825-day retention period, causing cases that were previously set to archive indefinitely to be scheduled for permanent deletion. Investigation showed this was caused by the upgrade process defaulting archival settings to include data retention policies when only archival was previously enabled. This has been resolved by modifying the upgrade process to preserve existing archival configurations without automatically enabling purge functionality by updating the pzPolicySettings section to separate the Enable archival policy and Enable data retention policy options. The Enable data retention policy checkbox will be shown only when Enable archival policy is selected, for both "Based on time since resolution" and "Based on business logic and time since resolution" configurations. For new case types, Archival days will be defaulted as 10 years and Data retention days will be defaulted as 100 years for both "Based on time since resolution" and "Based on business logic and time since resolution" configurations. | Case Management |
| INC-D30480 | 1014026 | TrackSecurityChanges activity deprecated | Field-level auditing (FLA) has been replaced by the current Case Type Design Settings implementation. The TrackSecurityChanges activity rule has been marked as deprecated to clearly indicate it is no longer the supported method for field-level auditing. | Case Management |
| INC-D30924 | 1009439 | Feature toggle guard added for purge/index deletion behavior | Archival operations were failing with exceptions during indexing when the workenabled parameter was set to false, and the message "Failed to delete live indexes" was generated. Investigation showed the purge flow did not gate live-index deletion on the indexing/workenabled dynamic setting. As a result, purge logic still called deleteLiveIndexes in code paths where work indexing was intentionally off. This has been addressed with a check for whether work indexing is enabled before trying to delete live search indexes during archival purge. If the setting is false, purge code skips live-index deletion (deleteLiveIndexes) and returns without calling the archive indexer, preventing unnecessary failures. | Case Management |
| INC-D32395 | 1013035 | SLA queue processor lock timeout corrected | When workflows transitioned from Wait shapes to Assignment shapes and errors occurred during transitions, the pyProcessSLA Queue Processor would lock cases for SLA processing, but if transactions encountered errors and rolled back, locks would persist until the 30-minute lease timeout expired automatically. This was caused by improper lock release handling when transaction rollbacks occurred during SLA processing. This has been resolved by updating the lock cleanup procedures in the Case Locking feature to ensure locks acquired in restore assignment are released correctly on commit. | Case Management |
| INC-D33776 | 1009829 | Popup data refresh functionality restored | After update, the pyRefreshData data transform specific to the List class was not being invoked when submitting popups from modal windows invoked from grids. Investigation showed this was caused by the pzFormPageInstructionsForRowOperations activity missing page context when adding Param.InterestPage for applying the data transform, causing pyRefreshData to be resolved using the work page context during certain refresh operations instead of the embedded page context associated with the list item being refreshed. This has been resolved with an update to run the pyRefreshdata data transform based on interestPage parameter populated and to not run for v1 APIs. | Case Management |
| INC-D34094 INC-D18233 |
1010274 1008947 |
Archival SQL generation logic updated | Archival jobs were failing with ORA-01489 errors when processing cases with large text content during SQL generation. This was due to the archival SQL generation logic using nested Oracle CONCAT implementations that exceeded Oracle's 4,000-character VARCHAR2 limit when handling large note content. To address this, the archival SQL generation logic has been updated to replace the existing nested Oracle CONCAT implementation with a TO_CLOB() based approach to support larger content without data loss. | Case Management |
| INC-D34778 | 1012397 | Process Fabric archival policy purge functionality enabled for PPF work classes | Archival policies configured for direct purging of PPF-Work-Case and PPF-Work-Task classes were failing to remove resolved cases older than the specified retention period. Investigation showed that pyID can be blank in PPF cases, causing null map keys in getPyIDsMap(). To resolve this, null and blank checks for pyID have been added, with fallback handling for the map key if pyID is blank. | Case Management |
| INC-D35134 | 1011442 | Bulk processing assignment pagination display fixed | Pagination was not displaying in the pyBulkProcessingAssignDisplay section, preventing proper navigation through bulk assignment lists. The issue was caused by incorrect pagination placement/rendering logic in pyBulkProcessingAssignDisplay, which incorrectly added pygridpaginator to the table footer instead of the recommended header location. This has been resolved by moving the pagination component to the table header where it will execute properly and display at the top of the table. | Case Management |
| INC-D35204 | 1013422 | Optimistic locking local action context preserved | Users were being navigated away from local actions and losing their work when clicking "Refresh" in the optimistic locking stale case dialog, as the refresh process updated case pages but did not maintain the local action context. This was caused by the refresh mechanism updating pyWorkPage and newAssignPage without preserving the current local action state. This has been resolved by modifying the refresh process to retain local action context so users remain on the same screen and can continue their work after refreshing stale case data. | Case Management |
| INC-D35205 | 1010117 | Case archival search capability expanded to support embedded properties | Case archival search functionality was limited to embedded page-list and embedded page-group properties, preventing searches using standard embedded properties. This has been resolved by adding comprehensive logic to support search operations using embedded properties, expanding the search capabilities for archived case data. | Case Management |
| INC-D35647 INC-D34239 INC-D34684 |
1013225 | Assignment creation restored | After update, Review Requirement assignments were not being created when completing Action assignments in requirement case flows, preventing cases from progressing from Pending-Response to Pending-Review status. Investigation showed this was caused by changes to step 8 in the pxDeleteAssignmentsForWork activity within the Pega-ProcessEngine ruleset to handle cleanup of flow pages. This step invoked the RecalculateAndSave method, which unexpectedly interrupted the flow progression and caused cases to stall at a stage. This has been resolved by adding a boolean parameter CleanupFlows to the pxDeleteAssignmentsForWork activity, where step 8 will only execute to delete flow pages when this parameter is true, and by enabling the CleanupFlows parameter in step 11 of the pzUpdateAndDeleteAssignments activity to properly control assignment cleanup behavior. | Case Management |
| INC-D37420 | 1013455 | Non-PDF attachment processing restored | Non-PDF file attachments (.xlsx, .docx) were failing to save to cases with a NullPointerException in the SaveAttachment activity while PDF attachments continued to work correctly through the AttachToWork activity. Investigation showed this was caused by improper page context handling in the SaveAttachment, and has been corrected. | Case Management |
| INC-D38391 | 1014609 | Navigation paths parent handling updated | Screen-flow breadcrumb icons were being reported as non-clickable, preventing navigation between steps. This was traced to the parent flow path not being appended to screen-flow step identifiers in the DX API navigation response, and has been corrected. | Case Management |
| INC-D39472 INC-D39403 INC-B37227 INC-D35279 INC-D35160 |
1011093 1011398 1014638 |
Null check added for assignment drag and drop | Assignment transfers using drag and drop functionality were failing with error popups and preventing successful work transfers between workbaskets and worklists. This was traced to a null pointer exception in Step 2 of the pxTransferAssignment activity, and has been resolved by adding a condition to verify whether the step page exists, and if the step page is empty, Step 2 will be skipped to prevent null step page issues. | Case Management |
Cloud Services
26.1.1 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D23798 | 996666 | Database upgrade DDL generation corrected | Platform update from Infinity 24.2 to Infinity 25.1 was failing during DDL application due to incorrect "drop function" command generation when duplicate database functions existed with different argument types (varchar vs text). Investigation showed this was caused by the DDL generator not properly handling metadata inconsistencies when multiple versions of the same function existed in the database. This has been resolved by improving the DDL generation logic to correctly handle function metadata variations during database upgrades. | Cloud Services |
Conversational Channels
26.1.1 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-D35855 |
1011803 | Bot interaction timeout resolution improved | Bot interactions were failing to resolve automatically after the configured 24-hour timeout period, resulting in an excessive number of accumulated bot sessions. This was traced to the system not properly evaluating the pyIsExpired condition when determining which bot interactions should be automatically resolved, and has been corrected. | Conversational Channels |
| INC-C55557 | 999510 | Email attachment issue resolved when using email draft saving | Issues were seen with email attachments for certain file types including Excel and MP4 files when saving draft emails through the Pega email bot. Investigation showed that when attachments were uploaded in the email composer and then saved as a draft, the attachment data was being partially cleared during the save process. As a result, the system tried to re-upload those attachments during the send process, but since they had already been saved to the external storage repository the duplicate upload caused an error and the send failed. To address this, an update has been made to prevent re-uploading attachments that are already stored in the repository, resolving the error and allowing emails with draft attachments to be sent successfully. | Conversational Channels |
| INC-D27614 | 1003516 | Email notes count display corrected | When working with email interactions, the private notes count displayed in the email interaction header was not updating after posting new private notes through the notebook panel and required a manual refresh to display correctly. This was traced to the notebook panel not triggering the header count refresh when notes were added, and has been resolved by implementing automatic count updates when the notebook panel is closed after adding notes. | Conversational Channels |
| INC-D32442 | 1009189 | Email channel configuration reference corrected | Incoming email interactions were failing due to an incorrect variable reference in the pyTreatIncomingText activity for Work-Channel-Triage. This was caused by an incomplete variable reference in the activity step configuration, and has been resolved by correcting the declaration in the IVA Email feature. | Conversational Channels |
| INC-D37526 | 1013973 | Agent conversation history and tool configuration issues resolved | Case Agent conversation history was disappearing following application version upgrades, and tool default values were failing to resolve when systems were running on different Infinity versions. Investigation showed the first issue was caused by the pzGetConversationsByContext Report Definition filtering conversations based on application version, making earlier conversations invisible after update. This has been resolved by changing the pzGetConversationsByContext report definition to pyGetConversationsByContext to make it available for customer customization. The second issue resulted from version compatibility problems when resolving Chat_with_your_data tool parameters. In some scenarios, the MCP failed to resolve default values for tool parameters, which could lead to missing-parameter errors or inconsistent tool behavior when optional inputs were omitted. This has been resolved by correcting the default-value resolution logic so tool defaults are consistently applied when explicit values are not provided. | Conversational Channels |
Data Integration
26.1.1 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D11498 | 1003416 | Debug logging accuracy improved | The LockManagerImpl.expireRequestorLocks() method was consistently printing 0 in debug logs regardless of actual expired locks, making troubleshooting difficult when invoking the getDatabase().getLockManager().expireRequestorLocks() API. This was caused by incorrect logging implementation in the lock manager, and has been resolved. | Data Integration |
| INC-D18648 | 1008631 | JSON data transform class resolution corrected | JSON data transforms were not resolving to the correct circumstanced rules when called from REST services during case creation, causing incorrect rule selection. Investigation showed that the class context was not being properly maintained for JSON data transforms, and this has been corrected. | Data Integration |
| INC-D21220 INC-D26722 INC-D36733 |
1005446 1009245 1011273 |
File listener parsing errors resolved for structured data processing | After update, file listeners were stopping processing during structured data parsing after a variable number of records (typically 6-7 records) and throwing the error "com.pega.pegarules.pub.PRRuntimeException: Attempting to read more data than available on reader" at ParseStateImpl.parseCharsText. This has been addressed by updating ParseStateImpl.parseCharsText to replace the single reader.read(chars, 0, length) call with a new readFully(...) helper so it can correctly read character fields even when the underlying Reader returns partial reads. | Data Integration |
| INC-D22620 | 1004810 | Email listener message deletion resolved | Email listeners were experiencing intermittent failures when attempting to delete processed messages from Microsoft Exchange mailboxes through MS Graph API integration. The failures manifested as HTTP 404 "object not found" errors with specific error messages including "The specified object was not found in the store" and "The process failed to get the correct properties" appearing in logs with MSGraphEmailClient and ExceptionAlertResolver components. Investigation showed this was caused by Microsoft Graph changing underlying message item IDs during high mailbox activity or synchronization events, which invalidated previously retrieved message identifiers used for subsequent delete operations. This has been resolved by implementing the 'Prefer: IdType="ImmutableId"' request header to obtain stable message identifiers that persist across mailbox changes, ensuring reliable message deletion regardless of mailbox synchronization activities. | Data Integration |
| INC-D25431 | 1005583 | Decision table import validation updated | Applications could corrupt decision tables when importing modified Excel files with deleted 'if' statement rows, causing runtime issues due to different page list sizes without showing import or save errors. This was caused by insufficient validation during the import process when "allowed to return value" and "Evaluate all" rows were unchecked. This has been resolved by implementing proper validation checks during decision table import operations. | Data Integration |
| INC-D27013 | 1009237 | Added handling for file attachment names with leading spaces | File attachments with leading space characters in their filenames were generating "file does not exist" errors when uploaded using the Select file button in Cosmos and UI Kit themes on Mac and Linux systems. Windows systems were unaffected due to OS filename restrictions. This was due to an updated library version which began internally trimming leading/trailing whitespace from the filename parsed out of the Content-Disposition header. To restore the earlier behavior, this has been resolved by adding FileUploadHandler.getUnTrimmedFileName(FileItem fileItem) to support files with leading space characters across all operating systems. | Data Integration |
| INC-D29725 | 1004034 | PDF generation performance improved for heavy data scenarios | PDF generation was experiencing performance issues when processing heavy data scenarios, particularly during invoice export operations. Investigation showed this was caused by PDFBox 3.0 using legacy mode instead of the more efficient JOIN_FORM_FIELDS_MODE during PDF append operations. This has been resolved by introducing configuration to use JOIN_FORM_FIELDS_MODE and suppressing redundant warning logs related to missing dummy font files to reduce log noise. | Data Integration |
| INC-D33899 | 1010267 | FTP internal server connectivity enabled | After update, FTP connectivity to trusted internal server hostnames was being unexpectedly blocked with SSRF protection errors. This was a result of new Server-Side Request Forgery (SSRF) protection that blocked FTP/SFTP connections to internal or private IP addresses by default. To support this use, configurable prconfig allowlists have been added to enable sites with internal FTP/CMIS servers to bypass site-local SSRF blocking for trusted hosts while maintaining security protections for loopback and link-local addresses. | Data Integration |
| INC-D34683 | 1009812 | JSON schema validation updated | After update, case creation via REST API was failing during schema validation with "validateJSONAgainstYAML method undefined" compilation errors. This has been resolved by updating to a newer networknt library to improve how YAML is validated, and adding robust support for validating JSON payloads against both JSON and YAML schemas in the AutomationUtils utility. | Data Integration |
| INC-D34910 | 1010718 | Corrected Decision table import operator override | Decision table imports were incorrectly overriding result column operators to '=' when importing tables with 'Evaluate all rows' enabled and operators other than '=', such as '+='. This was caused by incorrect logic in DecisionTableWorkbenchConverter.java that used '>1' instead of '>2' in the condition check, and has been resolved by correcting the condition logic to prevent unintended operator modification during import operations. | Data Integration |
| INC-D35152 | 1009070 | Legacy model aspect casting issue fixed | Multiple application actions were generating ClassCastException errors with the message "class com.pega.platform.clipboard.adapters.internal.LegacyPageAdapter cannot be cast to class com.pega.pegarules.data.internal.clipboard.ClipboardPageBase" after update. This was caused by incompatible class casting in the LegacyModelAspectInvokableRuleContainer.invoke method, and has been resolved by adding a safeguard to prevent ClassCastException when both the Tracer tool and the ReferencePropertyLink debug logger are enabled. | Data Integration |
| INC-D40977 INC-D30946 INC-D26722 INC-D34269 INC-D21220 INC-D36733 INC-D36925 |
1012800 1015915 |
File processing updated for non-standard streams and problematic input data | File listeners were failing to process some records after update. Investigation showed that short reads from streams were causing record-type parsing to be incomplete or incorrect, and NUL bytes in log fields were causing database persistence errors for log messages and stack traces. To address this, file processing has been updated to be more robust, handling has been added for partial reads, and log messages and stack traces are sanitized before persistence to prevent database errors caused by NUL bytes. | Data Integration |
| INC-D9419 | 1003676 | Autopopulate blob growth prevented | Case opening was becoming slow as persisted data grew substantially when reference-type autopopulate properties were configured across multiple stages. Investigation showed that missing data pages could alter page hashes, clear reference metadata, and leave forward links accumulating in persisted data. To address this, cleanup logic has been implemented to remove stale forward link references at critical points and bulk-clean accumulated entries exceeding a configurable threshold. | Data Integration |
Decision Management
26.1.1 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D15986 | 1003692 | Prediction response timeout validation improved | It was possible to set prediction response timeout values that exceeded the corresponding TTL settings in ADMShortTimeoutForDelayedLearning or ADMTimeoutForDelayedLearning DSS, particularly when setting timeouts to 30 days or more. This has been resolved by implementing validation warnings that alert users when response timeout values approach or exceed the relevant TTL thresholds. | Decision Management |
| INC-D16199 | 1009116 | Case ID security updated | Cross-site scripting (XSS) protections have been updated for case ID. | Decision Management |
| INC-D19329 | 1003359 | Application overlay save performance improved | Application Overlay save functionality was failing when overlays contained a high number of rules, with the RevisionRecords data instance not updating with saved rules and success banners failing to appear, though minor overlay ruleset versions were still being generated. This was caused by performance bottlenecks in the code when processing large rule sets. This has been resolved by implementing code optimizations that allow overlay saves to work properly regardless of the number of rules. | Decision Management |
| INC-D21632 | 1007473 | Audience simulation results display corrected for mixed engagement policies | Audience simulation was not displaying eligible counts when actions contained a mix of engagement policy rules including both 'when' rules and strategies, preventing proper simulation analysis. Investigation showed this was caused by PropositionFilter in Explain Mode not passing context pages correctly to sub-strategies when proposition filters were not inlined. This has been resolved by updating the strategy execution flow so sub-strategies receive the same context page data as the parent path. | Decision Management |
| INC-D26381 | 1010026 | Email processing with large attachments made configurable | Email processing was failing when large attachments were sent through background processing via the DelayedItemsDataFlowService, generating "IllegalArgumentException: Unsupported property mode J. Property: pyPayload" errors during serialization. Investigation showed this was caused by the system's inability to properly serialize large Java objects in the queue processor when handling substantial email attachments. This has been resolved by adding serialization options for Java objects in queue processors and implementing the "PegaEngine:queueprocessors/serialization/maxJavaObjectSizeMb" DSS to control the maximum attachment size that can be serialized (default is 32MB). | Decision Management |
| INC-D26599 | 1000591 | Kafka certificate documentation updated | The documentation for obtaining external certificates to import into Pega Platform has been updated to clarify that if you do not plan to add the keystore to the platform truststore, you must restart the application server. Updating the Kafka certificates and not performing any restart of the nodes may result in "PEGA0073" errors and the messages "Error connecting to Kafka. Timeout expired while fetching topic metadata" and "Failed to construct Kafka consumer". |
Decision Management |
| INC-D27869 INC-D36960 |
1003617 1011887 |
Campaign data flow startup timing issue resolved | Campaign data flows were failing during system startup when the data flow batch service was becoming available before the ADM (Adaptive Decision Manager) service had fully initialized on the same pod. This was occurring because the ADM service is designed to start sequentially across pods, creating a timing window where campaign processing could begin and then fail when attempting to access ADM functionality that was not yet ready. This has been resolved by updating the data flow startup behavior to ensure that pods do not begin processing data flow runs until the node is in running state, which guarantees that all dependent services including ADM are fully available before campaign processing begins. | Decision Management |
| INC-D28112 | 1002150 | Adaptive analytics batch processing stabilized |
Daily batch runs were failing intermittently with NullPointerException errors while saving decision data into the pxAdaptiveAnalytics dataset, affecting one or two records out of every 1000 processed. Investigation showed this was caused by a race condition where concurrent FutureCallback invocations in ClientImpl.handleStrategyResult corrupted the internal ArrayList in HandledStrategyResult.Builder. This has been resolved by making the HandledStrategyResult.Builder thread-safe to prevent concurrent access issues. | Decision Management |
| INC-D28403 | 1009898 | Diagnostic logging improved for DSM property cache | In order to assist with diagnosing issues related to interaction History files being generated with properties lacking proper datatype definitions, existing log statements have been refined to improve troubleshooting information. | Decision Management |
| INC-D29522 | 1003699 | Hyphen character validation made consistent in Prediction Studio | Validation errors occurred when attempting to configure initial response event labels containing hyphens such as "card-displayed" in Prediction Studio settings despite the system allowing the same hyphen-containing values in target labels. This was caused by inconsistent validation rules between the initial response and target label fields, and has been resolved by updating the validation logic to consistently allow hyphen characters in both initial response and target label configurations across Prediction Studio. | Decision Management |
| INC-D31631 | 1009216 | Ethical bias simulation threshold evaluation fixed | Ethical bias simulation reports were incorrectly flagging bias as True even when bias values were within configured threshold ranges and outside confidence interval ranges, particularly affecting numeric fields that were not actually biased. Investigation showed the threshold and confidence interval evaluation logic was inverted and incorrectly processing the conditional statements. This has been resolved by correcting the threshold comparison logic in the Bias Check feature so bias will be detected only when the lower bound of the confidence interval is greater than the configured upper threshold. | Decision Management |
| INC-D31906 | 1008268 | Kafka OAuth authentication scope error corrected | OAuthBearer authentication for Confluent Kafka integration was failing during server startup with "invalid_scope" error messages stating "missing required scopes, [openid]" in the api.StreamOAuthBearerCallbackHandler logger. This was caused by the callback handler not including subproperty keys, so valid nested config values were silently dropped. This has been resolved by ensuring nested/sub-properties are included when building the JAAS config for Kafka OAuth bearer auth. | Decision Management |
| INC-D32353 | 1010046 | Interaction history summary cache memory handling refactored for improved performance | Campaign runs were experiencing significant performance degradation after update, accompanied by abnormal increases in strategy performance profile samples. The original batch cache implementation used multi-level nested maps that stored results keyed by every unique combination of optional parameters. In scenarios where queries had many optional keys with varying values (like interaction IDs, ranks, etc.), the cache would create exponentially many entries - one for each combination - leading to unbounded memory growth as the cache was never pruned. This has been resolved by restructuring how the cache stores and retrieves data. Instead of caching at the granularity of every unique combination of optional keys (which could lead to exponential memory growth), the new approach caches at the subject level and filters results in-memory, dramatically reducing memory consumption and improving cache efficiency. | Decision Management |
| INC-D35006 | 1010537 | GOS performance profile download functionality restored | Attempting to download Globally Optimized Strategies (GOS) full performance profiles failed with the error message "Index -1 out of bounds for length 7136". CSV format downloads continued to work without issue. Investigation showed this was caused by the internal state of the execution profile data becoming corrupted under specific conditions. This has been resolved by refactoring the execution-tree nodes handling and adding internal structure validation so merged profiles stay consistent and serializable. | Decision Management |
| INC-D38615 | 1012615 | Reference tracker differential processing optimized to return targeted properties | ReferenceTracker.diff() operations were returning entire page contents instead of only referenced properties during HTML template streaming, resulting in excessive data volume when persisting shallow copies to database storage, unnecessary data serialization/deserialization, and larger payloads in Kafka streams. This was caused by overly broad property inclusion logic in the differential processing mechanism, and has been resolved by implementing precise property filtering to return only actually referenced data elements. | Decision Management |
Low-Code Application Development
26.1.1 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D14440 | 1014650 | Handling updated for unavailable SOAP services | A SOAP request to an unavailable service was returning an unexpected HTML error response. Previously, the exception path treated the missing service as a generic server error and generated a SOAP fault. To resolve this, an explicit HTTP 404 Not Found response will be returned with a clear message. | Low-code App Development |
| INC-D18430 INC-D19506 |
1002718 1005111 |
System information page display corrected for IBM WebSphere | After update, the System Information page was becoming inaccessible on IBM WebSphere server environments when accessed through the Pega logo in the bottom right corner, displaying the message "Error There has been an issue; please consult your system administrator" instead of the expected system information. This was traced to JSON deserialization encountering unknown properties like "java.fullversion" that were not defined in the SystemProperties POJO, combined with XML serialization format issues where INDENT_OUTPUT was adding newlines that broke regex-based XML declaration replacement. This has been resolved by updating the exact-string regex with a relaxed, anchored matcher to better handle differences in declaration formatting. | Low-code App Development |
| INC-D23612 | 1003220 | Proposition filter corruption prevention added | The Proposition Filter was experiencing corruption when rule conditions were automatically processed through the pyAddSpecificCriteria API. This was caused by the API immediately calling pzSetSelectedPropertyDetails without proper preparation or validation of the proposition filter state. To resolve this, proper validation and state management have been implemented in the proposition filter processing to prevent corruption during automatic rule condition handling. | Low-code App Development |
| INC-D26613 | 1007045 | Workspace rule creation streamlined | Platform Designer Studio was incorrectly prompting users to manually enter ruleset and ruleset version information when creating new rules with workspace feature activated and all rulesets locked. This was caused by improper handling of workspace private branch assignments during rule creation, and has been resolved by implementing automatic assignment of rules to workspace private branches (ruleset version 01-01-01) without requiring manual input. | Low-code App Development |
| INC-D27602 INC-D29756 INC-D26104 INC-D24802 INC-D36327 INC-D17133 |
1003031 1010507 1003738 1016226 1017624 993652 |
Character encoding corrected for Word document generation | When using the standard document generation feature with Microsoft Word templates, Latin and technical characters such as the micro symbol (µ) were appearing incorrectly, with values like "20µm-500µm" being rendered as "20µm-500µm" in the generated output. Investigation showed this was caused by character encoding defects during the processing stage, specifically affecting Section tags rather than P tags, and creating additional complications with table of contents duplication when TOC elements appeared outside sdtContent containers. This has been resolved by preserving non-ASCII characters as authored along with making the DOCX generator more Word-template-aware. Instead of treating TOC or field content too broadly, it now distinguishes real TOC fields from plain text, preserves template TOCs for Word to refresh, and fixes field/page-break handling so generated documents keep the intended structure. | Low-code App Development |
| INC-D29776 | 1005991 | DevStudio logging display updated | In order to prevent exposing internal system paths in diagnostic requests generated from the alerts view, the MyAlerts HTML rule has been updated to remove the logFile hidden field and change the displayed file link on the UI to show only the basename of the log path instead of the full path. | Low-code App Development |
Mobile
26.1.1 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D23964 INC-D33553 INC-D25664 |
1004343 1008466 1001777 |
Date/time handling updated for zh_TW (Taiwanese) and in_ID (Indonesian) locales | After migration to Cloud, entering a date/time value on mobile applications with Native Control enabled would cause the input to revert to the current date/time instead of preserving the user's entry when a Save action was configured on Change and the zh_TW (Taiwanese) or in_ID (Indonesian) locales were set. This has been resolved by updating the UI datepicker control handling in Offline mode for mobile applications to preserve meridiem labels (上午/下午) in offline mode via formatDateTime for zh_tw, and offline-gated support for localized meridiem in in_id (PAGI/SORE). Calendar time formatting has also been corrected for these locales by normalizing dot-separated time values and improving AM/PM display handling. | Mobile |
| INC-D29509 | 1011865 | Background process execution stabilized for cases using custom HTML fragments | Cases were becoming stuck and failing to auto-resolve when custom flows executed SIHistoryAndAttachments HTML rules as part of background processes. Investigation showed this was caused by the pzPegaBaseScripts fragment attempting to access OperatorID.pyPreferences when the OperatorID page was null during background execution. This has been resolved by removing the unnecessary conditional logic and implementing proper null checks to ensure background processes can execute HTML fragments without operator context dependencies. | Mobile |
| INC-D29726 | 1006462 | Stream loading error resolved | Users were encountering "Failed to load stream" errors when attempting to create streams in the mobile application. This was caused by over-broad screen detection which incorrectly treated some non-worklist screens as WorkList WebView screens. To resolve this, an update has been made to better handle fast-loading pages by avoiding false Worklist detection on case pages, and filter empty offline reconciliation records. | Mobile |
Project Delivery
There were no 26.1.1 Resolved Issues for Project Delivery
Reporting
26.1.1 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D19802 | 1004828 | Insight column filter scrollbar display corrected | Column filters in insights were displaying two nested vertical scrollbars at 100% zoom. This has been resolved with an update to the SelectFilter dialog layout to prevent nested/double scrollbars by constraining the dialog content with a flex “height chain” so the checkbox list is the only element that scrolls, instead of both parent and child containers competing for overflow. | Reporting |
| INC-D19967 INC-D35580 INC-D39935 INC-D42836 |
1006048 1010184 1015512 1017211 |
InvalidReferenceException resolved for report definitions with external table mappings | Report definitions were failing with InvalidReferenceException ".pxObjClass Unexposed properties cannot be selected for classes mapped to external tables" when using a specific class hierarchy involving data classes mapped as parents of abstract classes with subclasses containing report definitions, particularly after creating Access Control Policies on the parent class. This was an inadvertent side effect of work done on attribute-based access control functionality for complex inheritance hierarchies, has been resolved by correcting a property population with a stale/incorrect class reference that interfered with the SQL generation path for secured properties. | Reporting |
| INC-D20561 | 1000980 | BIX metadata provided for improved validation/troubleshooting | When publishing CDC data to external Kafka, metadata details were not surfaced, reducing visibility into published event context. To address this, metadata details are now available as part of the external Kafka publish flow for traceability and downstream interpretation. | Reporting |
| INC-D24582 | 1002612 | Search group column data isolated | Shared columns between multiple search groups were displaying the same entered values across all search group tables, causing data confusion when users performed searches with common column configurations. This was traced to the publish-subscribe mechanism not properly isolating column data between different search group contexts, and has been resolved by including view name as a key in the publish-subscribe mechanism to ensure proper data isolation between search groups. | Reporting |
| INC-D31861 INC-D42358 |
1012478 1017361 |
Datetime function timezone handling standardized | Report definitions and datetime functions were not properly considering user timezone settings when processing constant parameters, causing date filtering mismatches. This has been resolved by implementing explicit type casting for datetime constants in SQL queries to ensure consistent timezone behavior. | Reporting |
| INC-D33072 | 1007305 | Localization support improved for insight charts | Case status values were displaying in English within Insight chart legends despite localization being enabled for the application. This has been resolved by implementing proper localization handling for case status values in Insight charts. | Reporting |
| INC-D33338 | 1012085 | ABAC condition evaluation improved for blank properties | Attribute-Based Access Control when conditions were not evaluating correctly for records with blank or null property values, causing inconsistent masking behavior between report definitions and individual record access. This has been resolved by updating the query generation to include an explicit IS NOT NULL guard for every field used in ABAC conditions, except when the condition itself is IS NULL or IS NOT NULL. | Reporting |
| INC-D34445 | 1010947 | Report browser element focus corrected | Report field editing was becoming unresponsive when users attempted to modify column formats using the magnifier glass icon, causing screen freezes. This was traced to the system not sufficiently validating state/target conditions before attempting to move focus, and has been resolved by adding a conditional guard so focus navigation only proceeds when the target element is valid for focus movement. | Reporting |
| INC-D34878 | 1012037 | Report definition query generation fixed for descendant classes | Report definitions were failing with PostgreSQL SQLState 42703 errors when using "Convert Time Units" function aliases on decimal fields from descendant classes mapped to different tables. This has been resolved by correcting the SQL generation logic to ensure proper column reference alignment between inner and outer queries when processing descendant class data with function aliases. | Reporting |
| INC-D35741 | 1014016 | Report filter display formatting improved | Report definition filters were displaying technical function names rather than the expected localized captions. This has been resolved by modifying the control logic to properly display localized captions and creating a new control pzGetLocalizedValueForReports in the pzEditSingleFilter section to ensure consistent filter display formatting. | Reporting |
| INC-D35856 | 1012410 | DateTime table rendering corrected | Tables configured with DateTime properties as primary fields were generating JavaScript download requests for incorrect files at runtime. This was traced to improper file path generation for DateTime controls in table configurations, and has been resolved by correcting the JavaScript file path generation for DateTime controls in table views. | Reporting |
| INC-D37588 | 1013473 | Reports landing page options restored | After update, My Reports and All Reports navigation options were missing from the reports landing page. This was due to configuration changes made to prevent cross-site scripting, and has been resolved by refactoring the label handling in the Report Browser tabs so the counts and tab titles are rendered through secure reusable label logic. | Reporting |
| INC-D38202 | 1016386 | Excel export security configuration updated | The Pega-Reporting/UseDataViewsExport DSS setting was not properly controlling the Microsoft Excel export option in Queryable Data Pages. This has been corrected. | Reporting |
| INC-D40778 | 1016454 | List type landing page edit functionality restored | After update, edit actions were missing from list type landing page tables in Contact Center applications, with only delete actions remaining visible despite having Add, Edit, and Delete enabled on Data Page-backed views. This was traced to Hybrid portal logic not enabling the Edit operation for Data- class objects , and has been resolved. | Reporting |
Security
26.1.1 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D15835 | 1005836 | Corrected Content security policy relogin handling | SAML authentication environments with disabled Unsafe Inline and Unsafe Eval in Content Security Policies were experiencing non-responsive relogin popups in Constellation portals, requiring manual intervention to proceed after token expiration. This was caused by the relogin screen using Traditional UI portal CSP settings that blocked required JavaScript execution. This has been resolved by updating the relogin mechanism to properly handle CSP restrictions while maintaining security compliance. | Security |
| INC-D16804 | 1008636 | Application checklist guide generation stabilized | Application checklist guides in Dev Studio were failing to display properly after application version upgrades, showing identical guide names and generating null pointer exceptions with the error "Cannot invoke com.pega.pegarules.pub.clipboard.ClipboardPage.getProperty(String) because currentRulePage is null". This was caused by improper rule page handling during security analysis for checked-out rules, and has been resolved by implementing proper null checking and page validation in the security analysis framework. | Security |
| INC-D17832 | 1008448 | URL mapping authentication restored | Applications were experiencing 403 forbidden errors when users clicked "Go to dashboard" buttons after being redirected back to Pega through URL mapping from external payment websites, despite successful URL mapping redirection. This was caused by improper BAC (Business Action Control) registration handling after external redirections that replaced the browser window context. This has been resolved by updating the authentication context restoration logic for URL mapping scenarios involving external redirections. | Security |
| INC-D21294 | 1007816 | Blended UI action permissions stabilized | Applications were generating "action is not allowed" exceptions when users were working on cases in blended UI environments. This was traced to thread selection during token reissue: in concurrent request scenarios, the refresh token process could return an in-flight case-processing thread rather than the portal’s STANDARD thread, causing UI actions to be rejected as being outside the current transaction. To resolve this, the refresh-token reissue flow has been updated to always use the dedicated STANDARD thread so transaction-id tracking stays isolated to the correct thread and concurrent case-processing activity no longer interferes with portal UI state. | Security |
| INC-D23970 | 1005765 | Password change method security enforced | HTTP method validation has been updated to ensure password change operations only accept POST requests. | Security |
| INC-D24517 | 1001717 | Application alias validation updated | Applications continued to function when users manually changed the application alias in the URL and updated cookie paths. This has been resolved by implementing proper validation checks for the app alias with access group upon change. | Security |
| INC-D28118 | 1009533 | JWT Bearer grant type authentication restored | JWT Bearer grant type connectors were failing with "Unable to fetch token page" errors, preventing SSO-based data page connections from functioning properly. Investigation showed this was caused by OAuth2 token retrieval issues affecting existing authentication profiles. This has been resolved by enhancing OAuth2 token retrieval with database fallback mechanisms to ensure reliable token access. | Security |
| INC-D29649 INC-D31577 INC-D32814 |
1005426 1006700 1008457 |
OIDC authorization parameter encoding corrected | OIDC authentication was failing after platform upgrades with the error message "error=invalid_request&error_description=unable+to+parse+claims+parameter&state" appearing during the authorization step. This was traced to the pxCreateAuthURL activity applying double encoding to OAuth2 parameters, and has been resolved by correcting the encoding logic to apply only standard URL encoding to OAuth2 parameters, eliminating the redundant HTML encoding step that was corrupting the authorization URLs. | Security |
| INC-D30018 INC-D41186 |
1007292 1017338 |
Password change flags properly reset after forgot password flow | Users who reset passwords through the Forgot Password functionality were being prompted to change their password again upon first login. Investigation showed that when the 'Force password change on next login' flag was enabled on operator profiles, the system was setting pyChangePassword and pyChangePasswordOnNextLogin flags to True, but after users completed password changes via the Forgot Password flow the flags were not reset to False. This was caused by incorrect state handling in the Forgot Password flow, and has been resolved by implementing proper flag clearing logic in the Security Policies component. | Security |
| INC-D30917 | 1006916 | Security updated for SVG file uploads | SVG content validation and sanitization has been updated for improved security. | Security |
| INC-D31125 | 1010499 | Security updated for multi-select control | Cross-site scripting (XSS) protections have been updated for the multi-select control. | Security |
| INC-D34469 | 1009767 | DPoP authentication reliability improved for multi-node environments | DPoP-enabled authentication profiles were experiencing intermittent failures when accessing APIs, particularly when UserInfo requests were processed on different nodes or threads from where tokens were originally issued. Investigation showed this was caused by DPoP nonce caching issues and keypair ID lookup problems across pooled threads and distributed nodes. This has been resolved by updating the userinfo endpoint API call to ensure it uses the same keypair which was used for the access endpoint invocation. | Security |
| INC-D34857 | 1008859 | Log filter security improved | Log filtering has been updated to ensure that credential values are not included in debug output. | Security |
| INC-D35629 | 1012656 | Production alert security updated | The generation process for PEGA0117 alerts has been updated to ensure PII data is correctly suppressed. | Security |
| INC-D36943 | 1011629 | OAuth toggle label length constrained | Installation of new Pega instances was failing during the data loading phase when attempting to save the OAuth security toggle with the error "String or binary data would be truncated in table 'pegadata.pr_data_toggle', column 'pyLabel'. Truncated value: 'This toggle enables next generation OAuth security capabilitie'." Investigation showed this was caused by the pyLabel column having insufficient length (64 characters) to accommodate the full OAuth toggle description which required 65 characters. This has been resolved with an update to constrain the description/label value to ≤64 characters. | Security |
| INC-D37249 | 1012402 | Token keypair deserialization stabilized in FIPS security mode | Access token generation was failing in FIPS mode due to keypair deserialization errors when reading cryptographic material from the database. This was traced to the serialized FIPS RSA key pair including an algorithm object as part of its custom serialization path which was not included in the deserialization allow-list, causing PegaDeserializationFilter to block it during database reload, and has been corrected. |
Security |
| INC-D37752 | 1013030 | OIDC logout flow fixed with URL encryption | Authentication timeout scenarios were failing to properly logout users when both URL encryption and obfuscated URL submission were enabled, resulting in HTTP 400 Bad Request errors instead of successful logout. Investigation showed this was caused by PRErrorResponseBuilder.java appending logout parameters as plain text without accounting for URL encryption requirements. This has been resolved. | Security |
| INC-D38914 | 1019424 | Resolved auth service login failure after initial successful authentication | SAML authentication was working correctly on the first attempt but was consistently failing after approximately 15-30 minutes. The error message "Error during URL signing process: Could not derive JCA algorithm identifier from algorithm URI" appeared in logs during subsequent login attempts. This was an issue with the AlgorithmRegistry object from the openSAML 5.1.3 jar not holding algorithms when fetched during logoff, and has been resolved. | Security |
System Administration
26.1.1 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D15355 INC-D34669 |
1001982 1009130 |
Queue processor lag calculation corrected | Queue processor dataflows were displaying misleading lag metrics with extremely high lag values while the Ready to Process (RTP) count remained at zero. This was traced to a calculation mismatch caused by two edge cases where the source offset meets or exceeds the stream end offset, and is a race condition observed specifically with AWS Kafka's delayed offset pointer updates. This has been resolved by correcting the lag calculation algorithm to accurately reflect the true processing state, ensuring that lag metrics now properly correspond with the Ready to Process counts and provide reliable monitoring data for queue processor performance. | System Administration |
| INC-D24523 INC-D34219 |
1006333 1013293 |
Job scheduler graceful shutdown improved | Job schedulers were being terminated prematurely during Cloud Kubernetes cluster restarts, causing interruption of running jobs that were expected to complete before restart. This has been resolved by implementing proper graceful shutdown handling that allows sufficient time for job schedulers to complete their processing before node termination. | System Administration |
| INC-D34195 INC-D30034 INC-D31675 |
1009124 1009096 1009749 |
Support added for multi-node session management | When maximum concurrent session limit was set to 1 for an operator, logging into a second node (cross-node) with the same operator ID did not invalidate the first session. Both sessions remained active and fully functional simultaneously. This was due to the concurrent session enforcement mechanism having been designed only for same-node scenarios where both sessions share the same server memory. To resolve this, cross-node session invalidation mechanisms have been implemented that update the shared database and ensure sessions are properly terminated when operators log into different nodes. | System Administration |
| INC-D35623 | 1011401 | Kafka OAuth token retrieval stabilized under concurrent load | Applications were experiencing OAuth token retrieval failures when processing concurrent partition and case loads in Kafka streaming applications integrated with Confluent Cloud, encountering repeated "Unable to retrieve the token" messages from StreamOAuthBearerCallbackHandler despite OAuth tokens being issued successfully. Investigation showed this was caused by IDP rate-limiting triggered by HTTP 429 responses when multiple KafkaConsumer instances simultaneously initiated SASL/OAUTHBEARER handshakes, overwhelming the identity provider with concurrent token requests. This has been resolved by adding JVM-wide token caching, proactive refresh, and graceful fallback when the identity provider rate-limits token requests. | System Administration |
| INC-D38517 | 1013637 | Axios library updated | The Axios library has been updated to the latest version. | System Administration |
| INC-D33078 | 1012045 | Restrictive Kafka messaging topic naming supported for stricter ACL alignment | Kafka stream creation, publishing, subscription, and OAuth2 cache synchronization were failing or being blocked in environments enforcing restrictive Kafka ACL naming rules because internal topic names included uppercase letters, digits, underscores, dots, or other characters outside the permitted pattern. To address this, the opt-in messaging/restrictive/topic/naming/enabled setting has been added which will normalize Kafka topic names to the [a-z-]+ format across stream, publisher, subscriber, and OAuth2 cache-sync operations while preserving original logical names for message routing; the setting will default to false for backward compatibility and will require a node restart when enabled. NOTE: This applies only to Pega's internal system messaging that uses Kafka as the underlying transport - i.e. the Stream-API-backed pub/sub used for internal cache synchronization and internal messaging channels (platform/kernel/messaging and the OAuth2 cache-sync channel in core/printegrint). It does not apply to client-authored/application-level Kafka integrations, external Kafka connectors, or any other Kafka usage outside of Pega's own internal messaging infrastructure. | System Administration |
User Experience
26.1.1 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C58000 | 1002536 | Loader-on-refresh behavior enabled/disabled via toggle | Cascading dropdowns in table layouts were experiencing value deletion and changes when rows were deleted or reordered, with subsequent rows having their values unexpectedly modified. This was caused by the dropdown component setting values to empty during unmounting while connected to Redux, triggering re-rendering before proper row deletion. This has been resolved by implementing a toggle-controlled behavior for showing a loader during refresh flows. Instead of always showing (or not showing) loader behavior on refresh, the experience is now configurable. To enable loader on refresh, make the When rule pyEnableLoaderForFormRefresh evaluate to true (default is false), and pyFormRefreshLoaderDelayInMS controls how long to wait before showing the loader, default value 1000. | User Experience |
| INC-D15926 | 1007439 | Blended UI login modal visibility restored during token expiration scenarios | Blended UI login modal visibility restored during token expiration scenarios Login continuation prompts were becoming unresponsive during refresh token expiration in blended UI implementations due to UI masking elements obscuring the authentication modal. Investigation showed this was caused by incorrect z-index layering between the authentication modal and UI masking components during modal state changes. This has been resolved by adjusting the display layer prioritization to ensure login prompts remain accessible. |
User Experience |
| INC-D17037 | 997599 | Radio button display issue resolved | Radio buttons configured with segmented display type were briefly showing a circle overlay when selected or during page load. Investigation showed this was caused by improper CSS styling in the py-cosmos-control.css rule. This has been resolved by adding z-index:-1 to the appropriate class identifiers so focused segmented radio buttons now show box shadow + outline so they are clearly visible during keyboard navigation for improved accessibility. | User Experience |
| INC-D17344 | 996068 | Case title translation enabled in navigation panel | Case titles in the left navigation panel were not being correctly localized. This was due to incorrect handling for the pyLabel property in pyCaseTab ,and has been resolved. | User Experience |
| INC-D19366 | 1001241 | Component version retention corrected | Non-library mode components were losing their previous ruleset versions when new versions were published, preventing users from restoring or comparing earlier versions of components. This was caused by the prior ruleset context not being preserved/restored correctly in the non-library component flow, and. has been resolved by modifying the component publishing process so the previous ruleset is retained. | User Experience |
| INC-D20177 | 1011221 | GenAI agent session management improved | The Pega Gen AI agent was becoming unresponsive when left idle for approximately 10 minutes, and response chunking was not working correctly for multi-line responses. This was traced to the Constellation frontend framework's handling of the streaming API response lifecycle, and has been resolved by updating the streaming message state handling so incremental updates and final message content are handled consistently. | User Experience |
| INC-D20482 | 1002560 | Error message rendering restored for refresh failures | Error messages configured through pxAddMessageToPage were not displaying in the UI when form refresh operations failed. This was caused by the banner rendering logic in the Standard form component only checking for property validation errors and submission errors, not refresh failure scenarios. This has been resolved with an update to the Assignment banner focusing behavior so focus is triggered when banner message content changes rather than when the bannerMessages prop merely receives a new reference with the same content. | User Experience |
| INC-D21238 | 994322 | Textarea focus restored during zoomed scrolling | The focus was getting lost in a textarea with large text during scrolling, and pressing Enter caused the focus to jump back to the top of the screen. Investigation showed that when zooming in and out, some CSS rules were not being validated correctly. As a result, the height was not calculated properly and led to unexpected behavior in the text area. This has been resolved by shifting from margin/height-offset compensation to explicit viewport scroll preservation during textarea auto-resize. | User Experience |
| INC-D21305 | 1005171 | Harness footer accessibility corrected | The aria-label attribute was incorrectly persisting on the footer element within the Perform Harness when Display options were configured to show both Header and Footer. This occurred because the template_workarea.js file was not properly removing the aria-label from the footer element, and has been corrected. | User Experience |
| INC-D21979 INC-D31311 |
100198 1008087 |
Visibility condition rendering corrected for summary panel tabs | Applications were experiencing visibility condition failures when summary panels were collapsed or zoomed, where tabs configured with visibility conditions and "Reserve space when hidden" enabled were incorrectly displaying even when their conditions evaluated to false. Investigation showed that while the "show-space" class with visibility:hidden styling was being applied to individual elements, it was not being applied to their parent layout groups during panel state changes. This has been resolved by updating the CSS class application to ensure the show-space class is properly applied to layout groups when reserve space is hidden with visibility conditions. | User Experience |
| INC-D22142 | 1003808 | Accessibility corrected for left panel tabs | When using JAWS to navigate through the tabs on the left panel, the narration indicated to use the left and right arrow keys instead of the correct up and down arrow keys. This was caused by navigation logic in the menu control not accounting for the semantic role of the menubar element. To resolve this for correct accessibility, an update has been made to detect when navigating within a menubar role element and automatically map left/right arrow key presses to up/down navigation. |
User Experience |
| INC-D22822 | 1006154 | List view custom action submission corrected | Custom actions from the three-dot menu in list views were failing to submit when modal actions contained query fields sourced from the same data page as the list view. This was caused by incorrect data page metadata population where the linkedField parameter was not being set properly, causing metadata conflicts in the client redux layer. This has been resolved by correcting the addDataPageMetadata logic to properly populate linkedField parameters. | User Experience |
| INC-D23082 | 1001998 | Browser back button behavior corrected after attachment downloads | After downloading multiple attachments in the Theme Cosmos User Portal, the browser back button functionality was incorrectly triggering re-downloads of previously accessed files instead of navigating to the previous page. This was caused by improper handling of browser history state after attachment download operations, and has been resolved by explicitly removing the iframe to prevent the attachment from being re-downloaded when using the browser's back button. | User Experience |
| INC-D23381 | 1003430 | Assignment instructions display made consistent | Assignment instructions were not appearing when opening assignments from the Todo widget, while the same instructions displayed correctly when accessing cases through review mode. Investigation showed this was caused by the getCaseInfo().getCurrentAssignmentViewClassName() API not returning the necessary values when navigating through nested array paths (dot-separated) before indexing. This has been addressed by extending getValueByPath to resolve nested pyViewContext array keys via dotted-path traversal before applying the index, ensuring consistent API behavior across different launch contexts to properly display assignment instructions. | User Experience |
| INC-D23451 | 1002161 | Table group expand/collapse functionality restored | Table grid expand/collapse controls were not functioning correctly when Group By functionality was enabled, with the "Collapse All" option unexpectedly expanding previously collapsed groups instead of collapsing all groups. Users were also experiencing accessibility issues with incorrect aria-label updates and visual problems with row overlays such as clicking on a row causing the row value to become hidden due to an additional white-colored overlay/background being applied. This was caused by improper state management in the table grouping logic and missing accessibility attribute updates, and has been resolved by fixing the expand/collapse state handling and correcting the accessibility attributes for grouped table rows. | User Experience |
| INC-D24010 | 996582 | Improved promoted filter picklist handling | Promoted filters were failing to render when picklist properties were configured for search box or radio-style presentation. Investigation showed that field types were not being handled consistently when configuring promoted filter display options. This has been resolved by preventing duplicate display configurations for picklists without available options. | User Experience |
| INC-D24187 | 1001393 | Nested menu navigation improved | Applications were experiencing difficulty viewing the last option while scrolling in nested menus. Investigation showed deeply nested submenus with large numbers of menu items could extend beyond the viewport, preventing access to the last menu options. To resolve this, submenu positioning and height calculation logic have been updated to respect available viewport space and allow full access to all menu items, and the keyboard menu focus management logic has been adjusted to maintain correct tabindex during keyboard navigation. | User Experience |
| INC-D24251 | 1003989 | Keyboard navigation visibility corrected | When two CaseActionHeader sections were rendered on the page, keyboard focus incorrectly moved to the inactive header's Edit and Actions buttons before Collapse Summary, causing focus on controls that are not visible to the user. This was caused by duplicate button elements from case action sections remaining in the tab order when not visible, and has been resolved by keeping only the active CaseActionHeader keyboard accessible by applying inert to the inactive header based on the Summary Panel state, ensuring the correct tab order. | User Experience |
| INC-D24287 | 1002154 | Modal dialog accessibility corrected for zoom | Applications were experiencing focus navigation issues when using tab controls in modal dialogs at 200% zoom or above, where focus would shift to background elements instead of remaining within the modal dialog. This was caused by improper focus management in zoomed modal dialog implementations, and has been corrected. | User Experience |
| INC-D24561 | 1007676 | Autocomplete leave blank display corrected for embedded page properties | Autocomplete controls were displaying incorrectly for "Leave Blank" options when configured with embedded page property data sources from report definitions. This was traced to the markup handling where a blank value in the “TOP” result could show up as a narrow/incorrect blank entry, and has been corrected. | User Experience |
| INC-D25196 | 1001447 | Search updated for localized environments | When switching between "All instances" and specific case type filters in Constellation UI with German localization enabled, search results would disappear after applying case type filters and would not return even when switching back to "All instances" view. Investigation showed this was caused by the search context failing to reinitialize properly after filter changes in localized environments. This has been resolved by updating the Constellation UI search context management to apply localization logic for the case type list while comparing, so that it will be compared properly. | User Experience |
| INC-D25552 | 1010161 | Recent list population performance improved | The pzPopulateRecentList activity was experiencing significant performance degradation due to inefficient blob column retrieval in the recent items query. This was caused by missing optimization for large data retrieval in the recent list population logic. To address this, a DSS has been added to enable query optimization along with reducing blob column access frequency to improve database performance for recent list operations. This replaces a costly full-row scan/query pattern with an indexed retrieval + per-row hydration approach. The DSS "useIndexedHydration" defaults to false to maintain the current behavior of directly selecting the full set of needed fields (pySelectFields) in one go, without per-row open/hydration. When set to 'true', the query fetches lightweight row keys (uses pzInsKey/handle), then each result row is “hydrated” by opening the full record (Obj-Open by handle) to populate fields like label/description/content type. Note that some newly-created cases may be excluded from the results when "useIndexedHydration" is enabled and its use may not be preferred in all environments. | User Experience |
| INC-D25799 | 1003010 | Advanced search bar behavior standardized | The search bar was retaining entered strings after opening work objects through advanced search results, while properly resetting when opening objects through regular search results. This was caused by inconsistent reset behavior between different search result pathways, and has been resolved by explicitly clearing the tracked search input state on the case-open navigation event to standardize the search bar reset functionality across all search result interactions. | User Experience |
| INC-D25992 | 1006172 | Modal popup positioning corrected | Modal popups were appearing at the bottom of the screen instead of their intended centered position when launched within Constellation applications loaded in iframes. Investigation showed that a fix intended for mobile modal dialog positioning was appending inline CSS to iframe elements and modal-align-cell class, causing modal height to use full iframe scroll height rather than viewport height and resulting in bottom-screen placement in iframe mashup scenarios. This has been resolved by updating the modal positioning algorithm to properly calculate viewport coordinates and ensure modals appear in the correct screen location. | User Experience |
| INC-D26877 | 1001641 | Advanced search special character handling improved | Advanced search functionality was experiencing content disappearance when certain key combinations like parentheses were entered and submitted, causing console errors in the Constellation application. This has been resolved by updating the character encoding and validation in the advanced search processing, ensuring special characters are handled correctly without causing application content to disappear. | User Experience |
| INC-D27218 | 1007268 | Table empty value display restored | After update, empty text field values in configured tables were displaying as blank spaces instead of the expected "--" placeholder that was shown in previous versions. This was an intentional change made in an earlier release where "--" rendering was moved from DOM to CSS for accessibility reasons. To address this, the change has now has been modified by providing fine-tuned CSS changes to restore the "--" display for empty values while maintaining accessibility compliance. | User Experience |
| INC-D27678 | 1008172 | Dynamic text refresh functionality corrected | Dynamic text content using VerbatimParagraph templates was not refreshing after onChange data transforms, causing outdated content to persist even when underlying decision parameters changed. This was seen with static text display despite radio button selections that should have triggered content updates based on when rules. Investigation showed this was caused by the template rendering system not responding to state changes in react_pconnect views. This has been resolved by implementing proper re-rendering triggers for dynamic text in VerbatimParagraph templates when refresh conditions are met. | User Experience |
| INC-D27679 | 1003244 | Focus restored to date picker calendar icon | When using a date picker within a modal dialog, pressing the escape key to close the calendar was leaving focus in an undefined state rather than returning it to the calendar icon. This was caused by the modal dialog's closeChildOverlay function not properly handling the focus return for date time fields, and has been resolved by adding conditional logic to send the close reason as ""clickaway"" in the callback parameter, ensuring focus returns to the calendar icon after escape key usage. | User Experience |
| INC-D28177 | 1004418 | Dynamic text rules applied consistently across embedded repeating rows | Dynamic text configured through decision rules on embedded data properties was only functioning for the first row in repeating views, while subsequent rows displayed without the dynamic text evaluation. Investigation showed the rule evaluation was not being triggered for rows beyond the first instance. This has been resolved with an update that ensures all the dynamic properties of a paragraph rule are processed for each entry in a list. | User Experience |
| INC-D28395 | 1003929 | Stakeholder widget party labeling corrected | The stakeholder widget was displaying incorrect field labels for party role radio buttons, showing the internal technical party role instead of the user-friendly party label previously seen. This has been resolved by keeping the API role ID and role label as separate fields in Stakeholders role handling so the proper party label displays in the stakeholder widget role radio button fields. | User Experience |
| INC-D28467 | 1005458 | Preserved invalid date input | Date validation was displaying the replacement message "invalid is not a valid date value" instead of retaining the incomplete or incorrect value entered during date processing. This was due to the raw date input not being preserved in the validation state, and has been resolved with an update to save the original invalid datetime value in the redux state for consistent error handling. | User Experience |
| INC-D29577 | 1005462 | Search context properly cleared when navigating to home page | After performing a search operation and switching to advanced search mode, search context was not being reset when navigating back to home screen. This was caused by incomplete search state cleanup during navigation events, and has been resolved by ensuring search context is explicitly cleared whenever a navigation item is activated. | User Experience |
| INC-D29662 | 1008471 | Screen reader announcements consistent between modal types | When a flow action was opened using a modal window, the pyCaption was correctly announced by screen readers. However, when the same flow action was opened using an overlay modal, the screen reader announced the flow action name instead of the configured pyCaption. This was due to a missed localization path for a modal title, and has been resolved by updating to use getLocalizedTextForString so the title is now translated consistently. | User Experience |
| INC-D29835 | 1004770 | Delete confirmation message localized | Delete confirmation dialogs were displaying in English instead of the configured language on Constellation landing pages. This has been resolved. | User Experience |
| INC-D30168 | 1005676 | Accessibility labels maintained after section refresh for AnyPicker controls | The clear icon in AnyPicker controls was losing its aria-label attribute following section refresh actions. This was traced to incomplete DOM reconstruction during the refresh process, and has been resolved by adding dynamic aria-label generation to the clear icon to ensure consistent accessibility information. | User Experience |
| INC-D30243 INC-D34832 |
1011544 1018382 |
Corrected transaction search error message handling | Transaction search screens in customized Pega Smart Dispute Agentic Automation (SDAA) interfaces were displaying misplaced error messages that persisted after performing valid date searches. This was an unintended change made as part of a DSS configuration update, and has been resolved by adjusting the error message handling logic in Constellation. | User Experience |
| INC-D30341 | 1006209 | Data page picklist property display corrected | Data pages configured with table type were displaying incorrect values from associated properties in list views. When unexposed properties were mapped to associated properties in response data transforms, the unexposed property was holding display text values instead of code values, while direct reference to associated properties in list views was not functioning as expected. Investigation showed this was caused by incorrect mapping logic in the presentation layer despite the DX API correctly retrieving code values from the backend. This has been resolved by extending rule-store property metadata lookup to also match on associationClassID, enabling correct resolution for associated picklist properties. | User Experience |
| INC-D30362 | 1009151 | Hierarchical table link outline spacing improved | When tab focus was applied to link controls in hierarchical tables, a solid outline was appearing with insufficient padding around the content that caused values to appear cramped. This has been resolved by adjusting the outline spacing and padding properties to improve accessibility and visual appearance for focused link elements in hierarchical tables. | User Experience |
| INC-D31508 | 1008337 | Corrected hierarchical button behavior | Configured action buttons were functioning in standard forms but were failing when placed in hierarchical forms. This was traced to hierarchical components receiving an incorrect container name, and has been resolved by adding the hierarchical form container name to the deferred-load context. | User Experience |
| INC-D31585 | 1009397 | DX component builder template classification corrected | Custom templates created via DX Component Builder were being incorrectly classified as form views instead of partial views across multiple applications and data objects. Templates not containing the keyword 'details' in their names were being treated as form views and assigned 'embeddeddata' view type, which triggered unintended mode:editable properties in pxViewMetaData configuration. This was caused by flawed logic in pzAddView Activity step 4 that determined view type based solely on whether template names contained the 'details' keyword. This has been resolved by improving the template classification logic in the UI Authoring component. | User Experience |
| INC-D32432 | 1007649 | Expand/collapse navigation button layout corrected | The clickable area of the expand/collapse toggle button in case left navigation was not accessible due to being partially covered by the ShowSmartTip style overlay. This was caused by conflicting CSS positioning that created an invisible overlay blocking user interaction with parts of the toggle button, and has been resolved by adjusting the button format from Standard to TinyTipHeader and correcting the CSS positioning to ensure the entire button area remains clickable. | User Experience |
| INC-D32920 | 1008441 | Time input validation corrected for 24-hour format | Time-of-day controls were rejecting valid "00" hour values when 24-hour formatting was enabled, preventing the entry of midnight times like "00:30" and causing validation errors during data entry. This was caused by incorrect hour validation logic in the pzpega_ui_calendar_util.js file, and has been resolved by updating the appendToDate and getHoursIn24HoursFormat functions to correctly process "00" hour values when 24-hour formatting is enabled. | User Experience |
| INC-D33043 | 1008396 | Negative decimal values with leading zeros accepted in Constellation | Decimal number fields in Constellation were rejecting negative values that began with zero (such as -0.5). This was caused by input validation logic that incorrectly identified these values as invalid numeric formats, and has been corrected. | User Experience |
| INC-D33360 | 1012462 | Table validation alignment corrected | After update, required field validation warnings were appearing on incorrect grid rows. This was caused by incorrect row-to-data array mapping in pzpega_ui_doc_domUtils where the 4th visible row was incorrectly mapped to the 5th position in the data array, leading to misalignment between visible UI positions and underlying data array indices. This has been resolved by correcting the row indexing logic in the DOM utilities to ensure proper alignment between visible table rows and their corresponding data array positions during validation processing. | User Experience |
| INC-D33662 | 1010828 | Table checkbox validation error icons restored | Validation error icons were not displaying beside checkboxes in tables after update. This was an inadvertent side effect of work done on checkbox validation error icon positioning, and has been resolved. | User Experience |
| INC-D33684 | 1009262 | Case manager dashboard editor layout fixed | The dashboard widget editor in the UI Kit was experiencing overlapping content issues where the DELETE icon overlapped the right-hand panel and the stages view created additional overlap elements. This was caused by incorrect positioning and layering of UI elements in the dashboard personalization interface, and has been resolved. | User Experience |
| INC-D34215 | 1010437 | Related case opening corrected for blended UI | Attempting to open related cases in a new tab within Constellation blended UI environments generated a 404 error. This was caused by improper URL handling for Constellation cases when accessed through the "Open in tab" functionality from the related cases widgets in a traditional portal, and has been resolved by updating the generation logic so a semantic link now handles the open in tab for Constellation cases. | User Experience |
| INC-D34893 | 1009665 | Accessibility corrected for progress loading | Screen readers were announcing a "progressbar" for the loader div regardless of loading state. This was caused by incorrect ARIA role assignment in the AnyPicker control template, and has been resolved by removing the static role from the template and dynamically setting/resetting it in the JavaScript control, ensuring screen readers comply with W3C HTML-ARIA standards and correctly announce loading status based on actual UI state. | User Experience |
| INC-D35545 | 1011676 | Keyboard navigation improved for success dialogs | Success banner dialogs were not properly announcing the close button to assistive technologies during keyboard navigation. This was caused by improper focus management in the success banner dialog component, and has been resolved. | User Experience |
| INC-D35657 | 1012605 | TinyTipHeader smart tip format added | System warnings were being generated during case processing related to smart tips not being rendered as intended. This was due to a missing format component in the pyCaseMainInner section, and has been corrected by adding a new smart tip skin format called TinyTipHeader to Cosmos skin. This supports styling for the header variant to present a more compact/header-oriented smart tip appearance. | User Experience |
| INC-D36292 | 1011867 | Support added for external links in portal navigation | Portal navigation was limiting hierarchical menu organization and direct links to external destinations, rewriting them into standard landing-page items. This was due to grouping and external-link navigation items not being supported in the affected portal configuration. To address this, an update has been made that enables the navigation UI to render them as distinct external link entries with their label, icon, and URL preserved. | User Experience |
| INC-D36702 | 1013899 | Report navigation functionality restored for Blended UI | After update, work orders were not opening when clicked from Report Definition screens in Blended UI configurations. Investigation showed this was caused by broken navigation handling in the Blended UI report integration, and has been resolved by ensuring UI/report click handling and/or the route/open invocation logic resolves to a valid work-object open action. | User Experience |
| INC-D37287 | 1013180 | Search filter persistence maintained during work object search operations | Applied case filters were being cleared when performing work object searches outside the filter context, causing loss of previously established search criteria. This was traced to inconsistent filter state management during search transitions, and has been resolved by implementing proper filter context preservation across all search operation pathways. | User Experience |
| INC-D37671 | 1011905 | Banner message HTML encoding display corrected | Banner messages in the Global Operations Console were displaying HTML-encoded character values instead of proper text, particularly affecting quotation marks and other special characters in maintenance window notifications and banner-based content. This was caused by some values being encoded multiple times in the UI as part of the application of cross-site scripting filters, and has been resolved by implementing proper character decoding for banner content display. | User Experience |
| INC-D37675 | 1013917 | Job menu display updated | The UI behavior in core:ListToolbar has been updated so the view selector renders as icon-only when only a single view is available. The display label logic was also improved to show the extracted data object name instead of the data page name. | User Experience |