Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
As part of Pega's long-term security strategy, AI-assisted scanning has been implemented on a proactive basis. Pega strongly encourages all clients to stay current on the latest product versions, where security enhancements, patching, and hardening improvements are delivered.
Low-code Application Development
Case Management
25.1.3 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C46167 | 969147 | Post value and refresh section functionality updated | Post Value actions were not reliably submitting /updating the intended values, and Refresh Section actions did not refresh the correct section or failed to reflect changes. This was traced to FlowActionHTML not using the correct page context for the local-case branch. Because the section/action was being rendered against an incorrect BASE_REF, UI actions like post value and refresh section did not resolve against the expected page. This has been corrected so those actions execute in the correct Primary context. | Case Management |
| INC-C46548 | 961848 | Wait shape error with duplicate stage names fixed | Parent-child case configurations were encountering Constellation errors displaying "An internal error occurred, Please contact administrator" when submitting parent cases. This was caused by wait shape configurations where child and parent stages had identical stage names and the parent next stage used a screen flow. This has been resolved by correcting the stage name conflict handling in wait shape processing. | Case Management |
| INC-C54505 | 966457 | Database schema capacity expanded for instance identifiers | The system was rejecting or truncating longer instance identifier values during database operations, causing persistence failures when working with cases or rules exceeding the value capacity. This has been resolved by increasing the column sizes for pzInsKey from 512 to 900 characters and pxInsName from 255 to 768 characters in the pr_metadata table schema master. | Case Management |
| INC-D10624 | 984649 | Resolved field audit duplicate entries | Field level audit entries were displaying duplicate values for pyStatusWork and other properties, with UI controls appearing blank for these properties in user applications. This was caused by improper handling of field audit entries for properties without UI controls, and has been resolved by adding handling for empty conditions. | Case Management |
| INC-D12056 | 989163 | Archive policy duplication eliminated after migration | Applications migrated from Pega Platform 8 to Pega Infinity '25 were showing duplicate Archive Associated Classes entries in Archival Policy rules, with duplicates reappearing even after manual deletion. This was traced to redundant associations created by the migration script during the upgrade process, and has been corrected by updating the context handling for the pyClassName parameter. | Case Management |
| INC-D14606 | 987493 | Constellation form refresh pagelist synchronization improved | Inconsistent behavior was seen in Constellation when form refresh operations triggered data transforms that modified pagelist data during field change events, including stale rows persisting, deleted rows reappearing, or expected new rows failing to display after picklist selections. Investigation showed this was an issue in reconciling server-side pagelist mutations during form refresh operations, creating a disconnect between the server-side case state and the client-side view. This has been resolved by implementing enhanced page comparison logic and instruction formation capabilities that properly synchronize pagelist operations between server and client, including the addition of row identifiers for accurate change tracking and comprehensive page instruction generation for all refresh API endpoints. | Case Management |
| INC-D16719 | 989768 | Optimized Archival pipeline performance | Severe performance degradation was occurring in the archival pipeline (pzPerformArchiveUsingPipeline) where purge operations were limited to processing only one case every 15-50 seconds. This was due to inefficient DELETE queries on pc_FLAudit_ tables using LIKE conditions with leading wildcards on the pxHistoryReference column, forcing full table scans and generating PEGA0005 performance alerts. This has been resolved by updating the PurgeFLA query for Microsoft SQL Server to use more efficient query patterns that can utilize proper indexing, significantly improving archival throughput. | Case Management |
| INC-D17063 | 989078 | DX API preprocessing behavior made configurable | An intentional behavioral change in the DX API effective with Infinity '25 to execute pre-processing data transforms and activities during submission was creating issues with document processing in Angular page integrations where newly uploaded documents were being ignored due to repeated preprocessing. In order to improve backwards compatibility, this DX API behavior has now been made configurable by adding the DSS "DXAPIPreProcessOnce" to the pzApplyDataForPerformAction activity. Setting this to "true" will skip the preprocessing path. When the DSS is false, the system will follow the existing/default preprocessing path unless the request itself explicitly passes skipPreProcessing="true". | Case Management |
| INC-D193 | 973359 | Pagelist UPDATE support added for embedded attachment properties | When working with attachment properties configured on an initial screen and transferring them to a page list property with Embed-Attach-File object class on a subsequent screen, an "Invalid page instruction" error message was generated when attempting to submit the second screen. Investigation showed this was caused by the system generating unsupported UPDATE instructions for page list properties with Embed-Attach-File object class. This has been resolved by modifying the pzapplypageinstructions activity to allow UPDATE page instructions in addition to DELETE and INSERT for page list properties that have a page definition as the embed-attach-file class. | Case Management |
| INC-D2677 | 980683 | External repository attachment cleanup improved | Attachments stored in external repositories were not being deleted during case archival when "Directly purge without copying to archival location" option was enabled, leaving orphaned files in external storage. This has been resolved by adding logic to delete attachments from external storage when cases are archived or purged with the direct purge option. | Case Management |
| INC-D2732 | 976443 | File attachment keyboard accessibility corrected | Attempting to attach files through the pyAttachContent control in overlays using keyboard navigation generated the error “There has been an issue, please consult your system administrator.” Mouse interactions worked correctly. This was caused by the pzMultiFilePath control lacking proper keyboard event handling when configured in an overlay, and has been corrected. | Case Management |
| INC-D3165 INC-D14897 INC-D12319 |
977068 989167 986164 |
Field level auditing inconsistencies resolved | Inconsistent results were seen for Field Level Auditing of temporary cases migrated from older versions and cases processed through parent-child relationships where FLA did not capture changes correctly for cases in their first assignment, causing expected audit entries to be missing. This has been resolved by refining previous work on duplicate FLA scenarios to include additional handling for temporary cases and cases with utility steps in create stage. The DSS "PreventDuplicateFLA" has been added to help prevent duplicate FLA records in edge cases while preserving prior behavior by default. | Case Management |
| INC-D3223 | 975038 | Drag and drop file size limit handling corrected | File uploads through drag and drop controls were incorrectly rejecting files when the pyMaxDragDropAttachSizeMB setting was configured to 2048MB or higher. This was caused by integer overflow in the byte conversion calculation within the pzMultiDragDropControlStandard control, and has been resolved by changing the variable data type from int to long to properly handle large file size limits. | Case Management |
| INC-D3317 INC-D17696 |
980218 989280 |
Previous button navigation functionality restored in case management workflows | Applications were experiencing infinite loading screens and NullPointerException errors when attempting to navigate backwards using the Previous button in multi-step case creation workflows, particularly in scenarios involving case spin-offs with reference field data copying. Investigation showed this was caused by a limitation in the handling of backward connections and inner loops in screen flows, and this has been resolved by adding an iterator to expand autopopulates in the pzJumpToStep method, ensuring proper backward navigation functionality is restored for case management workflows involving complex case reference patterns. | Case Management |
| INC-D3373 | 984095 | Attachment widget count refresh updated | PDF generation from eForm templates was not immediately updating attachment widget counters in Constellation applications. While PDFs were successfully generated and attached to cases, the attachment count continued displaying "0" until the widget was manually expanded. This was caused by the attachment widget not receiving proper refresh signals after eForm PDF generation, and has been resolved. | Case Management |
| INC-D3407 | 975496 | Pagination limit removed for App Studio subprocess selection | Applications with more than 50 flow rules were unable to access all available flows when configuring subprocesses in App Studio. This was due to a default pagination limit of 50 records in the pyGetCategoryItems report definition, and has been resolved by disabling paging so all flows are returned. | Case Management |
| INC-D4292 | 981916 | Database class definition exception resolved | UI Kit applications were generating EXCP0001-5409 BadClassDefinition errors in logs when dragging records from worklist widgets to team member widgets, though functionality remained intact. This was traced to missing or blank report-definition parameters in pyPopulateAssignedWork, and has been resolved by adding a check and handling for this scenario. | Case Management |
| INC-D4775 | 977745 | Pipeline archival functionality restored for direct purge configurations | After update, pipeline archival was failing when the direct purge option was configured without copying data. This was traced to an issue with the SQL query generation for audit table purges and , and has been resolved by updating the archival logic to properly handle SQL query generation for audit table purges along with adding defensive null checks to file name processing in attachment status updates to prevent failures during attachment processing. | Case Management |
| INC-D4916 INC-D6170 |
976151 981373 |
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-D6203 | 977482 | Question import in branches enabled | Question import functionality was failing with "Please correct flagged fields before submitting the form!" alerts when attempting to import questions in development branches without unlocked rulesets. This was traced to the "Run visibility condition on client" checkbox being checked on the pyRulesetVersion dropdown in the pzSurveyRecordContext section rule, and has been resolved by unchecking the box. | Case Management |
| INC-D7300 INC-D17215 INC-D6574 |
984219 989540 984584 |
Case archival indexing resolved | Case archival processes were failing during the Search and Reporting Service (SRS) indexing stage when attempting to archive cases containing null or empty date values in various date properties including Expecteddateofclosure, LatestWOUpdateDT, and DocumentationCompletionDate. ERR_INSTANCE_VALIDATION messages were seen with the sub-code ERR_MALFORMED_PROPERTY_VALUE, specifically reporting "failed to parse field [field_name] of type [date] in document with id 'XXX-XXX-XXX-XXX'. Preview of field's value: ". This has been resolved by adding logic to exclude properties with null or empty values from the indexing request. | Case Management |
| INC-D7684 | 982566 | Added handling for resolved cases SLA processing race condition | Queue processor pyProcessSLA was accumulating broken items with "Unable to open an instance using the given inputs: ASSIGN-INTERNAL" errors for resolved cases where assignments no longer existed. Investigation showed this was caused by SLA processing attempting to access assignments that were removed during rapid case resolution cycles, and was due to cases/assignments being created and resolved without allowing enough time to process the SLA item. This has been resolved with an update to ensure the SLA queue processor item will not move to the broken queue if the corresponding assignment is not present, along with improved cleanup of queue items for resolved cases. | Case Management |
| INC-D7960 | 984264 | MaxFileSize added to file attachment handling | The file attachment functionality was missing the necessary configuration to set maximum file size limits for attachments. This has been corrected by adding the pymaxFileSize property to the Data-WorkAttach-File class to enable proper file size limit configuration and validation. | Case Management |
| INC-D7969 | 983491 | File upload replacement functionality restored | After update, multiple file uploads were not properly replacing previously attached files when using the standard configure user action attachment field. This was a missed use case for the pyGetAttachmentFieldInfo activity sorting the assignments in create date time ascending order, and has been resolved by restoring the expected file replacement functionality for attachment fields. | Case Management |
| INC-D8283 | 990485 | Remote case API authentication fixed | External automation tools were unable to create remote cases via the DX API, receiving "AAT cookie not found in the request" errors when providing the required remotesystemid header. Investigation showed the remote gateway validation required an AAT cookie even for API requests with proper authorization headers, and this has been resolved by updating the logic to read tokens from authorization headers when Pega-AAT cookies are not present and skipping CSRF validation checks for header-based authentication. | Case Management |
| INC-D8745 | 986208 | Bulk assignment transfer context handling updated | Bulk transfer of cases to worklists or workbaskets was not functioning when using the pxTransferAssignment activity in flow action post-processing. This was traced to an issue in the reassignment logic which could resolve the wrong work object page name during execution. This has been addressed by updating the Work- Reassign activity so it derives the work object name from the current step page instead of relying on the previous fallback expression so each assignment is processed in the right context. | Case Management |
| INC-D9409 | 979599 | Case flow cleanup improved | Flow accumulation issues were seen when closing cases from within subflows using custom close activities followed by pxForceCaseClose. Embedded subflow instances were remaining present in pyWorkPage.pxFlow(), and upon reopening the same case multiple times, new flow instances were being appended while previous subflow instances were retained, eventually causing system errors when the pxMaxFlowAddCount safeguard was exceeded. This was caused by pxForceCaseClose not properly removing embedded pxFlow pages from cases during closure, and has been resolved by ensuring pxForceCaseClose properly cleans up all embedded flow instances when cases are closed. | Case Management |
Cloud Services
25.1.3 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D12938 | 984690 | DDL generation script performance improved | The generateddl.sh script was requiring existing database schemas and taking an excessive amount of time to generate DDL for new installations. This was traced to the system performing excessive database queries, and has been resolved by updating the prdeploy version to one which eliminates that inefficiency. | Cloud Services |
| INC-D1366 | 972348 | Revalidate and save memo recording restored | Memos entered during Revalidate and Save operations were not appearing in the rule history. This was caused by the revalidation process not properly capturing and storing the memo text during rule processing, and has been corrected. | Cloud Services |
| INC-D14909 | 984780 | Oracle DDL upgrade handling updated | Database updates were failing with Oracle error ORA-30556 when attempting to modify the PYFOLDERNAME column in pr_log_service_email table. Investigation showed this was caused by functional or bitmap join indexes being defined on the column being modified, which is not supported by Oracle. This has been resolved by implementing the proper handling for indexes with descending columns during DDL generation. | Cloud Services |
| INC-D4207 | 975188 | Handling added for post-migration Message rules visibility | Message rules were becoming invisible and unusable following platform update from Pega version 7 to Pega Infinity 24.1. Investigation showed this was caused by the loss of pxobjclass data during the migration process from pr4_rule to pr4_rule_message tables. This has been resolved with an update to ensure the pxobjclass data is preserved during the migration process for improved backwards compatibility. | Cloud Services |
| INC-D8904 | 978591 | Performance metrics display accuracy improved | PDC was displaying nanosecond execution times incorrectly labeled as milliseconds, causing confusion during performance analysis. This was caused by improper unit conversion logic, and has been resolved by correcting time unit calculations and display formatting. | Cloud Services |
| INC-D963 | 971771 | Upgrade performance improved for large Data-Content-Image environments | The in-place update process was taking an excessive amount of time to complete. Investigation showed this was caused by a query SELECT pzInsKey related to WHERE pxObjClass = 'Data-Content-Image' which returned the entire table content and consumed excessive processing time. This has been resolved by optimizing the upgrade process to handle environments with large numbers of Data-Content-Image instances more efficiently. | Cloud Services |
Conversational Channels
25.1.3 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C45663 | 966556 | 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-C51533 | 975767 | 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 | 973504 | 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 | 973247 | 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-D14219 | 985481 | Email case lock handling corrected for inflight cases | Lock errors were occurring for inflight email cases with inline images after upgrade, particularly affecting service level agent queues after wait shape continuation. Investigation showed this was caused by premature lock release during the pxLinkAttachmentToCase commit process in pzUpgradeOldInlineImages activity. This has been resolved by removing the commit parameter when calling pxLinkAttachmentToCase to maintain proper lock handling. | Conversational Channels |
| INC-D14690 | 989134 | GenAI attachment handling updated | After update, PDC alerts were generated for GenAI rule execution timeouts during case creation. This was caused by pySetAttachmentFiledsWrapper being invoked from pxCreateCase without checking if the GenAI toggle was enabled, causing unnecessary GenAI connect rule calls for attachment classification. This has been resolved by preventing the call of pySetAttachmentFiledsWrapper as it is no longer required due to attachment mapping now being performed using GenAI Agent. The attachment-linking activity and related logic has also been updated to use ServiceCaseForEmail.pzInsKey instead of ServiceCase.pzInsKey. | Conversational Channels |
| INC-D16867 | 989615 | Email attachment filename property corrected | Email reply functionality was failing. This was due to missing pyFileName property references in Data-WorkAttach-File instances, causing attachment processing errors in the pzSendEmailReplyAPI activity. This has been resolved by updating the activity to use pxAttachName when populating the attachments page. | Conversational Channels |
| INC-D4559 | 986531 | Email body cross-contamination fixed | Outbound emails were being sent with incorrect email body content from different cases while maintaining correct recipients and subject lines. This was caused by conversation history being rebuilt from processed values rather than the original intended message in some reply/auto-reply flows, and has been resolved by updating the email body mapping logic to ensure proper case-to-email content association. | Conversational Channels |
| INC-D54 | 971884 | Email reply recipient name display corrected | When replying to inbound emails where the email account label differed from the email account name, the TO name on the original inbound email was being changed to the operator who sent the reply rather than maintaining the email bot name. Investigation showed this was caused by the GetDisplayName function not properly handling cases where the email account label differed from the account name, and this has been corrected so the account name will be used. | Conversational Channels |
| INC-D7776 | 977172 | Advanced URL override configuration enhanced for digital messaging channels | Organizations using Digital Messaging Service (DMS) with OAuth integration were experiencing difficulties navigating to application settings for URL overrides, and encountered issues with attachment names containing hyphens. To address this, an “advanced URL override” path has been added for Bot Agent integrations, allowing key endpoints (API endpoint, Integration Manager URL, Management API URL, webhook/auth notification URLs) to be sourced from Application Settings when the dedicated When rule "pyOverrideUrlsAdvanced" evaluates to true. This allows multiple Bot Agent activities to prefer parameter/app-setting driven URLs with fallback to existing override fields. | Conversational Channels |
Data Integration
25.1.3 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C19409 | 932118 | 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-C24844 | 952281 | 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. | Data Integration |
| INC-C34793 | 956664 | 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-C40045 | 951276 | 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-C45502 | 974619 | 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-C45726 | 980003 | Case update information persistence improved for optimistic locking | Applications using the CS Framework with optimistic locking were experiencing issues where the pyWorkPage.pyCaseUpdateInfo embedded page was appearing blank on second activation, causing end-users to lose their assignments during wrap-up actions on interaction cases. This was traced to a passivation issue where the logic did not sufficiently distinguish transient properties from ordinary empty properties. This has been addressed with an update to ensure transient properties are explicitly tracked and preserved correctly through encoding/passivation paths, along with a dedicated logger for transient-property encoding diagnostics. | Data Integration |
| INC-C49040 | 981507 | Box integration certificates updated with valid credentials | The BoxComTrust keystore has been updated with valid, current certificates to ensure proper Box integration functionality. | Data Integration |
| INC-C51032 INC-C59744 INC-D8424 |
960629 970376 978635 |
Database information visibility corrected for delegated data types | When delegated data types were accessed through the Web Portal, database and table information was unexpectedly being displayed to users on the landing page and through hover tooltips. Investigation showed this was caused by insufficient visibility controls that failed to distinguish between developer and business user contexts, and this has been resolved by adding proper visibility conditions and implementing appropriate access restrictions so the information is not displayed to a delegated user. | Data Integration |
| INC-C51762 | 967821 | 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-C53460 | 972156 | Embedded property support added for BIX Kafka message keys | When configuring Kafka data sets with embedded properties as message keys, the keys appeared empty in the published messages even when using proper page context references like ".Payload.pzInsKey". Investigation showed this was caused by the message publishing logic not properly handling embedded properties from single pages when setting Kafka message keys. This has been resolved by updating the pzPublishMessage Java step logic to fetch DataSet keys and set them as top-level properties, improving how messages are published to external datasets. | Data Integration |
| INC-C54480 | 964921 | Job scheduler node type configuration corrected | The job scheduler pyAxis2ConnectionPoolCleanup was failing to with the error "Job Scheduler ConnectionPoolCleanup registration failed". This was due to invalid mapped node types "RTDG,DDS,RealTime" being included in the configuration when they were not available in the cluster, and has been resolved by updating the configuration to use only valid mapped node types. | Data Integration |
| INC-C55739 | 968690 | 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-C56335 | 972658 | 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-C56616 | 979502 | EdgeServer file extraction download handling improved | The Extract EdgeServer Files feature for deploying static content to AWS CloudFront was failing with duplicate rule errors, specifically encountering failures at RULE-FILE-TEXT STYLE PALSTYLESHEET CSS rules during extraction. This was an issue with logic for downloading the files after running the ExtractEdgeServer process, and has been resolved. | Data Integration |
| INC-D10393 | 988102 | File repository API data page reloading issue corrected | Custom repository implementations were experiencing issues with the D_pxNewFile API where file paths were becoming blank during the save process. Investigation showed this was caused by improper data page caching and reloading logic in the repository API. With this update, if D_pxNewFile.pyPath is populated, behavior stays the same. If it is blank, the system now falls back to RepositoryFilePg.pyPath. | Data Integration |
| INC-D10625 | 981856 | NumberFormatException fixed in BIX extract execution status | The pzUpdateBIXExtractExecutionStatus activity was failing with NumberFormatException errors when executed on SQL Server databases. This was traced to column name resolution differences between database implementations, causing a type mismatch that resulted in a NumberFormatException when attempting to parse the retrieved value. This has been resolved with an update to ensure the column name references are consistent across all supported databases. | Data Integration |
| INC-D1091 | 979153 | JSON data transform property mapping corrected | JSON data transforms were not properly mapping properties to JSON keys with different names when inheritance support was enabled, causing incorrect data structure generation. This was due to initializing the inheritance tracker with the configured page class from the mapping model instead of the actual step page class at runtime. This has been resolved by correcting the class context used during mapping to restore the correct property-to-key mapping. | Data Integration |
| INC-D113 | 974824 | 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-D12769 INC-D6051 |
984372 985627 |
PDF form concatenation handling updated | Values were being removed during the PDF concatenation process and field flattening was not working properly, leaving fields editable when they should have been flattened. This was traced to the appearance generation for concatenateEform interfering with proper PDF concatenation, along with issues in checkbox and radio button mapping, null pointer exceptions in mapEForm, and flattening problems causing text to disappear. This has been resolved by disabling appearance generation for concatenateEform functionality and correcting checkbox and radio button mapping, addressing null pointer exceptions, and updating the flattening in the generateEForm activity to ensure forms are properly flattened and non-editable as intended. | Data Integration |
| INC-D13098 | 989903 | Data page load timeout made configurable | Service timeouts were occurring intermittently during peak periods where GetDecision service calls exceeded expected response times (10-30+ seconds). This was due to a hardcoded 60-second wait window for asynchronous data page loading operations that was not configurable for scenarios requiring shorter timeouts. This has been made configurable by introducing a new DSS key (datapage/waitingTime/seconds) to control wait timeout. | Data Integration |
| INC-D14223 | 986588 | ABAC association-based access control corrected for search operations | Attribute-based access control (ABAC) with associations was not functioning properly when using global search in Constellation portals. Investigation showed this was caused by the search index not properly applying ABAC policies that relied on association rules for indirect permission checks. This has been resolved by ensuring lookup data pages pass the security parameter as true when calling database open APIs, so that read ABAC policies are properly applied during search operations. | Data Integration |
| INC-D15791 | 987830 | Business calendar error handling improved | Exceptions were being generated when dates used were not within the business calendar range, producing "FATAL (ed.pega_rules_businesscalendar) FATAL - null" errors. This has been resolved by implementing proper error handling for dates outside business calendar ranges. | Data Integration |
| INC-D2442 | 973714 | Savable data page connector error resolved | After update, savable data pages using connectors were failing with "aParameterPage is null" errors when no parameters were passed to the data page. This has been resolved with the addition of null checks in the DataPageSaverImpl.java callDataPageSaveForConnector method to guard to avoid errors when copying the IF_MATCH parameter into the activity parameter page during data page save for connectors. | Data Integration |
| INC-D3981 | 978589 | REST connector Content-Type header automation implemented | Connect REST rules were not automatically including Content-Type and Content-Length headers in requests, causing API Gateway integrations to fail with 403 Forbidden errors when these headers were mandatory. The APIs would work correctly when headers were manually added to the Connect REST configuration, but this required additional manual configuration steps. This has been resolved by implementing automatic Content-Type and Content-Length header inclusion for Connect REST requests that will set the content type by parsing clipboard content. | Data Integration |
| INC-D4069 | 987462 | Data page rule validation consistency improved | In some cases, savable data pages with invalid or incomplete definitions could be silently ignored and left unresolved. This was caused by invalid or incomplete savable data page definitions/sources that were not being bulk-detected and revalidated. To address this, this update provides a structured way to identify all impacted savable data pages and bulk repair them by adding bulk validation/save support for savable data pages and tracking dirty data page definitions so invalid sources can be identified, revalidated, and saved correctly. | Data Integration |
| INC-D4073 | 973709 | Log level changed to debug for API call diagnostic messages | When making successful API calls using the PUT /data/{data_view_ID} endpoint, misleading error messages were appearing in Pega logs, specifically "Skip clearing default lookup data page as lookupDpName is empty" messages at error and info levels even though the API operations were completed successfully and no actual errors were occurring. Investigation showed this was caused by leftover debug messages in the datamgmt.dataapi.utilDataAPIUtilsImpl class that were incorrectly using error() and infoForced() logging methods instead of debug() methods in the clearDefaultLookupDataPage() function. This has been resolved by changing the log level for these diagnostic messages to ensure they only appear when debug logging is explicitly enabled. | Data Integration |
| INC-D522 | 981070 | Logging added for missing PageList element | In order to assist with diagnosing issues where a PageList element goes missing during clipboard/BLOB encoding, a dedicated DirectStreamEncoderV7DiagnosisPageListIssue logger has been added which will emit detailed debug messages in Page/PageList encoding paths. This includes a DSS-based filter "BLOBDebugPageListName" to only log for selected PageList/property references. | Data Integration |
| INC-D5683 | 977667 | REST connector PUT request payload issue resolved | PUT requests were failing and the payload appeared empty when using x-www-form-urlencoded configuration in REST connectors. This was caused by the request body not being populated due to a failure to set the reqMessageData variable in the mapping logic, and was traced to a conditional check in the MAP OUTBOUND DATA step that did not account for PUT method payload handling. This has been resolved with an additional check on method name so that list is being sent only if its post request and there is url_encoding in the mapping type. | Data Integration |
| INC-D6671 | 976386 | OAuth authentication support enabled for SMTP email communication | Microsoft has retired Basic authentication with SMTP protocol from March 2026, requiring applications to use OAuth authentication instead. With this update, OAuth support is provided for SMTP protocol to support using Microsoft as the email provider in the email account rule. |
Data Integration |
| INC-D6804 | 977471 | Null pointer exception handling added for SRS migration | Attempting to index regular class items during SRS migration data processing resulted in the error "java.lang.RuntimeException: Caught exception while expanding property null on page .pxFlow(Inbound).pyFlowParameters" . This was traced to a null PropertyName caused by data corruption in the blob storage stream processing, and has been resolved by adding handling for an empty property during deserialization. | Data Integration |
| INC-D6934 | 979427 | Doubled error message display corrected | Generic error messages were appearing alongside custom validation messages in Constellation UI components. This was caused by the DX API returning both generic and custom error messages simultaneously, and has been resolved by adding a new method for generic error message handling to prevent duplicate message rendering. | Data Integration |
| INC-D71 | 975724 | Data page functionality restored for embedded fields | After update, the error "Cannot invoke 'com.pega.pegarules.pub.clipboard.ClipboardPage.getString(String)' because 'dataPagesForClass' is null" appeared when trying to access data page D_testSavable. Additionally, attempting to update records containing embedded data fields through the DX Data API was not working. This was an unintended side effect traced to the introduction of the API mergeWithDBRecord(), and has been resolved by updating thread handling. | Data Integration |
| INC-D7199 | 981899 | Rate limit handling improved for data migration pipelines | Data migration pipelines were failing after processing only a few records with "429 Too Many Requests" errors from Google Cloud Storage, specifically encountering rate limit exceeded messages for object mutation operations. Investigation showed this was caused by excessive API calls during file dataset operations without proper rate limiting controls. This has been resolved by implementing intelligent retry mechanisms and request throttling to comply with Google Cloud Storage rate limits during data migration operations. | Data Integration |
| INC-D7424 | 982429 | Insight loading handling updated for embedded page configurations | Insights were showing only loading screens for data objects with embedded page properties configured using $any or @class, preventing proper metadata loading. This was caused by missing pyPageClass values for embedded fields being treated as valid input during metadata transformation, leading to the context class becoming null during metadata loading via pzGetClassDataModelFromDictionary. This has been addressed by adding warning messages and ensuring the system returns early when pyPageClass is blank to avoid processing failures. | Data Integration |
| INC-D7494 | 977570 | Windows file upload restored | File upload operations were failing on Windows environments with "Upload failed" errors and InvalidPathException messages showing "Illegal char ':' at index 4: file://web:/StaticContent/global/ServiceExport/". Investigation showed this was caused by the Web tier passing logical URI paths directly to java.nio.file.Paths.get() without proper URI-to-path resolution, which Windows file systems cannot process. This occurred when the configured upload directory was a Pega logical/VFS path instead of a native OS filesystem path, and was caused by FileUploadHandler passing that logical path directly into Apache Commons FileUpload. This has been corrected with an update which resolves the logical path first, normalizes it, and uses a safer bounded buffer size. | Data Integration |
| INC-D8485 | 978102 | Improved Kafka topic partition error logging | In order to assist with diagnosing Kafka errors such as "UnknownTopicOrPartitionException: This server does not host this topic-partition" errors, logging has been updated to print the stream name if there is an issue while fetching stream partitions. | Data Integration |
| INC-D9183 | 987418 | SOAP namespace preservation implemented | SOAP services requiring SAML assertions were experiencing signature validation failures when duplicate namespaces were removed from SOAP request XML. To resolve this, the handling has been update to ensure SOAP RPC-encoded requests are constructed so the generated SOAP body includes the right namespace declarations and type metadata at the operation/body level. | Data Integration |
| INC-D9324 | 987235 | Data type integration details error resolved | The D_pzGetIntegrationSystemDetails data page was throwing StringIndexOutOfBoundsException errors when opening newly created data types without fields or records. Investigation showed the pzGetIntegrationSystemDetails activity was attempting substring operations on empty systemsCSV strings when no integration results were present. This was caused by missing conditional checks before performing substring operations on potentially empty strings, and has been resolved by adding proper conditional validation before string manipulation operations. | Data Integration |
| INC-D966 | 972573 | SOAP connector response parsing restored | Connect-SOAP invocations were failing during response parsing when processing MIME parts, and a MimeConfig$Builder exception at com.pega.apache.axiom.attachments.MIMEMessage.<init>(MIMEMessage.java:126) was generated. This has been resolved by updating the apache-mime4j-core library to the latest version. | Data Integration |
Decision Management
25.1.3 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-C45773 |
962498 | 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-C22614 | 977540 | 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-C33467 | 953829 | Questionnaire file attachment support restored | Case creation was failing with "An internal error occurred. Please contact administrator" when using questionnaires with File type questions configured as "List of Records" in Constellation applications. Investigation showed this was caused by incorrect view metadata annotation where attachment properties were annotated with @p instead of @ATTACHMENT during questionnaire generation. This has been resolved by updating the questionnaire runtime generation logic to detect the underlying property mode for file questions and properly annotate attachment properties. | Decision Management |
| INC-C55752 | 971936 | 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. | Decision Management |
| INC-C58606 | 975821 | Execution profile array bounds handling corrected | Decision execution profiling was encountering "Index -1 out of bounds for length 4096" ArrayIndexOutOfBoundsException errors during profile merging operations, particularly affecting globally optimized strategy (GOS) execution profiles and causing InstrumentedExecutionProfile$WrongProfileState exceptions with "Something corrupted" messages. This was traced to incorrect variable usage in Binary Search Chunks (BSC) iteration within the scanChildIndices method during AOP profile merge operations, and has been resolved by correcting the variable handling in the InstrumentedExecutionProfile class merge. | Decision Management |
| INC-D10792 | 982262 | Improved backwards compatibility for Kafka legacy dataset validation | Kafka datasets created before consumer group functionality was introduced were failing application validation with "No enum constant com.pega.dsm.dnode.api.dataset.kafka.ConsumerGroupPrefixType" errors. Investigation showed this was caused by validation rules not accounting for legacy dataset configurations . This has been resolved by updating Kafka dataset validation artifacts to handle scenarios where the consumer group type is not set while maintaining compatibility with newer consumer group features. | Decision Management |
| INC-D11187 | 981564 | Connection resilience improved for GCP host migrations | Applications were experiencing connection resets during Google Cloud Platform (GCP) host migrations, causing service disruptions when the cloud infrastructure performed routine maintenance operations. This has been resolved by implementing enhanced connection reset timeout configurations and increased diagnostic logging to better measure connection drop timing. | Decision Management |
| INC-D12212 | 984604 | Adaptive model single-level-v1 pxDecisionResults format deprecated | The documentation for Pega Customer Decision Hub dynamic system settings - Adaptive Learning has been updated to note that the single-level-v1 value for the decision/adm/modelExecutions/format dynamic system setting (DSS) is deprecated. In an environment configured with single-level-v1, the system automatically uses multi-level-v1 for all new Decisions. Existing records created with the single-level pxDecisionResults format remain readable. To align with the supported pxDecisionResults format, update the value of the DSS to multi-level-v1 if it is currently set to single-level-v1. This information has also been updated in the documentation for Withdrawn and deprecated features in Pega Customer Decision Hub. | Decision Management |
| INC-D12999 | 983584 985189 |
Legacy component driver count mismatch resolved | ArrayIndexOutOfBoundsException errors were occurring when switch components in strategic filters fell back to legacy execution, particularly in "For each Strategy in StrategicFilter". Investigation showed this was caused by certain embedded legacy strategy components with hidden dependencies that introduced extra runtime references that were not counted up front, so the profiler allocated too-small ordered structures and overflowed. This has been resolved by forcing those legacy cases to use unordered iteration, which avoids the overflow. Additional diagnostic logging has also been added. | Decision Management |
| INC-D136 INC-D5368 INC-D2295 |
975748 976689 976767 |
Updated error handling for ADMDataSetSaveOperation | Data flow threads were becoming stuck in an unsafe park state after ADMDataSetSaveOperation encountered a ConcurrentModificationException during realtime data flow execution. This has been resolved by adding exception handling in SaveStageProcessor to properly release the latch. | Decision Management |
| INC-D14025 | 985934 | Data migration pipeline timeout handling improved | The data migration pipeline from Production was failing during Data Export with SocketException errors, with REST Service DataSync taking 300 seconds against a 30-second DMConnectorTimeout. Investigation showed this was caused by insufficient timeout handling and missing wait shapes in the Data Export flow compared to Data Import. This has been resolved by updating the pyInitializeDataExport flow to introduce a Wait assignment before continuing to repository-connection validation/export. | Decision Management |
| INC-D1441 INC-D1181 |
973009 973531 |
Repository based case attachments corrected for email notifications | Email digest notifications from Prediction Studio were being received but the attached CSV files were appearing as error files and could not be opened properly when repository-based attachments (pegacloudfilestorage) were being used. Investigation showed that the GenerateMailAttachment activity was only setting the pycategory field on the Link-attachment record while leaving the pxStorageType field blank, causing the content retrieval logic to fail in determining the correct handler for repository-stored files. This has been resolved by updating the pzGenerateMailAttachment activity to conditionally populate the pyStorageType field. |
Decision Management |
| INC-D14552 | 984867 | Data ingestion timeout and count mismatch issues resolved | Data ingestion operations were experiencing DriverTimeoutException errors occurring after one minute timeouts during Cassandra upsert operations, accompanied by "Query timed out after PT1M" messages in the UpsertStatementExecutionException stack trace. Additionally, reconciliation processes were showing count mismatches between expected and actual record counts after data ingestion, with subsequent reconciliation runs sometimes displaying correct counts without requiring data copy operations. Investigation showed these issues were caused by timeout handling problems in the Cassandra driver and data consistency issues during high-volume ingestion operations. This has been resolved. | Decision Management |
| INC-D16104 | 987079 | Troubleshooting documentation added for partition count mismatch between pxResponsesStream and InteractionFiles datasets | When importing InteractionFiles from a lower environment with fewer partitions into a production environment where the Kafka topic has been created with more partitions, a partition count mismatch may be seen between the pxResponsesStream and InteractionFiles datasets. To address this, comprehensive troubleshooting documentation has been added to provide clear guidance on regenerating the InteractionFiles dataset to match the actual number of partitions in the pxResponsesStream topic and recreating affected summary datasets to restore proper backfill operations. Refer to "Inconsistent Number of Partitions in pxResponsesStream and interactionFiles Dataset" for more detailed information. | Decision Management |
| INC-D1645 INC-D3558 INC-D9444 |
973459 979729 979465 |
Deserialized JSON date field handling updated | Data flows processing JSON records with date fields were failing when attempting to save deserialized date properties to DDS datasets, resulting in NullPointerException errors. This was traced to null values during date field conversion in the JSON data transform process when using TimeOfDay properties in the Strategy Result class, and has been resolved with an update to enhance logging, null date handling, and exception messages. | Decision Management |
| INC-D16966 | 986572 | Dataflow configuration settings properly recognized from JVM arguments | Dataflows were continuing to execute despite setting JVM arguments to disable them, preventing database refresh operations that required all dataflows to be stopped. Investigation showed this was caused by the system not properly recognizing the configurable dynamic system settings for dataflow max_active_runs when specified as JVM arguments rather than DSS settings, and this has been resolved. | Decision Management |
| INC-D17007 | 987868 | IH summary partial key read performance optimized | Outbound decision runs were experiencing significantly longer execution times than expected. This was traced to Interaction History summary read operations which had redundant client-side CPU processing that scaled with the number of keys defined on the summary. This has been resolved by optimizing the BrowseByKeys processing logic to eliminate the redundant processing overhead. | Decision Management |
| INC-D18972 | 990459 | Action analysis service authentication header handling fixed | Action Analysis Service Client was receiving 401 unauthorized errors when accessing the configurations endpoint. This was caused by the client not passing the required authorization header for configuration requests due to a missing entry in gradle/engineProjects.gradle, and has been corrected. | Decision Management |
| INC-D20792 | 994583 | Data migration export process corrected for interval-enabled configurations | Data migration pipelines were getting stuck in the Monitor Progress stage during the Initiate Data Export phase. Investigation showed this was caused by a missing skip ADM check in the data migration path when intervals were enabled, which created an empty clipboard reference that led to status check failures in the pyExportDataFlowRunStatus flow. This h | Decision Management |
| INC-D2667 | 976320 | Job scheduler check added for archive folders before purge | Daily job scheduler RemoveImportJobFilesAndProcesses activities were failing due to missing ArchivedDataFiles folders when data jobs were created but no ingestion occurred. This was caused by the system attempting to purge archive folders that were never created, and has been resolved by implementing proper folder existence checks before attempting purge operations. | Decision Management |
| INC-D2893 | 975127 | Keyspace prefix configuration resolved for usage metrics | Applications were experiencing connectivity issues due to the system defaulting to connecting to an unprefixed usage_metrics keyspace even when a prefix was configured in the Cassandra settings. This has been corrected. | Decision Management |
| INC-D331 | 977999 | Adaptive model predictor display limit increased | Adaptive model reports were displaying only 500 predictors in the predictor importance tab despite having more than 500 predictors available in the model. This was caused by hardcoded limits in the pzgbpredictorinfo and pzpredictorinfo data retrieval queries, and has been resolved by increasing pyMaxRecords from 500 to 2000 for predictor reports. | Decision Management |
| INC-D3777 | 988606 | Real-time data flow event cleanup performance optimized | Cleanup operations for the pr_log_dataflow_events table were timing out due to large data volumes generated by dynamic scaling of real-time Data Flow nodes creating frequent lifecycle and partition rebalance events. This has been resolved by optimizing the cleanup query and implementing batch deletion of old lifecycle events and dataflow errors to prevent query timeouts. | Decision Management |
| INC-D3882 | 976059 | PMML mining model output field population corrected | Issues were seen with Predictive Model Markup Language (PMML) models generated via sklearn2pmml conversion where target fields and output fields were not being populated correctly during model execution. This was traced to improper field mapping during the PMML conversion process, and has been resolved by updating the field population logic. | Decision Management |
| INC-D3944 | 973900 | Kafka dataset migration compatibility updated | Publishing messages to Kafka Data Sets was failing consistently with the error "IllegalArgumentException: No enum constant com.pega.dsm.dnode.api.dataset.kafka.MessageHeaderDataFormat" after moving the Kafka topic from one data center to another. The error occurred during message configuration extraction when Pega attempted to validate the Message Header Data Format, with the system expecting values like KVLIST or Custom but encountering an unsupported enum constant at runtime. This was traced to a compatibility issue when Kafka data sets created in Pega 8.5 were imported into Pega 8.6+ environments, and has been resolved by addressing the enum validation logic to properly handle legacy data set configurations. | Decision Management |
| INC-D4587 | 976296 | NLP model name passed to resolve runtime exception | Manual testing of Text categorization Topic models in Prediction Studio was resulting in error pages and system hangs, while the same functionality worked correctly in Dev Studio. This was traced to the model class name not being passed properly during testing, resulting in a PRRuntimeException. To resolve this, the model class name will be passed as a parameter. |
Decision Management |
| INC-D5272 | 976233 | Google Pub/Sub dataset topic handling updated | Google Pub/Sub datasets were failing to function properly when topic configurations used application settings, with the system using outdated topic names even after application setting updates and node restarts. This was traced to the pyTopicName property being set during connection testing and not being updated when application settings changed. This has been resolved by ensuring topic names are dynamically resolved from current application settings rather than cached values, with a fallback to legacy topic name behavior. | Decision Management |
| INC-D5321 INC-C35650 |
984602 1000214 |
Parameterized predictors synchronized with adaptive models | Parameterized predictors were being populated in strategy results during testing but were not appearing as available options in Prediction Studio monitoring, displaying "No predictors available" instead. Investigation showed this was caused by a missing fail-safe auto-sync mechanism during rule save-as operations. This has been resolved by implementing an automatic synchronization process that ensures parameterized predictors are properly made accessible to adaptive models during save operations. | Decision Management |
| INC-D6631 | 976644 | Proposition filter explanation values corrected for page collections | When evaluating proposition filters with conditions against page lists accessed through property reference chains, Engagement Policy explanations were displaying an accurate filter status, but the actual value was consistently displaying as "0" instead of showing the correct number of pages in the page list that satisfied the criteria. This has been resolved by correcting the explanation calculation logic so that actual values now properly reflect the number of qualifying pages in the collection when accessed through property reference chains. | Decision Management |
| INC-D7162 | 981388 | Bias check functionality restored for symbolic columns with mixed data types | Ethical bias simulation reports were returning empty results when analyzing symbolic columns that contained both numeric values and missing data. This was traced to the system incorrectly converting symbolic columns to numeric columns during data processing when missing values were filtered out, preventing the bias analysis from following the correct computational path for symbolic data types. This has been resolved by modifying the bias analysis logic to preserve the original column type of the bias field instead of inferring the type based on the content of the selected bias field after filtering. | Decision Management |
| INC-D7585 | 977427 | Monitoring message handling corrected | Messages were being lost during monitoring processes, causing discrepancies in response counts. This has been resolved with an update to ensure partitionOffsets are retained after truncation instead of being cleared. | Decision Management |
| INC-D7910 INC-D7573 INC-D15985 |
984114 984111 986685 |
Data flow validation logic updated for accurate record counting | Count mismatches were seen between processed record counts and input record counts, causing post-validation failures. Investigation showed this was caused by the PostValidation logic incorrectly relying on pySuccessfulRecords instead of pyProcessedRecords when validating data flow progress. This has been resolved with an update to rely on pyProcessedRecords so validation and reporting are aligned with the checkpointed partition progress to ensure accurate record counting. | Decision Management |
| INC-D8368 | 978544 | BigQuery WIF authentication flow completed | The authentication process was failing to complete properly when accessing BigQuery using Workload Identity Federation (WIF) configuration. This was traced to missing handling for the impersonation of the Foundry Application service account, and this has been resolved. | Decision Management |
| INC-D8370 INC-D16213 |
987147 993639 |
Explainability extract processing enhanced for embedded strategies | Explainability Extract operations were throwing exceptions when executed on top-level Globally Optimized Strategies (GOS) containing embedded strategies with data join components that reference other components for iteration. This was traced to embedded strategies being unable to process strategy result pages wrapped in execution audit-specific wrappers, and has been resolved by adding support for embedded strategies to handle strategy result pages with and without execution audit wrappers equally. | Decision Management |
| INC-D8475 | 978260 | GOS always-on profiling execution errors resolved | After update, both scheduled outbound runs and real-time events were failing with ArrayIndexOutOfBoundsException errors indicating "com.pega.decision.compute.ssa.exception.DecisionRuntimeException: Message Caused by ArrayIndexOutOfBoundsException. Possible components or rules causing exception: [mzCheckPropositionFilteredForTestMode]" with detailed evaluation stack traces showing componentExitLog and trackInput operations failing during strategy execution. Investigation showed this was caused by incorrect always-on profiling metadata being assigned to non-inlined strategy components, which resulted in wrong processing when execution was being recorded into execution profiles. This has been resolved with an update to generate correct profiling metadata and add the DSS "decision/strategy/gos/enforceComponentBoundaries" that forces the GOS compiler to apply optimizations only within component boundaries, preventing cross-component optimization propagation when enabled. | Decision Management |
| INC-D8642 | 979103 | Data Decision Store interface behavior corrected | The Data Decision Store UI had unexpected table scrolling and display issues when navigating through the specified steps in the application. This was caused by Decisioning landing page table overflow and has been corrected by adjusting the CSS targeting/scroll container for the deployment view. | Decision Management |
| INC-D8721 | 990881 | File dataset browsing capability restored | Datasets were showing zero records when browsing despite having files available in storage, preventing access to existing data. Investigation showed this was caused by missing .directory metadata in the meta directory structure that shadows the original file structure for performance optimization. This has been resolved by implementing a directory meta structure update mechanism that ensures consistent and recoverable state, along with a recovery activity to fix issues in existing structures. | Decision Management |
| INC-D885 | 989516 | Data flow file creation reliability enhanced | A transient failure during WriteDataToInteractionFiles data flows file creation/write/flush could cause the whole batch to be treated as non-retryable and effectively dropped. To address this, the legacy eager empty file creation has been eliminated, failed records are now marked retryable so the batch can be retried, and empty files no longer produce stray .meta files. | Decision Management |
| INC-D9234 | 981155 | Customer Decision Hub (CDH) explainability and upgrade testing enhanced | An update has been made to SetProperty shape instrumentation to ensure full visibility and auditability in explainability operations, and the CDH update analyzer has been improved with preupgrade testing capabilities to proactively identify function issues during version transitions | Decision Management |
| INC-D9517 | 986195 | Data dictionary relevance scope refined | After update, searches were returning increased relevant record counts with relevance spanning across multiple classes instead of being restricted to intended classes. This has been addressed with updates in auto tagging to suppress the creation of relevancy for the properties of parent classes in the child class. | Decision Management |
| INC-D9522 INC-D13100 INC-D17995 |
985986 988817 988825 |
Impact analyzer data display restored | Impact Analyzer displays were empty in the Impact Analyzer interface despite having run the pxSyncActuals activity and verified results through data flows. Investigation showed this was caused by incorrect GroupedValue filtering when filter conditions were applied to empty fields for records. This has been resolved by updating the GroupedValue filtering logic to properly handle filter conditions on empty fields. | Decision Management |
Low-Code Application Development
25.1.3 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C42814 | 968421 | Lock and roll application instance association fixed | Lock and Roll processes were incorrectly associating new application instances with previously locked ruleset versions when attachments were added during the process. This was caused by the attachment handling interfering with the proper version association logic during ruleset locking and rolling operations, and has been resolved by updating the application instance association logic to remove ruleset version from rule page if the class is Rule-Application. | Low-Code App Development |
| INC-C45469 | 965347 | 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 | 965511 | 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-C56696 | 970566 | 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-D10635 | 986083 | Warning logs and fallback added for lost or invalid production level | In order to assist with troubleshooting development environments where Production Level was sporadically being set as empty or 0 in the pxProcess page, a validation check has been added along with warning logging. If an invalid level is found during validation, it will fall back to the System rule value. | Low-Code App Development |
| INC-D12079 | 984549 | Application definition ruleset stabilized | When deleting branches while having a different branch selected, the application definition rule would change its ruleset from the base application name to the currently selected branch ruleset, potentially causing application access issues. Investigation showed this was caused by the pxChooseBestRuleSet function incorrectly selecting branch-specific rulesets during branch deletion operations. This has been resolved by ensuring application definition rules maintain their proper base ruleset assignments regardless of currently selected branch context during deletion operations. | Low-Code App Development |
| INC-D13186 | 983339 | Improved LogViewer resource release | Resource closure has been updated for the LogViewer HTML rule to ensure file input streams are consistently released. | Low-Code App Development |
| INC-D18113 | 989899 | Usage reporting data collection restored | The UVU Daily Usage report stopped collecting data after applying updates. This was caused by the sppr_aggregate_usage stored procedure containing unqualified table references that failed when executed by users with different default schemas. and has been resolved by updating the stored procedures to include proper schema qualification for all table references. | Low-Code App Development |
| INC-D2165 INC-D16973 INC-D9514 |
979907 988780 981277 |
System information button function corrected | After update, the System Information button was failing to load and displaying the error message "No JMS Base Context Found on this Platform" along with JsonGenerationException errors when attempting to access system diagnostic information through Dev Studio. This was caused by conflicts between JMS and StAX XML processing implementations, particularly affecting JBoss EAP and WebSphere application server environments, and has been resolved by adjusting XML declaration stripping and XML serialization configuration, with an additional work applied for WebSphere environments paired with IBM JDK to ensure complete compatibility across all supported application server platforms. | Low-Code App Development |
| INC-D2315 | 974399 | Application wizard division class validation improved | The New Application wizard was incorrectly validating class structures when divisional layers were included in the configuration, missing the divisional class from the validation sequence. Investigation showed this was caused by the validation logic not accounting for divisional layer classes in the class hierarchy check. This has been resolved by updating the validation sequence to properly account for Division and Unit class layers when checking for existence of a class. | Low-Code App Development |
| INC-D5425 | 979636 | Word content control functionality restored | Word content controls in document templates were not functioning properly after update. This was an unintended side effect of work done on the parseAndPopulate function of the docxGenerator API which resulted in compatibility issues with the updated docx4j library. This has been resolved by updating the code with a condition which will extract content if Word content control is used. | Low-Code App Development |
| INC-D6811 | 987117 | Page validation error resolved in tracer viewer | Page validation was failing in the PZINITIALVALIDATIONFORPERFORMACTION activity with the error message "DeclarePageReference' does not match top of stack" appearing in the tracer viewer. Investigation showed this was caused by a validation mismatch issue that could occur with the tracer accidentally changing the runtime state while collecting page messages if AutoPopulate and Declare Expressions were involved. This has been resolved with an update which ensures the tracer collects primary-page messages in a guarded way that temporarily disables the state-changing behaviors around that read. | Low-Code App Development |
| INC-D6854 | 986714 | Updated grammar for Expression Builder | After update, referring to a list/group property in AdditionalInfo from ContainerPayload generated an error in the Expression Builder. This was due to the introduction of stricter validation for the Expression Builder functionality in design time which prevented chaining property access after a function call within a single expression during design-time validation, even though the runtime engine could still evaluate these expressions correctly. This has been resolved by updating the grammar to support the <> operator, single-quoted strings '...', dot (.) in function examples / qualified usage, slash ( \ ) escape handling in strings, and function patterns such as whatComesAfterFirst(.pyFilterName,'.'). | Low-Code App Development |
| INC-D8785 | 980364 | Handling updated for requestor exception | The RequestorHealthDaemon was throwing ConcurrentModificationException errors and failing with stack traces showing "Invalid value for Requestor parameter" errors. This has been resolved by expanding the exception handling to cover the broader RuntimeException class needed for ConcurrentModificationException. | Low-Code App Development |
| INC-D9504 | 983459 | Tracer security updated | Cross-site scripting protections have been updated for the tracer. | Low-Code App Development |
Mobile
25.1.3 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-D1531 | 975488 | Mobile app worklist updates correctly synchronized | Mobile applications were not displaying updated worklist items after modifications were made to the List Item Information configuration. This was traced to synchronization issues between the mobile app and the updated pyWorkList configuration, and has been resolved by updating the Pega Rule-Mobile-View-List activities to refresh/generate the mobile list view state after save. | Mobile |
Project Delivery
25.1.3 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C34811 | 958999 | Documentation clarified for expected UDF alert behavior | The UDF alert documentation has been updated to clarify that PEGA0167 alerts can occur as expected behavior following long idle periods, and represent normal system behavior rather than defects. | Project Delivery |
Reporting
24.2.2 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C52711 | 964720 | 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-C57342 | 975240 | Corrected scheduled reports with timezone failure | After update, scheduled reports were failing with "unable to find instance" errors in multi-application environments. This occurred when the pyUpdateScheduledReportsWithCurrentTimezone activity was executed from one application context while the scheduled report shortcuts were created in a different application context, and has been resolved by modifying the timezone update activity to properly handle cross-application contexts so scheduled report shortcuts can be accessed regardless of which application context they were created in. | Reporting |
| INC-C59359 | 974441 | Insight relative date filtering accuracy improved | Relative date filters in Insights were returning records outside the expected date range, such as including multiple days when "is equal to current day" was selected. Investigation showed this was caused by improper date range calculation in the filter payload generation for relative date comparisons. This has been resolved by correcting the timezone handling when transforming relative date filters into date/time ranges in the condition builder. | Reporting |
| INC-D10340 | 982214 | Corrected batch index processor interference with case creation | Background case creation processes were being disrupted by SRS indexing operations related to pySASBatchIndexProcessor. The BatchEDIProcessor from Smart Claims Engine was unable to create work objects, and was receiving the error "Database-BadClassDef-BadObjectClass Trying to open rule PARSEX12!NM1 of class Rule-Parse-Delimited, but no defined-on class (pyClassName) was specified". Investigation showed this was caused by complex dependencies between claims processing and indexing caused by unnecessary thread-state cleanup calls for SRS Query Processors. This has been resolved by disabling calls to dictionaryReset and declarativeContextClear to prevent the thread state being cleaned more aggressively than needed, reducing interference between batch indexing and background case creation processes. | Reporting |
| INC-D11306 | 985653 | BIX extract functionality for single-stage cases enabled | When creating a case type with a single stage and configuring real time BIX extract rules, running the case type resulted in empty data sets with no case data being extracted. Investigation showed this was caused by a limitation in the BIX real-time extraction feature where the pzDeriveEventType (Final, Internal) activity contained a When condition that evaluated whether the number of stages >=2, preventing single-stage cases from being processed. This has been resolved by modifying the BIX RTE logic to support single-stage cases and removing the stage count restriction. Logging has also been modified from INFO to DEBUG. | Reporting |
| INC-D12487 | 983055 | GenAI access controls implemented for Explore Data feature | Configurable access controls have been made available to allow administrators to restrict GenAI capabilities for specific users or based on business rules while maintaining system-wide toggle functionality. The new pyShowExploreDataAIInput 'when' rule in @baseclass is used to gate AI input visibility and updates pxPopulateDataExplorerInfo to reference pyShowExploreDataAIInput. | Reporting |
| INC-D12830 | 985817 | Context handling updated for scheduled reports | After update, scheduled reports were failing to execute in production. Investigation showed incorrect context validation during scheduled report execution could lead to tasks being handled under the wrong application context, causing some scheduled reports to be skipped or not refreshed correctly. This has been resolved with an update to the scheduled-task activity to explicitly open the target task, verify the current application matches the task’s application, and clean up temporary pages during processing. | Reporting |
| INC-D13222 INC-D10608 INC-D18003 |
988675 984413 990801 |
Real-time BIX extract restored for legacy case types and documentation updated | Real-time BIX extract was failing to capture and transmit case modifications to configured data destinations such as Kafka topics and GCP PubSub when working with case types that had been created in Pega versions prior to 8.8.5. This was caused by the pzProcessChangeDataCaptureCaseTypes activity exiting prematurely at step 7 for case types that lacked initialization stages, preventing the posting of messages to the designated topics. To resolve this, the pzDeriveEventType flow has been updated to properly handle both legacy case types created in earlier versions and single-stage case configurations. In addition, the documentation for real-time BIX extraction has been updated to specify that the Case from which data will be extracted must have its first stage completed before proceeding. | Reporting |
| INC-D13258 | 985965 | Scheduled report end date handling updated | Scheduled reports with "EndBy" dates were continuing to schedule indefinitely because the pyRecurrenceDetails.pyUseEndDate property was always false. This was traced to incorrect end date flag handling in the scheduling logic, and has been corrected. | Reporting |
| INC-D14014 | 985947 | Data display corrected for report widget charts with ampersand | After update, dashboard charts were not displaying all data when the chart labels contained ampersand ("&") characters, though the same charts were rendering correctly when accessed directly through the report browser. This was caused by the ampersand character not being properly converted when passed as a query parameter in the chart rendering process, and has been resolved by updating the pzMultiSeriesData FusionCharts XML and pzComboData FusionCharts files to properly handle ampersand characters in chart labels. | Reporting |
| INC-D14250 | 987267 | Repeating view delete functionality restored | Delete icons were missing in Repeating View Panel when header property reference fields contained empty strings, preventing users from deleting corresponding views. This has been resolved by ensuring Field Group dynamic headers fall back to the default “Row N” label when the resolved header value is an empty string. | Reporting |
| INC-D14306 | 984391 | Database connection close during indexing improved | Batch indexing operations were causing database connection exhaustion and repeated node failures when encountering empty blob data, causing batch nodes to fail health checks and restart continuously until queue processors were manually disabled, particularly when processing items with null pzPVStream values. This was caused by the search indexing code not properly releasing database connections when encountering BadInstanceDataException errors from empty blob streams, and. has been resolved by updating the connection cleanup and error handling for empty blob scenarios during batch indexing operations. | Reporting |
| INC-D311 | 973421 | PDF filename extension duplication eliminated | The Create PDF functionality was generating files with duplicate .pdf extensions in Constellation applications, resulting in filenames like "document.pdf.pdf". The issue occurred because legacy attachment components displayed extensions as part of the filename, but Constellation separates extensions, causing the system to add .pdf twice when the extension was already included in the name. This has been resolved by updating the PDF creation logic to prevent the duplication. | Reporting |
| INC-D3168 INC-D14322 |
977867 990938 |
Report definition row key retrieval corrected | Report definitions configured with GetRowKey set to pzInsKey were experiencing inconsistent behavior where the pzInsKey column was appearing in query results in some environments but not others. Investigation showed this was caused by replica-mapped classes being incorrectly filtered out of internal table key resolution when using an alternate database, causing pzInsKey to be dropped from the generated SQL. This has been resolved by adjusting the internal table key resolution logic to always include keys for alternate-database replica tables. | Reporting |
| INC-D6108 | 977520 | Localization added for filtered date picker labels | Date picker "From" and "To" labels were displaying in English regardless of their configured locale when applying range filters to Date/DateTime fields in Inline Dashboards. This has been corrected. | Reporting |
| INC-D6592 | 988253 | Date picker year display corrected in dashboard filters | Year values were not displaying properly in DD-MM-YYYY format date range filters when multiple filters were added to Inline Dashboards. This was caused by CSS layout conflicts in the Insight template, and has been resolved by correcting the date picker layout handling for dashboard filters with multiple filter configurations. | Reporting |
| INC-D6593 | 984947 | Dashboard date range filtering corrected | Dashboard Insight date range picker was not displaying records when the same From and To dates were selected for filtering a specific day, instead showing no results. Investigation showed this was caused by the system using identical date and time values in the request, creating an impossible range condition. This has been resolved by adjusting the date range logic to properly handle same-day filtering by setting 23:59:59 for the end filter. | Reporting |
| INC-D8071 | 988120 | AI data exploration error handling improved | Explore data chat functionality was displaying "Unexpected output from the AI" errors when the dataObject was undefined. This has been addressed by updating the dataObject validation and error handling for AI-powered data exploration. | Reporting |
| INC-D8937 INC-D14471 |
980618 984293 |
BIX extract parsing improved for complex property structures | BIX extracts were failing with the error "InvalidReferenceException: The reference pxStageHistory().pxProcesses is not valid. Reason: unexpected character ')' at position 15, expected subscript (wildcards not allowed)" when attempting to extract data containing three-level pagelist property structures, particularly when XML extraction was selected with manifest generation. Investigation showed this was related to previous work that addressed incorrect pxTotalInstanceCount calculations but inadvertently introduced parsing issues for complex nested property structures involving multiple levels of embedded pagelists. This has been resolved by providing a solution for BIXXML Manifest XML parsing that correctly handles three-level pagelist structures, allowing extracts to complete successfully without the reference validation errors. | Reporting |
Security
25.1.3 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C42978 | 974385 | JWT audience mapping processing corrected | JWT processing was failing when mapping audience (aud) claims through token profile rules, while other claims like sub and iss processed correctly. The error "InvalidParameterException — class "java.util.ArrayList" does not match mode "String" " was generated. This issue was caused by improper handling of audience claim deserialization in the pxProcessJWT activity where list-valued claims—especially the standard aud claim as returned by Nimbus—were being mapped into Pega clipboard properties as if they were simple scalar values. To resolve this, claim mapping has been made type-aware, so JWT processing no longer fails on valid tokens that contain multi-value claims, and safe handling has been added for non-string scalar claim types while skipping null/blank claims more safely. | Security |
| INC-C56768 | 979029 | Pega Desktop security updated | Cross-site scripting protections have been updated for Pega Desktop support. | Security |
| INC-D10774 | 986943 | Access policy condition results accuracy improved | The access policy condition results page was not reflecting validation results correctly when using the "Actions > View policy condition results" option, while the "Verify Policy" option worked as expected. This was caused by the ABAC policy-condition results page evaluating index- and association-backed conditions incorrectly at the per-condition level, effectively relying on the overall policy verdict instead of independently evaluating those conditions. This has been resolved with an update to ensure the ABAC policy-condition results page evaluates each condition independently. | Security |
| INC-D10948 INC-D13780 INC-D14227 |
983566 984015 984517 |
Forgot password functionality restored | After update, authentication failures were seen when attempting to use the forgot password functionality, with the system continuously looping back to the login screen and displaying "Please enter valid username" error messages even when valid operator IDs were entered. This was traced to the username/operator validation logic within the forgot password flow experiencing increased processing time for OAuth token lookups that failed with cache lock errors and retried multiple times, and has been resolved. | Security |
| INC-D11065 | 982465 | Token storage capacity increased for OAuth authentication | OAuth2 token decryption failures were seen while creating the OAuth2 client token. This was traced to token truncation, and was caused by the column length limitations of 4000 characters for pyaccesstoken and 512 characters for pzrefreshtoken columns being insufficient to store full token lengths. This has been resolved by increasing pyaccesstoken column capacity to 8000 characters and pzrefreshtoken to 4000 characters in the pr_data_token table. | Security |
| INC-D12499 | 990791 | AWS identity federation credential retrieval resolved | Identity federation rules were failing to fetch AWS temporary credentials when running in background jobs, with the error message "Cloud Identity Federation failure : Failed to fetch AWS temporary credentials for identity federation rule:GlobalIdentityFed" appearing in logs along with SECU0023 security alerts. Investigation showed that access group values were appearing as blank or null during credential retrieval operations, preventing proper authentication with AWS services. This has been resolved by refactoring the access group retrieval mechanism to properly handle null and empty cases, along with enhanced token caching logic to avoid unnecessary invalidation broadcasts and improved handling of the Hazelcast decommission latency issue. | Security |
| INC-D12665 | 990970 | Cross site scripting protections updated | Comprehensive URL parameter encryption has been added to maintain security throughout the entire user session lifecycle. |
Security |
| INC-D1298 | 989557 | XSS prevention optimized for skin rules | The pyPreventXSSInLabel DSS setting was causing issues when applied to final skin rules, disrupting normal UI rendering and label display functionality. This has been resolved by implementing conditional XSS prevention that skips processing for final rules while maintaining security for editable content. | Security |
| INC-D13101 | 982545 | SAML authentication handling updated | In order to support site-specific needs for unsigned assertions, the DSS security/SAML/allowUnsignedAssertion (comma-separated list of auth service names, case-insensitive) has been made available. The default behavior is to enforce signature validation (DSS is set to false). | Security |
| INC-D14332 | 985473 | Multi-factor authentication handling improved for external authentication | A blank MFA page was displaying when logging in via SAML/OIDC/Platform Authentication with Multi Factor Authentication policies enabled but no associated email account configured. Investigation showed this was caused by insufficient validation of email account prerequisites for MFA policies. This has been resolved by ensuring MFA security policy handling behaves correctly even when an operator has no email account. | Security |
| INC-D15026 | 984655 | OAuth2 client registration deletion warnings added | Users were inadvertently deleting default OAuth2 Client Registration rules starting with "PegaApp_" without understanding their critical role, which prevented application login access. This has been addressed by implementing warning messages that inform developers when attempting to delete OAuth2 Client Registration rules that deletion will prevent user login to the application. | Security |
| INC-D15773 | 986438 | Cookie reuse security updated | Handling has been updated to improve security for cookie reuse scenarios. | Security |
| INC-D225 INC-D12258 |
974810 988566 |
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 | 983268 | 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-D4523 | 980779 | OIDC authentication flow streamlined for expired requestor sessions | The error "Requestor session on the server expired due to long inactivity" was generated when users took longer than 2 minutes to authenticate with their identity provider during OIDC single sign-on, requiring users to manually close the window and restart the login process. This was traced to the handling for expired short-lived requestor sessions when receiving valid authentication responses, and has been resolved by implementing automatic redirection to the identity provider instead of showing the error screen, allowing seamless re-authentication without user intervention. | Security |
| INC-D465 INC-D390 |
978792 979117 |
Property encryption validation for page and pagelist properties resolved | After update, attempting to configure PropertyEncrypt actions in Access Control Policies for Page and Page List properties resulted in the error message "Property name - This embedded property is not optimized. Please optimize the property before using it in PropertyEncrypt access control policy. Exposed properties other than text type are not allowed", even when properties were properly optimized. This was traced to overly restrictive validation logic incorrectly blocking Page and Page List properties from being used in PropertyEncrypt configurations, and has been resolved by removing the validation restrictions for pagelist and page group properties, implementing proper detection of PageList/PageGroup mode to resolve item classes correctly, and adding appropriate warning messages for non-optimized properties while allowing text-type properties to be saved successfully. | Security |
| INC-D4684 | 978317 | OIDC authentication service mapping error corrected | OIDC authentication was failing with NullPointerException errors when authentication services contained attributes in the mapping tab, specifically when dot notation variables were present. Investigation showed this was caused by realizeTheExpression prematurely fetching SSO attribute values from the clipboard before the request was generated, causing stale/empty data to be used during expression resolution. This has been resolved. | Security |
| INC-D5006 | 977233 | ABAC read policy access control restored | ABAC Read policies were not evaluating properly after update. This was traced to work done on PolicyConditionWhenAssembler.java, and has been corrected. | Security |
| INC-D5096 | 975409 | 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 INC-D18832 |
975550 975008 993754 |
API authentication performance improved | REST API calls using OAuth 2.0 token authentication were experiencing significant delays due to cache lock acquisition failures. This was caused by synchronization issues in the OAuth2 cache implementation following Hazelcast decommissioning, and has been resolved by updating the cache lock and node synchronization mechanisms. | Security |
| INC-D5346 | 974955 | HTTP 412 retry mechanism implemented for HashiCorp vault | Intermittent failures were seen when connecting to HashiCorp vault clusters, resulting in HTTP 412 errors. Investigation showed this was caused by token propagation delays within the HashiCorp vault cluster infrastructure. Automatic retry logic has been added to assist with request failures. | Security |
| INC-D6137 | 978594 | Hashicorp authentication connectivity corrected | After update, HashiCorp Vault authentication was failing with "Server returned HTTP response code: 400 for URL" errors. Investigation showed this was caused by changes in how HTTP request payloads were being formatted when communicating with HashiCorp Vault's authentication endpoints. This has been resolved by refactoring the VaultManagementService to use JsonObject for request payloads. Diagnostic logging has also been added. | Security |
| INC-D70 | 981028 | Security validation improved against improper access control | An update has been made to prevent unauthorized function execution. | Security |
| INC-D7107 | 980248 | JWT token expiration handling improved to reduce unnecessary alerts | Unnecessary runtime exceptions appeared in PDC monitoring when JWT tokens expired during validation, creating false alarms for developers investigating system issues. This has been resolved by modifying the error handling in the pxProcessJWT activity to log errors instead of runtime exceptions for expected token expiration events. | Security |
| INC-D7577 | 980862 | Azure identity federation connectivity restored | Azure identity federation rule testing was failing with authentication errors "MsalServiceException: AADSTS90061", "NoSuchMethodError related to io.netty.channel.SingleThreadEventLoop constructor", or "NoSuchMethodError: 'void io.netty.channel.SingleThreadEventLoop.(io.netty.channel.EventLoopGroup, java.util.concurrent.Executor, boolean, boolean)". Investigation showed this was caused by incompatible netty jar versions in the platform. This has been resolved by updating the jars. | Security |
| INC-D7744 | 984664 | OAuth 2.0 logging improved | In order to assist with diagnosing authentication issues, OAuth token endpoint failures will now log the provider’s actual error details (error / error_description) instead of only a generic HTTP status. | Security |
| INC-D8286 | 988108 | Open redirect security updated | Open redirect handling for OAuth2 authorize endpoints has been updated for improved security. | Security |
| INC-D9004 | 988751 | CIDR-based studio access implemented | CIDR-based access restrictions are now available to restrict studio access exclusively to IP addresses within client-defined CIDR blocks. | Security |
| INC-D9821 | 985339 | Security updated for cross-site scripting | Cross-site scripting protections have been updated for App Studio and rule set editing. | Security |
| INC-D9950 | 990368 | Updated security handling for Localization migration | SSL handshake failures were seen during localization migration when using self-hosted CDNs with custom certificates, resulting in messages such as "Error while generating localization bundle for locale nb-NO" and JsonSyntaxException messages. Investigation showed the migration activity used an OkHttp client that did not honor the Pega Platform trust store, and this has been resolved by replacing the OkHttp client with a Pega REST Connector that properly uses the platform trust store for secure retrieval of component localizations from CDN endpoints with custom SSL certificates. | Security |
System Administration
25.1.3 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C57992 | 983874 | Debug logging added for queue processor | Additional logging has been added to help trace queue processor enqueue operations by surfacing the generated message. | System Administration |
| INC-D10162 | 984904 | Log level changed for job scheduler lock recovery error | Multiple batch nodes were generating recurring alerts for job lock recovery failures across various jobs, with the error "Unable to recover lock for Job[pzQueueProcessorMaintenance ErrorMessage=Database-LockFailure-LockHeldByAnother" appearing repeatedly in logs. To prevent log overload, a failed job-lock recovery is no longer logged as an error; instead, it is logged only at debug level and only when debug logging is enabled. | System Administration |
| INC-D17298 | 989476 | Axios updated | The Axios library has been updated to a newer supported version. | System Administration |
| INC-D18637 | 995131 | Cassandra read operations optimized for response monitoring | The MKTResponseHandler dataflow was experiencing significant performance degradation. Investigation revealed that each ADM response was triggering duplicate Cassandra read operations for the same subject/interaction pair - one from the newly introduced ResponseMonitoringHelper and another from the pre-existing ClientImpl. Investigation showed this was caused by the Response Monitoring feature adding an extra readByKeys() call to Cassandra that duplicated existing functionality. This has been resolved by eliminating the unnecessary duplicate Cassandra read operations while preserving the monitoring functionality. | System Administration |
| INC-D1909 | 978105 | Queue processing stability improved for corrupted entries | Agent processing was stopping for 10 minutes when encountering queue entries with null pzpvStream values in pr_sys_queues or pr_sys_queue_sla tables, generating BadInstanceDataException errors. This was traced to corrupted queue items with null stream data that prevented proper page population from the database, and has been resolved by adding null checks to queries for the pzpvstream column and implementing table constraints to prevent insertion of null values, along with alert generation for handling such scenarios. | System Administration |
| INC-D2958 | 977297 | Job scheduler alert diagnostics enhanced | In order to assist with diagnosing Job Scheduler execution failures, the alert configuration and job scheduler alert logging have been updated to include additional alert settings and richer exception details. These include an extended default granular alert configuration (pySetting) with additional alert codes and thresholds, and exception stack traces in the generated error text. | System Administration |
User Experience
25.1.3 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C25821 INC-C32126 |
937685 944267 |
Table filter HTML tag display cleaned | HTML span tags appeared in optimized table filters when filtering integer columns with negative values. This has been corrected. | User Experience |
| INC-C30897 | 947301 | Flow action localization corrected | Flow action names were appearing in their default language rather than the localized values when accessed through mobile applications. This was caused by the localization packaging process not automatically including flow action name translations for work item classes, and has been resolved. | User Experience |
| INC-C32472 | 947605 | 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-C33179 | 945074 | Keyboard navigation improved for case lifecycle dialog | Process lifecycle dialogs were displaying content that could not be scrolled using keyboard navigation, preventing keyboard users from accessing information beyond the initial view. This was caused by missing keyboard scroll functionality in the modal dialog implementation, and has been resolved. | User Experience |
| INC-C37020 | 956353 | 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-C39402 | 956475 | Embedded table row deletion restored | Row deletion was failing in embedded tables containing dropdown components when no placeholder text was configured, while working correctly when placeholders were present. Investigation showed this was caused by child dropdown components re-rendering and populating Redux state even when no page reference existed for the embedded data. This has been resolved by preventing child component re-rendering when page references do not exist for embedded data structures. | User Experience |
| INC-C40613 | 953921 | Country code SXM added | Support has been added for country code SXM (Saint Martin, Dutch part). | User Experience |
| INC-C42330 | 955293 | Profile image display corrected in parallel assignments | Parallel assignments were displaying incorrect profile images where all assignments showed the same user image despite being assigned to different users. This was caused by a stale derived value which only fetched the avatar URL on the initial mount and did not refetch when metaObj.image changed, and has been resolved. | User Experience |
| INC-C43329 | 969101 | 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-C44604 INC-D6289 |
954540 980116 982808 |
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-C50601 | 980144 | Chat functionality restored for real-time messaging and agent availability | Customer service representatives were not receiving new chat assignments for extended periods and were missing real-time customer messages during active conversations. Customer responses were visible after navigating away from the current chat screen and returning, and some messages showed as "Undeliverable". This was caused by capacity updates during chat wrap-up processes and CASE/DATAPAGE_UPDATED events not being properly handled, and has been resolved by adding an extra parameter to the closeContainer Item to allow Customer Service to differentiate between wrap-up and dismiss case actions, and by implementing proper unsubscribe functionality for CASE and DATAPAGE_UPDATED events to ensure real-time message delivery. | User Experience |
| INC-C51191 | 960674 | Rich Text Editor keyboard button localization added | Localization has been added for the "Keyboard" button and "Rich Text Editor toolbar keyboard shortcuts" text in the RTE control. | User Experience |
| INC-C51543 | 961598 | Search functionality smart tip interaction resolved | Search functionality was malfunctioning when smart tips were enabled on search icons, preventing the search window popup from appearing during runtime. This was caused by conflicting interactions between smart tip overlays and search popup functionality, and has been resolved by removing the smart tip. | User Experience |
| INC-C52369 | 964294 | 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-C52779 INC-D5956 |
967080 975930 |
Military time format updated to resolve single digit hours | Applications working with 24-hour time formats were displaying single-digit hours (0-9) displayed without leading zeros, which conflicted with military time standards requiring double-digit hour formatting (00-09). This has been resolved by updating the date time calendar and input display logic with a new flag 'enable24HourFormatting' which is enabled by setting the pega.u.d.enable24HourFormatting value to true in userWorkForm. | User Experience |
| INC-C53585 | 973718 | 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-C54634 | 972484 | 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-C54852 | 956353 | Button keyboard navigation restored for dirty forms | Buttons configured with both Click and Enter events were not responding to keyboard Enter presses when forms were dirty and only perform harness was present. This was caused by a missed use case in new feature implementation that prevented proper keyboard event handling on dirty forms, and has been resolved. | User Experience |
| INC-C55697 | 970101 | Validation error labels fixed for pagelist properties | Validation error messages were not displaying field labels for pagelist properties even when the displayFieldNameInValidationMsg DSS was enabled. This was caused by the validation message system not properly handling pagelist property labels when the DSS setting was active, and has been resolved. |
User Experience |
| INC-C55748 | 973548 | Page list popup initialization error fixed | Opening popups in tables containing Page List properties was automatically triggering the pyDefault Data Transform of the referenced class, causing initialization errors during popup display. This was traced to improper automatic triggering of data transforms for multi-select page list properties, and has been resolved. | User Experience |
| INC-C56147 | 966724 | Date picker correctly announces current date | Date picker controls were applying aria-current="date" to selected dates instead of today's date. This has been resolved by implementing proper aria-current="date" for today's date and aria-selected="true" for selected dates when appropriate in the pzpega_ui_calendar.js functions to improve accessibility. | User Experience |
| INC-C56469 | 968256 | File path control upload behavior corrected | When FilePath Control was added in the section and a file other than png or jpg was uploaded, it was not possible to locate the uploaded file. Investigation showed file path controls were adding incorrect values to pxRequestor.pyFileUpload after update due to the upload handler assuming every multipart file part represented a valid selected file. This has been resolved with an update to FileUploadHandler which will skip file parts when the uploaded size is 0 or the filename is blank, so empty/unselected file inputs are ignored instead of flowing into normal file-save logic. | User Experience |
| INC-C56949 | 972770 | Data reference property navigation for data objects fixed | Data reference property links in data object details tabs were not displaying target data properly, showing blank screens instead of the expected data content. Investigation showed unique ID generation for the pyDetails view was only handled for case objects and not data objects, preventing proper component unmounting and refresh. This has been resolved with an update which uses caseId if present, otherwise a stable unique ID will be generated from dataInfo (dataContext + sorted dataContextParameters). | User Experience |
| INC-C56976 | 975657 | Screen flow attachment deletion behavior corrected | Screen flows were exhibiting incorrect attachment behavior where deleted attachments would reappear when navigating between steps, and attempting to delete them again would cause submission errors. This has been resolved by correcting the attachment lifecycle management in screen flow contexts to prevent deleted attachments from reappearing after cancel and reopen in multi-step forms. | User Experience |
| INC-C57109 | 968190 | Promoted filter null record display corrected | Applications were experiencing issues where promoted filters using True/False properties were not displaying records with null values when "False" was selected. This was traced to the cosmos Boolean Display component not properly handling null values in the filter logic, and has been resolved with an update which renders a display-only checkbox with null value as NoValue. | User Experience |
| INC-C57401 | 973264 | 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-C57828 | 971910 | Column menu display labels corrected | Table view column menus were displaying property IDs instead of configured labels when adding Page or Page list properties, even when proper labels were configured in the record definition. Investigation showed the column menu was referencing internal identifiers rather than display labels for these property types, and this has been corrected. | User Experience |
| INC-C57985 | 976727 | Class rename wizard reference handling updated | The Rename Class and Search/Replace String wizards were not updating references in View rules when renaming classes, causing referenced rules to show error messages about being unable to open rules with the old class names. This was caused by incomplete reference updating logic specifically for View rule types during class renaming operations, and has been resolved by ensuring all rule references are properly updated during class rename operations by regenerating rule references on updating Views / Landing Pages. | User Experience |
| INC-C58030 | 969316 | Corrected currency control duplicate symbol display | After update, currency controls were displaying currency symbols twice after users entered values and clicked outside the field. This was seen when an alternate “other currency symbol” was configured from the Presentation tab. To resolve this, the alternate-symbol branch has been removed during display formatting and always renders using pyCurrencySymbol, which prevents duplicate symbol output for the affected scenario. | User Experience |
| INC-C58048 | 970987 | 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 | 972472 | 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-C58416 | 974722 | Corrected unexpected date range calendar scrolling | Date range controls were causing unwanted page scrolling when opening the calendar, with the screen jumping to the top instead of maintaining the current scroll position. This was traced to the screen position adjustment logic in the calendar display mechanism, and has been resolved by adjusting the timing of focus setting in the date range picker component. The focus is now set after the container is fully displayed and positioned. | User Experience |
| INC-C58641 | 974498 | 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. | User Experience |
| INC-C58802 | 972621 | Screen reader accessibility improved for helper text overlays | Helper text configured as overlay local actions without the close icon was being read twice by screen readers. This was traced to duplicate accessibility markup in the overlay rendering logic, and has been corrected along with enabling "Disable clickaway" by default to improve the user experience. | User Experience |
| INC-C59174 | 972089 | Menu item focus behavior improved for reports tab | The My Reports tab in traditional applications was retaining the Menu-item-active CSS class even after clicking elsewhere on the screen or focusing on other elements. This was determined to be style inconsistency caused by a reload being triggered through customizations, and has been resolved. The styling has also been modified to update the selected-item indicator color and add a background color for the selected menu item anchor, making the active menu item clearer and more consistent. | User Experience |
| INC-C59175 | 973520 | Console error when opening constellation cases resolved | "Uncaught ReferenceError: PCore is not defined" console errors were generated when attempting to open Constellation cases in the Cosmos Portal, though no functional issues occurred. Investigation showed this was caused by the disconnectedCallback method being triggered for web components when the tertiary container div was removed, at a time when PCore was not yet initialized. This has been resolved by adding proper undefined checks to safely handle the PCore initialization timing. | User Experience |
| INC-C59187 | 973514 | Accessibility overlay dialog titles improved | Overlays launched in the application were displaying non-meaningful dialog titles containing camel case text, "py-" prefixes, or backend IDs, creating accessibility issues for screen reader users. This was traced to changes from previous accessibility work which automatically applied flow action short descriptions as aria-label attributes without validation. This has been resolved with an update to set overlays to use role="tooltip" if there are no interactive elements in the dialog. If there are interactive elements in the dialog, the overlay will have role="dialog" and aria-label value sourced from the flow action short description. | User Experience |
| INC-C59251 INC-C53488 |
972508 972989 |
Accordion accessibility state announcements restored for screen readers | Screen readers were not properly announcing the expanded state when accordion layout groups were opened. This was an unintended side effect of work done for focus indicator issues on expand/collapse headers, and has been resolved by updating the pzpega_ui_layoutgroup_js rule to restore proper ARIA state communication to screen readers while maintaining the focus indicator functionality, ensuring accordion expand/collapse states are correctly announced by NVDA and other assistive technologies. |
User Experience |
| INC-C59531 | 974551 | Search modal tooltip interference eliminated | In Theme Cosmos, search modal dialogs were closing immediately after opening when the cursor remained on the search icon. This was caused by conflicting hover and focus actions configured on the search button in WorkSearchGadgetHeader , and has been resolved by removing the “Smart tooltip” behavior from the header search button. | User Experience |
| INC-C59657 | 978244 | Processing error screen flash resolved | A "processing error has occurred" screen was briefly appearing for 1-2 seconds when opening subsequent cases using the "Create Work" functionality with pega.desktop.infinity.createNewWorkInDialogContainer script, particularly in configurations with layout groups containing multiple dynamic layouts with deferred loading. This was caused by timing issues in the deferred loading mechanism for dynamic layout sections, and has been resolved. | User Experience |
| INC-C59702 | 972287 | View property display fixed for matching page and property names | Views were not displaying property labels when the page name and property name were identical, such as when adding an embedded field named "Customer" to a page also named "Customer". This was traced to the pzAdjustContentClass activity evaluating where the condition !lastItem.equals(currentProperty) as false for matching names, causing the wrong class to be used for property evaluation. This has been resolved by updating the pzAdjustContentClass Activity logic to properly handle scenarios where page names and property names are identical. | User Experience |
| INC-C59988 | 979338 | Field group layout and conditional logic updated | 2-column layouts within field groups were rendering as stacked layouts instead of the configured column arrangement, and 'when' rules within field groups were not executing as intended. This was traced to logic that could incorrectly render the navigation template as a MultiStepForm instead of a normal StandardForm, and has been resolved by correcting the assignment component layout logic so that Standard navigation templates and single-step flows render with StandardForm, while only non-standard templates render MultiStepForm. | User Experience |
| INC-D10078 | 982265 | Date range picker accessibility improved | Date range picker modal dialogs were missing both accessible names and dialog roles. This has been resolved by adding proper dialog roles and localized aria-labels in pzpega_ui_daterangepicker and pzClientLocaleData. | User Experience |
| INC-D10116 | 980392 | Blended UI navigation and case creation issues addressed | When creating new cases from existing cases in the Blended UI (such as scheduling appointments), the parent case link was not updating to reflect the newly created case and the Recents list was not displaying new cases. Additionally, browser tabs were displaying Case Type names instead of Case IDs or Labels, and page loading was failing intermittently during navigation through landing pages despite correct URL updates. This was traced to case reference handling and tab management in the Blended UI framework, and has been resolved by updating case linking, Recents list refresh functionality, correct tab labeling with Case IDs, and improving page loading reliability in Blended UI navigation. | User Experience |
| INC-D10143 | 983138 | Case type localization fixed in browser tab titles | Case type names in browser tab titles were not displaying localized text in Constellation applications. This has been corrected. | User Experience |
| INC-D10282 | 982251 | Accessibility corrected for date control table markup | Date controls were generating inaccessible table markup in headers, including layout table semantics that were being read by screen readers during date picker interactions. This was caused by missing role="presentation" attributes on non-tabular table elements in the buildHeaderSpinners() function, and has been corrected. | User Experience |
| INC-D10515 | 985004 | Optimized table responsiveness checkbox behavior corrected | The Responsiveness checkbox was incorrectly remaining enabled and checked in optimized tables when users unchecked "Optimize code", selected responsiveness, then re-enabled "Optimize code", causing mobile-specific views to appear inappropriately. Investigation showed this was caused by the system retaining the last checkbox state before disabling rather than properly resetting it. This has been resolved by ensuring the Responsiveness checkbox is properly disabled and unchecked when Optimize code is enabled. | User Experience |
| INC-D10601 | 983143 | Corrected field flickering in summary UI views | Fields within summary sections of Interaction case full page views were flickering. This has been resolved by updating the styling to adapt more naturally when placed in different layouts, side panels, or constrained regions, especially around medium-width breakpoints. | User Experience |
| INC-D10676 | 981500 | Pulse search bar visibility corrected | The Search option for the search bar in Pulse was disappearing when the cursor moved over it. This was caused by conflicting Smart Tip configurations on the search icon and dropdown arrow elements, and has been resolved by removing the Smart Tip behavior from the Pulse search widget. | User Experience |
| INC-D10747 | 990031 | Autoclose handling updated for secure URL configurations | HTTP 400 errors were generated when attempting to use the autoclose functionality in end-user portals after enabling the Dynamic System Settings prconfig/initialization/urlencryption/default (set to true) and prconfig/initialization/submitobfuscatedurl/default (set to required). Investigation showed this was caused by the autoclose feature sending plain text URLs that were incompatible with the URL encryption requirements, and this has been resolved by implementing URL encryption handling in the autoclose request mechanism. | User Experience |
| INC-D10764 | 985185 | Left menu alignment corrected after update | After update, navigation panel menu items were displaying with misaligned child items. This has been resolved by updating the sub-menu alignment in left navigation by adding display: flex !important; to the .menu-item-anchor rule. | User Experience |
| INC-D1082 | 974024 | 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-D10861 | 990061 | SIAA email composition data persistence restored | When proceeding through the "Send AdHoc Message" outbound email creation process in Smart Investigate Agentic Automation Framework, selecting an email template, navigating to the corresponding ORCH case, and then returning to the "Compose Email" assignment caused all previously selected data to be lost. Investigation showed this was due to openWorkByHandle failing to recognize and reuse an already-open item when encountering a multi-document-portal case for child-case assignments, instead treating it like it needed to be opened again. This has been resolved by adding a fallback check for an existing assignment item with child-case context (parentCaseInfo) and a semantic URL, then explicitly activating that container item instead of always re-fetching when activation details aren’t returned by the standard activation lookup. | User Experience |
| INC-D11037 | 985497 | Optional actions functionality restored for resolved interaction cases | Case-wide optional actions on resolved interaction cases were becoming unresponsive after submission, preventing further actions like case dismissal. This was caused by missing refresh calls on pyCaseSummary for closed interaction cases, and has been resolved by ensuring key population when finishing an assignment on a resolved case. | User Experience |
| INC-D11102 | 988083 | Busy status indicator corrected for embedded sections | The data-state-busy-status attribute remained "busy" after save completion when save operations occurred inside Repeating Dynamic Layout (RDL) with embedded pages containing dots in property paths. This was caused by selector failures in pzpega_ui_doc_focus.js when handling property paths with dots, and has been resolved by adding handling for dots and other special characters. | User Experience |
| INC-D11122 | 981823 | Localization corrected for browser and requestor locale settings | Localization was not being applied as expected when using browser locale or pxRequestor.pxReqLocale settings, even after importing language packs and following standard localization procedures. Investigation showed this was caused by Constellation portals not properly determining locale priority when operator locale was left empty and browser language was set to non-English languages. This has been resolved by implementing a proper locale determination hierarchy where Constellation portals now follow the priority order of Operator locale → Browser locale → Default locale, ensuring that language bundles are correctly loaded in environment info for browser locale scenarios. | User Experience |
| INC-D1137 INC-D2580 |
977708 978233 |
Redundant screen reader announcements removed | Unnecessary screen reader announcements of "Top panel", "Bottom Panel region", and similar labels were triggered during page navigation, and announcements of "Information on the content" were duplicated when contentinfo roles were added to footer elements. This was due to redundant ARIA label announcements on header, main, and footer landmarks, and has been resolved by removing the unnecessary attributes in the GenerateLayout rule file. | User Experience |
| INC-D11672 | 987348 | DX API readonly field evaluation accuracy improved | Angular starter pack applications were incorrectly rendering embedded sections as read-only when developers configured WHEN rules in DATA- class for readonly conditions in Repeating Dynamic Layout (RDL), regardless of the WHEN rule evaluation. Investigation showed this was caused by two issues: WHEN rules were not being resolved correctly, and readonly tables present in the same section were affecting the readonly condition evaluation. This has been resolved by modifying the pzdxapifulljsonforvieworpage function to properly handle readOnly conditions in cases where table grids and RDL exist in the same layout. | User Experience |
| INC-D11723 | 988601 | Date entity highlighting restored | After update, email processing applications were extracting date entities correctly but failing to highlight them in the user interface. This has been corrected. | User Experience |
| INC-D11767 | 982260 | Visibility when rules corrected for embedded data modals | After update, visibility when rules were not functioning properly in embedded data modal views, causing configured fields to remain hidden inappropriately. Investigation showed this was caused by incomplete data merging that only included caseInfo content data without the necessary context data containing summary_of_when_conditions. This has been resolved by modifying the handling around updating context_data when merging interest-path data so context metadata stays in sync with the primary data merge. | User Experience |
| INC-D11789 | 983104 | Promoted filters functionality restored for list views | User reference properties configured as promoted filters were not displaying properly in list view landing pages, showing blank screens when attempting to add promoted filters. This was traced to an issue with the handling of user reference property types in the promoted filter rendering logic, and has been resolved by correcting the promoted filter display mechanism to properly support user reference properties and other complex data types in list view configurations. | User Experience |
| INC-D11991 | 987420 | PDF image orientation support enhanced | iPhone JPEG images were not displaying with correct orientation in generated PDFs due to EXIF orientation data not being processed. This has been resolved by updating pd4ml to a version which includes EXIF orientation support for JPEG images. | User Experience |
| INC-D12233 | 984075 | Localized date pasting handling updated | Date input fields were rejecting date values containing January when they were pasted into date input controls, while other months worked correctly. This was traced to date parsing logic that incorrectly handled January month values during paste operations, and has been corrected with an update to better parse locale-formatted date/time strings. | User Experience |
| INC-D12317 | 988953 | Menu accessibility improved for disabled items | It was not possible to close menus containing only disabled items using the Escape key. This has been resolved by updating the menu component to properly handle keyboard navigation and closure events regardless of item states. | User Experience |
| INC-D12327 | 982909 | Localization migration fixed for short ruleset names | Applications with main ruleset names of five characters or fewer were experiencing failures during localization bundle generation when running the pxMigrationToLocalizationV2 activity. The activity was throwing a StringIndexOutOfBoundsException and only creating the base bundle in the unlocked ruleset version, while the localized ruleset and localized bundle were not being generated. Investigation showed this was caused by string length assumptions that led to an invalid substring operation, and has been resolved by correcting the string handling logic in the activity. | User Experience |
| INC-D12360 | 992071 | Excessive client-side refresh calls resolved after Constellation upgrade | Applications were experiencing a significant increase in PATCH .../refresh calls immediately following the Constellation runtime upgrade. This has been resolved by modifying the system to call refresh only on composite keys when onlyAllowRefreshOnCompositeKeys is true. | User Experience |
| INC-D12361 | 985635 | DateTime picker timezone handling standardized | The "Set now" button in DateTime picker was using browser local timezone instead of the configured server timezone, resulting in incorrect timestamps when timezones differed. This has been resolved by standardizing "Set now" to use operator timezone when provided, instead of browser timezone. | User Experience |
| INC-D12426 | 982255 | Modal popup display restored | The Create Workbasket form was rendering inline below the workbasket list table instead of opening in the expected modal popup when users clicked the '+' (Add) button in Manage Workbaskets. Investigation showed that the preview modal functionality was not working correctly for Add operations, and this has been resolved. | User Experience |
| INC-D12567 | 985244 | Delete handling updated to prevent conflicts with custom actions | After update, a custom case-wide action named "Delete" was triggering a browser confirmation dialog ("Are you sure you want to delete this record?") instead of invoking the configured flow action. This was caused by the standard delete handling intercepting actions with the "Delete" name. To support customizations, the action name resolution logic has been updated so the case-wide Delete action is opened via openLocalAction instead of being executed via deleteWork. | User Experience |
| INC-D12603 | 985828 | Table column sort announcements localized | Screen readers were announcing sorted table column status in English instead of the localized language. This was due to case sensitivity mismatch between sort strings and localization bundles, and has been resolved by correcting the case matching. | User Experience |
| INC-D13081 | 984979 | Table column reordering with row selection restored | Column reordering functionality was not working properly in tables with row selection enabled, where header columns would move but the corresponding data columns remained in their original positions. Investigation showed this happened when row selection was enabled and categorization was disabled, and was caused by a mismatch in the 'expand-collapse' class handling between the header and data rows. This has been resolved. | User Experience |
| INC-D13229 | 984575 | Search and select component caching corrected | Search and select controls within page lists were displaying incorrect cached data after items were removed from the middle of page lists. This was caused by component caching using index-based keys that became misaligned when list items were deleted, and has been resolved by updating the caching mechanism to use stable identifiers that remain consistent when page list items are added or removed. | User Experience |
| INC-D13342 | 984662 | Constellation dynamic text localization restored | Dynamic text localization functionality was not working in Constellation applications after update. This has been resolved by updating the handling for the dynamic text localization functionality to replace localeUtils imports/usages with getLocaleUtils(). | User Experience |
| INC-D13778 | 984640 | Queue processor status transitions corrected | The pyProcessSLA Queue Processor was intermittently transitioning to a FAILED state and then returning to RUNNING approximately every 10-15 minutes, and null pointer exceptions were occurring from the pxIsAFollower function during FollowUnfollowHelperText operations. This was traced to a null pointer exception in the pzIsAFollower Rule-Utility-Function where the parameter defaulting logic was not properly handling null pages and values for Context/Follower parameters, and has been resolved. | User Experience |
| INC-D1391 INC-D9927 |
973177 981572 |
Looped assignment view rendering restored | Assignment views in case flows with loop conditions were not rendering and appeared blank, while the same assignments worked correctly when the loop was removed at runtime. Console errors were visible when attempting to display assignment views within looped flow steps, preventing users from completing their work. Investigation showed this was caused by the view rendering engine not properly handling assignment contexts within looped flow conditions, and has been resolved by correcting the MultiStepForm rendering for Standard navigation template. | User Experience |
| INC-D14132 | 985316 | Percentage field decimal validation corrected | Percentage fields were not properly detecting changes when users modified only the decimal point formatting, causing validation logic to evaluate previously submitted values instead of current input. This was caused by incomplete change detection for decimal-only edits in percentage field controls, and has been corrected. | User Experience |
| INC-D14161 | 983570 | Avatar status correctly localized | The avatar was showing "User status active" in English even when the application was configured for other languages. This has been corrected. | User Experience |
| INC-D14163 | 989312 | Screen reader accessibility updated for key-value pairs | Read-only key-value pair lists were using role="none" attributes that prevented screen readers from properly announcing content as definition lists. This was caused by overly restrictive semantic markup that removed necessary structural information, and has been resolved by adjusting the role attributes to maintain proper semantic meaning while preserving the intended visual presentation. | User Experience |
| INC-D14164 | 984321 | Empty list elements in navigation removed for improved accessibility | Empty <ul> elements in the Announcements area and left navigation bar were being generated by conditional rendering logic that created list containers regardless of whether content was available. This has been resolved with an update to prevent rendering of AppAnnouncement details and AppShell navigation components when their item arrays are empty. | User Experience |
| INC-D14169 | 988056 | File attachment field error messages corrected | Screen readers were announcing "invalid entry" when focusing on "Select attachment" input fields, with the error persisting even after successful file addition. This has been resolved by correcting the file status messaging handling for file attachment input fields. | User Experience |
| INC-D14191 | 987769 | Screen reader error messages improved for radio buttons | Screen readers were announcing compound error messages with technical terms like "undefined" when navigating radio button groups without selection. This was traced to non-localized state information being included in error announcements, and has been resolved by providing user-friendly error messages and removing technical state information from screen reader announcements. | User Experience |
| INC-D14195 | 984003 | High contrast mode focus indicators enhanced | Keyboard navigation was not providing visible focus indicators when using Windows 11 high-contrast mode. This has been resolved by implementing comprehensive visible focus indicators for all interactive elements when operating in Windows high-contrast mode. | User Experience |
| INC-D14211 | 986784 | Character limit feedback enhanced for message fields | Message fields were not providing adequate feedback when character limits were reached, only announcing character count without indicating limit exceeded. This has been resolved by adding appropriate user feedback when message character limits are exceeded. | User Experience |
| INC-D14344 | 985170 | Document generation library updated to resolve Constellation localization | Localization was failing in Constellation applications. This was traced to the document generation library, which had an issue with generating documents when processing more than 64K records resulting in failed generation, incorrect output, or inability to process very large datasets. This has been resolved by updating the document-generation library to a recent version where the issue has been corrected. | User Experience |
| INC-D15016 | 988410 | Console error resolved for apostrophe handling | Applications were experiencing console errors when field values contained apostrophes. This has been resolved by updating the character encoding and escaping mechanisms in the UI controls to handle apostrophes and other special characters. | User Experience |
| INC-D15487 | 986678 | DateTime seconds display supported in partial views | Seconds were not displaying in partial views for datetime properties formatted as DD/MM/YYYY HH:MM:SS, even when the "Display Seconds" option was enabled in Constellation applications. To support this use, a new "long numeric" format has been introduced in the datetime field authoring panel which allows seconds formatting in the field configuration options for partial views. | User Experience |
| INC-D15498 | 990510 | Portal metadata parsing stabilized | Custom landing pages placed at the top of portal channel lists were generating "Unable to parse view metadata" console errors during portal launch, though functionality remained intact. Investigation showed this was caused by metadata processing order issues when custom pages were prioritized in the channel configuration. This has been resolved by updating pzsetupviewpagetorender to check for the existence of a landing page using for Rule-UI-View-LandingPage. | User Experience |
| INC-D15512 | 986749 | Section refresh functionality restored for conditional local actions | After updating from Pega 7, clicking buttons configured with both "Refresh this section" and conditional local actions defined in separate classes resulted in the message "Error (Please contact system administrator)" . This was traced to a loss of base reference in the underlying JavaScript framework, and has been resolved by implementing a new configuration flag "pega.u.d.skipIECheck" in the webwb_pzpega_ui_doc_domutils.js rule's getBaseReference method, which can be explicitly set to true from UserWorkForm to bypass the problematic reference check and restore proper section refresh behavior. | User Experience |
| INC-D15899 | 990963 | Stage dropdown population restored | The pyChangeStage flow action was failing to populate stage name dropdown values when the Comments field was configured as Required (Always). Investigation showed this was caused by context metadata changes that disrupted the stage options retrieval process. This has been resolved by updating context metadata to add properties from the association. | User Experience |
| INC-D15930 | 986908 | Constellation dropdown search functionality improved | Users were experiencing difficulty locating intended options from large dropdown lists when typing search text in multi-select combo box fields and single-select dropdown fields. This was due to the system applying 'Contains' search logic instead of the expected 'Begins with' logic, with the result that all values that contained the search string anywhere within them were presented rather than filtering to values that started with the search text. Additionally, in single-select dropdown fields with large option lists, the system was not displaying the full list of matched values when users entered search input, requiring users to scroll down to find all matched values. This has been resolved by implementing 'Begins with' search logic and ensuring complete display of filtered results. | User Experience |
| INC-D16093 | 990872 | Case summary panel refresh corrected | Interaction case summary panels were intermittently failing to refresh after status changes made through stage optional actions for creating child cases, requiring manual browser refresh to see updates. This was traced to the event propagation between parent and child case contexts in the Constellation engine, and has been addressed. | User Experience |
| INC-D16316 | 987013 | Account manager message visibility corrected | Account Manager screens were displaying blank message areas with visible borders while the same messages were visible to customers. Investigation showed this was caused by role-specific message markdown rendering issues affecting Account Manager visibility. This has been resolved by adjusting chat message bubble styling to keep markdown code blocks readable and visually consistent with the surrounding chat bubble theme. | User Experience |
| INC-D16657 | 991231 | Radio button deselection behavior corrected | Radio buttons configured as picklists were unexpectedly deselecting when clicked a second time, even when the clear selection option was not enabled. This was caused by incorrect click handling behavior that allowed radio buttons to toggle their selected state rather than maintaining the standard mutually exclusive behavior. This has been resolved by implementing the pyEnabledRadioOnclickDeselection feature toggle that restores proper radio button functionality where selections remain persistent until another option is chosen, with deselection only possible through an explicit "Clear selection" button when that configuration is enabled. | User Experience |
| INC-D16722 | 987804 | Attachment field display corrected for page lists | Attachment fields in page lists were incorrectly displaying in the UI when entering assignments, even though they were deleted from the clipboard. This was traced to UI synchronization with clipboard state for attachment fields, and has been resolved by correcting the attachment field display logic for page list properties to avoid overwriting propertiesToReplace when already set. | User Experience |
| INC-D1686 | 974045 | Screen reader accessibility improved | Screen reader accessibility for optimized table navigation was providing incorrect instructions, reading "Click to Filter" and "Click to Hide Field" instead of the required "Enter to Filter" and "Enter to Hide Field". This was caused by incorrect aria-label text in the pzTemplateGridMenuNavRule navigation rule, and has been corrected. | User Experience |
| INC-D17039 | 988994 | Instruction text display corrected in partial views | Form views included within partial views were not displaying instruction text for field groups. This was caused by incomplete context propagation when rendering nested view components, and has been corrected. | User Experience |
| INC-D1723 | 974055 | Horizontal scroll bar at 400% zoom eliminated | When increasing browser zoom to 400% on work object details pages, a horizontal scroll bar appeared that interfered with accessibility. This has been resolved by adjusting the CSS layout calculations to properly accommodate 400% zoom levels without generating horizontal scroll bars. | User Experience |
| INC-D17715 | 989401 | Asterisk positioning corrected for form controls | Radio button and checkbox controls with large captions were displaying required field asterisks in incorrect positions. This was caused by CSS positioning calculations that didn't account for multi-line caption text, and has been resolved by updating the component styling to properly position asterisks relative to caption content regardless of length. | User Experience |
| INC-D18844 | 989840 | List view error message clearing behavior corrected | Error messages from failed delete actions in Constellation List Views were persisting after successful subsequent actions like add or edit operations. This was caused by error messages not being automatically cleared when new successful actions were performed, and has been resolved by displaying delete action error messages as part of modal dialogs to ensure proper message lifecycle management. | User Experience |
| INC-D19123 | 989816 | Rich Text Editor custom tag logic updated | Applications experienced blank screens after updating the rteCustomAllowedTags DSS value to include "a" and "svg" tags. Investigation showed the tag validation logic was failing when processing the updated allowed tags list. This has been resolved by correcting the tag parsing and validation mechanisms to properly handle custom tag configurations. | User Experience |
| INC-D1957 | 974504 | Busy indicator text localization added | Applications were displaying hardcoded, non-localized text in busy indicators that included a misspelled "inderminate, progress indicator" message. This has been resolved by correcting the spelling in English and by creating field value entries to enable proper localization of all busy indicator text elements. | User Experience |
| INC-D1973 | 984302 | Corrected handling for currency formatting with qualifiers | Currency fields were not displaying proper formatting in read-only mode when using specific currency qualifiers like XOF, XAF, JPY, or KRW. This has been resolved by updating the currency formatting algorithm to properly process and display currencies when qualifiers are specified. | User Experience |
| INC-D2050 | 988164 | Photo upload popup handling corrected for offline apps | Multiple attachment popups were appearing when uploading 2 or more photos/files using pxAttachContent control with action sets in offline-enabled applications. This has been resolved by adding a guard to prevent multiple attachment pickers from being launched during multi-file/photo uploads in the Hybrid Client attachment control. | User Experience |
| INC-D20646 | 992571 | Axios library updated | The Axios library has been updated. | User Experience |
| INC-D21163 | 993427 | Autocomplete clear button accessibility improved | Applications using autocomplete controls configured as combo boxes were experiencing accessibility issues where the clear button (X icon) was not properly accessible. This has been resolved by adding aria-label="Clear selection" and implementing proper keydown event listeners to enable keyboard navigation. | User Experience |
| INC-D2121 | 975856 | Restored autocomplete filtering in list views | After update, autocomplete filters in list views were not filtering results when the underlying data page was sourced by an activity rather than a report definition. Investigation showed this was caused by a gap in the handling of promoted filters for data sources that are searchable but not queryable. To resolve this, client-side filtering and pagination have been added for that case in PromotedFilters.jsx, while preserving server-side paging for queryable sources. | User Experience |
| INC-D21238 | 994321 | Textarea focus behavior improved during scrolling | Applications were experiencing focus loss in textarea components when scrolling through large amounts of text, even though the cursor remained visibly positioned within the textarea boundaries. This has been resolved by implementing proper focus retention logic that maintains textarea focus state during scroll operations, ensuring uninterrupted user interaction with text content regardless of scroll position. | User Experience |
| INC-D21746 | 997957 | Multiple Google address API calls resolved | Applications were experiencing excessive Google Address API calls when using the LocationInput control in Constellation. Investigation showed this was caused by the LocationInput control triggering a separate Google API call for each character entered rather than implementing proper debouncing or throttling mechanisms. This has been resolved by implementing optimized API call patterns to reduce and better manage Google Maps Places API usage by introducing debounced autocomplete calls and reusing AutocompleteSessionTokens across a “typing session”, while also threading the active token into place-details lookups (including map clicks). | User Experience |
| INC-D2373 | 974094 | 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-D2579 | 975871 | Advanced search error message clearing implemented | Error messages in Advanced Search components were persisting even after clicking the Search button, particularly for required field validations that should have been cleared when conditions changed. This was caused by required message clearing not functioning properly when requiredWhen expressions became false in modal contexts, and has been resolved by extending the error clearing mechanism to work properly in both work area and modal contexts by passing subType through the corejs messages API so reducers can differentiate message sub-types. | User Experience |
| INC-D2712 | 975564 | Search and select refresh functionality restored | The refresh functionality in search and select components was not properly retaining search parameters when using non-queryable data pages, causing filtered results to be lost and showing empty or unfiltered data instead. Investigation showed this was caused by search filter parameters not being preserved during the refresh operation, and has been resolved by ensuring search parameters are maintained when refreshing non-queryable data page results. | User Experience |
| INC-D2719 | 972845 | Accessibility improved for case icon | A role attribute/tag has been added to the case icon on the case details page to improve accessibility. | User Experience |
| INC-D2725 | 977381 | Date field validation made consistent | Date field validation messages were not being consistently retained when dates were entered manually through keyboard input, though validation worked correctly when using the calendar control. Investigation showed this was caused by the DateTime PartInput component incorrectly triggering onChange events during blur operations without actual value changes. This has been resolved by ensuring the onChange callback passed to PartInput is triggered when the value has changed. | User Experience |
| INC-D2925 | 973392 | Focus restored for embedded data table add operations | When adding records to embedded data field tables using the "Add" button configured as an action rather than a view, focus was incorrectly moving to the top of the screen instead of remaining on the modal. This was traced to incorrect focus handling in the "Action-based configuration for for adding rows to embedded data fields, and has been resolved by ensuring that the correct view is selected through the classID added to state, maintaining proper focus on the modal when adding table rows. | User Experience |
| INC-D2939 | 973237 | SDK link behavior standardized | External links in case instructions were behaving inconsistently between Pega portals and Angular SDK implementations, with links opening in new tabs in portals but replacing the current tab content in SDK applications. This was caused by the DOMPurifier logic in the SDK components not automatically adding target="_blank" attributes to external links, and has been resolved by implementing consistent link handling logic across all UI frameworks to ensure external links always open in new tabs. | User Experience |
| INC-D3156 | 983528 | Dev Studio context preserved on switch | After returning from the portal to Dev Studio, the Actions button in rules would only display "Get Help" instead of the full menu options, requiring logout and login to restore functionality. This was an inadvertent side effect of work done on context switching between different application interfaces, and has been resolved by ensuring proper context thread preservation when transitioning between Dev Studio and portal environments. | User Experience |
| INC-D3194 | 975714 | Corrected slider input synchronization with form refresh | Slider controls with numeric input enabled were displaying 0 instead of the actual slider value in the input box when auto-populated. This has been resolved by ensuring proper value synchronization between slider and input components during form refresh to ensure NumberInput does not display stale values. | User Experience |
| INC-D3261 | 977052 | 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 | 974737 | Layout group tab focus borders corrected | Tab layout groups were displaying incomplete focus borders when "Semantic tab Layout" and "Allow scroll for tab headers" options were enabled together. This was caused by CSS conflicts that removed the top border during focus state rendering, and has been resolved by updating the focus styling rules to maintain complete border visibility across all tab layout configuration combinations. | User Experience |
| INC-D3328 | 981815 | Invalid flow action banner resolved during case creation | Invalid flow action banners were intermittently appearing during Demand Request case creation, particularly in staging environments, with messages stating "CollectMarketInformation is not a valid action to use". This was traced to a race condition between refresh and FinishAssignment actions, and has been resolved. | User Experience |
| INC-D3352 | 979080 | Screen reader accessibility improved for required fields | Screen readers were not announcing required field status for several UI controls including TextArea, Rich Text Editor, Radio buttons, AnyPicker, AutoComplete, and Dropdown when client-side validation was disabled. This was due to the aria-label attributes not being properly set for required field indication in these controls for this scenario, and has been resolved by updating the backend rendering logic to ensure all required field controls include proper aria-label attributes for screen reader accessibility. | User Experience |
| INC-D3470 | 973605 | Keyboard navigation flow restored for optimized tables | Keyboard navigation was becoming trapped in the first column of optimized tables with group by results. This an issue with the focus management in grouped table rows where the first column appeared empty beneath the group caret, and has been resolved by updating the keyboard navigation logic for a grouped table. | User Experience |
| INC-D3535 | 978680 | Corrected Multiselect dropdown save error | Multiselect combobox controls were throwing "Invalid Request Data" errors when attempting to save selections in Constellation. This was caused by data page parameter metadata not being processed correctly for page list properties, especially when the page list was empty or nested under a composite path. To address this, parameter resolution has been made path-aware and class-aware, so Constellation can still derive parameter property paths and metadata even when there are no page list rows yet. | User Experience |
| INC-D4493 | 978726 | Constellation case work area display improved | Cases with 50 or more assignments were displaying excessive blank space under the case work area when all assignments were expanded in Constellation. This has been resolved by optimizing the layout calculations to properly size the work area container regardless of assignment count. | User Experience |
| INC-D4505 | 974521 | Text area character counter persistence fixed | After enabling max length on a paragraph and using the same field in multi-step-form (screenflow) process, the counter remained as 0 on the next screen even though it included values typed in the prior screen. This was caused by the text area control always initializing the counter value to 0 when rendered, regardless of existing content, and has been resolved by initializing the character counter with the actual length of existing value or default value when present. | User Experience |
| INC-D4570 | 976615 | Hover menu collapses as expected | Link controls configured with Hover Menu action sets were remaining expanded when focus moved elsewhere, causing multiple menus to stay open simultaneously and creating user interface confusion. This has been corrected by adding display:none inline style to implement proper menu collapse behavior when cursor focus moves away from hover menu controls. | User Experience |
| INC-D4579 | 979291 | Required field indication added for multiselect and RTE controls | Multiselect combobox controls and Rich Text Editor (RTE) fields were not indicating required field status to screen readers. This has been resolved by updating multiselect combobox controls to include required attributes and RTE controls to include required status in their aria-label values. | User Experience |
| INC-D492 | 976249 | Table cell text formatting preserved | Text and paragraph fields within table cells were not respecting user-defined formatting configurations, causing text to wrap incorrectly and ignore line breaks regardless of the intended display behavior. Investigation showed this was caused by table cell rendering overriding user-specified text formatting settings. This has been resolved by ensuring user-defined formatting configurations are properly applied to text fields within table cells. | User Experience |
| INC-D5058 | 981285 | View loading reliability improved after case submission | Applications were failing to load views after case submission due to messaging service subscriptions being unsubscribed prematurely without proper validation checks. This was caused by incorrect execution order where subscriptions were being unsubscribed before dependent operations completed, and has been resolved by improving AtomicSubscription message handling to safely handle cases where a subscriber is removed while iterating subscribers. | User Experience |
| INC-D5197 | 977915 | JSP tags fixed in table headers | Sections containing non-optimized tables were failing to save when JSP tags like "<pega:include name=\"pyLabel\" type=\"Rule-HTML-Property\"/>" were used in column header labels. This was traced to the GenerateCellContent Rule-Utility-Function not properly handling JSP tag processing in table header contexts, and has been corrected. | User Experience |
| INC-D5414 | 988123 | Remote case actions menu restored | The Actions button was not visible for remote cases launched from Process Fabric applications, preventing access to case-wide actions. This was traced to a missing Remote System ID parameter when calling actionsApi.openLocalAction and actionsApi.openProcessAction, and has been corrected. | User Experience |
| INC-D5674 | 981754 | Picklist behavior corrected during horizontal table scrolling | Search box picklists within horizontally scrollable tables were remaining open and moving with scroll position instead of closing, causing the open picklist to overlap and block UI elements during navigation. Investigation showed the ComboBox popover was not explicitly configured to hide when its anchor/target became hidden, even though the ComboBox’s open state could still indicate it should be shown. This allowed the popover to outlive the visible ComboBox target and remain rendered or visually inconsistent. To resolve this, the handling has been updated to ensure the popover now hides automatically when the ComboBox target is no longer visible. | User Experience |
| INC-D5931 | 978290 | Autocomplete pagination resolved for REST connector data sources | Applications using autocomplete controls with REST connector data sources were experiencing infinite loading when scrolling through results. This was traced to the autocomplete component not properly handling REST API responses that did not include pagination metadata (pageSize) in their response structure. This has been resolved by modifying the component logic so that for external data pages, if pageSize is not returned in the response, additional results are not loaded on scroll, preventing the infinite loading behavior and allowing proper display of all available autocomplete results. | User Experience |
| INC-D5954 | 977377 | Address control editing in modals corrected | Address controls in modal dialogs were allowing initial data entry but preventing subsequent editing of postal code values, and any changes were reverted after refresh. Investigation showed this was caused by conflicting Update and Replace instructions during address field modifications, where Replace instructions containing old values were overriding Update instructions with new values. This has been resolved by correcting the instruction merging logic for Address fields in embedded data scenarios to bypass the “merge with previous UPDATE instruction” behavior when replaying/merging page instructions. | User Experience |
| INC-D6154 | 978288 | Application name special character encoding corrected | Application names containing special characters like brackets (e.g., "App (Name)") were displaying with encoded special characters in the Switch Application menu within the End User portal. This was caused by improper HTML encoding of the pyApplications.pyLabel property, and has been corrected. | User Experience |
| INC-D6236 | 977444 | Corrected unexpected menu collapse | The Constellation portal expanded navigation menu was collapsing unexpectedly when closing cases. This has been resolved by updating the event propagation control for on-click case close actions in the navigation menu. | User Experience |
| INC-D6306 | 979878 | Global search functionality restored in constellation applications | Applications were experiencing an issue where the global search box was disappearing after creating new cases while on the advanced search results page. This was caused by a rendering issue which affected the search component visibility during case creation workflows, and has been resolved. | User Experience |
| INC-D6514 | 979179 | Browser timezone handling fixed for empty operator settings | Date and time values were displaying in GMT instead of browser timezone when operator timezone settings were removed, and pulse feed functionality was generating errors. Investigation showed the environment timezone detection was not properly falling back to browser timezone when operator locale was empty, and this has been corrected by updating PCore.getEnvironmentInfo().getTimezone() to return undefined when user locale is empty, enabling proper browser timezone fallback. | User Experience |
| INC-D6634 | 978677 | Corrected validation trigger logic | Validations were not triggering properly after update. This was traced to an issue with the boolean-comparison in the corejs expression evaluator, which could mis-handle boolean fields when runtime field metadata was missing, causing expressions like .pyFlag == 'true' or comparisons against false to evaluate incorrectly. To address this, a RulesStore-based metadata fallback has been added to infer field type when _context.getFieldMetadata(...) is unavailable. | User Experience |
| INC-D6674 | 978717 | Coexistence case rendering behavior standardized | Traditional parent cases were incorrectly rendering as Constellation cases when accessed from child Constellation cases in coexistence environments while parent cases loaded correctly as traditional cases when accessed directly from the portal. Investigation showed the logic was not properly maintaining the parent case rendering context during navigation in the coexistence environment. This has been resolved by updating parent-case breadcrumb navigation in CaseView to correctly handle this scenario. | User Experience |
| INC-D6724 | 980463 | Radio button placeholder selection issue resolved | Radio button controls with "Not Applicable" placeholder options were automatically selecting when there was a click anywhere on the control area, including white space or labels, even when existing values were already present. This was an issue with improper ID assignment logic in the template_radiogroup.js rule template that failed to distinguish between placeholder and regular value selections, and has has been resolved by implementing conditional ID assignment logic that properly differentiates placeholders. | User Experience |
| INC-D709 | 973362 | Case summary panel refresh implemented for local actions | The case summary panel was not updating when local actions created renewal cases, continuing to display resolved case details instead of the new case information even though assignments appeared correctly in the work area. This was caused by missing refresh logic for the summary panel during local action execution, and has been resolved by adding a check to dispatch mergeData when parent and child containers hold different contexts. | User Experience |
| INC-D7170 | 983536 | Skin rule handling updated to prevent out-of-memory errors | Skin rule operations were causing system unresponsiveness and Java heap out-of-memory errors during check-in, check-out, and save operations. This was caused by excessive memory consumption in the skin processing pipeline when certain formats within a Skin rule contained corrupted color styles without valid HEX values, typically originating from overridden or “Save As” formats. To resolve this, a server-side sanitizer has been added to repair corrupted RGBA values in skin data and the ColorPicker has been hardened so it only emits safe, valid CSS color formats. | User Experience |
| INC-D7325 | 977575 | Question page answer field borders restored | Answer input boxes in question pages were losing their visual borders when receiving focus, affecting the user interface appearance for editable text fields configured from page lists. Investigation showed that when an input or textarea received keyboard/mouse focus, its border color was being set to transparent, which could make the focused field lose its visible border. This has been corrected by updating the rule to border-color: inherit, so the field keeps its intended border color while focused. | User Experience |
| INC-D7397 | 984940 | Work portal favicon configuration fixed | Custom favicon configured in pyPortalIcon was being applied to the work portal while correctly appearing in the dev portal. Investigation showed this was caused by URL hash replacement with semantic URLs in src/initialiser/index.js, which broke relative URL resolution for icon fetching. This has been resolved with an update to prevent favicon and Apple touch icon URLs defined as relative paths from breaking after history.pushState updates the page URL. | User Experience |
| INC-D7408 | 979196 | Administrator landing page localization enabled | The pxAdministrator landing page and configuration sets were not translating properly when language packs were installed and operator locale was changed, with many values remaining in English despite other locale selection. This has been resolved by implementing the necessary translation framework to support universal localization across all Constellation administrator components. | User Experience |
| INC-D7507 | 980761 | Remote case types mapping error handling updated | Applications were showing step failures in tracer logs when attempting to open RemoteCaseTypesMapping. This has been resolved by adding a check to prevent an Obj-Open against RemoteCaseTypesMapping when the target rule instance does not exist. | User Experience |
| INC-D7657 | 983776 | Text area auto-resize behavior corrected | Text area controls were displaying unwanted scroll bars when populated with data from other controls while in hidden tab states. This was caused by the auto-resize logic attempting to determine dynamic height while the element was not visible, and has been resolved by updating the height calculation logic. | User Experience |
| INC-D7718 | 978712 | TODO operator name display adjusted | Operator names were not completely visible and urgency values were being cut off at certain zoom levels in the redesigned TODO component, requiring a hover over truncated names to see full assignment details despite available white space on the screen. Investigation showed the component layout was not properly utilizing available screen space for text display due to a hard width cap (max-width: 16ch) plus layout/padding choices. This has been addressed by widening the space available for assignee names in the HierarchicalAssignments UI so names truncate later, and adjusting padding, max-width, and flex behavior in the layout. | User Experience |
| INC-D7724 | 983001 | Identifier type handling made consistent in Nebula renderer | Simple tables in read-only mode were throwing errors when adding identifier type fields from runtime. Investigation showed this was caused by type identifier misalignment between the Nebula renderer getNebulaTypes method and the authoring UI type_mapping definitions. This has been resolved by correcting the type mapping logic to ensure Identifier fields render as TextInput and Double fields render as Decimal, which aligns runtime behavior with the expected UI component types. | User Experience |
| INC-D7756 | 985231 | Case-wide actions restored for split for each assignments | Case-wide actions were not appearing when Split For Each assignments were launched directly from the flow, though they displayed correctly when opened from the worklist. This has been resolved by ensuring case-wide actions aren’t inadvertently cleared when opening a “Split For Each” assignment (i.e., when parent/child contexts reference the same item). | User Experience |
| INC-D7907 | 977752 | Improved Date field year spinbox accessibility | The Date field spinboxes year field was starting at value "1" when using arrow keys, regardless of any configured date range restrictions. Investigation showed the year range restrictions were only being applied within the calendar dialog and not to the spinbox min attribute. This has been resolved by updating the year spinbox to reflect configured range restrictions in its minimum and maximum value attributes. | User Experience |
| INC-D7924 | 980545 | Table row count display corrected for large datasets with filters | Applications were displaying "NaN" instead of the actual selected row count in table toolbars when working with optimized tables containing more than 5000 rows and applying filters with select all functionality. Investigation showed this was caused by a grid selection count calculation error in the templates and layouts component when handling large dataset that contained undefined values. This has been resolved by initializing missing count values and updating the grid toolbar styling to ensure the count text is consistently targetable. | User Experience |
| INC-D7965 | 978108 | Constellation validation banner displayed as expected | Edit Validate rules configured on properties were only showing field-level errors without displaying the validation banner at the top of the screen in Constellation applications. This behavior differed from expected validation display patterns where both field-level and banner notifications should appear. Investigation showed the Assignment component only treated hasErrors or hasFormSubmissionErrors as failure conditions, so when a form refresh failed and surfaced errors only through bannerMessages, the error banner was not rendered or focused. This has been corrected. | User Experience |
| INC-D807 | 974594 | Focus functionality restored for Checkbox help text | Checkbox controls with "Help icon with overlay on focus" were not displaying help text when field values contained line breaks or spaces. This has been resolved by adding proper newline-to-HTML conversion in the pzpega_ui_template_checkbox.js rendering logic for tooltip display when using the focus-based help text feature. | User Experience |
| INC-D8318 | 978798 | Multi-step progress bar visibility enhanced for accessibility | Multi-step form progress bars were appearing as disconnected floating circles when Windows high contrast mode was enabled. This has been resolved by implementing proper high contrast CSS styling to ensure progress bar connectivity remains visible in all accessibility modes. | User Experience |
| INC-D8581 | 979294 | Data reference combobox 'required' attribute implemented | Data reference combobox controls were not indicating required field status. This has been resolved by adding proper required attribute support to data reference combobox controls. | User Experience |
| INC-D8597 | 981919 | Table column overlay positioning corrected | The show/hide column overlay in tables with many columns was appearing detached from its trigger button when positioned near page edges. This was caused by the overlay's top position calculation not accounting for scrollbar presence and overlay height, and has been resolved by updating the popover.js calculation. | User Experience |
| INC-D8815 | 984259 | Web embed widget loading performance improved | Chat widgets embedded using the web embed feature were experiencing significantly slower load times after update. Investigation showed the pxGetEnvironmentInfo data transform was redundantly including pyHasCreateAccess alongside pyClassAccessList. This has been resolved by removing the duplicate pyHasCreateAccess property to restore previous loading performance. | User Experience |
| INC-D888 | 977019 | Preview action functionality works for hybrid UI environments | Preview actions were failing in Constellation landing pages embedded within UI-Kit portals, showing "Cannot read properties of undefined (reading 'showSlideInPanel')" errors. This was caused by missing panel functionality in hybrid UI setups, and has been corrected. | User Experience |
| INC-D8926 | 979769 | Date filtering updated for optimized tables | When applying a Date/Time filter on an optimized table and selecting “Tomorrow” with the checkbox “Also include today” enabled, the filter returns only records for today. This was an issue with an off-by-one-day boundary in symbolic date resolution, and has been resolved so that filtering with Tomorrow + Include Today correctly includes both today and tomorrow (especially for date-time end-of-period calculations). | User Experience |
| INC-D8930 | 981751 | Checkmark icon removed from hover | Autocomplete fields were displaying a checkmark icon on hover that was failing accessibility contrast requirements and was marked with role="presentation" making it invisible to screen readers. This decorative checkmark provided no meaningful information to users and has been removed. | User Experience |
| INC-D8967 INC-D8966 |
978812 978814 |
High contrast accessibility improvements | Dropdown and calendar control carets were invisible in Windows high contrast mode. This has been resolved by adding contrast-aware styling. | User Experience |
| INC-D8989 | 986225 | Corrected clearance of authorization error message | Authorization error messages were persisting in the PEGA Legal Group Advisory User Portal interface even after successfully accessing valid cases. This has been resolved by updating the context handling to ensure authorization messages are properly cleared from the interface once valid access is confirmed. | User Experience |
| INC-D9136 | 982507 | Bulk attachment download functionality enabled | The bulk download option for multiple attachment records in read-only mode was not functioning when users clicked the "download all" option in Constellation applications. This was a missed use case and has been resolved by implementing bulk download handling for read-only attachment categories. | User Experience |
| INC-D9181 | 980750 | Localization corrected for embedded fields | Single page properties with page definitions were displaying non-localized labels in runtime environments. This was traced to the system using the deprecated "@L Country" notation instead of the proper "@FL .Address.pyCountry" format for embedded single page fields, and has been resolved by updating the metadata generation to use the correct field localization notation format. | User Experience |
| INC-D9233 | 987523 | Corrected assignment due date display accuracy | Constellation assignments were incorrectly displaying due dates for assignments that had no due date configured, with the same due date appearing for multiple assignments until page refresh. The issue occurred when opening the second assignment in assignment lists, causing due date information to persist incorrectly across assignments. This was caused by a change in the dx API's response assignments array, and has been resolved by updating the date state management in the Constellation assignment display logic. | User Experience |
| INC-D9660 | 981795 | Session timer modal positioning corrected | Session timer warning windows were appearing in the top left corner when other popups were present on screen, with the close icon either missing or causing the browser window to close instead of the modal when clicked. This was caused by improper modal template selection when existing popups were detected, and has been resolved by ensuring the session timer uses the correct modal template regardless of existing popup states. | User Experience |
| INC-D9789 | 983025 | Multi-step form refresh timing corrected | Multi-step forms were experiencing errors when users changed fields with visible-when conditions and clicked next. The issue occurred due to a race condition between the setTimeout refresh handler and onClickHandler, resulting in finish assignment executing before refresh calls could register for blocking actions, and has been resolved by properly synchronizing refresh and click handler execution order. | User Experience |