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.)
Low-code Application Development
Case Management
25.1.2 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-C46937 |
967416 | Logging added for automatic stage transition failure | Cases were experiencing intermittent failures during automatic stage transitions from Product Assignment to Closure stage, with the system performing OOTB rollbacks to the last active commit step in the early Enrich stage. In order to assist with diagnosing the issue, a try-catch block has been added around the queueBatchActivity call the EVALUATE_AGENT case for better error diagnostics, and logging of declarative context information has been implemented when exceptions occur during agent evaluation. The caught exception will be re-thrown after logging to preserve the original behavior. | Case Management |
| INC-B32878 | 948271 | Assignment repair button functionality restored | After update, the "Repair this assignment" button was failing with the error "The flow this assignment corresponds to is no longer at this task". This was traced to additional conditional logic that was added to the FixBrokenAssignments activity which was not compatible with assignments which had validation messages on the last flow step. This has been resolved by modifying the conditional logic handling for the activity. | Case Management |
| INC-C37564 | 953639 | Assignment skill validation implemented for Go button visibility | Assignment Go buttons were appearing in Constellation for users lacking required skills, only showing unauthorized access errors after clicking. This was a difference in behavior from previous versions, and was caused by the required skills not being loaded to the pxFlow page during assignment list formation. This has been resolved by ensuring required skills are properly copied to the pxFlow page and validated before displaying the Go button. | Case Management |
| INC-C38149 | 958657 960260 |
SMS attachment download functionality updated | SMS attachments were not downloading when accessed through the Constellation CS application. This was caused by the pzGetAttachment activity only checking for Email correspondence types while missing the necessary code to handle PhoneText correspondence, and has been resolved by extending the attachment handling logic to support SMS correspondence downloads in both the DX API and Constellation UI components. | Case Management |
| INC-C38268 | 958693 | Audit history restored for archived cases after cloud migration | During cloud migration from Oracle to PostgreSQL databases, the audit history was missing due to a difference in the datetime format between the databases. This has been resolved by implementing logic to manage date conversion for various databases by deriving the database type based on the date format regular expressions carried from previous databases. | Case Management |
| INC-C40492 | 952547 | Embedded page attachment duplication eliminated | Multi-attachment fields configured within embedded page properties were creating duplicate empty attachment list pages alongside actual attachments. This has been resolved by updating pzApplyPageInstructions to prevent an empty page from being created when processing attachments within embedded page contexts. | Case Management |
| INC-C42045 | 959753 | DX API v1 validation processing corrected | DX API v1 services were failing with validation errors after upgrade. This was traced to modifications made to the handling of Declare OnChange triggers and changes in the pzApplyDataForPerformAction activity which applied mapInputJSON() logic designed for DX API v2 to v1 requests. This has been resolved. | Case Management |
| INC-C42220 | 964843 | Case context passed to upload API | File uploads to external systems via REST API calls were missing the case context information needed for proper case tagging. This has been resolved by adding the necessary logic to pass ContextID in the Upload API to access the case context in pzSavetoRepository activities. | Case Management |
| INC-C43508 | 959092 | Case attachments widget report definition made available | Previously, the pzGetAttachmentsCountOfACase report definition was used to display the attachment count on the utility panel when collapsed. In order to support customization, this has been replaced with the available rule pyGetAttachmentsCountOfACase. | Case Management |
| INC-C43576 | 961267 | Child associations listed with parent associations in archive | After adding child case associations to the parent case settings, the association was not shown in the case settings even though the corresponding record was added to the d_archivalassociation table and the associated record was archived. This has been resolved by adding a pzListArchivalAssociation activity and updating D_pzListArchivalAssociation. | Case Management |
| INC-C44033 | 956773 | "Previous" button navigation behavior restored | After update, a behavior change was seen with the "Previous" local action. Originally, while sitting in the 1st assignment of the 2nd subflow in a flow with two back to back sub-flows, the "Previous" local action brought you back to the last step in the 1st subflow. After update, the "Previous" local action returned to the first assignment in the parent flow. This was caused by changes in the flow navigation logic that affected how the system determined the previous step in complex flow structures. This has been resolved by restoring the previous navigation behavior to match the expected flow traversal patterns. | Case Management |
| INC-C44509 | 957569 | Work object search correctly refreshes windows | When accessed through search functionality, work objects were opening in new windows instead of refreshing existing ones. This created multiple instances of the same work item. Investigation traced this to missing function definitions in the Navigation HTML fragment rule affecting the display_showImageErrors function, and this has been resolved by updating the navigation logic to properly detect and refresh existing work object windows rather than creating new instances. | Case Management |
| INC-C4509 | 915943 | Added handling for upload file parsing with special characters | File parsing during upload with the pzMultiFilePath control was failing if the file contained special characters. This was due to a mismatch in the file name which resulted in a "file not found" exception, and was caused by the pzMultiFilePath encoding the file name if it contained any special characters while the parsing function checked the file name without any encoding. To resolve this, the handling has been updated to ensure consistent encoding of file names during both upload and parsing processes. | Case Management |
| INC-C45742 | 962042 | PDF attachment accessibility retained after name changes | PDF attachments generated during case processing were becoming inaccessible after being renamed. This was caused by the pySaveFileContent activity creating new repository files without proper context when the pzSaveToRepository method was triggered during name update, and has been resolved by implementing logic to skip unnecessary repository calls during name changes while maintaining proper file context and accessibility. | Case Management |
| INC-C46918 | 961745 | Property max length display corrected | Properties were incorrectly displaying a maximum length value of 256 characters in the Advanced configuration section when no maximum length had been explicitly set. This has been resolved by correcting the Advanced configuration display to show empty values when no maximum length is configured, and documentation has been clarified to provide specific guidance on database column size limits rather than ambiguous references to multiple possible values. | Case Management |
| INC-C49224 | 960391 | File upload exception busy indicator handling updated | When file size validation messages appeared in modal dialogs, the screen was sometimes freezing with busy indicators remaining visible after clicking "OK" on size limit alerts. This was caused by the busy indicator not being properly dismissed, and has been resolved by adding a script to hide the busy indicator when the exception happens during file upload using pzMultiFilePath control. | Case Management |
| INC-C51780 | 961845 | Corrected DX API authorization handling for assignment urgency updates | DX API v1 calls were failing with 400 authorization errors when cases contained multiple open assignments including Wait (Case Dependency) assignments. This was traced to a missed use case of the pzSyncAssignmentUrgency declare trigger attempting to lock assignments without proper access privileges during urgency recalculation, and has been resolved by modifying the handling in the UpdateAssignmentUrgency activity to keep all assignment in sync with case urgency. | Case Management |
| INC-C52052 INC-D3152 |
963013 | Support added to include private pulse posts in email digest notifications | Private posts were not appearing in daily and weekly email digest notifications despite being properly created and mentioned recipients being configured for digest notifications. This was traced to the email digest report definition not including instance handle keys for private posts, causing them to be treated as deleted during digest processing. This has been resolved by creating a new report definition rule 'pzGetEmailDigestPvtNotifications' to fetch private notifications, and the 'pzRetrieveNotificationsData' activity has been updated to include those in the email digest.. | Case Management |
| INC-C52114 | 961728 | Document file removal behavior restored for reference deletion | After upgrade, document attachments were being permanently deleted from the repository instead of only removing the case association link. This was caused by modifications to the pzRemoveDocumentReference activity that were intended to avoid orphan records in the system without any association to a case, and has been addressed by restoring the original behavior to remove document associations while preserving the source documents. | Case Management |
| INC-C52257 | 965840 | Related case partial text search limited to 100 results | Related Cases widget searches in Constellation were hanging indefinitely when typing search characters in high-volume production environments. To address this, the auto-complete search for partial text in the Related Cases widget will be limited to 100 results. | Case Management |
| INC-C52381 | 965670 | API field validation error details restored | API responses were returning generic error messages instead of detailed field-level validation information when invalid data was submitted through the Case Creation API and other standard Pega APIs. Investigation showed this was caused by previous work that altered how validation errors were handled, and has been resolved by restoring the previous behavior of detailed field-level validation error responses that help with debugging and troubleshooting invalid API requests. | Case Management |
| INC-C52742 | 962298 | Documentation updated to address DX API case retrieval performance impact | Retrieving cases with pyWorkPage data sizes over 1.5MB through the DX API v1/cases/{id} endpoint can lead to performance degradation. To assist in avoiding this impact, the documentation for Traditional DX API -> Understanding the response page & Constellation DX API -> Understanding the response has been updated to recommend the use of Data References to avoid excessively large cases. | Case Management |
| INC-C54149 INC-D884 |
967142 972103 |
Field level auditing functionality restored for case creation | Field level auditing was not functioning properly during case creation, where the initial ADD operation for properties like pyStatusWork was not being captured in the audit trail. This was traced to previous work done to avoid duplicate field level auditing records which prevented the previousPage variable from being cleared properly during case creation, causing both previousPage and primaryPage to remain identical and blocking the audit capture mechanism. This has been resolved by updating the function in pxFieldlevelauditing to properly handle cases without create stage and ensuring the previousPage variable is correctly managed during the case creation process. | Case Management |
| INC-C54329 | 968463 | Child to parent case navigation corrected | Navigation from child cases to parent cases was automatically redirecting back to the child case after page loading completed. This occurred specifically when error dialogs were dismissed using the cancel button rather than the X button in edit details popups, and was caused by improper state management in the breadcrumb navigation logic following error dialog interactions. This has been resolved by adding "pega.desktop.infinity.clearCaseActionParams" to the cancel button action. | Case Management |
| INC-C55523 INC-C59726 INC-C56379 |
969207 969205 972907 |
DSS added to support case archival process for SRS | After update, case archival processes were getting stuck at "index-failed" status. Investigation showed that data model changes had been implemented on the archival side to support date range search functionality, but these changes were not supported by the SRS (Search and Reporting Service) side, creating a compatibility mismatch that prevented successful archival operations. This has been resolved by implementing switching logic that allows toggling between old and new schema versions for the archival index data model, with the system defaulting to the old schema for archival indexing to maintain backward compatibility while providing the option to enable new schema features when SRS support becomes available. | Case Management |
| INC-C56958 | 969879 | Embedded table data retention resolved | Deleted row data was being retained and incorrectly pre-populated when adding new entries to embedded tables and data grids within screenflows. Investigation showed this was caused by the Page-Validate method executing on a removed interest page, which created an empty page on the @baseclass instead of properly handling the deleted state. This has been resolved by adding a PageExistsWithClass check before executing the Page-Validate step in the pzFilterRefreshAPIFieldsInRequestBody activity, ensuring deleted row data is properly cleared from memory and new entries display with blank fields as expected. | Case Management |
Cloud Services
25.1.2 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B42656 INC-B31292 INC-C23421 INC-B30497 INC-C41068 INC-B40109 INC-B49213 |
953842 | Hotfix system scan file validation message updated | Hotfix system scans using Hotfix DL files were displaying incorrect error messages stating that files should be named CATALOG.ZIP, even though the scans completed successfully. Investigation showed that the file validation logic was checking for specific naming conventions while still processing the files correctly. To address this, the validation messaging has been updated to indicate that the catalog upload failed, but the process can continue with the scan using the existing catalog on the system if desired. | Cloud Services |
| INC-C57002 | 969355 | Requester pool size defaults to 1 for upgrade | Platform upgrades were experiencing blocking sessions during "Optimize Newly Exposed Columns" and "Generate Declarative Indexes" tasks. Investigation showed multiple concurrent threads were creating database contention between select and insert operations on rule tables due to the default thread pool size of 4 being used when the NumOfThreads property was not explicitly configured during expose operations. This has been resolved by setting the request pool size default to 1 for this scenario. | Cloud Services |
Conversational Channels
25.1.2 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C43147 | 955396 | Email draft attachments preserved correctly | Email draft attachments were being incorrectly retrieved when reopening cases, with attachments sometimes replaced or duplicated when multiple files were added to reply drafts. This was traced to pxSaveAttachmentstoDraft not updating the linkAttachment page with .pxAttachName property, and has been resolved. | Conversational Channels |
| INC-C45795 | 960028 | Email case timestamp made consistent | Email triage cases were displaying different create datetime values when accessed through class instances versus DISP case related views. This has been resolved by updating the the email manager portal display logic to standardize the timezone processing across all case access methods to ensure consistent timestamp display. | Conversational Channels |
| INC-C58483 | 969928 | Email thread timestamp handling updated for timezone differences | Email interaction threads were displaying incorrect timestamps with future dates and wrong day calculations, particularly affecting AEDT timezone (+11) environments where replies showed inconsistent timing. This has been resolved with an update to ensure the timestamp for 'email send' time is sent to client side based on user's timezone. | Conversational Channels |
Data Integration
25.1.2 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B48689 | 959304 | Table instance deployment synchronization handling updated | Changes to properties such as adding new properties, adding new database columns mapped to existing properties, or exposing properties through property optimization were not being recognized on all nodes after deployment, causing only the importing node to have access to the updated information. This has been resolved by implementing forced mapping which will fetch the necessary information from the database and build the property mapping when a property change pulse or a DADT re-save method call is received. This information is built once and will be used in subsequent calls until there is a pod restart, DADT resave, class resave, or a new property change pulse not received. | Data Integration |
| INC-C10777 | 955987 | Logging enhanced for large email attachment issues | Outbound emails with attachments of 25MB or larger were failing to send through the pxReply activity. To assist with diagnosing these issues, error logging has been added for chunk upload failures. | Data Integration |
| INC-C20700 | 930494 | Circumstanced rule resolution documentation updated | The documentation for Creating a Rule specialized by circumstance has been updated with links to Circumstance definitions and templates to assist with configuring the desired conditions and relevant processing. | Data Integration |
| INC-C25456 | 960939 | Property decryption enabled for association data | Encrypted properties were displaying in their encrypted form rather than being automatically decrypted when retrieved through report definitions using associations in Constellation interfaces. This was traced to the system not recognizing encrypted properties when accessed through this method, and has been resolved by adding the necessary decryption logic to support this use in the data_views API. | Data Integration |
| INC-C26129 INC-C58427 INC-C29220 INC-C33113 INC-C57821 INC-C34718 INC-C32103 INC-C17885 INC-C25880 INC-C32238 INC-C31541 INC-C56940 |
943188 | Field flattening enabled for GenerateEForm | PDF forms were experiencing issues where filled fields would disappear when opened in Adobe Reader. Investigation showed this was caused by the lack of field flattening in the GenerateEForm activity due to change in the dependency JAR from iText to PDFBox, and has been resolved by implementing functionality similar to the existing ConcatenateEForms activity, ensuring PDF fields remain properly populated and non-editable when viewed in external applications. | Data Integration |
| INC-C28380 | 955829 | Stack overflow tracing enhanced to assist with case loading issues | After updating to Cloud, cases were failing to load when accessed from the portal and pyWorkPage remained blank. This was traced to the pxCallObjOpen activity during D_CaseLookup operations, and the logs indicated "Error loading D_CaseLookup using activity {pxObjClass=Rule-Obj-Activity, pyClassName=BNS-FW-SCOBFW-Work, pyActivityName=pxCallObjOpen}". In order to assist with diagnosing this issue, detailed logging has been added to identify which property is causing the circular reference that leads to a StackOverflowError. | Data Integration |
| INC-C34085 | 964632 | Application page initialization fixed for prediction notifications | Email notifications were not being triggered in Prediction Studio. Investigation showed this was caused by the application page not being initialized when attachment logic was invoked via batch requestor and queue activity, and has been resolved by initializing the application page to prevent null pointer exceptions. | Data Integration |
| INC-C34795 | 958632 | Invalid property persistence resolved | Cases were being created with an invalid pyReportDefinition property persisted on case instances, causing DX API validation failures. Investigation showed this was caused by the pxConvertResultsToCSV activity incorrectly creating classless properties under pyWorkPage when generating CSV downloads through UI links. This has been resolved. | Data Integration |
| INC-C35583 | 956589 | Data view API behavior corrected for empty values | After update, custom components were failing to render when clicking Professional IDs from search results. Investigation showed the DX API endpoint /api/application/v2/data_views/{data_view_ID} response data transform behavior had changed, where the Default Automap Empty Behavior switched from Default value to Null, causing empty strings and arrays to be replaced with null values that were not expected by the custom components. This has been resolved by restoring the data view API Default Automap Empty Behavior to return default values instead of null for empty data. | Data Integration |
| INC-C36999 | 962613 | Rule sync pulse thread termination handling improved | Rule synchronization was failing due to pulse thread termination during handleTerminateRequestorRequest method execution, causing cache inconsistencies in distributed environments. Investigation showed this was caused by inadequate exception handling during requestor termination processes, and it has been addressed by adding a catch block to the handleTerminateRequestorRequest() method within NodeRequestorMgt to improve exception handling. This enhancement provides deeper insights into any errors that occur during requestor termination, facilitating easier debugging and more robust error tracking. | Data Integration |
| INC-C40236 | 960092 | Oracle database query limit handling improved | Database operations were failing with "ORA-01795: maximum number of expressions in a list is 1000" errors when retrieving property information for classes with large inheritance hierarchies. This was caused by Oracle's limitation on IN clause expressions when the ancestorAndClassGroupMemberList exceeded 1000 items during property lookups. To address this, an update has been made to detect the use of Oracle and modify the lookupPropertyQueryWithLimitedExpressions() function to build IN clauses with chunking to prevent reaching the restriction level. The original behavior is preserved for other databases. | Data Integration |
| INC-C40677 | 960732 | PDF form compatibility documented | The documentation for HTMLtoPDF parameters in Building custom UI capabilities has been updated to clarify that editable PDF files are not recommended and are a limitation of the Acroforms implementation. | Data Integration |
| INC-C42133 | 960370 | Authentication handling for service utilities improved | Export operations using prpcServiceUtils were failing with 401 Unauthorized errors when specific Dynamic System Settings for HTTP service response headers were configured, particularly those containing SET-COOKIE values. This has been resolved by modifying the authentication logic to properly handle custom response header configurations during service utility operations. | Data Integration |
| INC-C42476 INC-C51970 |
955092 961801 |
SOAP header handling improved for optional elements | ConnectSoap rules were failing when optional header elements had no runtime values, generating "Couldn't create OMElement from string value" errors. This has been resolved by adding empty string validation to skip processing of headers with no content values. | Data Integration |
| INC-C44025 | 963225 | Memory management improved for strategy execution | High-volume API testing was causing out-of-memory errors with PEGA0039 alerts indicating large pzpvstream references exceeding 499 MB and sometimes 1.8 GB during strategy execution. Investigation showed that GOSProgram2 blob objects were preserving excessive memory and creating orphan entries during Java object operations. This has been resolved by implementing proper memory cleanup to remove orphan entries whenever the orphan data exceeds 10% of the actual BLOB size. | Data Integration |
| INC-C47478 INC-C46353 INC-C56134 |
957252 956867 967023 |
Query runner display and performance enhanced | The query runner tool was displaying only 20 columns maximum, showing unformatted text data without word wrapping for XML/JSON content, and experiencing performance issues. This was caused by limitations in the query runner implementation, and has been resolved by implementing an HTML/JS/JSP/Java-based solution that increases the column display limit to 100, adds pagination functionality, enables dynamic table column generation, and improves text formatting with proper word wrapping. | Data Integration |
| INC-C47722 | 958823 | Resource management improved | Resource management handling has been updated for CMIS, REST, and HTTP connectors using try-with-resources blocks in the connector activities to ensure resources are properly closed. | Data Integration |
| INC-C48714 INC-C56859 INC-C57591 |
958419 966302 970135 |
Google cloud storage file operations issues resolved | ConcurrentModificationException and NullPointerException errors were generated indicating "There was an issue during checking if a file or directory exists" when connecting to Google Cloud Storage for hourly data updates and file retrieval operations. This was traced to the authentication page handling and synchronization of cached authentication profiles in the Google Cloud Storage connector, and has been been resolved by removing cached tools objects, eliminating the RetryCounter usage, implementing null checks on authentication pages, and ensuring synchronized copies of authentication profiles are passed throughout the connector. In addition, the global authPage variable has been replaced with AuthenticationPageHolder for improved thread safety. | Data Integration |
| INC-C49446 | 966310 | SOAPAppender race condition resolved for node startup | Nodes and their events were not appearing in the Pega Diagnostic Center (PDC) across multiple environments, with only background nodes remaining visible in the event viewer. Investigation showed this was caused by a race condition between multiple threads (AlertThread, HealthThread, and BatchThread) during node startup that led to incomplete SOAP Appenders initialization, where the BatchThread would reset shared member variables to null while other threads were actively using them. This has been resolved by making the SOAPAppenderPega class thread-safe to prevent synchronization issues when multiple threads trigger appender initialization simultaneously. | Data Integration |
| INC-C49518 | 967620 | Auto-populate property logging added | Loggers have been added to identify which property is causing the error in order to assist with diagnosing issues where saving an auto-populated data page referenced in a property was throwing a null pointer exception with the error "Cannot invoke PropertyReferenceImpl.toString() because ref is null". | Data Integration |
| INC-C51112 | 963222 | Email validation rule enhanced to require domain names | The ValidEmailAddress rule was accepting email addresses without domain names (e.g., xxx@xxxx), which are not valid email formats for production use. This has been corrected by adding top level domain validation in the ValidEmailAddress edit validate rule. | Data Integration |
| INC-C51402 | 967706 | Corrected XML literal mapping runtime exceptions | Parse XML rules using "Literal XML" mapping mode were generating runtime exceptions regardless of assembler configuration settings. This was caused by conflicts between the new and old XML assembler implementations when processing literal XML content, and has been resolved by correcting the assembler selection logic. | Data Integration |
| INC-C51507 | 966180 | Resolved memory leak in report data retrieval | Applications were experiencing out-of-memory errors when generating reports through the pxRetrieveReportData activity. Investigation showed that orphaned PageMetaDataImpl instances were accumulating in memory due to improper cleanup of temporary report pages during Page-Rename operations, with the Page-Remove calls not properly targeting the temporary report pages as configured. This has been resolved by correcting the page cleanup logic in pxRetrieveReportData to ensure temporary pages are properly removed from memory after report generation. | Data Integration |
| INC-C52181 | 966223 | Filename truncation at comma resolved | File uploads were being truncated at comma characters, causing filenames like "abc,def,ghi.txt" to be stored as just "abc" without the file extension. Investigation showed this was caused by improper handling of special characters in the filename encoding process within the FileUploadHandler.java uploadFile() method. This has been resolved by updating the logic for the filename encoding. | Data Integration |
| INC-C53144 | 969916 | Database cache purge job improved | The pyPurgeAssemblyDatabaseCache job was failing consistently in production environments with a PEGA0099-197 exception. This was caused by query timeout and excessive cache table size, and has been resolved by optimizing the purge query to improve performance and reliability. | Data Integration |
| INC-C53572 | 965044 | Table instance synchronization fixed across cluster nodes | Database commit errors were occurring when new columns were added to FDQuestions and CRQuestions tables, with changes not reflecting properly across all cluster nodes despite successful rule imports. Investigation showed this was caused by incomplete column-to-property mapping updates when table schemas changed. This has been resolved by implementing automatic column-to-property map updates after each column change to ensure consistency across all nodes. | Data Integration |
| INC-C55701 INC-C55698 INC-C55559 INC-C49731 INC-C42223 |
964381 | ConcurrentModificationException resolved for clipboard | CDH inbound container requests were experiencing authentication failures and service interruptions. Investigation showed this was caused by a ConcurrentModificationException occurring when Redux-based clipboard pages were shared across multiple requestors. In the Redux implementation, each read operation created new properties if they were not available on the page. If any of these properties were referenced in Declare Expressions, the system attempted to add or remove declarative metadata, which led to a ConcurrentModificationException. This has been resolved with an update to prevent the creation of a Redux-based clipboard for shared or system (application) pages across multiple requestors. | Data Integration |
| INC-C55924 | 968780 | Advanced search functionality corrected for data transform sourced pages | Advanced search and select controls configured with data pages sourced from data transforms were failing to return search results. This has been resolved by correcting the data page caching mechanism to ensure that searchable data pages receive the same implicit parameter treatment as queryable data pages for pagination support. | Data Integration |
| INC-C56940 | 968704 | Handling updated for EForm generation with unmapped fields | PDF generation was failing when Map EForm rules had no properties or fields mapped, producing "cannot be null or blank" errors during post-processing activities. This has been resolved by adding validation checks and updating the handling for this scenario. | Data Integration |
| INC-C58064 INC-C59664 INC-C54777 |
966809 968856 970392 |
DSS added to support token refresh for non-RFC compliant identity providers | REST connector integrations were experiencing authentication failures when OAuth 2.0 access tokens expired. This was traced to the system not receiving the expected RFC-compliant invalid_token value/format (e.g., case/underscore/spacing differences), which caused the system to not detect the condition necessary to trigger the retry/token refresh flow. To resolve this, the DSS configuration option "allowTokenRefreshAndHttpRequestRetry" (Boolean) has been added which allows the REST connector to refresh tokens and retry requests on 401 errors regardless of WWW-Authenticate header content, providing backward compatibility for non-RFC compliant identity providers while maintaining the ability to prevent endless retries when needed. | Data Integration |
| INC-C7526 | 961170 | Null pointer exception handling improved | Regular null pointer exceptions were occurring in production environments during list action processing. This has been resolved by adding safe null checks in the pzDolistAction activity to handle null grid metadata pages and prevent exceptions during list action execution. | Data Integration |
| PRB-B72 | 972753 | Database operation logging accuracy improved for report execution | System alert PEGA00167 was incorrectly identifying database operations from report execution as originating from Query-Runner, causing confusion in system monitoring and troubleshooting. This was caused by incorrect source identification logic in the database operation logging mechanism when reports were executed to populate data pages, and has been resolved by updating the logic for distinguishing between report execution and query runner activities. | Data Integration |
Decision Management
25.1.2 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A23778 | 879832 | Dataflow performance improved for Cassandra datasets | After upgrade, dataflows combining RDMS and DDS datasets were experiencing significant slowness when Cassandra datasets were included, while RDMS-only dataflows maintained high bandwidth performance. This was traced to multiple lookup keys in DDS Data Set browse by keys operation being processed sequentially, not in parallel, and this has been addressed by refactoring the dataset handling in dataflow operations to optimize Cassandra performance. | Decision Management |
| INC-B51876 | 924718 | Accessibility improved for question help icon | Smart Info help icons configured for questions in question pages were not accessible via keyboard navigation. This has been resolved by implementing proper keyboard navigation support for Smart Info help icons to ensure visible focus indications and activation with the enter key. The icon has the semantic role of button and a programmatic label. | Decision Management |
| INC-C22331 | 955193 | Improved DSMClipboardPage self-diagnostics | An update has been made to enforce periodic self-diagnostics for DSMClipboardPage which will check whether the current indexed property access matches the correspondent non-indexed property access, and reports an error if there is mismatch. | Decision Management |
| INC-C31299 | 956422 | Strategy parsing performance optimized to eliminate redundant analysis | Globally Optimized Strategy (GOS) reports were timing out due to excessive processing times during strategy analysis. This was caused by the same strategy being analyzed multiple times when used in default criteria of proposition filters with large numbers of actions, and has been resolved by removing the second parsing pass when generation the GOS report, incorporating all the analysis into a single pass. | Decision Management |
| INC-C32564 INC-C50768 |
955304 961555 |
Data migration bucket assignment handling updated | Data migration processes were intermittently failing during the additional data export stages with the error "VBDException: api.core.service.cache.operations.BucketAssignedException: Bucket '5' is assigned but not yet active [operation='VBDBrowseOperation']". This was caused by timing issues in the Visual Business Director's bucket management system, and has been resolved by implementing Retry for broadcast release events, adding logging for bucket assignment events, and ensuring that missing assignment events are added when bucket is activated and that pulse message sending is delayed until subscription to the event stream is completed. | Decision Management |
| INC-C32691 | 959120 | Mobile browser case feed scrolling corrected | The pyCaseFeed section launched from pyCaseHeaderMobile action button was not scrollable in mobile browsers, preventing users from viewing overflow pulse messages. This has been resolved by updating the scroll handling CSS. | Decision Management |
| INC-C36371 | 957475 | Decision data invalidation mechanism corrected | Globally Optimized Strategy (GOS) containers were not reflecting updated decision data after changes were made to DDRC class rules. This was caused by GOS invalidation not occurring when decision data rules in the DDRC class were modified while related strategy rules existed in the DDRC-App class, and has been resolved by ensuring proper invalidation of affected GOSes when decision data, decision table, IH summary, and adaptive model rules are changed on parent classes. | Decision Management |
| INC-C38444 INC-C57391 |
956631 966776 |
Single action group end date enforcement restored | Actions within single-action groups were being offered to users even after their configured end dates had passed. This was traced to an incorrect optimization in the globally optimized strategies code which resulted in an action being always active if it had a begin date and an end date, was the only action in the group, and it was active at the moment of compilation. To resolve this, an update has been made to ensure the "Is Proposition Active" flag is correctly set to false when the proposition data reaches the end of its defined period. | Decision Management |
| INC-C39256 | 958410 | Handling added for GOS rule deserialization null pointer exceptions | Globally Optimized Strategy (GOS) processing was experiencing null pointer exceptions during rule deserialization and rule name extraction operations. This has been resolved by updating the null validation handling, replacing StringMap usage with RuleDescriptor for rule definitions, and ensuring inlined rules collections are never null even for failed revisions. | Decision Management |
| INC-C40466 | 963975 | Pulse gadget note persistence improved during refresh | Contact notes were disappearing from the Pulse gadget when users clicked refresh in the notes dialog during interaction wrap-up processes. This was caused by improper state management during the refresh operation in the notes dialog, and has been corrected. | Decision Management |
| INC-C41598 | 962940 | Handling updated for revision simulation empty segment failures | Revision simulations were failing and corrupting the revision case when configured with empty segment datasets.This was caused by the pyTriggerPerformanceTest activity completing assignments even after simulation failures, leaving error messages on the page without providing navigation options back to the pyViewRevision flow, and has been resolved by updating the handling for pyViewRevision so that if the simulation fails, the process remains in the viewRevision stage instead of progressing to simulateRevision. Validation has also been added to ensure the segment is verified before creating the simulation. | Decision Management |
| INC-C42626 | 964985 | Screen refresh performance improved after artifact generation | Operation management cases were experiencing significant slowness due to large numbers of DDR records and database queries exceeding 5 second thresholds, with screens not refreshing properly after artifact generation. Investigation showed this was caused by inefficient DDR queries and circumstance value handling across rule versions. This has been resolved by optimizing database query performance and implementing proper screen refresh mechanisms post-artifact generation. | Decision Management |
| INC-C43226 | 964639 | Support added for escaping double quotes in CSV dataset processing | CSV files containing escaped double quotes in the format "This is a ""Test"" data" were not being processed correctly when uploaded through data flows to data tables. This was traced to the parsing of escaped quote sequences in the CSV processing logic, and has been addressed with the addition of the DSS value "dnode/file/csv/enableEscapedQuotes". By default, the parser and serializer without support for escaped double quotes are used. If the DSS is set to true, the new parser and serializer with support for escaped quotes are used. The default will be set to 'true' in Pega Infinity '26. | Decision Management |
| INC-C43635 | 955267 | Group DDR section autogeneration corrected | Group-level decision data rules (DDR) sections were not being auto-generated for groups with spaces in their names, causing section rules to reference artifacts rules instead of proper group-specific sections. Investigation showed the pzSetAutoGenerateFlag Data Transform was incorrectly relying on the 'pzIsAutoGenerated' property instead of the 'pzIsAutoGeneratedForm' flag. This has been resolved by updating the data transform to use the correct property flag for auto-generation validation. | Decision Management |
| INC-C43714 | 955706 | DSS added to specify BigQuery connector quota limits | Applications were experiencing quota exceeded errors when using the BigQuery connector during data ingestion operations, with API calls hitting the tabledata.list limit of bytes per second per project. This has been addressed by implementing a MAX_PARTITIONS_COUNT DSS with the following default retry values: dnode/bigquery/max_attempts - 50 dnode/bigquery/initial_retry_delay_seconds - 1 dnode/bigquery/retry_delay_multiplier - 2.0 dnode/bigquery/max_retry_delay_seconds - 30 dnode/bigquery/total_timeout_seconds - 900 |
Decision Management |
| INC-C45466 INC-C45205 |
956975 957534 |
Pulse message timestamp display corrected for ReplyDetailsHeader | Pulse messages posted in previous days were displaying incorrect date-time values in the pyReplyDetailsHeader, where the minutes portion was showing as months in the custom date format. This was caused by improper date formatting logic in the pulse message display component, and has been resolved by correcting the "Custom date-time format" field from "MMM dd, yyyy h:MM a" to "MMM dd, yyyy h:mm a" to display minutes correctly. | Decision Management |
| INC-C45511 | 961111 | Adaptive decision management commit log reads stabilized | Applications were experiencing continuous large amounts of responses being triggered to the ADM commit log when processing records with processing lag. Investigation showed this was caused by the system attempting to read from Cassandra commit log records that had already been deleted due to TTL expiration, resulting in tombstone reads that destabilized the commit log processing. This has been resolved by implementing logic to prevent reading from old partitions containing only TTL'ed records and making commit log reads more stable by avoiding tombstone reads entirely. | Decision Management |
| INC-C45993 INC-C55321 |
960779 965968 |
Corrected GOS authentication during campaign execution | After update, outbound campaigns were failing with authentication errors during Globally Optimized Strategy (GOS) compilation, specifically when processing behavioral limits strategies. Investigation showed this was caused by GOS local compilation not properly switching to access group-only compilation for non-developer operators who are not allowed to check out rules, resulting in authentication failures when the system attempted to authenticate batch users with developer access groups. This has been resolved by implementing proper context switching during GOS local compilation that uses access group-only compilation for operators so changes in the operator and their private rules does not affect compilation for the access group-only context. | Decision Management |
| INC-C47266 INC-C53731 |
960474 | BigQuery data flow processing improved | BigQuery data jobs were intermittently getting stuck in "In Progress" status without processing any records, and attempts to stop these data flows were taking up to 10-12 hours to transition to "Stopped" status. Investigation showed this was caused by the system continuously attempting to recreate temporary tables even when they already existed, which exceeded BigQuery's rate limits for table update operations. This has been resolved by reducing the number of table.insert requests and fixing data flow handling in case of job failure. | Decision Management |
| INC-C49055 INC-C56266 |
960633 966371 |
Datetime formatting corrected in dataflow exports | After update, datetime columns were being exported via dataflows with 'GMT' appended to the values in output files, causing downstream import jobs to fail. Investigation showed this was caused by the convert step in dataflows modifying the pxObjClass property, preventing the system from properly identifying the property type and causing it to default to Pega's internal datetime format. This has been resolved by enhancing datetime properties parsing in CSV file datasets, and a related issue where duplicate double quotes were being created in exported files has also been resolved with this change. | Decision Management |
| INC-C50138 | 961426 | Real-time data grid proxy configuration updated | Actions were failing to load and sessions were hanging when proxy JVM settings were configured, particularly affecting development and test environments. This was caused by real-time data grid (RTDG) communications incorrectly using JVM proxy settings, and has been resolved with an update to use DefaultHttpRoutePlanner instead of ProxySelectorRoutePlanner. The DefaultHttpRoutePlanner will not make use of any Java system properties, nor of system or browser proxy settings. | Decision Management |
| INC-C51087 INC-D2112 |
962087 972434 |
Corrected missing Kafka response properties | After upgrade, applications were had missing pxStreamPartition and pxStreamPosition properties in Kafka responses. This was traced to incomplete property mapping in the Kafka dataset response by the DSMClipboardPage function, and has been resolved by updating the handling to not use DSMClipboardPage in DataSets. | Decision Management |
| INC-C51773 | 961371 | Handling added for Cassandra exceptions on platform-only deployments | Platform deployments without CDH services were experiencing CassandraConnectionManagerException errors when attempting to connect to non-existent Cassandra clusters for interaction summary datasets. This has been resolved by implementing proper service availability checks and providing configuration options under pzIsCassandraAvailable to disable Cassandra-dependent features when CDH services are not present. | Decision Management |
| INC-C51825 | 967048 | Data flow service level configuration updated | Agent queues were experiencing failures when attempting to process data flows that were no longer available in the system. Investigation showed that the pxRunDDF and pxRunRTDataFlow flows were incorrectly configured to use service level settings, causing orphaned assignment instances to remain after data flow deletion and resulting in SLA agents attempting to reference deleted data flows. This has been corrected by removing the default SLA configuration from data flow run process flows. | Decision Management |
| INC-C52553 | 966163 | Predictors tab loading improved in Prediction Studio | The Predictors tab in some Prediction Studio models was not loading information, particularly affecting email and push models in the Monitor tab. Investigation showed that large amounts of data were causing loading failures in the predictors display. This has been resolved by adding modelId as a filter for optimized query reads to improve performance. | Decision Management |
| INC-C53234 | 963622 | Erroneous GenAI agent email error messages corrected | The GenAI agent was intermittently displaying failure messages to users when sending emails through the pySendEmailWithAttachments tool, even though emails were successfully sent in the background. This was caused by missing handling for an empty response parameter in the automation response processing, and has been resolved by adding the Response Parameter to pzSendEmailWithAttachmentsWrapper and Automation: pxSendEmailWithAttachment. | Decision Management |
| INC-C54551 | 965982 | Data flow batch mode processing corrected | Data flows were failing with "Cannot do this in batch mode error" during partition state updates, causing runtime exceptions and stuck data flow runs. Investigation showed the batch operations process did not reset the thread properly from batch mode to regular mode. This has been resolved by modifying the conditions in updatePartitionStates and ensuring batch mode is temporarily disabled during partition state commits and properly restored afterward. | Decision Management |
| INC-C56419 | 967016 | Dataflow initialization timeout handling improved | Multiple dataflows were failing to start when COUNT(*) queries against large datasets were timing out after 90 seconds, causing I/O errors and preventing dataflow initialization. This was caused by the system requiring successful completion of record count operations before allowing dataflow runs to proceed, and has been resolved by allowing dataflow runs to initialize even when the getNumberOfRecordsOperation fails, with warnings added to the dataflow run and exception details logged for troubleshooting purposes. | Decision Management |
| INC-C56533 | 971026 | Property chain access restored for platform pages in SSA mode | Strategy components were unable to retrieve property values from platform pages when using reference chains like Request.Payload.Customer.Subscriptions in SSA/GOS execution mode, causing an issue where an empty page list might be returned when the pages were actually present. This was traced to the nested property resolution handling for chained property access in the SSA execution environment, and has been corrected. | Decision Management |
| INC-C56713 | 969070 | ADM data migration status reporting corrected | Data migration export processes were incorrectly marking ADM (Adaptive Model) stages as failed despite successful completion. This occurred when repository persistence was enabled for Adaptive models, and was caused by incorrect status evaluation logic in the ADM migration factory component. This has been resolved. | Decision Management |
| INC-C56916 | 965846 | Decision table evaluation accuracy improved | Decision tables were producing incorrect results when evaluating When rules, particularly with isInPageListWhen and @CallWhen functions on Customer pages, and when using additional allowed results mapping. This was caused by named pages not being properly published to clipboard during platform rule execution in strategy and proposition filter contexts, and has been resolved by ensuring named pages are published to clipboard when non-strategy or non-proposition correspondent platform rules are executed. | Decision Management |
| INC-C57075 | 967571 | Kafka dataset class loading issues resolved | Dataflows utilizing Kafka datasets with AVRO data format were failing sporadically with NoClassDefFound errors. This was traced to the data flow overwrite functionality which allows source or destination shapes to be 'overwritten' by a different dataset / data flow implementation. In the process of using the rule class loader and the assembly of the data flow object, the Avro class is referenced. This leads to the failure as the rule class loader does not allow loading these classes in this context. To address this, a fallback class loader has been introduced in the context of data flows using overwrites. | Decision Management |
| INC-C57753 INC-C58277 |
966711 967392 |
Prediction model arithmetic exception resolved | Prediction Studio was experiencing failures when attempting to open prediction models that contained performance metrics with decimal values other than .00 (such as 92.56 or 72.02), generating a java.lang.ArithmeticException during the weighted average calculation of performance numbers. This was traced to an improper rounding mode configuration during the mathematical operations, and has been corrected. | Decision Management |
| INC-C58010 INC-C53850 INC-D1040 |
968116 968355 970992 |
Prediction model learning issue resolved | After update, prediction models were not learning properly and response timeout configurations were not functioning as expected. Investigation showed this was caused by the event-based response timeout mechanism not triggering independently for each prediction configured within the same decision flow, and unwanted information being persisted on the pxDR object during delayed learning processes. This has been resolved. | Decision Management |
| INC-D1273 | 971540 | Handling added for non-time-based UUIDs in ADM commit log processing | Predictive Decision Composer was experiencing UnsupportedOperationException errors during model updates when processing non-time-based UUIDs in the commit log system. This was caused by the TimeUUIDUtils attempting to extract timestamps from standard UUIDs rather than time-based UUIDs, and has been resolved by implementing proper UUID type detection and handling for non-time-based UUIDs. | Decision Management |
Low-Code Application Development
25.1.2 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C36061 | 958922 | Node data page preference loading access errors fixed | After update, access denied errors were generated for D_PZCACHEDPREFERENCE during portal launch and page load operations. This was caused by missing role context resolution for developer preferences, and has been resolved by updating the preference loading mechanism to properly resolve role contexts and access permissions for cached preference data pages. |
Low-Code App Development |
| INC-C41441 | 953242 | Empty values removed from Operator profile | Operator profiles were accepting and persisting empty skill entries, allowing invalid configuration data to be saved. To resolve this, empty skills will be removed from the operator page during validation. | Low-Code App Development |
| INC-C42580 | 955079 | Decision table header rendering updated | Decision table headers were not rendering correctly when using specific function combinations in property headers. The issue manifested when switching between different function expressions like @startsWith with @substring versus @whatComesAfterFirst. Investigation showed this was caused by improper parsing of nested function expressions in the decision table header rendering logic, and has been resolved by modifying the function used in the decision table to ensure proper rendering. | Low-Code App Development |
| INC-C44532 | 956969 | Division name validation handling updated | Application creation was failing with ruleset validation errors when division names contained spaces while using the generate division layer option. This was caused by inconsistent space handling between different validation activities, where one removed spaces while another retained them. This has been resolved by standardizing the space handling logic across all division name validation processes. | Low-Code App Development |
| INC-C45874 | 957282 | Multiple branch development ruleset save improved | While attempting to create multiple branches consecutively through the branch development preferences window, an error occurred after creating the second branch when trying to create the third. This was traced to application rules being saved to incorrect branch rulesets during the multi-branch creation process, leading to ruleset selection conflicts. To address this, pzAddBranchToApplication has been updated to use the standard Rule-!Save function and not call pxUpdateRecord. | Low-Code App Development |
| INC-C50733 | 959369 | Date formatting error resolved | Email listener threads were encountering ParseException errors and remaining in running state, preventing processing of unread emails from the inbox. This was traced to incorrect date pattern formatting for elapsed time in the pyDeprecationDate processing within the GenAI Connect Rule, and has been corrected. | Low-Code App Development |
| INC-C52261 | 966732 | Admin Studio requestor management error corrected | Users were encountering "Node id cannot be blank" runtime exceptions when accessing RequestorManagement and other functionality within Admin Studio. This was caused by the pzIsProfilingStarted activity expecting NodeID and RequestorID as required parameters that were not being passed from the pzRequestorDetailsGrid section, and has been resolved. | Low-Code App Development |
| INC-C53140 | 965780 | Branch preferences auto-disable implemented | Applications were experiencing broken processes when merged branches were removed from the application stack while branch preferences remained enabled, causing "Branch development preferences are in an invalid state" errors during data record operations. This was caused by branch preferences not being automatically disabled when branches were removed from application definitions. This has been resolved by turning off branch preferences when branches are removed from the application stack. | Low-Code App Development |
| INC-C53874 | 965859 | Corrected configuration settings access in system runtime context | Configuration settings were not returning valid values when accessed from System Runtime Context, particularly in job schedulers and queue processors. This was caused by improper context handling when accessing configuration settings from system-level processes, and has been corrected by updating ConfigurationHelper.java. |
Low-Code App Development |
| INC-C55128 | 965126 | Workspace creation enabled for numeric-prefixed operator IDs | Operators with IDs starting with numbers received "Workspace ID cannot start with a number" errors when attempting to enable workspaces. This was caused by the pzGetUniqueWorkspaceID function creating invalid branch IDs that failed downstream validation, and has been resolved by prepending a "W" prefix to workspace IDs for numeric-starting operator IDs, ensuring proper validation compliance. | Low-Code App Development |
| INC-C55854 | 967377 | Excel decimal value parsing precision corrected | Excel file parsing was altering decimal values by adding extra zeros, with values like 0.00001 becoming 0.000010 in the clipboard. This was caused by the internal clipboard API treating decimal values as doubles and converting them to BigDecimal during the parsing process, which added trailing zeros. This has been resolved by implementing proper decimal handling in the ExcelUtils.java parsing process to preserve original precision. | Low-Code App Development |
| INC-D1150 | 971588 | Cross-site scripting updated in App Studio | Cross-site scripting (XSS) protections have been updated for App Studio. | Low-Code App Development |
Mobile
25.1.2 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C25264 | 935514 | File selection dialog focus management improved | When touchscreen functionality was enabled, opening file selection dialogs incorrectly placed the initial focus on the close 'x' button instead of the primary "Select Files" action. This was caused by inconsistent modal focus management logic implemented in a previous fix that changed behavior based on input method detection. This has been resolved with the addition of the DSS setting "ModalDialogXIconFocus" to control the behavior, and will set the focus to the close icon when is set to true. | Mobile |
| INC-C42855 | 955892 | Mobile modal button alignment fixed | Modal dialog buttons were incorrectly aligned on mobile devices, with both Submit and Cancel buttons appearing on the left side instead of Submit on the right and Cancel on the left. This has been resolved by adding the necessary CSS code to align pyModalButtons properly on mobile devices. | Mobile |
| INC-C53708 | 971404 | Back button visible for notification-launched cases | The back button was not appearing on some mobile headers when cases were launched through push notifications. This was traced to an uncaught exception which prevented the web views from loading after a notification was clicked in certain scenarios, such as users being logged out during notification receipt. As a result, the mobile header navigation was not properly initialized and there were no previous navigation items were available to return to. This has been resolved. | Mobile |
Project Delivery
25.1.2 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C42022 | 955116 | Keystore URL documentation updated | The documentation for Configuring a keystore by using a URL reference has been updated to clarify that when a keystore is created by using a URL reference and the JSON Web Key keystore type, Pega Platform fetches the JSON web key set (JWKS) at runtime, and processes it depending on the content of the JWKS. | Project Delivery |
| INC-C44913 | 959812 | Documentation updated for field validation behavior with conditional logic | The documentation for Common issues in Constellation has been updated to provide information about using When conditions to disable editable fields such as dropdowns. Given a field, such as “prop1,” which is editable but also has a “disable” attribute set based on a When condition, the field is not immediately disabled. Please refer to the section "Errors when disabling editable fields with a When Condition Rule" for guidance on using custom conditions as a workaround, which validate at runtime and immediately update field states on tabout or on blur events. | Project Delivery |
| INC-C45477 | 957398 | Documentation updated to clarify branch behavior changes in Application Development | The documentation for Rule resolution with Branch development preferences has been updated to clarify two key changes from previous behavior: application rulesets no longer require locking to use branch development preferences, and the ability to move rules from higher branches to lower branches has been removed. | Project Delivery |
| INC-C46918 | 962194 | Property form documentation updated | docThe documentation for Property form - Completing the Advanced tab has been updated to clarify that if the max length field is left blank, the system will not limit the length of property values but other operational constraints and system performance considerations might apply. | Project Delivery |
| INC-C47145 | 961913 | File listener documentation corrected for failed processing behavior | The documentation in Integration Types for using file listeners in has been updated to reflect the current system behavior of failed files being moved to the Completed directory when recovery is disabled, not the Work directory that was previously used. | Project Delivery |
| INC-C56022 | 968395 | Documentation updated for embedded property references in policy conditions | The documentation for Creating an access control policy condition has been updated to clarify that embedded properties are not currently supported in Access Control Policy conditions. Attempting to save the condition with an embedded property in the Column source field will generate a "Property case mismatched" error. | Project Delivery |
Reporting
25.1.2 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C21667 | 959307 | BIX manifest count accuracy improved for nested structures | BIX extract manifest files were showing confusing and intermittently inconsistent values in pxTotalInsertsCount and pxTotalInstanceCount properties, with insert counts sometimes unexpectedly exceeding instance counts. Investigation showed this was caused by incorrect counting logic in the manifest generation process for chunked extracts with nested structures, and has been resolved by correcting the pxTotalInstanceCount manifest count calculation to accurately reflect the actual processed records when the extract includes a structure that has pagelist inside a pagelist. | Reporting |
| INC-C30200 | 945927 | Scheduled insights evaluate date filters correctly at runtime | Scheduled insight exports were producing identical data sets across multiple runs when relative date filters such as "Current day" were applied. Investigation showed this was caused by the system transforming relative dates into static values at the time of schedule creation rather than dynamically at each execution. This has been resolved by replacing the transformation of relative dates during the scheduling process with a new activity that dynamically converts relative date filters to appropriate static date literals using the current server datetime at the time of each scheduled export execution. | Reporting |
| INC-C34148 | 962671 | Cambria Math font rendering updated | PDF documents containing both Chinese and English characters were not properly displaying Cambria Math font content, resulting in missing or corrupted mathematical symbols and text. This was caused by ligature processing limitations in the PD4ML 4.0.19 library when handling complex font rendering, and has been addressed by introducing an enableLigatures parameter in the "pyPDFSettings" data transform that can be utilized to ensure proper Cambria Math font rendering in mixed-language documents. | Reporting |
| INC-C36386 | 955703 | Batch processor queue validation improved | Data was being pushed to the pySASBatchIndexClassesProcessor queue even when automatic updates were disabled. This was caused by DSS validation checks being applied at the processing end rather than when data was initially queued, and has been resolved by modifying the ModelChangeDispatcher to validate the automatic updates setting before queuing data. | Reporting |
| INC-C36852 | 954455 | Report definition class hierarchy handling updated for use with Access Control Policies | Report definitions were failing with pxObjclass exceptions when Access Control Policies (ACP) were defined on parent data classes in complex inheritance hierarchies. The issue occurred specifically when data classes served as parents to abstract platform classes that contained report definition subclasses, and was caused by improper class resolution when ACPs were present in the inheritance chain. This has been resolved by adding handling to prevent .pxObjClass exceptions in the subclass report definition when an ACP exists on the top Data-class. | Reporting |
| INC-C38967 | 958665 | Handling updated for Azure BIX extract nested stream closures | BIX extract operations in CSV file mode were generating "Stream is already closed" errors in logs when run multiple times. This was caused by the Azure repository implementation closing the underlying fileOutputStream when the zipOutputStream was closed. To resolve this, the stream management logic has been updated to skip connection closure for an Azure repository as it’s handled by the zip output stream. | Reporting |
| INC-C40950 | 963530 | PDF generation timeout handling updated | PDF generation processes were not terminating properly when exceeding configured timeout limits, with pd4ml processes continuing beyond the 1-minute timer threshold. This was caused by the timer starting after preprocessing rather than before, excluding preprocessing time from timeout calculations. This has been resolved by starting the timer before preprocessing to include all PDF generation time in timeout enforcement. | Reporting |
| INC-C41991 | 955908 | Lucene syntax support added for search | Lucene syntax search queries were failing due to conflicts with property level security mechanisms when property encryption was enabled. This has been resolved with an update to conditionally apply Lucene syntax with the pyLabel property for higher search scores only when the Data System Setting (DSS) EnableAttributeBasedSecurity is set to false. | Reporting |
| INC-C45896 | 960616 | Excel export consistency stabilized on Constellation for localized list | After creating a landing page in Constellation with a data page as the data source, configuring promote filters, and localizing column headers using field values, the Excel export functionality was producing inconsistent results when performed multiple times on the same list, with variations occurring in column order, column content, column name translations, and promote filter application. Investigation showed this was caused by the pyPageName not being properly maintained during the export process, and this has been resolved by copying the old pyPageName in the pzGetFiltersFromContent activity to ensure stable and consistent Excel export results. | Reporting |
| INC-C46150 INC-C43821 |
957461 959942 |
Chart drill-down functionality restored for date dimensions | Column chart drill-down operations were failing with HTTP 500 errors when date fields were used as chart dimensions. This was traced to the system incorrectly converting date values to epoch timestamps in the filter criteria during drill-down operations, and has been corrected. | Reporting |
| INC-C47259 | 965570 | Report definition grouping syntax error corrected | Constellation views with report definitions using "Include all descendant classes" were throwing SQL syntax errors when grouping by case type columns, displaying "syntax error at or near comma". This was caused by incorrect comma placement in generated SQL queries when multiple aggregate fields were present, and has been corrected. | Reporting |
| INC-C50853 | 960277 | Report browser horizontal scrolling restored | Horizontal scroll bars were missing in the Report browser. This has been resolved by updating the pyReportEditorStyling CSS. | Reporting |
| INC-C50968 | 960307 | commons-csv library updated | CSV file attachments were failing to index with NoSuchMethodError exceptions, preventing content-based search functionality. This has been resolved by upgrading the commons-csv library. | Reporting |
| INC-C51543 | 961598 | Search functionality smart tip interaction resolved | Search functionality was malfunctioning when smart tips were enabled on search icons, preventing the search window popup from appearing during runtime. This was caused by conflicting interactions between smart tip overlays and search popup functionality, and has been resolved by removing the smart tip. | Reporting |
| INC-C51714 | 962406 | Work ID search functionality improved in Dev Studio | Work ID searches in Dev Studio were failing for certain formats like CC-C1903 because they did not match the hardcoded regex expression. Investigation showed that the regex pattern was not flexible enough to accommodate different customer work ID formats. To address this, the activity has been enhanced to read regex expressions from DSS to allow for customization. DSS : "Pega-SearchEngine", "indexing/workIdRegex" If no DSS provided, default "[a-zA-Z0-9-]+-[0-9]+" regex will be considered |
Reporting |
| INC-C51966 | 962722 | Improved backwards compatibility for report definition datapage filters | Report definitions with filter conditions configured as datapages were not displaying the filter conditions in the interface after upgrading from on-premises Pega Platform 8.6 to Pega Cloud 24.2, though reports continued to produce correct results. This was traced to intermediate changes made to the handling in pzResolveCopyFilters for DateTime timestamp values, and has been resolved with an update to the filter resolution logic to manage backwards compatibility for diaplying datapage-based filter conditions. | Reporting |
| INC-C53463 INC-C60008 |
967648 970771 |
Aggregate function validation updated | After upgrade, reports and insights were failing with the error "You need to specify a property with the aggregate function: 'COUNTWITHNULL'" when attempting to execute report definitions or explore data functionality. Investigation showed this was caused by overly restrictive validation logic that incorrectly required a property specification for the COUNTWITHNULL aggregate function. To resolve this, the logic has been modified to allow COUNTWITHNULL aggregation without requiring any property specification. | Reporting |
| INC-C53493 | 962969 | BIX DDL generation permissions issue resolved | After update, BIX extract rules with Database Schema output format were failing during DDL generation with "Invalid output directory OR user doesn't have required permissions" errors. This was caused by incorrect S3 bucket validation during the DDL generation process, and has been resolved by bypassing S3 bucket validation during BIX database extraction operations. | Reporting |
| INC-C55301 | 965171 | Report format popup functionality restored | The Edit Report format option magnifying pop-up was not opening as expected. This was traced to a missing security validation in the popup invocation code, and has been corrected. | Reporting |
| INC-C57912 | 968111 | API errors resolved in experimental CWYD experience | The experimental Chat with Your Data (CWYD) experience was generating API errors when the EnableGenAIChatWidgetInExploreData feature toggle was enabled. Investigation showed that the pyGetExploreDataAIResponse activity was overriding the model configuration and always defaulting to the pega-default-fast model. As a result, updates made in the pySuggestAIInsight GenAI Connect rule were not being applied. This has been resolved by updating the pySuggestAIInsight connect rule to read the model properly and configuring it to use the pega-default-smart model. | Reporting |
| INC-C58002 | 966800 | Extract rule table name character limit corrected | Extract rules were preventing saves when table names reached exactly 30 characters, despite error messages indicating the limit should be 30 characters. This was caused by using a greater-than-or-equal-to comparison (>=30) instead of a greater-than comparison (>30) in the validation logic, and has been corrected to allow table names up to 30 characters in BIX database schema generation. | Reporting |
| INC-C58702 | 969716 | PDF export filename handling updated for special characters | PDF exports were displaying HTML entity codes in filenames when report names contained special characters such as parentheses, while Excel exports handled the same characters correctly. This was caused by improper HTML entity encoding during the PDF filename generation process, and has been resolved by modifying the handling for retrieving the report title for the PDF file name. | Reporting |
| INC-C58957 | 969485 | Report sorting functionality corrected for top-ranked records | Reports were displaying incomplete results when sorting columns containing non-unique values while using the "top ranked" feature, causing records to disappear from the display unexpectedly. Investigation showed this was caused by changes made to the handling of sort parameters as part of disabling pagination, and has been resolved by adding an "if" condition in the pzGridSortPaginate activity to properly manage sort order and type parameters when pagination is not enabled. | Reporting |
| INC-C59538 | 972777 | Filter interaction issues resolved | Dashboard filter interactions were experiencing an unexpected focus jump to the first element when entering values in promoted filters, and date range selections were clearing previously entered from dates when users selected to dates without first clicking outside the from date field. This has been resolved by updating the focus behavior and date selection logic in the Constellation UI filter components to ensure proper field retention and user interaction flow. | Reporting |
Security
25.1.2 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C29028 INC-C59122 |
945850 968792 |
Password security policy enforcement standardized across authentication methods | In some circumstances, inconsistent security controls were seen for SSO-authenticated administrators. This has been resolved by updating the password policy validation logic to consistently enforce security policies regardless of the administrator's authentication method. | Security |
| INC-C29398 INC-D1687 |
942411 971651 |
Corrected handling for TimeOfDay values in Redux-based data pages | TimeOfDay property values were being incorrectly modified when retrieved directly from Redux-based read-only data pages with report definitions as sources. This was traced to Java's binary floating-point representation (IEEE 754) returning incorrect precision values during arithmetic operations on double values in the format conversion APIs used by Redux clipboard implementation, causing 1 second to be lost during conversion. This has been resolved by updating the logic to use BigDecimal for accuracy. In addition, an issue with millisecond to date conversion has been corrected. | Security |
| INC-C35485 | 952159 | Mitigation available for Notes protocol links blocked in Rich Text Editor | After upgrade, Rich Text Editor was not processing notes:// protocol links. This is due to the implementation of DOMPurifier, which restricts certain custom protocols, specifically the 'notes://' links due to security concerns. In order to support backwards compatibility, an update has been made which will support adding specific code in the UserWorkForm to permit the desired tags. This a mitigation mechanism for backward compatibility issues that might have been introduced by limiting tags. However, reintroducing the blocked tags carries the risk of creating security vulnerabilities for XSS and HTML injections. Please refer to the documentation for Security in Rich Text Editor for additional information. | Security |
| INC-C36518 | 955862 | OIDC authentication flow corrected for multiple JWT authorization servers | OIDC authentication was failing with "Unable to execute OIDC flow: Caught exception while parsing the id token" errors when environments were using multiple OIDC authorization servers with JWT-based client authentication. This was traced to the handling for TokenProfileCacheImpl.java which incorrectly merged JWT profile details from different authorization servers when alternating between OIDC flows, resulting in invalid client assertions being sent with incorrect issuer claims. This has been corrected to ensure each OIDC flow maintains its proper JWT profile isolation. | Security |
| INC-C3699 | 962192 | CSRF token validation handling improved | Production environments were experiencing numerous CSRF alerts with blocked requests due to token mismatches even when client and server tokens appeared identical during inspection. This was caused by timing issues in CSRF token validation logic that created false positive security blocks, and has been resolved by improving the token validation process to handle edge cases and reduce false positive alerts. | Security |
| INC-C37512 | 957237 | Rule history access with security headers enabled | Rule history snapshots were not opening properly when the Cross-Origin-Opener-Policy (COOP) same-origin header was configured for security purposes. This was caused by the COOP header preventing the proper opening of modal windows containing rule history information, and has been resolved by updating the rule history display mechanism to work correctly with security headers while maintaining the required security posture. | Security |
| INC-C38031 | 958255 | Decision Tree rule execution CSRF validation corrected | Decision Tree rules were returning HTTP 403 errors with SECU0008/SECU0017 when attempting to run them from Dev Studio with CSRF settings enabled. This has been resolved by updating the Decision Tree rule execution flow to properly handle CSRF token validation. | Security |
| INC-C39326 | 955502 | History added for operators automatically disabled by security policies | When the Operator disablement policy was enabled with the "Number of days of inactivity," the DisableDormantOperators Agent would run at the appropriate time and invoke the pzDisableDormantOperators activity without any audit trail or history records being maintained. This was caused by the DisableDormantOperators agent's pzDisableDormantOperators activity lacking logic to update operator history records, and has been resolved by adding history tracking functionality to the operator disablement process. | Security |
| INC-C39718 | 963101 | Operator profile security updated | Cross-site scripting protections have been updated for operator name fields. | Security |
| INC-C43863 INC-C55680 |
961941 | Identity Federation authentication refresh handling updated | Email listeners were experiencing authentication failures when using the newly developed Identity Federation feature with Azure Key Vault integration for external secret storage. The authentication profile would successfully retrieve client credentials from Azure Key Vault during initial startup, but subsequent access token renewal attempts were failing with 401 errors when the JWT tokens expired, causing email listeners to lose connectivity to Microsoft Graph services. Investigation showed this was caused by the system not properly handling batch and application requestors during token refresh operations for Identity Federation configurations. This has been resolved, and the issuer URL validation has also been updated to support configurations where the public link URL does not end with "prweb". | Security |
| INC-C46073 | 958202 | Handling updated for proxy authentication password decryption | Email accounts configured to connect to Microsoft Graph API through corporate proxies requiring basic authentication were failing with "407 Proxy Authentication Required" errors. Investigation showed this was caused by the system sending encrypted password values directly to the proxy instead of decrypting them first, resulting in authentication failures. This has been resolved by ensuring proper password decryption occurs before sending credentials to proxy servers during OAuth 2.0 authentication flows. | Security |
| INC-C46138 INC-C52309 |
961416 961419 |
CSRF validation security enhanced for DX APIs | CSRF validation checks have been updated for hybrid apps DX APIs. | Security |
| INC-C46596 | 958259 | Security updated for DisplayAuthScreenSelector | Cross-site scripting protections have been updated for DisplayAuthScreenSelector. | Security |
| INC-C47105 | 957067 | Date time difference calculation note | The @DateTimeDifference function expects the date input to be in a GMT format (YYYYMMDDTHHMMSS.mmm TZ) and might return incorrect results if the datetime property is used to provide input for this function instead of String property(GMT). This is due to the input values being parsed to the server timezone in milliseconds, and that difference in milliseconds is returned as an output of the function without considering decimal value. It is also recommended to use GMT variants for the timezone (TZ) value as functions comparing dates may interpret the Date string as GMT leading to incorrect results at run-time. For example, represent Hong Kong Time (HKT) as GMT+08:00. A simple date string (yyyyMMdd) does not provide a timezone. | Security |
| INC-C47134 | 962489 | Mashup page security updated | Cross-site scripting protections have been updated for the pzLoadMashupPage activity. | Security |
| INC-C47786 | 960138 | SAML authentication context database transaction handling improved | Applications were experiencing slow database performance and idle transactions remaining open for extended periods when processing SAML authentication requests, with some transactions staying idle for over 20 minutes on the pr_data_saml_authreqcontext and pr_data_saml_logininfo tables. Investigation showed this was caused by concurrent thread access in the SAMLRequestHandler attempting to save the same authentication context record simultaneously, leading to database contention and connection pool issues. This has been resolved by updating the thread synchronization and transaction management in the SAML authentication context handling logic to prevent concurrent database operations on the same record. | Security |
| INC-C50018 | 962227 | OAuth token refresh timing updated | OAuth token refresh timing optimized. REST connector applications making continuous API calls were intermittently receiving 401 authentication errors from external systems due to expired access tokens being sent in requests. This was caused by insufficient buffer time in the default token refresh timing configuration. This has been resolved by increasing the default value for the security/token/refreshEarlyBefore DSS to provide adequate refresh buffer time. | Security |
| INC-C52805 | 962620 | SAML SSO session timeout corrected | This was caused by incorrect JWT token expiry handling when the "Set refresh token expiry from IDP session expiry" option was enabled in OAuth2 client registration. This has been resolved by correcting the token lifetime calculation to respect configured session timeout values along with setting a default minimum refresh token lifetime of 3600 seconds (1 hour) when using IDP session expiry and improving SAML assertion processing to use the more appropriate SessionNotOnOrAfter timestamp. | Security |
| INC-C53847 | 962936 | Enhanced logging for OAuth2 access token errors | Enhanced logging for blacklisted access token errors. Applications were receiving generic "AccessToken is Blacklisted" 401 errors without sufficient context for troubleshooting, particularly during production incidents with large error spikes. Investigation showed that the error logging lacked key identifiers needed for effective debugging. This has been resolved by enhancing the logging to include operator ID, jti value, and psyncID in error mode, and the full access token in debug mode. | Security |
| INC-C53879 | 964172 | Security updated for timeout activity | An update has been made to improve security related to pyTimeoutActivity in URLs. | Security |
| INC-C54303 | 964591 | Password grant type authentication restored after upgrade | After update, REST connectors configured with Authentication Profile using Password GrantType were failing with NullPointerException while Client Credentials grant type continued working normally. Investigation showed this was caused by a null tokenPage reference during access token retrieval in the OAuth2 implementation. This has been resolved by fixing the token page handling logic to properly manage password grant type authentication flows. | Security |
| INC-C54382 | 964317 | Access group timeout logout behavior fixed | After access group timeout occurred, users attempting to log off were being redirected to a success landing page instead of the login screen. This was caused by incorrect evaluation in the logoff activity step 5, which was returning true instead of false in post-timeout scenarios, and has been corrected. | Security |
| INC-C54667 | 970346 | Operator validation exception handling improved | The system was throwing null pointer exceptions during operator ID validation when processing PreDispute case creation flows, specifically when attempting to validate operator records with non-existent access groups. This has been resolved with the addition of a null check and updated error handling in the operator validation workflow to ensure cpAccessGroup is not null before accessing its properties. | Security |
| INC-C54725 | 964488 | Session handling and authentication security updated | Authentication sessions were experiencing synchronization issues and potential security vulnerabilities related to SSO handler management and operator integrity validation. This has been resolved by updating the synchronization mechanisms and introducing operator integrity validation to verify operator ID authenticity post-authentication. | Security |
| INC-C55147 | 967598 | Authentication error message display corrected | Authentication error screens were displaying rule names instead of proper error messages when expired requestor errors occurred, showing the message "key pyAuthenticationErrorForExpiredRequestor cannot be resolved in the html pyDisplayAuthErrorScreen" instead of user-friendly error text. This was caused by the pyDisplayAuthErrorScreen rule referencing an incorrect message key. To resolve this, the new message rule pyAuthenticationErrorForExpiredRequestor has been added to handle authentication failures when a requestor session expires due to inactivity. The message informs users that their session has expired and instructs them to close the popup and start again. | Security |
| INC-C56202 | 968668 | Cosmos theme delegation and attachment loading issues corrected | After update, applications using the Cosmos theme were experiencing loading loops and stuck screens when accessing case attachments and rule delegation functionality. This was caused by a redirected encrypted action attribute in mMappeddata that interfered with proper screen rendering, and has been resolved. | Security |
| INC-C57070 | 967146 | Cross-site scripting protections updated for tracer settings | Cross-site scripting protections have been updated for the TraceOptionsDialog stream. | Security |
| INC-C57934 | 966819 | Bouncy Castle jar updated for improved memory performance | Outbound campaigns were running significantly slower than normal. This was traced to memory issues in the Bouncy Castle FIPS library version 2.1.1, and the jar has been upgraded to resolve this issue. | Security |
| INC-C59087 | 968775 | Prediction Studio security updated | Cross-site scripting protections have been updated for Prediction Studio. | Security |
System Administration
25.1.2 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B19295 | 965887 | Access role description corrected for clarity | Viewing the PegaRULES:TestID access role description in the history tab indicated "Role used by Pega developers which grants privilege to see all Threads in the clipboard viewer. May be used for other things later." This was a misleading description caused by outdated documentation and has been updated to display "Please refer pxTestID privilege for description". | System Administration |
| INC-C42700 INC-C47501 INC-C48247 INC-C55592 |
954390 961333 962390 965746 |
Session management and requestor lifecycle improved | Users were experiencing unexpected logouts and session disruptions during active work sessions. This was traced to requestor passivation and activation processes happening during requestor lifecycle management as part of infrastructure scaling events. To address this, the requestor activation sequencing has been updated and error handling during passivation processes has been improved. Additionally, unused properties have been removed from PAL pages during passivation, and the default retry attempts for on-demand passivation have been increased to 4 to provide better resilience during node scaling operations. | System Administration |
| INC-C47107 INC-C56898 |
963196 966055 |
Push notification service compatibility resolved | After upgrade, push notification execution was failing with the Publish-Notifications activity throwing PushServiceException errors and the pzIsPushServiceEnabled rule returning false, indicating the push engine had failed to start. Investigation showed this was caused by a Java version compatibility issue where the atmosphere-runtime JAR expected properties files to be located in different paths between Java versions - in the main directory for older Java versions but in the resources classpath for Java 17. This has been resolved by updating the atmosphere-runtime-3.0.13.jar file to relocate the properties file from the main path to the resources path, ensuring proper compatibility with Java 17 environments. | System Administration |
| INC-C55525 INC-D2445 |
965522 972589 |
Job scheduler database compatibility improved | The pyCleanupExpiredRequestors job scheduler was failing with Oracle database error "ORA-00936: missing expression" when attempting to clean up expired requestor sessions. This was traced to an incompatible RDB-delete query in step 4 of the pzCleanupExpiredRequestors activity that utilized the DATE() function, which is not supported by Oracle databases. This has been resolved by updating the query to use database-compatible syntax with CAST(pxcreatedatetime AS DATE) to ensure proper compatibility across Oracle and PostgreSQL database environments. | System Administration |
| INC-C58655 | 968075 | Corrected Jakarta servlet references for SSO compilation | After update, the pySAMLWebSSOAuthenticationActivity was encountering compilation errors when attempting to reference javax.servlet classes in custom pyEstablishOperatorContext code. This was traced to the platform migration from javax.servlet to Jakarta servlet APIs, and has been resolved by updating the servlet API references to use the appropriate Jakarta equivalents. | System Administration |
User Experience
25.1.2 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C11245 | 957711 | Follow and unfollow actions now provide user notifications | Users were not receiving any confirmation or notification when selecting follow or unfollow actions from the Actions menu in the Preview section. This has been resolved by implementing notifications to confirm when the actions have been completed successfully. | User Experience |
| INC-C12345 | 917816 | Report button icon accessibility corrected | To improve accessibility, the role of the expand/collapse icon for the Summary/Chart tables reports in Dev Studio has been updated from link to button. | User Experience |
| INC-C14202 | 956939 | Agent selection functionality restored | When using node agnostic view in the admin studio "Agents" landing page, the checkbox for selecting all agents was not functioning. This was traced to the "Optimize code" checkbox being enabled for the table, and has been resolved by changing the optimized table to a non-optimized table. | User Experience |
| INC-C15899 | 927345 | Any Picker clear selection accessibility enhanced | Screen readers were not properly announcing the clear selection cross icon when hovering over selected values in Any Picker controls. This has been resolved with an update to ensure the clear icon is focusable and actionable with keyboard, with an aria-label reflecting the selected value. | User Experience |
| INC-C17807 | 959141 | Multiselect readonly display corrected | Optimized table multiselect controls configured as readonly were displaying as editable. This was caused by inconsistent handling in the renderControl function where multiselect controls did not follow the same readonly logic as other control types due to it being a a page-list type property. This has been resolved by implementing consistent readonly handling for multiselect controls in an optimized table. | User Experience |
| INC-C18782 | 928594 | Dialog close button accessibility resolved | The dirty check popup close button was not accessible via keyboard after focus had moved to the Cancel or Submit button when working in the perform harness. This has been corrected with an update to ensure focus on the close icon when ModalDialogXIconFocus is true. | User Experience |
| INC-C22921 | 935147 | Resolved error for Ajax container tab deletion | Ajax container tabs were experiencing null pointer exceptions when attempting deletion operations. This was caused by data-record-key attributes not being generated for tab elements during page refresh operations, and has been resolved by setting recordKey for tabs on refresh. | User Experience |
| INC-C25293 | 954405 | Launch harness file download behavior clarified | The documentation for Available UI actions has been updated to clarify that using the Harness action with target set to New document to download a file is no longer supported in Pega Platform versions 8.5 and later. Following this change, downloading a file is available only through the Open URL in window action. | User Experience |
| INC-C26338 | 947761 | Browser tab title application name corrected | Browser tab titles were displaying the previous application name instead of the current application when navigating between multiple applications in a portal. This was traced to the GenerateLayout RUF file using a common title from the Theme-Cosmos application ruleset regardless of the active portal context, and has been resolved by implementing dynamic title updates that reflect the current application context during navigation. | User Experience |
| INC-C29841 | 942493 | Declare trigger execution logic corrected | Declare triggers configured on page list properties were executing unexpectedly when screens were submitted without any property modifications. This was traced to the PageList processing handling, and has been resolved by correcting the trigger evaluation logic to only execute when actual property changes occur. | User Experience |
| INC-C31256 | 945358 | Corrected data update when grouping removed | When grouping was applied to an optimized table with a queryable data page, changing the option back to the "Select field" option in the dropdown returned "No results" instead of removing the grouping. This has been resolved by resetting the page index to 1 when select field option is selected. | User Experience |
| INC-C32532 | 945060 | Improved accessibility for case lifecycle completion status | Completed steps in case lifecycles displayed green checkmarks in Constellation that were not accessible, preventing screen readers from identifying finished steps. This has been resolved adding a "Completed" announcement to the steps, including scenarios where a step can be passed as a link (react node). | User Experience |
| INC-C32635 | 943001 | Case summary follow button focus behavior corrected | When clicking the star icon to follow or unfollow cases in the case summary header, keyboard focus was being lost, requiring users to press tab again to regain focus indication on the button. This has been resolved by updating the button state change event handling so focus consistently remains on the button when activated. The screen reader announcement also reflects the label changing upon follow/unfollow. | User Experience |
| INC-C350 | 967977 | Modal dialog accessibility labeling corrected | Some modal dialogs were unlabeled for screen readers due to aria-labelledby attributes pointing to non-existent DOM elements. This was caused by dialog templates inconsistently including the modaldialog_hd_title ID that the aria-labelledby attribute referenced, and has been resolved by implementing logic to verify the existence of the target ID before setting aria-labelledby attributes and to find the header element when the primary ID is not present. | User Experience |
| INC-C35239 | 949342 | Corrected radio button selection issue | Radio buttons marked as mandatory were not getting selected on the first attempt when they were the first field on a form. Users had to make a second selection for the radio button to register. This has been resolved by correcting the focus and blur behavior. | User Experience |
| INC-C36448 INC-C36734 INC-C36789 INC-C36801 INC-C36941 INC-C37168 INC-C37236 INC-C37237 INC-C37276 INC-C37353 INC-C37566 INC-C37624 INC-C37824 INC-C37994 INC-C38285 INC-C38376 INC-C39213 INC-C40100 INC-C41015 INC-C41020 INC-C41029 INC-C44165 INC-C45714 |
957417 | Live UI functionality restored for Chrome/Edge browsers | Live UI was failing to load when using the default Content Security Policy (CSP) configuration 'pxDefaultAllowAll' in Google Chrome and Microsoft Edge browsers version 139.X.X and later. This was caused by a Chrome 139 update which introduced a change that fires an error event when CSP blocks a Worker script, preventing Live UI from functioning properly. The issue may be addressed with a local workaound by adding "blob:" to the list of allowed websites in the Child Frame-Source section. This has been resolved by updating the platform to handle the new browser behavior and ensure Live UI compatibility with the latest Chrome/Edge versions. | User Experience |
| INC-C36784 | 955339 | Cascading dropdown value persistence logic fixed | Applications were experiencing validation errors when using three-level cascading dropdowns, where changing the first dropdown would reset the second but incorrectly persist values in the third dropdown instead of clearing all dependent fields. This was caused by incomplete dependency chain handling in the cascading dropdown implementation, and has been resolved by ensuring all dependent fields at any level are properly cleared when parent dropdown values change. | User Experience |
| INC-C36809 | 947701 | Promoted filter display fixed for radio button picklists | Picklists configured to display as radio buttons appeared as normal text fields in promoted filters. This has been resolved by updating the type mappings for Picklist:pxRadioButton to set conditionFieldType to "PICKLIST". | User Experience |
| INC-C36919 | 949466 | Date field required message clearing behavior made consistent | Required validation messages for date fields were persisting when fields became readonly and no longer required, while text fields properly cleared their messages under the same conditions. This has been resolved by standardizing the validation message clearing behavior across all field types when requirement conditions change. | User Experience |
| INC-C36982 | 960542 | Constellation tab count refresh control added | Tab counts in landing pages were not refreshing when underlying table data changed, causing user confusion as displayed counts remained stale even after bulk actions modified record quantities. This was due to the behavior of thread-level data pages: when a data page is configured to reload once per interaction, it may not always refresh as expected during complex interactions or when navigating between different views. Additionally, if the UI is not set to refresh automatically upon returning to the tabbed view, the count will remain unchanged until a manual refresh of the browser is performed. In order to address this limitation, the setting "pyAutoUpdateLandingPageTabCounts (Boolean)" has been added which will cause the TabbedPage template to refresh the tabCount when case/process events have been triggered. | User Experience |
| INC-C37214 | 962061 | JavaScript execution continues during SLA message display | JavaScript functionality was becoming unresponsive when SLA messages were displayed, preventing task completion in mobile applications used for field work. This has been resolved by modifying the SLA message display mechanism to allow continued JavaScript execution. | User Experience |
| INC-C37604 | 959851 | Local actions functionality restored in Constellation portal | After update, local actions were not functioning properly from dashboards, causing the TransferInteraction flow action to display an unexpected summary screen instead of dismissing cases as expected, and Constellation portals were failing to load. This was traced to an issue with displaying confirm-view for local actions from list view in multi-document applications, and has been resolved. | User Experience |
| INC-C37775 | 954549 | User saved views persistence in Theme Cosmos addressed | Applications were experiencing deletion of user-created personalized views when using the refresh action on worklists in Theme Cosmos, with views from different harness classes appearing instead. This has been addressed with an update to save the Table views in a single appropriate Harness class. | User Experience |
| INC-C38028 | 951863 | Date picker accessibility improved for labels with apostrophes | Date picker controls were displaying incomplete alt text when labels contained apostrophes. This has been resolved with an update to encode the apostrophe symbol as HTML Hexadecimal code in the date picker template so the full alt text is present. | User Experience |
| INC-C38047 | 954095 | Timezone conflict handling updated in datetime controls | When operators had specific regional timezone settings that differed from a datetime control timezone configured through a property, the control was showing time according to the operator's timezone rather than the specified property timezone. This has been resolved by updating the handling in the calendar JavaScript rule. | User Experience |
| INC-C38056 | 949846 | Table grid functionality restored after search operations | Table grids were becoming unresponsive after performing basic search operations, preventing hiding columns, accessing details, or performing other grid actions. This was caused by the pzDoGridPersonalize activity receiving invalid column numbers as NaN values during refresh operations after filtering, and has been resolved by updating the pyInitialOrder value retrieval from column objects in the templatizedgrid component to use the DOMParser API for safer HTML parsing. | User Experience |
| INC-C38112 | 955110 | Table pagination accessibility enhanced | Accessibility issues were seen with unoptimized table pagination controls. This has been resolved by adding the necessary focus elements. | User Experience |
| INC-C38126 | 952184 | Date time field audit history display corrected | Date and time field values were displaying the date portion in field history audit trails without the time component. This was caused by the FieldHistory component not being able to match "DateTime" format when the data page property was "Date Time" with a space. This has been resolved with an update to convert property type strings to a consistent format. Property type values that contain spaces or hyphens (e.g., "True-False", "Date Time") will be given camelCase format (e.g., "TrueFalse", "DateTime"). | User Experience |
| INC-C38484 | 950220 | Dirty check alerts resolved for hybrid Constellation applications | Users were encountering persistent alert messages about unsaved changes when creating new Constellation cases in hybrid applications, with the page becoming unresponsive when canceling the alert. Investigation showed this was caused by improper dirty state management between theme-cosmos and Constellation applications during case creation workflows, and has been resolved. | User Experience |
| INC-C39574 | 960839 | Form validation errors resolved during view refresh | Form submissions were failing with infinite loops and console errors when validation rules were triggered on fields that became invisible after unchecking form elements with refresh settings enabled. Investigation showed this was caused by the system attempting to validate invisible fields during the merge data action after view refresh. This has been resolved with an update to ensure there is validation on the field only when visible. | User Experience |
| INC-C40876 | 966070 | Table sorting functionality after filter changes restored | Table columns could not be sorted after saving a view with column filters and subsequently removing those filters. This was caused by gridObjJSON.gridTable.isDPEmpty incorrectly remaining true after filter removal, preventing sort operations. This has been resolved by properly updating the state parameter isDPEmpty based on the length of the filtered records. | User Experience |
| INC-C41144 | 956426 | Optimized grid row focus resolved | Optimized grids were not consistently focusing on the first row by default. This was traced to a conditional check that was preventing focus from being applied in certain scenarios, and has been corrected. | User Experience |
| INC-C41475 | 954827 | Promoted filter localization functionality corrected | Applications were displaying non-localized values in promoted filters even when the underlying table data was properly localized. This was caused by the promoted filter component not inheriting localization settings from the referenced picklist field, and has been corrected. | User Experience |
| INC-C41479 | 960826 | Dynamic questionnaire UI refresh corrected | When switching picklist options in dynamic questionnaires, the next question would load on the backend but the UI would continue displaying the previous question instead of refreshing to show the new content. This has been resolved. | User Experience |
| INC-C41858 | 954553 | Modal resize handle removed for improved accessibility | A modal dialog launched in the portal included a resize handle/button in the bottom right of the modal. The resize handle could be clicked and dragged to resize the modal using a mouse, but it could not be interacted with by keyboard or screen reader. This has been addressed by removing the resize button for consistent accessibility. | User Experience |
| INC-C42060 | 965188 | Constellation worklist grouping logic updated | Applications were experiencing errors when attempting to group columns in Constellation Worklist views, particularly when applying both grouping and sorting operations on date columns within pagelist configurations. Investigation showed this was caused by incorrect calculation ID preparation in the underlying query generation logic when processing date column operations in list view landing pages. This has been resolved by correcting the query calculation logic. | User Experience |
| INC-C43151 | 959970 | Case search loading indicator fixed | Searching for restricted case IDs and pressing Enter resulted in infinite loading indicators despite proper security restrictions being applied. Investigation showed this was caused by improper handling of the busy indicator state when keyboard navigation triggered unauthorized access scenarios. This has been resolved by ensuring the loading indicator properly terminates after displaying security restriction messages. | User Experience |
| INC-C43329 | 956108 | Scroll position maintained during field editing autosave | When editing fields located at the bottom of assignment screens in Data Center, the autosave feature was triggering and automatically scrolling the view back to the top of the page. This was caused by the autosave mechanism not preserving the current scroll position during the save operation, and has been resolved. | User Experience |
| INC-C43395 | 957698 | Text wrapping improved for long content in text boxes | Long text content was overflowing beyond text box boundaries in Constellation. This has been resolved by updating the text wrapping mechanisms for FieldGroup text overflow. | User Experience |
| INC-C43413 | 954820 | Grid actions delete icon accessibility improved | Tooltip support has been added for the delete icon of the Sort Action in the Grid Actions. | User Experience |
| INC-C44746 | 955163 | Decimal field clearing behavior corrected | Applications were allowing form submission without required field validation in Constellation when decimal fields were cleared. This was traced to the system setting values to 0.00 instead of null when fields were emptied, and has been corrected. | User Experience |
| INC-C45450 | 957861 | 24-hour date format selection enabled for non-optimized grids | It was not possible to select 24-hour date format for calendar controls within non-optimized grids. This has been resolved by adding the necessary support to the editable date time picker controls for non-optimized grid configurations. | User Experience |
| INC-C45450 INC-C36335 |
955323 955842 |
24-hour date format added for localized calendar controls | Support has been added for a 24-hour date format in the editable date time picker controls when using localization. | User Experience |
| INC-C45461 | 955633 | Data reference table checkbox focus visibility enhanced | Users navigating with keyboards were unable to clearly see focus indicators when the keyboard focus was on the first checkbox inside the data reference property simple table layout. This was caused by insufficient visual styling for focus states on checkbox elements in table contexts, and has been corrected by adding padding to the row select checkbox to give space for an outline focus ring. | User Experience |
| INC-C45593 | 960603 | Screen reader accessibility improved for audit attachments | Screen readers were announcing and focusing on a hidden attachment data frame in the audit tab, causing confusion during navigation. This has been resolved by adding aria-hidden='true' and tabindex='-1' attributes to hide the frame from screen readers so that the iframe label and contents are not announced by screen reader when navigating case history dialog. | User Experience |
| INC-C45690 | 957811 | Checkbox validation error icon positioning fixed | Validation error icons were covering checkbox UI controls in UIKit applications. This has been resolved by adjusting the error icon positioning and margin calculations. | User Experience |
| INC-C45733 | 959524 | Modal dialog error message properly cleared | Error messages in flows running within modal dialogs were persisting even after screen refresh and control value changes. This has been resolved by ensuring error messages are properly cleared when control values change or screens refresh within modal dialog flows. | User Experience |
| INC-C45912 | 963325 | Query list preview rendering fixed in view editing | Query type fields containing scalar lists were not rendering in the preview pane when editing case view screens, despite appearing correctly in actual case views. This was caused by preview rendering logic not properly handling embedded scalar list fields within query lists, and has been resolved. | User Experience |
| INC-C45944 | 961402 | Screen reader error message announcements added for table validation | JAWS screen reader users were not receiving announcements of error messages when navigating to tables with validation errors. This has been resolved. | User Experience |
| INC-C46027 | 959791 | Table column width distribution corrected | The delete column in embedded tables was consuming all remaining width when entering full screen mode, disrupting the intended layout. This was caused by incorrect application of flex-grow properties to the last column instead of columns with fillAvailableSpace set to true, and has been resolved by updating the styledTableContainer to apply flex-grow only to designated columns and properly calculate auto-sizing for screen resizing. | User Experience |
| INC-C46701 | 960155 | Decimal formatting behavior standardized | Decimal properties were inconsistently appending zeros after entering integer values and then clicking outside the field. This has been resolved by updating the handling to ensure trailing zeroes are removed on blur for Decimal. | User Experience |
| INC-C46850 | 957549 | Landing page overlay display issues corrected | Landing pages created with the Tabbed template in Constellation-based setups were displaying overlay issues affecting table column headers. This was caused by CSS rendering conflicts in the Theme Cosmos environment when preview panels were opened alongside tabbed landing page content, and has been resolved. | User Experience |
| INC-C46933 | 958027 | SVG application logo rendering restored | SVG files uploaded as application logos from the Channels & Interfaces page were uploading successfully but were displaying as empty in the runtime portal. This has been resolved by adding the MIME type to image blobs for proper format identification. | User Experience |
| INC-C46979 | 957634 | Date-only field display corrected | Date-only fields in list view promoted filters were not displaying the default year when users selected just the date, with the year only appearing when selecting the To date. This has been corrected. | User Experience |
| INC-C47204 | 960043 | Axios updated | The Axios library has been updated. | User Experience |
| INC-C47257 | 959029 | Apple Safari browser focus behavior for embedded data tables corrected | Embedded data table headers were not receiving proper focus when navigating with keyboard controls in Apple Safari browser environments. Investigation showed this was caused by Safari-specific focus handling differences in the data table header cell implementation. This has been resolved by adding outline-offset to show focus in embedded data table header elements. |
User Experience |
| INC-C47263 | 958710 | Helper text focus corrected | Focus was not working for the helper text if there there was a space or line break in the field value for "Help icon with overlay on focus". This has been resolved by adding a check for overlay on focus helper text. | User Experience |
| INC-C47390 | 959777 | Check added to update 'when' triggered for embedded table | The UI did not update correctly when a rule-based read only 'when' condition was triggered in an embedded table. This was traced to the 'when' condition calculation being done on the server and the cell not being re-rendered by the network call in a timely manner. To address this, a readOnly check has been added to update displayMode in react_pconnect instead of cellRenderers.js to ensure 'when' conditions are honored. Additional refinement to this work will be done in a future release. | User Experience |
| INC-C47590 | 960218 | Skin rule preview functionality restored | After update, preview panels were displaying blank content when opening skin rules. This was traced to the cross-site scripting filters which passed the converted ascii value for the parenthesis and blocked the Preview from loading, and has been resolved by replacing this ascii value with parenthesis in the pzSelectivePreview activity. | User Experience |
| INC-C48743 | 959334 | Table delete column accessibility enhanced | Screen readers were unable to identify delete column headers in configurable tables due to missing accessibility labels. This has been corrected. |
User Experience |
| INC-C48949 INC-C56393 |
962663 967166 |
BlendedUI navigation issues for landing pages and assignments corrected | Navigation functionality was experiencing problems where clicking menu icons failed to switch screens and URL and tab names were changing across all browser tabs in Constellation applications. This has been resolved by updating the traditionalGadgetId to ensure proper gadget reloading for landing pages and by adding support for launching assignments of traditional cases from the Constellation portal using assignmentURL. Additional work has been added to prevent URL and tab name synchronization across multiple browser tabs. | User Experience |
| INC-C49227 | 960862 | Picklist value persistence corrected | Picklist values were reverting to their original state after being updated and saved on certain screens. Investigation showed this was caused by custom expressions incorrectly evaluating string comparisons in the Constellation frontend. This has been addressed with by updating the expression evaluation logic to properly handle string value comparisons with equals and not equals operators for nullish values. | User Experience |
| INC-C49325 | 963720 | Custom DX component visibility consistency restored | Custom field-level DX components for bulk data onboarding were intermittently not appearing when users first accessed assignments, requiring cancel and reopen operations to display correctly. Investigation showed this was caused by timing issues in the component rendering lifecycle during initial assignment loading. To resolve this, an update has been made to the component initialization sequencing to ensure consistent visibility. | User Experience |
| INC-C49366 | 962918 | Focus navigation restored for form fields accessibility | Form fields were experiencing focus lock on the first field when page messages were displayed after validation errors, preventing navigation to other fields via keyboard or mouse. This has been resolved. | User Experience |
| INC-C49511 | 967237 | Multi-select dropdown values included in DX API responses | Multi-select dropdown controls were not returning complete option values when assignment views were being published to front-end mobile applications through DX APIs. Investigation showed this was caused by the API response only including key values while omitting additional field values configured in the data page source, preventing mobile applications from displaying proper dropdown options with both keys and descriptive values. This has been resolved by modifying the pzdxapifulljsonforvieworpage and pzdxapijsonformodes functions to provide additional option values in API responses. | User Experience |
| INC-C50255 | 960760 | Corrected table reordering with RTE | Reordering tables containing embedded fields with Rich Text Editor (RTE) properties was causing content display failures or RTE disappearance. Investigation showed this was caused by improper handling of RTE components during table reordering operations in the Constellation UI, and has been corrected. | User Experience |
| INC-C50529 | 963441 | Unnecessary tracer failures eliminated during case creation | Case creation was generating false failure entries in the tracer due to attempts to access a non-existent CoexistenceCasesDT data transform in the pxGetCaseTypesForCoexistence activity. This was caused by hardcoded references to data transforms not supplied with the Pega product, and has been resolved by adding proper existence checks before attempting to access the coexistence data transform. | User Experience |
| INC-C50675 | 964412 | Date time spinner year restriction corrected | Date time controls with spinner navigation were displaying additional years beyond the current year even when configured to restrict both previous and future years to zero. This has been resolved by adding a "restrictToCurrentYear flag" to restrict the date range in spinner mode when 0 is set for both next and previous. | User Experience |
| INC-C50741 | 961539 | DX API payload handling corrected after upgrade | After upgrading from Pega 8.7 to Infinity 24.1, multi-select dropdown values in DX-API assignment/action/refresh calls were showing index values replaced with characters in the payload. This has been resolved. | User Experience |
| INC-C50833 | 960783 | Datatype edit view enabled | Previously, the pyEdit view could not be created directly in the Views tab for datatypes in Cosmos theme Constellation landing pages. With this update, pyEdit has been added to the Section rule in Data- so that it can be overridden into a data type's class and edited for List page table column editing purposes. | User Experience |
| INC-C51009 | 964348 | Embedded table focus behavior updated | Inline editable embedded tables were triggering validation errors when adding new rows due to focus shifting from mandatory fields back to the cell container. This was caused by conflicting autofocus attributes interfering with the accessibility-focused cell navigation system, and has been addressed by removing autofocus attributes when whole-cell focus is required for proper table navigation. | User Experience |
| INC-C51282 | 962169 | Notification timestamps corrected to local time | System notifications were displaying timestamps in GMT rather than respecting local time zone settings. This has been resolved by implementing proper time zone conversion in the notification display. | User Experience |
| INC-C51589 | 967587 | Date range control warning popup resolved | Warning popups were appearing incorrectly when navigating away from forms containing date range controls, even when no changes had been made to the form. This was traced to the date range control not properly tracking its initial state, leading the system to incorrectly detect unsaved changes. To resolve this, a data-initialvalue attribute has been added to the date range control to properly track the control's initial state and prevent false dirty form detection. | User Experience |
| INC-C51769 | 962273 | DateTime field value persistence fixed | Users were experiencing datetime property fields becoming blank when clicking on the field and submitting without making changes, particularly in meeting scheduling workflows. This was traced to the handling of unchanged datetime values during form submission processing, and has been resolved by correcting the datetime component logic to preserve existing values when no modifications are made. | User Experience |
| INC-C51822 | 965619 | Text truncation and icon overlap issue resolved | Stage labels with excessive characters were displaying ellipses truncation while check mark icons overlapped with chevron elements. This was caused by improper spacing calculations between text elements and styled icons with border-radius, and has been resolved by updating the CSS. | User Experience |
| INC-C52132 | 963025 | Optimized table date filter styling corrected | The "Filter by" section of an optimized table date column was displaying over the content above it. This was caused by incorrect CSS styling in the filter popup layout, and has been resolved by adding padding to correct the styling issue. | User Experience |
| INC-C52455 | 966491 | Custom action submission error resolved for operator preferences | A 500 error was occurring when submitting custom actions to update the pyUseLocale property from operator preference landing pages that were mapped to Operator ID data types. This was caused by improper handling of the view submit action API when processing locale updates, and has been corrected. |
User Experience |
| INC-C52533 | 966065 | Flow action work object close handling updated | When using the "Close the Work Object" option under "If an assignment is not being performed" for a flow action, the application displayed a gray screen on the first attempt instead of properly navigating or closing the work object. On subsequent attempts, the work object closed as expected and returned to the Home harness. This has been resolved with an update to close the Work Object after the flow action. | User Experience |
| INC-C52644 | 962095 | Corrected duplicate values shown in promoted filters | Duplicate work status values were appearing repeatedly when scrolling through promoted filter pick lists on landing pages. This was caused by the fetchPossibleValues function in ValueSelector duplicating the same list of values multiple times during load operations, and has been resolved. | User Experience |
| INC-C52811 | 961971 | Web embed errors properly displayed | Web embed implementations were displaying blank screens instead of error messages when case creation failed due to rate limiting or other validation errors. Investigation showed this was caused by the web embed framework not properly handling and displaying error responses from case creation failures. This has been corrected. | User Experience |
| INC-C53192 | 968602 | AnyPicker search handling corrected | When searching for a field in the Engagement Policy AnyPicker dropdown and selecting it, the displayed value differed from the one chosen. Additionally, if a value was selected from the dropdown, the system incorrectly selected the next value in the list instead of the intended one. This was an issue with the field search functionality not correctly handling the first row, and has been corrected. | User Experience |
| INC-C53523 | 965230 | Read-only number formatting consistent for all digit lengths | Read-only formatting for number controls was not being applied to 3-digit numbers and below, while working correctly for 4-digit numbers. This has been resolved by updating the data-changed attribute condition conditional logic in the pzpega_ui_events.js changeHandler function to properly handle formatting for numbers of all digit lengths. | User Experience |
| INC-C53836 | 966394 | Date format display consistency improved | Date fields in case left panes were not displaying with configured formats on initial load, showing proper formatting only after refresh or case reopening. This was caused by improper dependency referencing in scalar list components within case summaries. This has been resolved by adding componentType to pxDependencies for ScalarList metadata. | User Experience |
| INC-C54056 | 964458 | Custom DX components loading fixed in Dev Studio | Custom DX components were failing to load when launching cases from Dev Studio, displaying 404 errors and preventing component functionality. This was caused by missing component loading logic specific to the Dev Studio environment, and has been resolved. | User Experience |
| INC-C54074 | 967999 | Corrected duplicate row creation during attachment upload | Adding attachments while editing new rows in repeating views was causing duplicate rows to appear in the grid. This was caused by improper state management during the attachment modal workflow in Constellation, and has been resolved by clearing saved properties from the context tree when the openLocalAction API is invoked. | User Experience |
| INC-C54097 | 965218 | Decimal field length validation restored | Decimal fields were accepting more than the expected 12-digit maximum length and displaying NaN values when exceeding 16 digits. Investigation showed this was an unintended side effect of previous work on decimal field validation logic, and has been resolved by implementing client-side validation to restrict the number of digits accepted and ensure proper input validation to prevent excessively large numbers from being entered. | User Experience |
| INC-C54122 | 970097 | Currency field display corrected for empty values | Currency fields in table views were incorrectly displaying "0.00" when the actual value was blank, particularly when data was populated through VRL responses or refresh calls. This has been resolved by ensuring currency fields maintain proper null values when no data is present, preventing the automatic conversion to zero. | User Experience |
| INC-C54311 | 966466 | Screen reader accessibility improved for table fields popup | Screen readers were reading the entire popup content after navigating past the last row in the Fields popup within optimized table configurations. This has been resolved by making the dialog body focusable when firstFocusableElement is not present in modal or popover. | User Experience |
| INC-C54427 | 968618 | Constellation case can be created from traditional case in Blended UI | Applications using Blended UI were experiencing issues when attempting to create Constellation cases from traditional cases, with new cases incorrectly opening in blended mode instead of the expected Constellation mode. This has been resolved with an update that implements UI mode detection and routing logic that ensures cases created from blended traditional cases correctly open in Constellation mode when the target case type is configured for Constellation, with flow parameters now properly converted to starting field properties to maintain compatibility with Constellation's architecture. | User Experience |
| INC-C54603 | 968650 | Corrected handling for parameterized checkbox inside repeating views | Checkbox groups backed by data reference properties with different parameters were experiencing option changes when users interacted with multiple checkbox groups on the same view. This has been resolved by updating the parameter handling logic to maintain distinct options for each checkbox group. | User Experience |
| INC-C54843 | 967723 | Anypicker control error accessibility updated | Screen readers were not announcing validation errors for anypicker controls. This has been resolved by adding the necessary aria-describedby attributes for the server side validations. | User Experience |
| INC-C54894 | 965326 | Display stages restored for case type processes | Case type processes were not displaying in stage views after update. This was traced to a rule mismatch which resulted in the removal of the embedded section pyDisplayStagesAndSteps from the pxDisplayStages rule in the Cosmos theme, and has been corrected. | User Experience |
| INC-C54972 | 965950 | Modal keyboard navigation accessibility improved | Modal dialogs containing multiple tables with hidden default action buttons were not allowing proper keyboard tab navigation through all elements, with focus cycling back to the modal top instead of progressing through table elements. This was caused by the isSrcfromLastTable function incorrectly returning true even when the source was not from the last table, and has been resolved by correcting the table source detection logic. | User Experience |
| INC-C55204 | 965338 | Case preview corrected for hybrid applications | Case preview was not functioning for Constellation cases within hybrid application models that utilized both Cosmos and Constellation case types. Investigation showed this was caused by missing PreviewViewContainer components in the RootContainer and incorrect context handling that restricted preview loading in hybrid environments, and has been corrected. | User Experience |
| INC-C55318 | 968784 | Attachment field error clearance corrected | Error messages were persisting in attachment fields even after removing invalid files. This has been corrected. | User Experience |
| INC-C56309 | 965408 | Localization bundle creation corrected in Constellation applications | Applications were experiencing failures when attempting to create localization bundles in Constellation, particularly affecting Japanese language pack creation where users encountered "Failed generation" error messages during the localization process in App Studio. This was traced to the handling for type conflicts in bundles during bundle merges with an additional issue of limitations processing Excel imports exceeding 64K rows, and has been resolved. | User Experience |
| INC-C56366 | 968656 | Rich Text Editor resize toggle default updated | After upgrade, Rich Text Editor controls were missing the resizing capability which had been available by default. This was traced to the introduction of a resize toggle feature that changed the default behavior without maintaining backward compatibility, and has been resolved by restoring the default of pyRTEResizeToggle to true for better backwards compatibility. | User Experience |
| INC-C56722 | 967431 | Label display issue with dots resolved in Angular UI | Labels containing dots were not displaying properly in Angular UI applications. This has been resolved by modifying the RUF's pzdxapifulljsonforvieworpage and pzdxapijsonforfield to properly quote label values, ensuring labels with dots and other special characters display correctly in Angular UI applications. |
User Experience |
| INC-C56896 | 968976 | Grid view switching restored for parameterized data pages | Applications were experiencing null pointer exceptions when attempting to switch back to the default view from any other view of a table sourced from a parameter datapage. This was traced to the system deleting parameterized data page instances from the clipboard while they were still being referenced by the view switching API, and has been resolved with an update to necessary instances in the clipboard during view operations. | User Experience |
| INC-C57552 | 970901 | Complex embedded data structures persist for case reopening | Saved data including radio controls, dropdowns, and search results did not load correctly when cases with complex embedded structures were reopened from the flow after using the "Save for Later" functionality. This has been resolved by enhancing the data restoration logic to properly handle complex embedded structures during case reopening operations. | User Experience |
| INC-C58029 | 967560 | Debug headers removed for web embed compatibility | Web Embed applications hosted in third-party environments were experiencing CORS policy violations when performing Cancel and Save for Later actions. Investigation showed this was caused by x-pega-app-debug-* headers being sent unconditionally to all client applications, including those not configured to accept these debugging headers in their CORS policies. This has been resolved by removing the debug headers for Cancel and Save for Later. | User Experience |
| INC-C58145 | 970160 | Screen reader accessibility enhanced for error messages | Error messages displayed through the NoID harness and pyIdNoHeader section were not being announced by screen readers like JAWS. This has been corrected by adding the necessary roles. | User Experience |
| INC-C58233 | 967543 | View designer data persistence improved in Constellation | JavaScript errors were occurring when closing the view designer in Constellation, resulting in incomplete saving of view changes. This has been resolved with an update avoid a NullType error by verifying contentDocument before rendering the content onto IFrame in Preview. | User Experience |
| INC-C58357 | 968586 | Nested page list data integrity maintained during refresh operations | Data was being lost in nested page lists when refresh operations occurred, specifically affecting QuestionGroups.Questions structures where EmbedUUID values were regenerated causing previously submitted values to become inaccessible. This was traced to differences in the path handling between pathPrefix and nestedPath in the cascade manager, and has been resolved by updating the replace logic for proper UUID matching. | User Experience |
| INC-C58580 | 968182 | Mashup modal dialog positioning corrected for mobile screens | Modal dialogs containing file upload controls were appearing at the top of mobile screens in mashup scenarios, making the loading indicator invisible to users during file uploads. This was caused by hardcoded vertical alignment and padding styles in the pega_ui_modaldialog component, and has been resolved. | User Experience |
| INC-C59383 | 969121 | Focus indicator corrected for collapsible dynamic layouts | Collapsible dynamic layout headings were not displaying focus indicators when the summary pane was collapsed. This has been resolved by adding appropriate CSS handling to ensure focus indicator styles appear correctly when navigating to collapsible headings in all states. | User Experience |
| INC-C59384 | 970032 | Decision table and paragraph editing access corrected for coexistence mode | Users were receiving 403 forbidden errors when attempting to edit decision tables or paragraphs in Blended UI coexistence environments. This was caused by the Pega-desktop-api openrule action missing required skin and portal name parameters for coexistence cases, and has been corrected. | User Experience |
| INC-C59544 | 969504 | Search and select controls handling updated for multiple entity configurations | Applications using repeating views with multiple Search and Select controls were experiencing issues where only the last control would return search results while earlier controls remained in a loading state, and searching in one control was causing all other Search and Select controls in the repeating view to refresh unexpectedly. This was traced to the same property reference being assigned to multiple controls, and has been resolved by updating the handling of multiple associated entities within the same repeating view context. | User Experience |
| INC-C60124 | 970792 | Date field year range configuration accuracy improved | After configuring a date field to be of precisely the current year range by configuring next and previous years in range as zero, it was not possible to select December 31 of the current year, the year drop down had the previous year entry available, and selecting January 1 of the current year enabled the previous year. This was traced to timezone-related calculations affecting year boundary determinations and dropdown population logic, and has been corrected. | User Experience |
| INC-D88 | 970522 | Promoted filters autocomplete search functionality updated | Autocomplete search in list view promoted filters was exhibiting inconsistent behavior, working correctly for 2 characters while ignoring case, but requiring exact case matching after 4 characters. This was caused by inconsistent application of "ignoreCase" in the filters, and has been resolved by standardizing the case-insensitive search behavior across all character length scenarios. | User Experience |