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
24.2.4 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| EA-C16583 | 965841 | 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 |
| EA-C16759 | 967417 | 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 | 884295 | 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 | 953640 | 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 | 958658 | 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 | 958694 | 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 | 952548 | 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 | 959754 | 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 | 964844 | 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 | 959093 | 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 | 961268 | 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 | 956774 | "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 | 957570 | 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-C45742 | 962043 | 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-C49224 | 960392 | 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-C52052 INC-D3152 |
963014 974833 |
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-C52742 | 962299 | 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-C54329 | 968464 | 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-C56379 |
969208 972909 |
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-D2732 | 976445 | File attachment keyboard accessibility corrected | Attempting to attach files through the pyAttachContent control in overlays using keyboard navigation generated the error “There has been an issue, please consult your system administrator.” Mouse interactions worked correctly. This was caused by the pzMultiFilePath control lacking proper keyboard event handling when configured in an overlay, and has been corrected. | Case Management |
| INC-D3223 | 975040 | Drag and drop file size limit handling corrected | File uploads through drag and drop controls were incorrectly rejecting files when the pyMaxDragDropAttachSizeMB setting was configured to 2048MB or higher. This was caused by integer overflow in the byte conversion calculation within the pzMultiDragDropControlStandard control, and has been resolved by changing the variable data type from int to long to properly handle large file size limits. | Case Management |
| INC-D3407 | 975498 | Pagination limit removed for App Studio subprocess selection | Applications with more than 50 flow rules were unable to access all available flows when configuring subprocesses in App Studio. This was due to a default pagination limit of 50 records in the pyGetCategoryItems report definition, and has been resolved by disabling paging so all flows are returned. | Case Management |
| INC-D4916 INC-D6170 |
976153 981374 |
ase archival process corrected to prevent unintended data deletion | Systems were experiencing complete deletion of audit data tables when attempting to archive individual cases, including removal of audit records for unresolved cases that should have been preserved. Investigation showed this was caused by previous work on the field level audit (FLA) purge query logic. This has been resolved by updating the FLA purge query to target only the intended records. | Case Management |
| INC-D884 | 972105 | 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 |
Cloud Services
24.2.4 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 |
953844 | 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-C40496 | 951910 | Hotfix utility parameter handling corrected | The prpcUtils hotfix management utility was failing with invalid parameter errors when the hotfix.accessgroup property was configured. This was caused by incorrect parameter order validation in the utility that checked the access group value instead of the operation value, and has been resolved. | Cloud Services |
| INC-C57002 | 969356 | 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
24.2.4 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C43147 | 955397 | Email draft attachments preserved correctly | Email draft attachments were being incorrectly retrieved when reopening cases, with attachments sometimes replaced or duplicated when multiple files were added to reply drafts. This was traced to pxSaveAttachmentstoDraft not updating the linkAttachment page with .pxAttachName property, and has been resolved. | Conversational Channels |
| INC-C45663 | 966557 | Migration guide provided for Digital Messaging Services | Documentation is now available for Pega Platform and Pega Customer Service applications with comprehensive guidance for successfully deploying Digital Messaging channels to higher environments. | Conversational Channels |
| INC-C45795 | 960029 | Email case timestamp made consistent | Email triage cases were displaying different create datetime values when accessed through class instances versus DISP case related views. This has been resolved by updating the the email manager portal display logic to standardize the timezone processing across all case access methods to ensure consistent timestamp display. | Conversational Channels |
| INC-C51533 | 975769 | Chat attachment and transcript delivery issues fixed | Customers were unable to download chat transcripts despite seeing "Transcript Requested" status, and agents could not deliver image attachments to customers when filenames contained hyphens in date formats like "screenshot 2025-12-19 2013". This has been addressed by updating the attachment processing logic to remove the unsupported character (the dash -) from the allowed set, to prevent creating invalid/unsupported keys that break delivery when encryption is applied. | Conversational Channels |
| INC-C51565 | 973506 | Entity mapping validation updated for assignment submissions | Assignment submissions were failing with "Invalid Request Data" errors when entities detected in channels were mapped to non-existent properties on the assignment UI. This was caused by the system attempting to submit unrelated data through the changeTracker when entity mappings referenced properties not available in the assignment context. To resolve this, the validation handling has been updated to ensure entity mappings only reference valid assignment properties before submission. | Conversational Channels |
| INC-C53198 | 973249 | Email bot triage lock management stabilized | Email bot triage was losing lock when clicking "All Case Types" in the pyTriageActionsPortal_Cases section, resulting in attachments not being transferred to newly created cases during manual triage. This has been resolved by correcting the lock management. | Conversational Channels |
| INC-C58483 | 969929 | 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
24.2.4 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B48689 | 959305 | 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 | 955988 | 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-C17807 | 926762 | 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. | Data Integration |
| INC-C19409 | 932117 | Configuration table validation messaging improved | Users were seeing duplicate error messages when working with configuration table primary keys, including both ".RecordsCode: Records Code cannot be blank" and ".pyRefToFocusKey: Records Code cannot be blank" appearing after the first validation attempt. This was traced to improper error message state management during field validation cycles, and has been resolved by updating the ValidateKeysContent activity. | Data Integration |
| INC-C25456 | 960940 | 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 |
943189 | Field flattening enabled for GenerateEForm | PDF forms were experiencing issues where filled fields would disappear when opened in Adobe Reader. Investigation showed this was caused by the lack of field flattening in the GenerateEForm activity due to change in the dependency JAR from iText to PDFBox, and has been resolved by implementing functionality similar to the existing ConcatenateEForms activity, ensuring PDF fields remain properly populated and non-editable when viewed in external applications. | Data Integration |
| INC-C26290 | 945725 | Rule creation XML display issue resolved | Rule creation XML display issue resolved When attempting to create rules in certain locked ruleset scenarios, XML content was being displayed instead of the proper rule creation interface. This has been resolved by adding an Activity-Clear-Status step in the 'pzUpdateDataTypes' activity. |
Data Integration |
| INC-C27968 | 939785 | Flag added to bypass removing duplicate rows during Insights | The "Remove duplicate rows" checkbox used in report definitions was causing visual inconsistencies when using the Insights function, especially when data was grouped in a table. This was due to the fundamental way the report definitions work, which caused the checkbox to not be consistently applied for the query that fetches groups vs the one that fetches data rows. To avoid this confusion, a an update has been made to Insights to pass a flag that always treats the "Remove duplicate rows" checkbox as false so duplicate rows are now displayed in Insights regardless of the checkbox configuration on the report definition. | Data Integration |
| INC-C28380 | 955830 | 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-C31315 | 950531 | Data table search functionality updated to skip encrypted properties | Search functionality in data tables was failing when any property column had encryption enabled, affecting both elastic search and normal search scenarios across all columns. This has been resolved by modifying the filter logic to skip to skip the properties that are encrypted from the filters that are formed in pzFilterDataTableRecords data transform when forming search filters, allowing search to work on non-encrypted columns. | Data Integration |
| INC-C34085 | 964633 | Application page initialization fixed for prediction notifications | Email notifications were not being triggered in Prediction Studio. Investigation showed this was caused by the application page not being initialized when attachment logic was invoked via batch requestor and queue activity, and has been resolved by initializing the application page to prevent null pointer exceptions. | Data Integration |
| INC-C34793 | 956665 | Server path sanitization updated | In some circumstances it was possible for the system to disclose the server path in a file upload failure error message. This has been resolved by sanitizing error messages and exceptions to display only file names instead of complete server paths. | Data Integration |
| INC-C34795 | 958633 | 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 | 956590 | 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-C40045 | 951277 | JSON data transform property reference corrected | Property references within JSON Data Transform update page actions were failing to set values correctly when the property and data transform existed in the same class. This was caused by improper property resolution during the update page action execution, and has been corrected with an update to explicitly set the Param.PageClass property from .pyPageClass to prevent null reference issues. | Data Integration |
| INC-C40236 | 960093 | 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-C40613 | 953923 | Country code SXM added | Support has been added for country code SXM (Saint Martin, Dutch part). | Data Integration |
| INC-C40677 | 960733 | 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 | 969481 | 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 | 955093 | SOAP header handling improved for optional elements | ConnectSoap rules were failing when optional header elements had no runtime values, generating "Couldn't create OMElement from string value" errors. This has been resolved by adding empty string validation to skip processing of headers with no content values. | Data Integration |
| INC-C42700 INC-C47501 INC-C48247 |
954391 961334 962391 |
Session management and requestor lifecycle improved | Users were experiencing unexpected logouts and session disruptions during active work sessions. This was traced to requestor passivation and activation processes happening during requestor lifecycle management as part of infrastructure scaling events. To address this, the requestor activation sequencing has been updated and error handling during passivation processes has been improved. Additionally, unused properties have been removed from PAL pages during passivation, and the default retry attempts for on-demand passivation have been increased to 4 to provide better resilience during node scaling operations. | Data Integration |
| INC-C44025 | 963226 | Memory management improved for strategy execution | High-volume API testing was causing out-of-memory errors with PEGA0039 alerts indicating large pzpvstream references exceeding 499 MB and sometimes 1.8 GB during strategy execution. Investigation showed that GOSProgram2 blob objects were preserving excessive memory and creating orphan entries during Java object operations. This has been resolved by implementing proper memory cleanup to remove orphan entries whenever the orphan data exceeds 10% of the actual BLOB size. | Data Integration |
| INC-C45502 | 974621 | Websocket connection stability improved during session passivation | Applications were experiencing websocket connection failures and requestor accumulation when browser sessions were being passivated during periods of inactivity. Investigation showed this was caused by Remote OnDemand Passivation jobs failing to properly clean up batch requestors when errors occurred during browser requestor passivation. This has been resolved by updating the batch requestor lock release and return to pool mechanisms. | Data Integration |
| INC-C46353 INC-C47478 INC-C56134 |
956868 957253 967024 |
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-C47145 | 961914 | 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. | Data Integration |
| INC-C4768 | 938266 | Embedded pages handling updated for REST Connector wizard | The REST Connector Wizard was generating Data Transforms that failed to properly map nested JSON objects to embedded page properties. This was traced to the handling of embedded page structures which called UpdatePage methods without child steps, and has been resolved with an update to ensure that nested JSON objects are correctly mapped to their corresponding embedded page properties in the generated data transform. | Data Integration |
| INC-C47722 | 958824 | 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-C47786 | 962433 | 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. | Data Integration |
| INC-C48714 INC-C56859 INC-C56824 |
958420 966303 973388 |
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-C49518 | 967621 | 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 | 963223 | 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 | 967707 | 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 | 966181 | Resolved memory leak in report data retrieval | Applications were experiencing out-of-memory errors when generating reports through the pxRetrieveReportData activity. Investigation showed that orphaned PageMetaDataImpl instances were accumulating in memory due to improper cleanup of temporary report pages during Page-Rename operations, with the Page-Remove calls not properly targeting the temporary report pages as configured. This has been resolved by correcting the page cleanup logic in pxRetrieveReportData to ensure temporary pages are properly removed from memory after report generation. | Data Integration |
| INC-C51762 | 967822 | Content-disposition header encoding corrected for international filenames | The Content-Disposition header was being omitted from DX API responses when downloading attachments with filenames containing national or special characters such as Polish diacritics. This was caused by character encoding issues in the header serialization logic within the servlet layer, and has been resolved. | Data Integration |
| INC-C51964 | 964268 | Insights promoted filters localization corrected | Promoted filters in Pega Insights were behaving like plain text instead of Date/Time controls when using non-English locales. This was caused by locale-specific handling issues in the filter interface, and has been resolved. | Data Integration |
| INC-C52779 | 967079 | Military time format updated to resolve single digit hours | Applications working with 24-hour time formats were displaying single-digit hours (0-9) displayed without leading zeros, which conflicted with military time standards requiring double-digit hour formatting (00-09). This has been resolved by updating the date time calendar and input display logic with a new flag 'enable24HourFormatting' which is enabled by setting the pega.u.d.enable24HourFormatting value to true in userWorkForm. | Data Integration |
| INC-C53144 | 969917 | 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-C53523 | 965231 | 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. | Data Integration |
| INC-C53572 | 965045 | Table instance synchronization fixed across cluster nodes | Database commit errors were occurring when new columns were added to FDQuestions and CRQuestions tables, with changes not reflecting properly across all cluster nodes despite successful rule imports. Investigation showed this was caused by incomplete column-to-property mapping updates when table schemas changed. This has been resolved by implementing automatic column-to-property map updates after each column change to ensure consistency across all nodes. | Data Integration |
| INC-C54480 | 964922 | Job scheduler node type configuration corrected | The job scheduler pyAxis2ConnectionPoolCleanup was failing to with the error "Job Scheduler ConnectionPoolCleanup registration failed". This was due to invalid mapped node types "RTDG,DDS,RealTime" being included in the configuration when they were not available in the cluster, and has been resolved by updating the configuration to use only valid mapped node types. | Data Integration |
| INC-C55559 INC-C42223 INC-C49731 |
964528 965426 965309 |
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-C55739 | 968691 | File listener parse segment retry corrected | File Listener was incorrectly re-reading records that were marked with the "once" checkbox during failure recovery scenarios, causing duplicate processing of clipboard parse segments that should have been processed only once. This was traced to a NullPointerException when evaluating lsf.isProccessingStatusError, and has been resolved by adding a null check so the "once" condition is properly evaluated and honored. | Data Integration |
| INC-C55752 | 971938 | Circumstanced flow action title display corrected | Flow actions using circumstanced variants were displaying incorrect titles from the base version instead of the appropriate circumstanced version, while the section content correctly loaded from the circumstanced rule. Investigation showed the title resolution logic was not properly following the same circumstance evaluation path as the section loading when flows are displayed in modal dialogs with default standard templates. This has been resolved by introducing a customizable 'when' rule to switch between doActivity and doAction APIs in the pzModalTitle control. | Data Integration |
| INC-C55924 | 968781 | Advanced search functionality corrected for data transform sourced pages | Advanced search and select controls configured with data pages sourced from data transforms were failing to return search results. This has been resolved by correcting the data page caching mechanism to ensure that searchable data pages receive the same implicit parameter treatment as queryable data pages for pagination support. | Data Integration |
| INC-C56335 | 972660 | Attachment migration updated for better locale handling | Duplicate attachment migration was failing to process all attachments when JVM was configured with non-English locales, causing only one of multiple duplicate attachments to be migrated. This was caused by a check which relied on a hardcoded English message in pzUploadAttachment activity that failed when framework messages were generated in other languages. This has been resolved by implementing locale-independent logic for duplicate attachment handling during migration. | Data Integration |
| INC-C56896 | 968977 | 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. | Data Integration |
| INC-C56940 | 968705 | 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 |
966810 968857 |
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-D113 | 974827 | Improved backwards compatibility for date property parsing | After upgrade from Pega version 8.7, applications were unexpectedly storing full ISO datetime strings in date properties when previously only the date portion was extracted from service responses. This was due to modifications in the JSON data transformation logic. To improve backwards compatibility, the JSON-to-Property date handling has been adjusted to prevent Date properties from accepting date-time strings by default, with an opt-in DSS "parseDateTimeForDateProperty" to utilize the old behavior. | Data Integration |
| INC-D6671 | 976388 | OAuth authentication support enabled for SMTP email communication | Microsoft has retired Basic authentication with SMTP protocol from March 2026, requiring applications to use OAuth authentication instead. With this update, OAuth support is provided for SMTP protocol to support using Microsoft as the email provider in the email account rule. |
Data Integration |
| PRB-B72 | 969379 | 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
24.2.4 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-C45773 |
962499 | Customer Profile Viewer persona test data usage corrected | Failures were seen in Customer Profile Viewer persona tests where the system was incorrectly querying actual Cassandra data instead of using configured persona test data when running in test mode or single action mode. This was caused by the mxIHSummaryBrowseByKeys() function not properly propagating the IH summary cache parameters in test scenarios, and has been resolved. | Decision Management |
INC-D3882 |
976061 | PMML mining model output field population corrected | Issues were seen with Predictive Model Markup Language (PMML) models generated via sklearn2pmml conversion where target fields and output fields were not being populated correctly during model execution. This was traced to improper field mapping during the PMML conversion process, and has been resolved by updating the field population logic. | Decision Management |
| INC-B51876 | 924720 | 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 | 955194 | Improved DSMClipboardPage self-diagnostics | An update has been made to enforce periodic self-diagnostics for DSMClipboardPage which will check whether the current indexed property access matches the correspondent non-indexed property access, and reports an error if there is mismatch. | Decision Management |
| INC-C22614 | 936718 | Cosmos theme localization key mapping corrected | The text "Replies to my messages" was not being properly localized in Cosmos. This was traced to the getLocalisedText function in the pzRetrievePulseFeed activity not referencing the correct pyGenericFields key, and has been resolved by updating the activity to differentiate the handling of traditional and Constellation scenarios. | Decision Management |
| INC-C31299 | 956423 | 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 | 955305 | 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-C34067 | 951362 | Strategy compilation performance optimized for large operations | Very long compilation times were occurring for Globally Optimized Strategy (GOS) operations. This occurred when the context manager contained duplicate context variables with the same name in a Deque structure. To resolve this, Collectors.toMap() has been replaced with a manual loop using putIfAbsent(). This preserves only the first occurrence of each variable name (representing the latest context variable in the Deque) and prevents duplicate key exceptions. In addition, several related areas have been refactored for improved performance and robustness. | Decision Management |
| INC-C36371 | 957476 | 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-C38194 | 954281 | Resolved invalid parameter error for eligibility data flow | After update, data flows were encountering InvalidParameterException errors and failing to persist error records to the data flow run error report. Investigation showed that on change of treatment eligibility, the 'when' rule selection was picking up the pylabel, resulting in the decision data rule holding the label instead of the name in the EligibilityConditions property. This has been corrected. | Decision Management |
| INC-C38444 INC-C57391 |
956632 966777 |
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-C40466 | 963976 | 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 | 962941 | Handling updated for revision simulation empty segment failures | Revision simulations were failing and corrupting the revision case when configured with empty segment datasets.This was caused by the pyTriggerPerformanceTest activity completing assignments even after simulation failures, leaving error messages on the page without providing navigation options back to the pyViewRevision flow, and has been resolved by updating the handling for pyViewRevision so that if the simulation fails, the process remains in the viewRevision stage instead of progressing to simulateRevision. Validation has also been added to ensure the segment is verified before creating the simulation. | Decision Management |
| INC-C42350 | 954137 | Prediction model documentation updated | The documentation for Strategy design with multiple Predictions has been updated to explicitly warn against using identical alternative labels in the same strategy execution path to avoid the processing of duplicate responses for the underlying models. | Decision Management |
| INC-C42626 | 964986 | Screen refresh performance improved after artifact generation | Operation management cases were experiencing significant slowness due to large numbers of DDR records and database queries exceeding 5 second thresholds, with screens not refreshing properly after artifact generation. Investigation showed this was caused by inefficient DDR queries and circumstance value handling across rule versions. This has been resolved by optimizing database query performance and implementing proper screen refresh mechanisms post-artifact generation. | Decision Management |
| INC-C42945 | 954046 | Strategy expression null handling updated | After update, strategy expressions containing conditional date formatting operations were throwing null pointer exceptions. This has been resolved by updating the implementation to use Objects.toString() which safely handles null values by converting them to the string "null". | Decision Management |
| INC-C43226 | 964640 | 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 | 955268 | 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 | 955707 | 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-C45511 | 961112 | 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-C45865 | 961337 | Kafka serialization handling corrected for empty PageList properties | After update, Kafka serialization was failing when non-null PageList properties were left without values. This was caused by the DSM Clipboard page conversion process incorrectly removing empty properties and lists for optimization, and has been resolved by modifying the process to maintain empty properties and lists as defined on the original page. | Decision Management |
| INC-C45993 INC-C55321 |
960780 965969 |
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 |
960475 963156 |
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 |
960634 966372 |
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 | 961361 | 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-C51825 INC-C58870 |
967049 967995 |
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-C51864 | 961979 | 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-C52034 INC-C54080 |
960879 963991 |
Batch dataflow thread setting correctly honored | The data flow thread count environment setting was not being applied for batch runs. This has been resolved by moving the thread count population logic from run creation time to run initialization time, ensuring that environment variables are properly consulted when initializing batch runs. | Decision Management |
| INC-C54551 | 965983 | 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 | 967017 | 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-C56916 | 965847 | 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 | 967572 | 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 | 966712 | 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 |
968117 968356 |
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 | 971539 | Handling added for non-time-based UUIDs in ADM commit log processing | Predictive Decision Composer was experiencing UnsupportedOperationException errors during model updates when processing non-time-based UUIDs in the commit log system. This was caused by the TimeUUIDUtils attempting to extract timestamps from standard UUIDs rather than time-based UUIDs, and has been resolved by implementing proper UUID type detection and handling for non-time-based UUIDs. | Decision Management |
| INC-D1441 INC-D1181 |
973011 973533 |
Repository based case attachments corrected for email notifications | Email digest notifications from Prediction Studio were being received but the attached CSV files were appearing as error files and could not be opened properly when repository-based attachments (pegacloudfilestorage) were being used. Investigation showed that the GenerateMailAttachment activity was only setting the pycategory field on the Link-attachment record while leaving the pxStorageType field blank, causing the content retrieval logic to fail in determining the correct handler for repository-stored files. This has been resolved by updating the pzGenerateMailAttachment activity to conditionally populate the pyStorageType field. |
Decision Management |
| INC-D1645 INC-D1645 |
974615 979728 |
Deserialized JSON date field handling updated | Data flows processing JSON records with date fields were failing when attempting to save deserialized date properties to DDS datasets, resulting in NullPointerException errors. This was traced to null values during date field conversion in the JSON data transform process when using TimeOfDay properties in the Strategy Result class, and has been resolved with an update to enhance logging, null date handling, and exception messages. | Decision Management |
| INC-D2189 | 973028 | 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-D2309 | 974642 | Chart image export functionality restored | After update, the chart image export functionality was producing errors or generating blank PNG files when attempting to save charts as images. This was caused by the SVG→canvas conversion relying on an older synchronous call which could lead to the form being submitted before rendering completed. To resolve this, the FusionCharts export helper has been updated to work with the newer canvg API and the export flow has been made asynchronous so the image is rendered before form submit. | Decision Management |
| INC-D2667 | 976322 | Job scheduler check added for archive folders before purge | Daily job scheduler RemoveImportJobFilesAndProcesses activities were failing due to missing ArchivedDataFiles folders when data jobs were created but no ingestion occurred. This was caused by the system attempting to purge archive folders that were never created, and has been resolved by implementing proper folder existence checks before attempting purge operations. | Decision Management |
| INC-D3944 | 973902 | Kafka dataset migration compatibility updated | Publishing messages to Kafka Data Sets was failing consistently with the error "IllegalArgumentException: No enum constant com.pega.dsm.dnode.api.dataset.kafka.MessageHeaderDataFormat" after moving the Kafka topic from one data center to another. The error occurred during message configuration extraction when Pega attempted to validate the Message Header Data Format, with the system expecting values like KVLIST or Custom but encountering an unsupported enum constant at runtime. This was traced to a compatibility issue when Kafka data sets created in Pega 8.5 were imported into Pega 8.6+ environments, and has been resolved by addressing the enum validation logic to properly handle legacy data set configurations. | Decision Management |
| INC-D5368 | 976690 | Updated error handling for ADMDataSetSaveOperation | Data flow threads were becoming stuck in an unsafe park state after ADMDataSetSaveOperation encountered a ConcurrentModificationException during realtime data flow execution. This has been resolved by adding exception handling in SaveStageProcessor to properly release the latch. | Decision Management |
| INC-D6631 | 976645 | Proposition filter explanation values corrected for page collections | When evaluating proposition filters with conditions against page lists accessed through property reference chains, Engagement Policy explanations were displaying an accurate filter status, but the actual value was consistently displaying as "0" instead of showing the correct number of pages in the page list that satisfied the criteria. This has been resolved by correcting the explanation calculation logic so that actual values now properly reflect the number of qualifying pages in the collection when accessed through property reference chains. | Decision Management |
| RCA-C1501 | 958411 | 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 |
Low-Code Application Development
24.2.4 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C21025 | 954106 | URL error message security updated | In order to improve security, the ShowMessage HTML rule in @baseclass and Code-Pega-List has been updated to remove requestor and operator details. | Low-code App Development |
| INC-C28803 INC-C24072 |
938721 948363 |
Null handling updated for case creation | The create flow was not being automatically added when creating case types in workspaces, resulting in save errors. This was caused by incomplete workspace initialization logic during case type creation, and has been resolved by adding null checks for ThreadContainer.get() and a check whether the operator ID .pyuseridentifier is empty. An additional issue with null pointer errors being generated due to uninitialized requestor components when accessing developer preference data pages has been resolved by improving exception handling to prevent unnecessary logging of non-functional errors. | Low-code App Development |
| INC-C36061 | 958923 | 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 | 953243 | 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 | 955080 | 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 | 956970 | Division name validation handling updated | Application creation was failing with ruleset validation errors when division names contained spaces while using the generate division layer option. This was caused by inconsistent space handling between different validation activities, where one removed spaces while another retained them. This has been resolved by standardizing the space handling logic across all division name validation processes. | Low-code App Development |
| INC-C45469 | 965348 | pyRelativePath property serialization issue resolved | Applications were experiencing PageCannotBeSerializedForPassivationException errors with the message "Property not serializable: pyCorrList.pxResults(1).pyRelativePath" when sending correspondence with the Tracer enabled, causing screens to hang and preventing rule access. Investigation showed this was caused by the pyRelativePath property being added to clipboard pages during rule checkout but not being present in the Rule-Obj-Corr class hierarchy or its parent classes, making the property non-serializable during passivation. This has been resolved by adding the pyRelativePath property to the @baseclass to ensure proper serialization support across all rule types. | Low-code App Development |
| INC-C51416 | 965512 | Font size scaling issue resolved in RTE-generated Word documents | When using Rich Text Editor (RTE) properties with custom font styling and sizes in Microsoft Word document templates, the generated documents were experiencing incorrect font size scaling where the configured font size was being reduced by a factor of 0.75. This was caused by improper handling of font size conversion between the RTE formatting and the Word document generation process which applied an unintended scaling factor during the conversion. This has been corrected by updating the logic to maintain the original formatting specifications from the Rich Text Editor. |
Low-code App Development |
| INC-C52261 | 966733 | 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 | 965781 | 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-C55854 | 967378 | Excel decimal value parsing precision corrected | Excel file parsing was altering decimal values by adding extra zeros, with values like 0.00001 becoming 0.000010 in the clipboard. This was caused by the internal clipboard API treating decimal values as doubles and converting them to BigDecimal during the parsing process, which added trailing zeros. This has been resolved by implementing proper decimal handling in the ExcelUtils.java parsing process to preserve original precision. | Low-code App Development |
| INC-C56696 | 970565 | Compliance score purge error handling improved | Systems were generating EXCP0001 exceptions regularly when the pzPurgeComplianceScore activity attempted to delete non-existing compliance score instances. This has been resolved with an update that enables mutual exclusion for agent queue execution, ensuring the agent runs on only one node at a time. | Low-code App Development |
| INC-C57070 | 967147 | Cross-site scripting protections updated for tracer settings | Cross-site scripting protections have been updated for the TraceOptionsDialog stream. | Low-code App Development |
| INC-D1150 | 971828 | Cross-site scripting updated in App Studio | Cross-site scripting (XSS) protections have been updated for App Studio. | Low-code App Development |
Mobile
24.2.4 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C21926 | 929878 | Mobile create menu positioning corrected | The create menu overlay was displaying in incorrect positions when accessed from mobile footer navigation, sometimes overlapping with the footer or extending beyond screen boundaries. This was caused by forced width styling conflicting with dynamic position calculations, and has been resolved by updating the CSS positioning logic. | Mobile |
| INC-C25264 | 935511 | 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-C37214 | 962062 | JavaScript execution continues during SLA message display | JavaScript functionality was becoming unresponsive when SLA messages were displayed, preventing task completion in mobile applications used for field work. This has been resolved by modifying the SLA message display mechanism to allow continued JavaScript execution. | Mobile |
| INC-C42855 | 955893 | 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 | 971403 | Back button visible for notification-launched cases | The back button was not appearing on some mobile headers when cases were launched through push notifications. This was traced to an uncaught exception which prevented the web views from loading after a notification was clicked in certain scenarios, such as users being logged out during notification receipt. As a result, the mobile header navigation was not properly initialized and there were no previous navigation items were available to return to. This has been resolved. | Mobile |
| INC-C58580 | 968183 | Mashup modal dialog positioning corrected for mobile screens | Modal dialogs containing file upload controls were appearing at the top of mobile screens in mashup scenarios, making the loading indicator invisible to users during file uploads. This was caused by hardcoded vertical alignment and padding styles in the pega_ui_modaldialog component, and has been resolved. | Mobile |
| INC-C58641 | 974500 | Mobile overlay display corrected | Applications were experiencing modal popups that occupied the entire height of mashup screens on mobile browsers when using the overlay configuration for validation alerts. This has been corrected with a phone-specific override so local-action modal wrappers/content don’t force full height. | Mobile |
Project Delivery
24.2.4 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C42022 | 955117 | 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-C42146 | 955779 | OAuth authentication profile documentation updated | The documentation for Configuring an OAuth 2.0 authentication profile has been updated to explicitly specify that scopes must be configured in identical order between the Authentication Profile and Authentication Service, and that all required scopes must be granted in the Identity Provider. | Project Delivery |
| INC-C44913 | 959813 | 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 |
Reporting
24.2.4 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| EA-C6832 | 959308 | 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 | 945928 | Scheduled insights evaluate date filters correctly at runtime | Scheduled insight exports were producing identical data sets across multiple runs when relative date filters such as "Current day" were applied. Investigation showed this was caused by the system transforming relative dates into static values at the time of schedule creation rather than dynamically at each execution. This has been resolved by replacing the transformation of relative dates during the scheduling process with a new activity that dynamically converts relative date filters to appropriate static date literals using the current server datetime at the time of each scheduled export execution. | Reporting |
| INC-C31709 | 952831 | PDF margin settings corrected to allow zero values | PDF documents were not respecting explicitly set margin values of zero. Investigation showed the PDFUtilsImpl Java file contained a condition that applied default parameters when margin values were set to zero or less. This has been resolved by modifying the logic to properly honor explicitly set zero margin values in PDF generation. | Reporting |
| INC-C34148 | 962672 | 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 | 955704 | 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-C38967 | 958666 | 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 | 963531 | 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 | 955909 | 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-C42060 | 959727 | Worklist column grouping functionality corrected in Constellation | Attempting to group columns in Worklist views within Constellation resulted in the error ""Expecting input data of type Page (Pega-API-DataExploration-Request) and received {...}". Investigation showed this was due to the value being passed as an integer while the left-hand operator expected a text type. This has been resolved by modifying the pxHourOfDay function alias to return the proper integer type. | Reporting |
| INC-C42154 | 955202 | Content security policy commenting format updated | FusionCharts JavaScript was triggering Content Security Policy violations due to commented localhost URLs in the code. This was caused by single-line comment syntax that CSP parsers were interpreting as active URLs, and has been resolved by converting the single-line comments to block comment format to prevent CSP interpretation as executable content. | Reporting |
| INC-C44676 | 957310 | Search dropdown functionality restored for Explore Data | The search dropdown in the Explore Data landing page was disappearing when clicked in applications running on UI-KIT with Explore Data Landing Page enabled. Additionally, the Data pages menu option in AppStudio Explore Data was not responding to mouse clicks, though keyboard navigation was functioning properly. This was traced to the handler for the focusin/mouseup event not correctly determining whether the event happened within a tracked element, and has been resolved by updating the target check for more accurate detection across shadow boundaries. | Reporting |
| INC-C45896 | 960618 | 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 |
957462 959943 |
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-C47847 | 964339 | Explore Data result counts made consistent | The Explore Data functionality was displaying incorrect insight counts in App Studio and inconsistent behavior in end user portals, showing correct counts initially but higher counts after refresh. This was traced to post-processing logic in the Insights and Dashboards list data pages, and has been corrected by removing those activities from this view to avoid confusion. | Reporting |
| INC-C50853 | 960278 | 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 | 960308 | 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-C51966 | 962723 | 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-C52711 | 964721 | Filters cleared when changing tabs | Filters configured within specific tabs were incorrectly influencing other tabs in inline dashboard templates, causing unintended data filtering across multiple tab contexts. This was caused by shared filter state management across tabbed interfaces using the same data object source, and has been addressed with an update which will clear all dashboard filters so any promoted/active filters from the previous tab will not be carried over to the next tab. | Reporting |
| INC-C53493 | 962970 | 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 | 965172 | 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 | 968112 | 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-C58702 | 969717 | 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 | 971795 | 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-C60008 | 970770 | 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-C9570 | 918575 | Multiple filter values correctly translated | Localization was not correct when filtering a report on multiple selected values. This was due to multiple values in the filters of the report definition being treated as a single value with comma separation, and has been resolved by updating the logic in the RRFilters_Logic Control. | Reporting |
Security
24.2.4 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C22149 | 928469 | Documentation updated for BLOB encryption data key creation | The documentation for encrypting the storage stream (BLOB) has been updated to clarify that the BLOB encryption process cannot generate a new Pega Platform data encryption key and uses the existing CDK. Information is provided to assist with manually generating a new data encryption key. | Security |
| INC-C23350 | 929154 | Improved regex algorithm for masking logic | Users were unable to login when DEBUG logging was enabled for the HttpUtilities class. This was due to complex pattern matching operations exceeding the regex processing capacity in the requestor ID masking logic and causing PatternSyntaxException errors. The regex algorithm has been updated to improve performance. | Security |
| INC-C25230 | 934937 | File upload security validation enhanced | Security has been updated by improving the logic checks to prevent the upload of malicious files. | Security |
| INC-C29028 INC-C59122 |
945851 968793 |
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 |
942412 971650 |
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 | 952160 | 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 | 955863 | OIDC authentication flow corrected for multiple JWT authorization servers | OIDC authentication was failing with "Unable to execute OIDC flow: Caught exception while parsing the id token" errors when environments were using multiple OIDC authorization servers with JWT-based client authentication. This was traced to the handling for TokenProfileCacheImpl.java which incorrectly merged JWT profile details from different authorization servers when alternating between OIDC flows, resulting in invalid client assertions being sent with incorrect issuer claims. This has been corrected to ensure each OIDC flow maintains its proper JWT profile isolation. | Security |
| INC-C36852 | 954972 | Report definition class hierarchy handling updated for use with Access Control Policies | Report definitions were failing with pxObjclass exceptions when Access Control Policies (ACP) were defined on parent data classes in complex inheritance hierarchies. The issue occurred specifically when data classes served as parents to abstract platform classes that contained report definition subclasses, and was caused by improper class resolution when ACPs were present in the inheritance chain. This has been resolved by adding handling to prevent .pxObjClass exceptions in the subclass report definition when an ACP exists on the top Data-class. | Security |
| INC-C37512 | 957238 | 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 | 958256 | 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-C39151 INC-C40806 |
953619 955872 |
Delegation security token handling corrected | Applications were experiencing SECU0019 "The mashup is not consistent with the latest security enhancements" alerts and blank screens when attempting to edit data type rules from delegated landing pages in blended UI environments. This was traced to the system incorrectly adding an active CSRF token (pzCTkn) to URLs when the signature token was already present, and has been resolved by modifying the UI logic to prevent duplicate token parameters from being sent. | Security |
| INC-C39326 | 955503 | History added for operators automatically disabled by security policies | When the Operator disablement policy was enabled with the "Number of days of inactivity," the DisableDormantOperators Agent would run at the appropriate time and invoke the pzDisableDormantOperators activity without any audit trail or history records being maintained. This was caused by the DisableDormantOperators agent's pzDisableDormantOperators activity lacking logic to update operator history records, and has been resolved by adding history tracking functionality to the operator disablement process. | Security |
| INC-C39526 | 953515 | Modified confusing URL error message | URL validation was incorrectly displaying error messages that indicated FTP protocol could be used when FTP was not supported. This has been resolved by removing the reference to FTP in the error message presented to the user if the URL is not valid. | Security |
| INC-C39718 | 963102 | Operator profile security updated | Cross-site scripting protections have been updated for operator name fields. | Security |
| INC-C43863 | 958180 | 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 | 958203 | 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 |
961417 961491 |
CSRF validation security enhanced for DX APIs | CSRF validation checks have been updated for hybrid apps DX APIs. | Security |
| INC-C46461 | 960575 | OIDC dynamic parameter processing enhanced | Dynamic parameters for OIDC authorization endpoints were being treated as literal strings rather than processed values, and authentication profiles were requiring quotes for constants after hotfix application. Investigation showed this was caused by incomplete parameter expression processing in the Authentication Service. This has been resolved by correcting the logic to properly process parameters as expressions. | Security |
| INC-C46596 | 958260 | Security updated for DisplayAuthScreenSelector | Cross-site scripting protections have been updated for DisplayAuthScreenSelector. | Security |
| INC-C47105 | 957068 | 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 | 962490 | Mashup page security updated | Cross-site scripting protections have been updated for the pzLoadMashupPage activity. | Security |
| INC-C50018 | 962232 | 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-C51161 INC-C46454 |
960711 958150 |
Authentication scheme selection corrected for Constellation applications | After update, PRAuth-based Constellation applications were incorrectly displaying the Web-Login (PRBasic) page during reauthentication instead of the expected authentication selector screen, preventing users from accessing SSO login options when switching applications or using application alias URLs. This was caused by the authentication scheme selection logic not properly preserving the scheme type during reauthentication processes, and has been resolved in addition to updating the default scheme for Constellation apps to PRAuth. | Security |
| INC-C52805 | 962621 | 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 | 962937 | 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 | 968142 | Access security updated | An update has been made to improve security access controls to ensure authentication and proper authorization. | Security |
| INC-C54303 | 964592 | 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 | 964318 | 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 | 970345 | 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 | 964489 | 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-C56768 | 975758 | Pega Desktop security updated | Cross-site scripting protections have been updated for Pega Desktop support. | Security |
| INC-C57934 | 966820 | 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 | 968776 | Prediction Studio security updated | Cross-site scripting protections have been updated for Prediction Studio. | Security |
| INC-D225 | 974812 | SSO re-authentication flow corrected | OIDC single sign-on was working for initial authentication but failing during token expiration re-authentication scenarios, generating the error "Exception is thrown for OIDC flow java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "ssoAttrValues" is null "when accessing SSO attribute values. This has been resolved by updating the null checking and error handling in the OIDC re-authentication process. | Security |
| INC-D2915 | 982142 | Documentation clarified for OAuth authentication profile configuration | The OAuth 2.0 authentication profile documentation has been updated to clarify that multiple authentication profiles cannot use identical client ID, grant type, scope, and tenant ID combinations. | Security |
| INC-D5096 | 975411 | OAuth2 refresh token checkbox now defaults to disabled | Constellation applications were experiencing frequent "Login to Continue" prompts due to short-lived refresh tokens inherited from Identity Providers. This was caused by the "Set refresh token expiry from IDP session expiry" checkbox being enabled by default in automatically generated OAuth2 Client Registration rules. To address this, the OAuth2 client registration request template has been modified to set use_idp_session_expiry to false by default, allowing the standard 24-hour token expiry to apply unless explicitly overridden. | Security |
| INC-D5237 INC-D2167 |
975552 975010 |
API authentication performance improved | REST API calls using OAuth 2.0 token authentication were experiencing significant delays due to cache lock acquisition failures. This was caused by synchronization issues in the OAuth2 cache implementation following Hazelcast decommissioning, and has been resolved by updating the cache lock and node synchronization mechanisms. | Security |
System Administration
24.2.4 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C47204 | 960044 | Axios updated | The Axios library has been updated. | System Administration |
| INC-C55525 | 965523 | 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 |
User Experience
24.2.4 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B19295 | 965886 | Access role description corrected for clarity | Viewing the PegaRULES:TestID access role description in the history tab indicated "Role used by Pega developers which grants privilege to see all Threads in the clipboard viewer. May be used for other things later." This was a misleading description caused by outdated documentation and has been updated to display "Please refer pxTestID privilege for description". | User Experience |
| INC-C11797 | 919479 | Skip links accessibility navigation corrected | Tab navigation was bypassing the skip links target element when initially loading the user portal. This was caused by improper focus handling during initial page load, and has been resolved by updating the handling for pyIsWindowStealFocusInIEAllowed to ensure skip links are properly accessible on first navigation attempt. | User Experience |
| INC-C12345 | 917817 | 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-C15899 | 927343 | 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-C18782 | 928592 | 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-C21617 | 931578 | Currency formatting in localized dynamic layouts corrected | Currency values were displaying incorrect formatting when entered in repeating dynamic layout rows, particularly affecting locales where the grouping is "." and the separator is ",". Investigation showed the readonly formatter was not properly handling locale-specific formatting rules in dynamic contexts, and this has been resolved with the addition of a check to verify if the value is already formatted. | User Experience |
| INC-C24844 | 952282 | Modal dialog form submission with filepath control made more robust | Values entered in any control were not being submitted after the initial refresh if a FilePath control was used in the modal dialog to attach a file and the option "SetEncodingNow" was enabled for the FilePath control. This was traced to the form handling when filepath controls were embedded in modal contexts. This has been resolved by updating the handling for hasFile so the request correctly uses FormData and preserves the file-upload flow. | User Experience |
| INC-C25293 | 954406 | 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-C26736 | 937879 | Corrected focus management | The scrollbar was not automatically returning to the top of the page after form submission, causing users to remain at their current scroll position instead of being repositioned to view the top of the updated content. In addition, radio buttons marked as mandatory were not getting selected on the first attempt when positioned as the first field on a form, forcing users to make a second selection attempt. These issues have been resolved by updating the handling for focus and blur in forms. | User Experience |
| INC-C28836 | 940612 | Modal close button accessibility behavior corrected | Modal dialog close buttons were unexpectedly activating on mouse down instead of mouse up when using pzModalTemplate, though it did not occur with the close icon in pyFlexModalTemplate.pzModalTemplate. The event handling inpzModalTemplate has been updated to correct this issue. | User Experience |
| INC-C29841 | 942494 | 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-C31047 | 943892 | Optimized grid focus retention fixed | After closing modal dialogs launched from optimized grid rows, the focus indicator was not returning to the originating row. This has been resolved by updating the handling for the display border on the focused grid cell when modal is launched and closed from that cell. | User Experience |
| INC-C31256 | 945359 | 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-C32472 | 947606 | Caret symbol visibility restored in user views | The caret symbol was disappearing when specialists changed personalized views, preventing proper navigation between view options. This was caused by the parameter page not being properly forwarded during view transitions, and has been resolved. | User Experience |
| INC-C32635 | 943002 | 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-C34626 | 954557 | Constellation view template error resolved | The message "Error in UI Authoring: Mismatch between View's template name and Template definition name!" was generated when attempting to configure the Transfer Assignment view (pyTransferAndAdjustSLA) while using certain Constellation CDN URLs. This was traced to template definition mismatches when accessing views through specific Constellation service URLs versus the standard CDN, and has been resolved by updating the template name resolution logic. | User Experience |
| INC-C350 | 967978 | 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 | 949343 | 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 |
957418 | 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 | 955340 | 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-C36899 | 954164 | Duplicate case search results refreshed properly after input changes | When users navigated back to modify search inputs in a duplicate case detection process, the duplicate case list was not updating to reflect the new search criteria and continued showing results from the previous search until a browser refresh was performed. Investigation showed the duplicate case view was not properly refreshing when input values changed during backward navigation in the process flow. This has been resolved by ensuring the duplicate case search results are properly refreshed when users modify input values and re-execute the search step. |
User Experience |
| INC-C36919 | 949467 | 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 | 960543 | Constellation tab count refresh control added | Tab counts in landing pages were not refreshing when underlying table data changed, causing user confusion as displayed counts remained stale even after bulk actions modified record quantities. This was due to the behavior of thread-level data pages: when a data page is configured to reload once per interaction, it may not always refresh as expected during complex interactions or when navigating between different views. Additionally, if the UI is not set to refresh automatically upon returning to the tabbed view, the count will remain unchanged until a manual refresh of the browser is performed. In order to address this limitation, the setting "pyAutoUpdateLandingPageTabCounts (Boolean)" has been added which will cause the TabbedPage template to refresh the tabCount when case/process events have been triggered. | User Experience |
| INC-C37020 | 956354 | Hovering text color change supported for custom layout group | Hovering font color changes were not applying to custom layout group format headers when users moved their cursor over the elements. This has been resolved by adding the necessary CSS for hovering text color change for the tabs | User Experience |
| INC-C37240 | 954001 | Modal dialog submission behavior fixed | Modal dialogs launched via openLocalAction API were displaying blank screens after submission. Investigation showed this was caused by an overly broad clearView flag condition that was clearing screens inappropriately in modal contexts. This has been resolved by adding a condition to execute clearing the view only if activeContext has 'workarea' in it to ensure clearView only applies to appropriate review mode scenario | User Experience |
| INC-C37604 INC-C56603 |
959852 967786 |
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 INC-D1724 |
954551 975722 |
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 | 951864 | 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 | 954098 | 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 | 949847 | 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 | 955111 | 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 | 952185 | 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 | 950221 | 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 | 960840 | 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-C40744 | 951730 | Page focus behavior improved | Page loading was automatically focusing on h3 table label elements instead of appropriate form controls. This has been resolved by updating the focus handling logic to target appropriate interactive elements on page load. | User Experience |
| INC-C40876 | 966071 | 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-C40887 | 952502 | Rich Text Editor resizing constrained in multi-column layouts | Rich Text Editors in two-column layouts were expanding beyond their designated column boundaries when resized, overlapping adjacent fields and disrupting form layout. This was caused by insufficient boundary constraints in the resize functionality for scenarios with multiple Rich Text Editors, and has been resolved. | User Experience |
| INC-C41144 | 956427 | 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-C41196 | 960769 | Advanced search group switching improved | When switching between search groups in advanced search functionality, manual filter reset was required before additional searches would function properly. Investigation showed this was caused by improper state clearing when transitioning between search group configurations. This has been resolved with an update to ensure the transient container data is refreshed by automatically resetting the search state during group transitions. | User Experience |
| INC-C41475 | 954828 | 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 | 960827 | 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 | 954554 | 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-C42000 INC-D3084 |
954027 975977 |
Dirty popup handling corrected for "close all" operations | When multiple tabs were opened in the portal and the "Close All" option was selected, no confirmation popup appeared for tabs with unsaved work. This was traced to the handling for the dirty state when a section or control had a post value or refresh section action configured. To resolve this, the logic has been updated for range controls along with the AnyPicker and Slider components. | User Experience |
| INC-C42060 | 965189 | 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-C42559 | 956529 | Post-processing methods fixed for optional actions in interaction cases | The post-processing methods in an intent case did not execute as expected when optional actions were performed within an interaction case, but did trigger when optional actions were launched directly from the intent case. Investigation showed this was caused by an issue with workarea context in the save assignment function, and has been corrected. | User Experience |
| INC-C42884 | 953776 | User reference display names corrected in insight tables | User reference properties in Constellation insight tables were displaying operator IDs instead of readable display names when rendered in home widgets. This was traced to the insight table component not properly resolving user reference field display labels at runtime, and has been resolved. | User Experience |
| INC-C43151 | 959971 | 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-C43193 | 956068 | Japanese error message display corrected | Error messages in Japanese were displaying vertically instead of horizontally in error banners when multiple error messages appeared on screen. This was caused by CSS text orientation issues specific to Japanese character rendering in the Constellation UI, and has been resolved by updating the CSS to address banner text wrapping. | User Experience |
| INC-C43329 | 956109 | 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-C43413 | 954821 | 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-C43656 | 960416 | PDF attachment loading issue resolved | After using the popup Attachment field in an Embedded List Table (Editable Modal type) to add a record, the uploaded PDF was displayed as attached but did not open. The file remained in a loading state both from the table view and edit popup. This has been resolved by syncing the modal’s “local files” view with the Redux-backed attachments list. | User Experience |
| INC-C44604 | 954541 | Constellation SLA deadline calculation corrected for assignment widgets |
Assignment SLA deadlines were displaying incorrect due dates in Constellation, showing 2-3 additional days beyond the configured deadline values. When assignment SLAs were configured with deadline intervals of 19 or more days, the system was adding extra days to the original SLA due dates - for example, a 24-day deadline would display as 27 days, and a 30-day deadline would show as 32 days. Investigation showed this was caused by incorrect relative time token calculations in the Constellation DateTimeDisplay component while the underlying pxGoalDateTime and pxDeadlineDateTime values remained accurate in the assignment XML. This has been resolved by modifying the way relative time tokens are calculated in the Constellation components, ensuring that displayed SLA due dates now match the configured deadline values in both Case Review and Perform modes. | User Experience |
| INC-C44746 | 955164 | 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-C45192 | 958221 | List view editing error resolved | Sporadic internal errors indicating "The reference $key is not valid. Reason: unexpected character '$' at position 0" were appearing when editing items in list views after applying and clearing filters. This was traced to the refresh callback that performs an updateRow operation not correctly maintaining the key for the particular row, resulting in a failed data page call. This has been resolved by updating the table refresh behavior after row edit/delete actions in repeating structures. | User Experience |
| INC-C45205 INC-C45466 |
957535 956976 |
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. | User Experience |
| INC-C45450 | 957862 | 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 |
955324 955843 |
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 | 955634 | 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 | 960604 | 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 | 957812 | 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 | 959525 | 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 | 963326 | 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 | 961403 | 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-C46097 | 957299 | Currency field digit capacity corrected | Currency fields were displaying validation errors when attempting to enter high-value payments, accepting only 7 digits before the decimal point instead of the expected 10 digits. This was caused by the field validation logic treating the character limit as inclusive of formatting elements rather than restricting only the digit count, and has been resolved by modifying the currency field validation to properly accommodate 16 digits while maintaining appropriate formatting constraints. | User Experience |
| INC-C46570 | 967252 | Personalized table harness context persistence corrected | Personalized tables were changing to incorrect harness contexts after page refresh or tab switching when the table was inside a dynamic layout and had defer load option enabled, causing created views to become invisible to users. This has been resolved by adding proper harness name parameter handling so personalization views can be saved/retrieved consistently across contexts (initial harness launch vs. inside-case rendering). Debug logging has also been added around harness parameter resolution. | User Experience |
| INC-C46701 | 960156 | 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-C46979 | 957635 | 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-C47230 | 960177 | Corrected Constellation summary panel blank record | Blank rows were appearing in Constellation summary panels after deleting records from pagelists, showing empty table entries alongside valid data. This has been resolved by adjusting the instruction-submission logic to allow “page instructions” to be sent for editable list-reference fields. | User Experience |
| INC-C47257 | 959030 | 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 | 958711 | 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-C47590 | 960219 | 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-C48174 | 965391 | Updated handling for portal/thread context in URL mapping scenarios | Applications were experiencing failures where publish notifications were not reaching screens when using URL mapping functionality. This was traced to issues in the notification delivery mechanism for URL-mapped scenarios, and has been resolved by updating the logic in the Data-Portal.ShowSpaceHarness activity to better handle MTSP (multi-portal session) behavior and maintain the portal/thread context when an auto-generated thread (isAutoThread) is involved. | User Experience |
| INC-C48743 | 959335 | Table delete column accessibility enhanced | Screen readers were unable to identify delete column headers in configurable tables due to missing accessibility labels. This has been corrected. |
User Experience |
| INC-C48771 | 961617 | Auto-fill behavior corrected | After Google Chrome updates, unsupported auto-fill was being allowed which resulted in unexpected behaviors. This was due to browser changes that were no longer honoring the previous settings, and has been resolved. | User Experience |
| INC-C48945 | 958227 | Bulk action record limit error addressed | Bulk actions were failing with "Narrow the query to 5000 records" error messages even when selecting fewer than 250 records from datasets containing more than 5000 total records. This has been resolved by refreshing the list view after bulk action execution. | User Experience |
| INC-C48949 | 962664 | 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 | 960863 | 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 | 963721 | 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 | 962919 | 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 | 967238 | 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-C50000 | 962309 | Task list refresh corrected | The task list UI was only partially refreshing when using pxC11NPublishMessage, with stage progression indicators not updating properly despite assignment transitions completing successfully. This was caused by incomplete UI refresh scope in the publish message handling, and has been resolved by adding a React useEffect that updates internal state whenever the stageID prop changes. | User Experience |
| INC-C50675 | 964413 | Date time spinner year restriction corrected | Date time controls with spinner navigation were displaying additional years beyond the current year even when configured to restrict both previous and future years to zero. This has been resolved by adding a "restrictToCurrentYear flag" to restrict the date range in spinner mode when 0 is set for both next and previous. | User Experience |
| INC-C50741 INC-D851 |
961540 970921 |
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 | 960784 | 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-C51769 | 962274 | 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 | 965620 | 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 | 963026 | 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-C52369 | 977913 | Constellation hidden mandatory field validation corrected | Applications were experiencing validation errors on mandatory fields that had been configured as hidden in Constellation UI due to the validateHiddenField configuration setting not being properly respected. This has been resolved by updating the field validation logic. | User Experience |
| INC-C52455 | 966573 | 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 | 966066 | 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-C52811 | 961972 | 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-C52940 | 969186 | Summary panel widget data page loops eliminated | Custom widgets in pySummary panels were causing infinite data page reload loops when source data pages were missing or blocked, and were causing validation messages to disappear immediately. This was traced to non‑stable React keys causing the widget/component(s) to unmount + mount repeatedly, which in turn made a useEffect run multiple times, triggering multiple network calls. This has been resolved with an update which will generate a new unique key on each render with a stable key derived from the component configuration. | User Experience |
| INC-C53192 | 968603 | 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-C53585 | 973720 | Rich Text Editor spellchecker issue corrected | The spellchecker in the Rich Text Editor was not flagging any misspelt words starting with upper case 'R'. This was caused by a faulty regex pattern in the spellchecker_v2 file, and has been resolved. | User Experience |
| INC-C53744 | 965114 | File validation error messages localized | Attachment validation error messages such as "File is too big" and "File has invalid extension" were not being properly localized. This has been corrected. | User Experience |
| INC-C53759 | 963252 | Embedded data modal submission fixed | Auto-populated embedded data values in modal dialogs were not updating in corresponding table rows when forms were submitted, preventing new rows from being added. This was caused by missing page instructions in the second refresh of submit embedded modal payload, and has been resolved by ensuring proper page instruction handling during embedded modal submissions. | User Experience |
| INC-C53828 | 967591 | Attachment listing preserved during record deletion | Deleting the first record in a repeating view was incorrectly removing attachments from other records in the UI, though the underlying data remained intact in the system. This was traced to the field group indexing during record deletion operations, and has been corrected. | User Experience |
| INC-C54074 | 968000 | 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 | 967616 | 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-C54311 | 966467 | 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-C54523 | 965210 | Landing page popup display layering fixed | Tabbed layout headers were displaying over popups on Constellation UI landing pages, obscuring modal dialogs for adding or editing records. This was caused by incorrect z-index layering in the Constellation UI rendering, and has been resolved by adjusting the display layering to ensure popups appear above tabbed layout headers. | User Experience |
| INC-C54634 | 972486 | Theme preview display for migrated environments corrected | After update, migrated environments were showing blank previews instead of the configured colors in theme previews for mobile channels. This has been resolved by adding a check for pzLegacyTheming with getIfPresentMethod. | User Experience |
| INC-C54843 | 967724 | 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-C54972 | 965951 | 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 | 965339 | 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-C55601 | 966388 | TASK-1843335 - Doug Miller | User Experience | |
| INC-C56324 | 965445 | Repeating view item duplication corrected | Additional items were being incorrectly added to repeating views when users changed radio button selections that controlled different view displays. This has been resolved by improving the handling for mergeListChanges during mergeData and clean up page instruction when the array length is different. | User Experience |
| INC-C56366 | 968657 | 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-C56949 | 972772 | Data reference property navigation for data objects fixed | Data reference property links in data object details tabs were not displaying target data properly, showing blank screens instead of the expected data content. Investigation showed unique ID generation for the pyDetails view was only handled for case objects and not data objects, preventing proper component unmounting and refresh. This has been resolved with an update which uses caseId if present, otherwise a stable unique ID will be generated from dataInfo (dataContext + sorted dataContextParameters). | User Experience |
| INC-C57109 | 968191 | Promoted filter null record display corrected | Applications were experiencing issues where promoted filters using True/False properties were not displaying records with null values when "False" was selected. This was traced to the cosmos Boolean Display component not properly handling null values in the filter logic, and has been resolved with an update which renders a display-only checkbox with null value as NoValue. | User Experience |
| INC-C57351 | 973215 | Filter modal layout corrected for multiple custom fields | The Insight filter modal was pushing submit and cancel buttons off-screen when creating custom filters with multiple fields, particularly when starting from a column rather than the whole table. This was caused by insufficient scroll handling and layout constraints in the filter modal container and has been resolved by improving the modal's layout management to properly contain all filter elements within the visible area. | User Experience |
| INC-C57382 | 970154 | Mashup landing page headers restored | Traditional landing pages in blended Constellation applications were losing their headers and page content after refresh, displaying blank pages. This has been corrected. | User Experience |
| INC-C57401 | 973266 | Page message display enhanced for search and select component | Messages set on pages through activities were not being cleared after correct values were entered in search and select components, and page-level messages were not displaying properly at the flow container level. This was caused by error classification issues and missing message propagation to the flow container, and has been corrected. | User Experience |
| INC-C57552 | 970900 | Complex embedded data structures persist for case reopening | Saved data including radio controls, dropdowns, and search results did not load correctly when cases with complex embedded structures were reopened from the flow after using the "Save for Later" functionality. This has been resolved by enhancing the data restoration logic to properly handle complex embedded structures during case reopening operations. | User Experience |
| INC-C57828 | 971912 | Column menu display labels corrected | Table view column menus were displaying property IDs instead of configured labels when adding Page or Page list properties, even when proper labels were configured in the record definition. Investigation showed the column menu was referencing internal identifiers rather than display labels for these property types, and this has been corrected. | User Experience |
| INC-C57930 | 974735 | View rule generation bypass option added |
Applications were experiencing unwanted automatic view rule generation for decision data rules through the pzGenerateView process, creating issues for circumstanced sections. This has been addressed by introducing a bypass option pySkipViewGeneration property within pzGenerateView that allows users to disable automatic view rule creation for auto-generated sections. | User Experience |
| INC-C58048 | 970986 | Corrected portal data type editing freeze on operator icon click | Data type editing sessions were freezing when clicking the operator account menu without moving the cursor away, specifically affecting the top record on screen while subsequent records remained functional. This was caused by missing context setting in the grid action handler, and has been resolved by updating the pzPega_ui_grid JavaScript rule to properly set context on the grid div during pzdoGridAction execution. | User Experience |
| INC-C58105 | 972474 | Date input validation corrected for promoted filters | Manual date range entry in Insights promoted filters was being rejected with the error message "Invalid date range". This has been resolved by updating the handling for focus-within detection when focus/mouse events occur inside the Shadow DOM and when using portals/iframes. | User Experience |
| INC-C58145 | 970161 | 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-C58518 | 973180 | Action menu localization enabled for work object preview | Action menu labels including "Assign To Me", "Add Memo", "ToDo", and "ToDo(Group)" were appearing in English during work object preview regardless of the user's locale settings. This has been resolved by adding the necessary localization support for optional actions in the preview interface. | User Experience |
| INC-C58844 | 970629 | Tabbed template content positioning stabilized | Landing pages using tabbed templates were experiencing content displacement when switching between tabs, causing top table records to become invisible and requiring manual scrolling to restore proper display. In tabbed layouts, the virtualized container was able to briefly report 0x0 dimensions (hidden tab, not yet laid out), leading to incorrect measurements/scroll position behavior. This has been resolved with an update to make recalculations conditional on having valid geometry first so they are not run when the row container or target element has zero dimensions. | User Experience |
| INC-C59383 | 969122 | 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 | 970033 | 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 | 969505 | 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 | 970791 | Date field year range configuration accuracy improved | After configuring a date field to be of precisely the current year range by configuring next and previous years in range as zero, it was not possible to select December 31 of the current year, the year drop down had the previous year entry available, and selecting January 1 of the current year enabled the previous year. This was traced to timezone-related calculations affecting year boundary determinations and dropdown population logic, and has been corrected. | User Experience |
| INC-C9516 | 919550 | Accessibility list structure corrected | Applications were displaying incorrect list structures for case ID text elements, affecting screen reader accessibility. This has been resolved by correcting the list structure generation MetaList configuration in the accessibility framework to ensure proper accessibility. | User Experience |
| INC-D1082 | 974026 | Personalized grid persistence fixed when localized | Personalized table views were not saving properly when the operator was set to a non-English locale, particularly when adding columns with localized field values or image controls. This has been resolved by correcting the localization handling in the personalized view save functionality to use a localized string instead of the headerLabel. If there is no localized value or field value, the plain label is returned. | User Experience |
| INC-D1626 | 972963 | Country code selection corrected for stakeholder phone numbers | The Stakeholders widget was restricting phone number country code selection to only +1 (US), preventing entry of international contact information. The same Phone control worked correctly when used outside the widget. This has been resolved by correcting the control configuration within the Stakeholders widget context to provide the full country code list. | User Experience |
| INC-D1686 | 974047 | Screen reader accessibility improved | Screen reader accessibility for optimized table navigation was providing incorrect instructions, reading "Click to Filter" and "Click to Hide Field" instead of the required "Enter to Filter" and "Enter to Hide Field". This was caused by incorrect aria-label text in the pzTemplateGridMenuNavRule navigation rule, and has been corrected. | User Experience |
| INC-D1957 | 974506 | Busy indicator text localization added | Applications were displaying hardcoded, non-localized text in busy indicators that included a misspelled "inderminate, progress indicator" message. This has been resolved by correcting the spelling in English and by creating field value entries to enable proper localization of all busy indicator text elements. | User Experience |
| INC-D2373 | 974096 | Popup harness JavaScript error resolved | After update, custom close buttons on popup harnesses were failing with the error "window.opener.pega.u.d.getThreadName is not a function". This has been resolved by adding proper null validation before attempting to access parent window thread information. | User Experience |
| INC-D2719 | 972847 | Accessibility improved for case icon | A role attribute/tag has been added to the case icon on the case details page to improve accessibility. | User Experience |
| INC-D2939 | 973239 | SDK link behavior standardized | External links in case instructions were behaving inconsistently between Pega portals and Angular SDK implementations, with links opening in new tabs in portals but replacing the current tab content in SDK applications. This was caused by the DOMPurifier logic in the SDK components not automatically adding target="_blank" attributes to external links, and has been resolved by implementing consistent link handling logic across all UI frameworks to ensure external links always open in new tabs. | User Experience |
| INC-D3261 | 977053 | Auto-save validation behavior corrected for tree navigation | Applications using TreeNavigation7 with auto-save functionality were triggering unexpected client-side validation popups when non-required fields were modified, even when required fields remained properly filled. This was traced to auto-save incorrectly running validation checks on the entire form rather than just modified sections, and has been resolved by adjusting autosave to save without running client validations when using TreeNavigation7. | User Experience |
| INC-D3276 | 974739 | Layout group tab focus borders corrected | Tab layout groups were displaying incomplete focus borders when "Semantic tab Layout" and "Allow scroll for tab headers" options were enabled together. This was caused by CSS conflicts that removed the top border during focus state rendering, and has been resolved by updating the focus styling rules to maintain complete border visibility across all tab layout configuration combinations. | User Experience |
| INC-D3470 | 973607 | Keyboard navigation flow restored for optimized tables | Keyboard navigation was becoming trapped in the first column of optimized tables with group by results. This an issue with the focus management in grouped table rows where the first column appeared empty beneath the group caret, and has been resolved by updating the keyboard navigation logic for a grouped table. | User Experience |
| INC-D599 | 973733 | Page title localization improved | Page titles in "My Work" and Insights sections were not being correctly localized. This has been resolved by adding a localeReference attachment in the pxViewMetaData configuration of the pyWorklist page. | User Experience |
| INC-D6108 | 977521 | Localization added for filtered date picker labels | Date picker "From" and "To" labels were displaying in English regardless of their configured locale when applying range filters to Date/DateTime fields in Inline Dashboards. This has been corrected. | User Experience |
| INC-D709 | 973364 | Case summary panel refresh implemented for local actions | The case summary panel was not updating when local actions created renewal cases, continuing to display resolved case details instead of the new case information even though assignments appeared correctly in the work area. This was caused by missing refresh logic for the summary panel during local action execution, and has been resolved by adding a check to dispatch mergeData when parent and child containers hold different contexts. | User Experience |
| INC-D807 | 974596 | Focus functionality restored for Checkbox help text | Checkbox controls with "Help icon with overlay on focus" were not displaying help text when field values contained line breaks or spaces. This has been resolved by adding proper newline-to-HTML conversion in the pzpega_ui_template_checkbox.js rendering logic for tooltip display when using the focus-based help text feature. | User Experience |