Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
Low-code Application Development
Case Management
24.1.4 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B19295 | 869091 | Access role description corrected for clarity | Viewing the PegaRULES:TestID access role description in the history tab indicated "Role used by Pega developers which grants privilege to see all Threads in the clipboard viewer. May be used for other things later." This was a misleading description caused by outdated documentation and has been updated to display "Please refer pxTestID privilege for description". | Case Management |
| INC-B20720 | 889323 | createReferencesForParameters updated to return 500 results | Attempting to generate correspondence resulted in the error "Unable to open an instance using the given inputs: ..." in one particular ruleset. This was traced to the correct rule not being picked up due to only 50 circumstanced rules being returned by default when there were actually 58 results. To resolve this, the parameter pyMaxRecords has been added to the createReferencesForParameters2 Rule-Utility-Function with a value of 500 on browsePage. | Case Management |
| INC-B29899 | 882471 | "Enable Action Section" removed from available UI actions | The deprecated "Enable Action Section" function was incorrectly appearing in the action palette when adding actions to a control in the Traditional UI. This has been removed. | Case Management |
| INC-B32813 | 890262 | Corrected attach content handling when combined with pop-up | When using a screen which had both Overlay and Attach Content buttons, opening a pop-up with the overlay button and then clicking on the attach content button without closing the pop-up caused the attach content control to open as an overlay instead of a modal dialog and the UI was distorted. This has been corrected by updating "pzpega_control_attachcontent" to properly pass callbacks to processAction. | Case Management |
| INC-B32878 | 884296 | Assignment repair button functionality restored | After update, the "Repair this assignment" button was failing with the error "The flow this assignment corresponds to is no longer at this task". This was traced to additional conditional logic that was added to the FixBrokenAssignments activity which was not compatible with assignments which had validation messages on the last flow step. This has been resolved by modifying the conditional logic handling for the activity. | Case Management |
| INC-B33540 | 886936 | Updated breadcrumb handling for subflows with decision shapes | Navigation breadcrumbs were not working when decision shapes followed subflows which contained assignments that had navigation disabled. This has been resolved by updating the logic for the "addSubFlowToNavPath" function to return the pyStatus as current to the parent pyFlowData element for this scenario. | Case Management |
| INC-B40045 INC-C41531 |
899242 954770 |
Corrected FLAudit class archiving | Field level audit class records were not being archived properly when associations with FLAudit prefix classes were created. This has been corrected. | Case Management |
| INC-B43058 | 911704 | Updated thread handling to avoid archiving deadlock | Case archival processes were failing due to database deadlocks when multiple cases shared the same attachment and were processed simultaneously in different batches. This was due to the multiple threads conflicting when trying to update the same Data-WorkAttach instance with different update statements in separate transactions, and has been resolved by including batchName in the where clause to filter the records. | Case Management |
| INC-B44819 | 901216 | Application category picks up latest version rules | After creating an application category and using "save as" to save the rule in two more versions, creating a work object in Constellation, attaching a file, and then editing to see the attachment category showed the previous version name for the category. This has been corrected by updating the value of myStepPage to cpAttachmentCategory in the pzGetAttachmentCategoriesImpl activity. | Case Management |
| INC-B52085 | 916076 | Added busy indicator to block refresh during mobile upload | A transaction error was generated when attaching large files over mobile if a pull-down refresh was performed during the upload. This has been resolved by updating the attachment control to show the busy indicator until all the attachments are uploaded. | Case Management |
| INC-C10036 | 915658 | File download name encoding corrected | Downloaded attachment files with Japanese characters and special symbols like "(1)" displayed incorrect filenames. This has been corrected by updating the URL encoding handling for international characters in filenames in the in "pzDownloadFromWebStorage" activity. | Case Management |
| INC-C10844 | 920258 | Null check added for OnSend | After implementing multi-factor authentication, the error "database.BadInputException. Handle is empty or null" was generated from the doActivity Rule-Obj-Activity:OnSend. This has been resolved by adding a null check for pzInsKey in the OnSend activity. | Case Management |
| INC-C1161 | 911867 | Embedded table editing exception resolved | Editing rows beyond the first row in embedded data tables configured with modal dialog caused IndexOutOfBoundsException errors in system logs. Investigation showed the 'getProperty' method was creating a new Page for the first index even though the InterestPage was not present in the WorkPage. This has been resolved by updating the getProperty method to getIfPresent method so a new Page will not be created and the Page details will be fetched only if it is present in the WorkPage, this change will make the behavior same for all the rows in the table. | Case Management |
| INC-C12121 | 920033 | Archive handling updated for PegaSocial-Pulse-Post instances | PegaSocial-Post-Private instances were left behind following the archival process. This has been corrected by updating the logic to mark PegaSocial-Post-Private instances to Pending-Purge so the entries will be handled as expected. | Case Management |
| INC-C13699 | 934515 | FLAudit instance purge performance optimized | Field level audit instances could not be deleted due to SQL query timeouts (HY008 errors), causing purge operations to fail and instances to remain in Purge-Failure state. This has been resolved by optimizing the purge query logic to improve performance and prevent timeout failures when processing large FLAudit datasets. | Case Management |
| INC-C14193 | 919916 | AttachPDFFromPDM updated to explicitly close streams | The AttachPDFFromPDM function was not properly closing used resources. This has been resolved by adding logic to close the open input streams used in the activity. | Case Management |
| INC-C14202 | 921314 | Agent selection functionality restored | When using node agnostic view in the admin studio "Agents" landing page, the checkbox for selecting all agents was not functioning. This was traced to the "Optimize code" checkbox being enabled for the table, and has been resolved by changing the optimized table to a non-optimized table. | Case Management |
| INC-C14218 | 930230 | Updated case lock handling for same case accessed via webembed | When the same case was opened in multiple browsers by the same user and one browser submitted changes, the case updates were not being applied correctly. This has been addressed by updating the case locking mechanism handling for scenarios where there is concurrent access via webembed. | Case Management |
| INC-C14769 | 922191 | Notification count accessibility corrected | Screen readers did not announce the notification counts next to the notifications bell button. This has been resolved by updating the accessibility settings in the pyDesktopNotificationGadget section to get focus on the bell icon and modifying the pzSubscribeDesktopNotifications section to ensure the screen reader can read the unread notification count on the bell icon. | Case Management |
| INC-C15065 | 923212 | Improved accessibility for linked email attachments | When an email attachment was linked to another case by using the pxLinkAttachmentToCase activity, the Link-Attachment record was missing the pyMemo information. As a result, the name of the linked email attachment was blank under the Recent content of the case (pyCaseRelatedContent) and could not be read by a screen reader. This was a missed use case and has been resolved by updating the logic to retrieve pyMemo. | Case Management |
| INC-C15245 INC-C33988 |
928130 946024 |
ABAC handling updated for PegaArchiverUsingPipeline | Case archival was not working as expected when attribute-based access control (ABAC) was enabled to enforce row-level and column-level security. This was due to queries being adjusted to exclude data that the current user was not authorized to access, and has been resolved by updating the handling for the query in CrawlerHelper.java and ArchivalRuleAssociationResolver.java when ABAC is enabled. | Case Management |
| INC-C16158 | 925356 | SetFlowParameter handling improved | Flows with assignment shapes that had auto process enabled were failing with null pointer exceptions when attempting to resume flow execution. This was a missed use case for previous work done to fetch the flow name from the step page for a flow spun off from the Split For Each smart shape, and has been resolved by updating the handling so the FlowPageRef is set to workObjectPageName when that parameter has some value, else setting to myStepPage. | Case Management |
| INC-C16631 | 923351 | StorageType property correctly set by AttachConvertedPDF | The AttachConvertedPDF activity was not setting the pxStorageType property on Link-Attachment objects. This was a missed use case, and has been resolved with an update to correctly set the pxStorageType property during attachment creation. | Case Management |
| INC-C17010 | 924448 | ShowNotificationDefaultWrapper updated for accessibility | Elements with ARIA roles requiring parent roles were not properly contained within their required parent elements. This has been resolved with an update to the ARIA role structure to ensure proper parent-child relationships for accessibility compliance. | Case Management |
| INC-C17128 | 924064 | Updated handling for SLA queue item deletion | SLA queue item deletion failed when assignments were transferred to users immediately after SLA execution. Investigation showed this occurred due to timing conflicts between SLA processing and assignment transfer operations happening within milliseconds. This has been resolved by improving the synchronization between the processes by setting the assignment open time to a parameter in the pzopenassignmentforgetnextwork function and comparing this parameter with the case update time in movetoworklist activity. If the case is updated after opening it, it will open the assignment to get the latest assignment data. | Case Management |
| INC-C18792 INC-C32980 |
929286 948671 |
Updated handling for null JSON values to ensure backwards compatibility | After upgrade, validation errors appeared on the pzInitialValidationForPerformAction activity. This was traced to null values passed to mapInputJson which were being set as the value for properties, leading to dictionary errors. This is a difference in behavior from Pega 8.8, where if the traditional DX API request contained any fields with null values, they were ignored. To address this issue, an update has been made to replace nulls in the request JSON with an empty string, which will unset the property. This behavior is consistent with Constellation DX API endpoints. Additionally, a DSS named EnableDXAPIv188CompatMode has been added. When this DSS is configured to true, null value properties present in the request JSON will be ignored (not mapped). This behavior mirrors that of the Pega 8.8 DX API V1 endpoints, thus enabling compatibility with Pega 8.8. | Case Management |
| INC-C19910 | 928524 | Step tracker status accessibility improved | Step tracker breadcrumbs in UIKit applications did not communicate their status (current, past, future) to screen readers. This was due to missing aria-label status information that was present in Theme Cosmos but absent in UIKit, and has been corrected. | Case Management |
| INC-C21101 | 933037 | Database query limits standardized | The pzGetPostsWithUserMentions report had no query limits for PostgreSQL databases while Oracle and MSSQL had limits configured. This has been resolved by removing the hardcoded limit and allowing configuration through the pyMaxRecords application setting for all database types. | Case Management |
| INC-C22363 INC-C33988 |
929772 945752 |
Null pointer handling added for AddCaseExclusionFromArchival | Attempting to use PegaArchiverUsingPipeline was generating the message "NullPointerException: Cannot read field caseTypeClass because this.parentCaseHierarchy is null". This has been resolved by updating the handling for CaseHierarchy.toString to prevent exceptions. | Case Management |
| INC-C23933 | 931874 | Parameter page passing fixed in assignment transfer | Assignment transfer using pxTransferAssignment failed when canPerform access rules required parameter checks, causing errors during the transfer process. Investigation showed this was caused by the parameter page not being passed when RecalculateAndSave was introduced in place of Obj-Save. This has been resolved by enabling the "Pass current parameter page" option in the RecalculateAndSave activity call. | Case Management |
| INC-C24316 | 946698 | Logic added to clear temporary files created by archive search | Logic added to clear temporary files created by archive search CSV files were being created in the temporary directory when archived cases were searched and opened, but these files were not being deleted after the case was closed. This was causing disk space exhaustion over time. This has been resolved by adding logic to clear the archival temp folder after opening the archived cases. |
Case Management |
| INC-C3183 | 917958 | Added exception handling for AutomationErrors parameter | When the Case Optional process was launched, the error message set on the flow's first connector was not returned in the DX API response. Instead, an HTTP status code 201 with an empty response was returned and the assignment list and case actions disappeared. This was traced to clipboard handling for the pyAutomationErrors parameter in the pzStartFlowInternal activity, and was due to the parameter not being retained during an exception. To resolve this, logic has been added to set the pyAutomationErrors parameter when any exception occurs during the execution of the startFlow activity. | Case Management |
| INC-C33358 | 948990 | Data page autopopulate corrected | Auto-populate properties were not loading as expected when executed in the pyWorkCover context during the parent case resume process after a child case was completed. The same auto-populate rule functioned correctly in the pyWorkPage context. This was an inadvertent side effect of previous work done to handle an exception generated by the RecalculateAndSave activity, and has been corrected. | Case Management |
| INC-C33867 | 944925 | Corrected accessibility for notification gadget | Screen readers incorrectly announced navigation instructions for the notification gadget. This was caused by the dynamic layout role being configured as "ListBox" in the pyShowNotificationDefault section, which triggered arrow key navigation expectations. This has been resolved by removing role="listbox" from the dynamic layout of the pyShowNotificationDefault section. | Case Management |
| INC-C3734 | 916759 | Updated flow handling for path without assignment | If a flow was modeled with a decision shape and the flow in runtime followed a path that did not contain an assignment, the previous/back button did not work and the flow stayed at the same spot. This has been resolved by updating findLastEntryPointInFlowPath. | Case Management |
| INC-C37564 | 953642 | Assignment skill validation implemented for Go button visibility | Assignment Go buttons were appearing in Constellation for users lacking required skills, only showing unauthorized access errors after clicking. This was a difference in behavior from previous versions, and was caused by the required skills not being loaded to the pxFlow page during assignment list formation. This has been resolved by ensuring required skills are properly copied to the pxFlow page and validated before displaying the Go button. | Case Management |
| INC-C3802 | 913340 | HIstory type "A" restored for reassign activity | When a case was being reassigned, an audit message stating the case will be reassigned (with "R" in the pyHistoryType field) would be followed by another entry showing the case being assigned to the new workbasket (with "A" in the pyHistoryType field). After update, the "A" history was not being recorded. This was due to previous work done regarding an SLA rule to reassign an assignment after a timer expiration, and has been restored. | Case Management |
| INC-C38268 | 954005 | Archived case accessibility and audit history restored following cloud migration | During cloud migration from Oracle to PostgreSQL databases, "Invalid clipboard stream detected" errors were generated when attempting to deserialize archived case data, preventing access to migrated archival files. This was caused by differences in how Oracle and PostgreSQL store BLOB data - PostgreSQL's BYTEA format included an extra 32 bytes compared to Oracle's 64-byte BLOB format, corrupting the stream header signature that Pega expected. This has been resolved by adding logic to detect hexadecimal strings and apply the appropriate database-specific BLOB processing logic. In addition, the audit history was missing due to a difference in the datetime format between the databases. This has been resolved by implementing logic to manage date conversion for various databases by deriving the database type based on the date format regular expressions carried from previous databases. | Case Management |
| INC-C40010 | 951537 | Archived case search filtering corrected | Filter searches returned inconsistent results when applied to archived cases with decimal or datetime properties through report definitions. Investigation showed the indexing request was incorrectly sending property types as TEXT for archived cases instead of their actual data types (decimal, datetime), while regular cases had correct type mapping. This has been resolved by adding the property type of columns to the IndexArchivalDataModel class so the archived cases are filterable based on decimal and date. | Case Management |
| INC-C42045 | 959752 | DX API v1 validation processing corrected | DX API v1 services were failing with validation errors after upgrade. This was traced to modifications made to the handling of Declare OnChange triggers and changes in the pzApplyDataForPerformAction activity which applied mapInputJSON() logic designed for DX API v2 to v1 requests. This has been resolved. | Case Management |
| INC-C44955 | 957277 | Configuration sets loading performance improved | Configuration sets were loading slowly when accessed through the Connect GenAI rule. This has been addressed by optimizing the configuration sets datapage loading process. | Case Management |
| INC-C4509 | 915946 | Added handling for upload file parsing with special characters | File parsing during upload with the pzMultiFilePath control was failing if the file contained special characters. This was due to a mismatch in the file name which resulted in a "file not found" exception, and was caused by the pzMultiFilePath encoding the file name if it contained any special characters while the parsing function checked the file name without any encoding. To resolve this, the handling has been updated to ensure consistent encoding of file names during both upload and parsing processes. | Case Management |
| INC-C49224 | 960390 | File upload exception busy indicator handling updated | When file size validation messages appeared in modal dialogs, the screen was sometimes freezing with busy indicators remaining visible after clicking "OK" on size limit alerts. This was caused by the busy indicator not being properly dismissed, and has been resolved by adding a script to hide the busy indicator when the exception happens during file upload using pzMultiFilePath control. | Case Management |
| INC-C6160 | 913790 | Corrected accessibility issues with pzMultiFilePath control | After creating a case type and adding a pzMultiFilePath button in a section, using the tab key to advance to the “Add file” button resulted in the NVDA screen reader announcing “application”, “table”, and “Add file row1 column1”. This has been corrected by removing role = "Application" from the pzMultiFilePath control and adding role="presentation" in the control button. | Case Management |
| INC-C6648 | 917708 | Attachment widget repaired | When using the attachment widget, files smaller than the configured size limit were rejected with errors, and required attachment fields could be bypassed by deleting files before submission. This has been resolved by updating the usage field in the rule pyMaxDragDropAttachSizeMB to ensure the size specified must be an valid integer. | Case Management |
| INC-C9078 | 917563 | Updated handling for ProcessSLA exceptions | After setting the DSS 'UseSLAQueueProcessor' to utilize the pyProcessSLA queue processor instead of the ServiceLevelEvents agent, a broken queue item was generated for an SLA deadline event. Since the assignment was no longer present, the Activity-End step in EstablishContext executed and generated a broken item with the ActivityTerminateException message. When using the ServiceLevelEvents agent, no broken items are generated for this scenario. This was a missed use case, and has been addressed by adding "when" conditions to skip the Activity-End Method in the queue processor scenario and display the appropriate exception message instead of the Activity termination message. | Case Management |
| INC-C9640 | 915853 | StageStatus field value added to StageName | Case stages did not indicate the current status or provide enough context to understand what stage has already been completed, was in progress, or in a future step. To improve accessibility, the StageStatus field value for StageName has been added in the pyStageName section. | Case Management |
| SR-C2171 INC-C42668 |
939264 957565 |
Added batch file handling for SRS migration | SRS migration was failing due to OutOfMemoryError during archival data migration processing. This has been resolved by adding logic to process large files in batches during this process. | Case Management |
Cloud Services
There were no 24.1.4 Resolved Issues for Cloud Services
Conversational Channels
24.1.4 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C2588 | 941756 | Schedule report functionality restored | Attempting to update or add operators when scheduling reports from the portal or Dev Studio resulted in "cannot render section" errors. This was an inadvertent side effect of previous work to improve accessibility for the review harness which caused it to be rendered in screen layout, and has been resolved by correcting the review harness to be rendered in the container with the accessibility updates. | Conversational Channels |
| INC-C34859 | 947930 | Corrected email content display in cases | Incoming emails from Pega-based client systems appeared empty in case email panes despite containing content. This was caused by the pyGetHtmlMessage activity incorrectly removing email content enclosed in div tags with "pega-email-message-reply" IDs, treating legitimate content as previous conversation threads. This has been resolved by updating the email parsing logic to preserve original message content while properly handling conversation threading. | Conversational Channels |
| INC-C8189 | 918511 | Email Messages hidden on public pulse | Emails attached to public pulse notes were visible in the user portal. This was a missed use case, and has been resolved with an update to pzPostsWithReplies and the pyRetrieveActivityPosts report definition to filter email related pulse posts and hide them from the public pulse feed | Conversational Channels |
Data Integration
24.1.4 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B27282 | 881112 | Corrected EForm rule saving in locked ruleset version | Creating an EForm rule in a branch resulted in the binary file being saved in the locked ruleset version instead of the branch. This has been corrected. | Data Integration |
| INC-B30143 INC-B11802 |
886848 887679 |
Audit history tab displayed properly for archived cases | When clients ran case archival processes on cases with extensive audit histories, the archived cases were displaying audit history entries in incorrect chronological order. This was due to the case archival functions not properly maintaining the SaveDateTime and pxTimeCreated values when transferring audit data from active to archived storage, and has been resolved by correcting the timestamp handling. | Data Integration |
| INC-B31324 | 935295 | JFrog Artifactory authentication for deployment fixed | Application deployment processes failed when retrieving artifacts from JFrog Artifactory repositories that required authentication, blocking automated deployment pipelines. Investigation showed some requests were made anonymously instead of using authenticated credentials. This has been resolved by adding HttpContext to HttpClient configurations to ensure all repository requests include proper authentication headers. | Data Integration |
| INC-B35227 | 934869 | Updated child class handling for report definitions using ACP | Access Control Policy (ACP) rules were failing to mask properties in report definitions for child case instances. This has been resolved by enabling PropertyRead for descendant classes in queries generated with the UNION clause. | Data Integration |
| INC-B41547 | 945233 | Corrected label handling for REST service configuration page | When configuring a REST connection, some labels were displaying the parameters instead of their values in the UI. This has been corrected with an update to the pzRARecordConfiguration section in the Rule-Service-REST class. | Data Integration |
| INC-B48689 | 959303 | Table instance deployment synchronization handling updated | Changes to properties such as adding new properties, adding new database columns mapped to existing properties, or exposing properties through property optimization were not being recognized on all nodes after deployment, causing only the importing node to have access to the updated information. This has been resolved by implementing forced mapping which will fetch the necessary information from the database and build the property mapping when a property change pulse or a DADT re-save method call is received. This information is built once and will be used in subsequent calls until there is a pod restart, DADT resave, class resave, or a new property change pulse not received. | Data Integration |
| INC-B49232 | 922474 | Token retry logic updated | REST connector calls were retrying token requests on any 401 status code without checking the specific error type. This has been resolved by updating the token retry logic to only retry when the specific "invalid_token" error code is returned. | Data Integration |
| INC-B49756 | 920873 | Corrected email listener handling for p7m file attachment | If an email had a .p7m file (digital signature) attachment, the encrypted content appeared in the email body when a case was created by the email listener when using IMAP. Cases created using Microsoft Graph did not show this issue. This has been resolved by correcting the if/else condition in the message parser to build the correct HTML content. | Data Integration |
| INC-B49938 | 934917 | Warning added for non-optimized properties in access control policies | In order to save an embedded property for the PropertyEncrypt access control policy, the property must be optimized. If this condition is not met, the error message "This embedded property is not optimized. Please optimize the property before using it in PropertyEncrypt access control policy. Exposed properties other than text type are not allowed." will be generated. This is applicable for both custom and standard properties. | Data Integration |
| INC-B51773 | 914646 | Added logging for datapage open errors | Additional logging has been added to assist with diagnosing scenarios where opening the datapage D_GetComplaintCaseDetails fails without any specific error message. | Data Integration |
| INC-B52540 | 905953 | Corrected reporting for SLA breaches | Reporting was not working correctly for resolved work items which breached the goal or deadline. When a case is initially created, the pySLADeadline property holds a valid value which is successfully indexed into Elasticsearch. However, upon case resolution, the pySLADeadline property was being set to a blank string due to a step in the "Resolve" activity in the "Work-" class which was clearing critical SLA tracking properties. Since Elasticsearch does not allow blank ("") values for date fields, this property was omitted from the case resolution index payload, leading to a mismatch between the pySLADeadline value stored in the database and the one indexed in Elasticsearch. This has been resolved with an update to ensure the pySLADeadline property retains its existing value upon case resolution and that the value is valid. | Data Integration |
| INC-C10425 | 918191 | Corrected checkbox tooltip location | When editing a delegated rule and then selecting Import, the skip validation icon tooltip was displayed in a blank area of the screen instead of near the checkbox. This has been corrected. The helper text has also been updated to give more information about the options. | Data Integration |
| INC-C10777 | 955986 | Logging enhanced for large email attachment issues | Outbound emails with attachments of 25MB or larger were failing to send through the pxReply activity. To assist with diagnosing these issues, error logging has been added for chunk upload failures. | Data Integration |
| INC-C11774 INC-C24634 INC-B39032 |
928137 936816 930478 |
Assembly cache purge logic improved | Applications experienced performance problems and RuleNotFound exceptions. Investigation showed the PurgeAssemblyDatabaseCache job scheduler was incorrectly targeting Vtable rules that should have been excluded from the database under certain conditions, causing rules to need re-assembly. This has been resolved by updating the query logic to exclude Vtable assemblies from the purge process. | Data Integration |
| INC-C12148 INC-C35034 |
923118 947674 |
Updated validation and null handling for MS Graph email integration | Email case creation failures were seen in the Microsoft Graph email integration, including emails failing to be processed and email attachments indicating "unknown attachment type". This was traced to null values in email address fields in the MSGraphRESTMessageConverter class, and has been resolved by updating the validation in the MSGraphRESTMessageConverter.getInternetAdresses() method before attempting to parse email addresses. The system has also been made more robust around handling null or malformed email address data to allow email processing to continue even when encountering problematic address fields. | Data Integration |
| INC-C13308 INC-C22889 |
928048 930083 |
Added exception handling for REST Invoke activity | When a data transform which automatically added an empty requestheader was combined with the pxintegration.connector.rest log category set to debug, the connect-REST debug code to print all request headers had an empty result with a null hash map. This caused an exception to be thrown with the error "Cannot invoke Object.toString() because the return value of java.util.HashMap.get(Object) is null". To resolve this, the handling for closing object and byte streams has been updated and a null check has been added to prevent the exception in scenarios where the header list is empty in Invoke Activity and debug is enabled. | Data Integration |
| INC-C13316 | 921375 | Corrected SRS Connection request timeouts | Numerous timeout exceptions were seen in production environments when Infinity indexer was trying to connect to SRS. This was an inadvertent side effect of work done to handle a background process thread interrupt, and has been resolved by updating the logic handling for the process. | Data Integration |
| INC-C13830 | 918552 | Updated error message for max repository file size | After updating the repository/maxFileSizeInMemory dynamic system setting in the Pega-IntegrationEngine ruleset to allow a file size larger than the default max value of 45MB, the error message still had the text "Only files with size 45 MB or less is supported with response type as STRING". This has been resolved by updating the text to be "Only files up to the configured size limit or the default limit of 45 MB are allowed when the response type is STRING." | Data Integration |
| INC-C16484 | 931425 | CSV export correctly handles long property names | CSV exports using the pxDownloadDataRecordsAsCSV activity had blank columns if a data type property had a name longer than 30 characters. This has been resolved by updating the handling to hash long column names so they can be correctly exported. | Data Integration |
| INC-C18282 INC-C24944 INC-C43848 |
929291 937604 955059 |
Added Connect-REST JSON handling for emails over 20M characters | After update, using Connect-REST to retrieve emails with an attachment size > 15 MB or a message size > 20 M characters was failing with errors which included "String value length (20054016) exceeds the maximum allowed (20000000, from StreamReadConstraints.getMaxStringLength())" and "Exception occurred while mapping incoming response to .response_GET". This was traced to an internal limitation in the updated version of the third-party library jackson-core, and has been resolved by adding the necessary handling for larger messages. | Data Integration |
| INC-C18771 | 945481 | Nested JSON data transform property mapping corrected | After update, the JSON data transform functionality failed to properly map properties to custom key names if the property name differed from the desired JSON key name. This was caused by missing class context, which resulted in the system using the original property names instead of the specified custom key mappings. This has been resolved by implementing changes to preserve the class context for nested structures. | Data Integration |
| INC-C20700 | 930491 | Circumstanced rule resolution warning updated | Applications experienced incorrect rule selection when circumstanced rules were qualified but base rules existed in higher versions. The text of the Base rule warning message label has been updated to clarify that checking Base rule is not recommended for modern applications as it causes circumstanced rules with a ruleset version number lower than the ruleset version of the Base rule (Highest ruleset version of the Base rule) to be ignored by rule resolution. After skimming, additional circumstance rules could be resolved by rule resolution. |
Data Integration |
| INC-C21148 | 929805 | Corrected spaces being trimmed in ALLOF conditions | When using ABAC rules with ALLOF conditions containing values with spaces, the spaces were being incorrectly trimmed from the input values. This has been resolved by modifying the logic to preserve spaces in ABAC condition values. | Data Integration |
| INC-C21278 | 954149 | Support added for .us endpoints for MSGraph | Microsoft Graph endpoints were hardcoded to use .com domains, preventing some systems from using required .us domains for Office 365 authentication. This has been resolved by adding support for configurable domain endpoints including .us domains for Office 365 deployments. | Data Integration |
| INC-C21857 | 931447 | Query runner export functionality restored | After update, the export functionality from the Query Runner history tab was not working properly. This was traced to an error in the parameter handling for the Microsoft Excel export, and has been resolved. | Data Integration |
| INC-C22902 | 942798 | Corrected progressive loading when querying allowed | Progressive loading was not functioning as expected when "Allow querying" was enabled, causing all records to load at once instead of loading data incrementally. This prevented accessing complete datasets when APIs returned data in limited batches. This has been resolved by updating the endIndex generation when count is 0. | Data Integration |
| INC-C23489 | 935031 | JMS connection validation error handling improved | JMSConnectionFactory.validateObject was generating a PRRuntimeException error when intercepting an exception during a validation check. Because the default behavior is to establish a fresh connection immediately, an update has been made to remove the runtime exception throw on object validation failure as it was being swallowed but still causing the connect-jms caller activity to fail. The validation exception will be caught and logged, ensuring the activity continues without interruption. | Data Integration |
| INC-C23705 | 933530 | Search indexing improvements | Search indexing operations failed in production environments with SRS connector timeout exceptions and null pointer errors. Investigation showed this was caused by timeout issues when making requests to the Search and Reporting Service (SRS) during incremental indexing operations. This has been resolved by improving the timeout handling and implementing connection stability enhancements. | Data Integration |
| INC-C26301 | 944300 | JSON mapping corrected for nested pagelist structures | JSON Data Transform functionality failed to properly map nested pagelist structures, causing only the first pagelist to appear in the generated JSON output while subsequent pagelists remained empty or were skipped entirely. Investigation showed this occurred specifically when using the Append and Map feature to construct JSON structures with nested elements like page.page.pagelist configurations and was caused by a loss of context. This has been resolved. | Data Integration |
| INC-C27043 | 942888 | Heap dump DSS added for including unreachable objects | Memory alert heap dumps captured only live objects due to the Boolean parameter hardcoded to "true" in the dumpHeap invocation, preventing comprehensive root cause analysis of memory issues. This has been resolved by making the live parameter configurable by way of the prconfig setting "alerts/memory/onalert/excludeUnreachableObjects" to control the inclusion or exclusion of unreachable objects in heap dumps to allow full heap dumps when needed for analysis. | Data Integration |
| INC-C27762 | 936729 | Modified "Existing entry overwritten" from oLog.error to oLog.debug | After upgrade from Pega version 7.1 to Pega version 8.7, information from one case was carried over to the next and the error "Existing entry overwritten for WORK-OBJECT-PAY xx-xxxx" was logged, where the object identified was from the original case. This was traced to thread destruction not occurring correctly, and that functional issue was resolved in previous releases. The handling for the residual error message has now been converted to a debug-level message to avoid confusion and clutter in the logs. | Data Integration |
| INC-C27847 | 938674 | DeleteRecord updated to evaluate localized error message | The pzDeleteRecord activity was incorrectly deleting both duplicate and original records when using non-English locales, particularly Japanese. This happened when duplicate records were added, a localized error message was displayed, then deleting the duplicate record also removed the original. This was traced to the error message evaluation logic only checking for English text ("This instance already exists") instead of localized versions, and has been resolved by updating the condition to comparing localized messages instead of the text directly. | Data Integration |
| INC-C27968 | 939787 | Flag added to bypass removing duplicate rows during Insights | The "Remove duplicate rows" checkbox used in report definitions was causing visual inconsistencies when using the Insights function, especially when data was grouped in a table. This was due to the fundamental way the report definitions work, which caused the checkbox to not be consistently applied for the query that fetches groups vs the one that fetches data rows. To avoid this confusion, a an update has been made to Insights to pass a flag that always treats the "Remove duplicate rows" checkbox as false so duplicate rows are now displayed in Insights regardless of the checkbox configuration on the report definition. | Data Integration |
| INC-C28380 | 955828 | Stack overflow tracing enhanced to assist with case loading issues | After updating to Cloud, cases were failing to load when accessed from the portal and pyWorkPage remained blank. This was traced to the pxCallObjOpen activity during D_CaseLookup operations, and the logs indicated "Error loading D_CaseLookup using activity {pxObjClass=Rule-Obj-Activity, pyClassName=BNS-FW-SCOBFW-Work, pyActivityName=pxCallObjOpen}". In order to assist with diagnosing this issue, detailed logging has been added to identify which property is causing the circular reference that leads to a StackOverflowError. | Data Integration |
| INC-C28599 | 940494 | Updated handling for special characters in the Date Time values | REST API calls to data views were failing with "pxCreateDateTime value are not of the same type" errors. This was traced to incorrect handling for special characters present in DateTime values, and has been resolved by removing the decoded method from non-queryable data pages. | Data Integration |
| INC-C28820 | 938056 | Updated mapping handling to avoid OutOfBounds exception for Constellation | After update, an IndexOutOfBoundsException indicating "declare page parameters not supported by PropertyReference" was generated during the content payload mapping of PageList data if the pagelist property was empty. If the pagelist had any existing entries this error did not occur. This was traced to the mapInputJSON API, which was designed to map only the Content section of the request payload where Page List or Group properties were not expected. To resolve this, if an IndexOutOfBoundsException occurs when mapping declarative properties, the system will defer mapping those properties and instead will first map the non-declarative properties. Once the list is properly initialized, the declarative properties can be mapped without error. | Data Integration |
| INC-C29398 | 942415 | Corrected handling for TimeOfDay values in Redux-based data pages | TimeOfDay property values were being incorrectly modified when retrieved directly from Redux-based read-only data pages with report definitions as sources. This was traced to Java's binary floating-point representation (IEEE 754) returning incorrect precision values during arithmetic operations on double values in the format conversion APIs used by Redux clipboard implementation, causing 1 second to be lost during conversion. This has been resolved by updating the logic to use BigDecimal for accuracy. | Data Integration |
| INC-C29786 | 951930 | DSS added to control RDA automation response mapping | JSON responses from RDA (Robotic Desktop Automation) were not being automatically mapped to the platform when automation status was not completed, causing integration failures. This was was a recent behavior change and has been resolved by introducing the ENABLEAUTOMATIONRESPONSEAUTOMAP DASS setting that allows modified fields to be copied from runtime responses even when automation completes with errors. | Data Integration |
| INC-C30214 | 948438 | Updated header handling for forwarded messages with attachments | Tracking codes were not being decoded properly for forwarded emails, causing new email triage cases to be created instead of appending to existing email threads. This has been resolved by updating content type handling during attachment processing. | Data Integration |
| INC-C31315 | 950533 | Data table search functionality updated to skip encrypted properties | Search functionality in data tables was failing when any property column had encryption enabled, affecting both elastic search and normal search scenarios across all columns. This has been resolved by modifying the filter logic to skip to skip the properties that are encrypted from the filters that are formed in pzFilterDataTableRecords data transform when forming search filters, allowing search to work on non-encrypted columns. | Data Integration |
| INC-C31368 | 946514 | Data class deletion prevented | Data classes were unexpectedly deleted when attempting to add the same class to Data Type Explorer twice through different methods. This was traced to the attempts triggering incorrect deletion logic, and has been resolved by updating pzAddDataType to prevent this issue. | Data Integration |
| INC-C32399 | 950080 | mAbortTimeout timeout handling updated | The mAbortTimeout value was not being picked up correctly by the HttpClient. This was caused by the use of the static keyword. Since static variables are shared across all instances, the mAbortTime outvalue was being overwritten when multiple HttpClient instances were in use. As a result, while one HttpClient was executing, another HttpClient could modify the timeout, leading to incorrect values being applied and ultimately causing request failures. This has been resolved by removing the static keyword. | Data Integration |
| INC-C3256 | 913448 | Updated sendemailnotification to set messageID OUT | After creating an activity and using the Property-Set method to assign values to the respective properties followed by calling the SendEmailNotification activity with the Pass current parameter page checkbox enabled, the messageID parameter and its value were missing from the parameter page. This has been corrected by updating the SendEmailNotification activity to set the messageID OUT parameter. | Data Integration |
| INC-C33044 | 953546 | Service requestor initialization stabilized | Production system became completely non-responsive with severe latency and white screens during pod scaling operations. Investigation showed a null pointer exception occurred when access group values were null during service requestor initialization. This has been resolved by adding null value validation in the GlobalContextCache to prevent null pointer exceptions during service requestor setup. | Data Integration |
| INC-C34793 | 956663 | Server path sanitization updated | In some circumstances it was possible for the system to disclose the server path in a file upload failure error message. This has been resolved by sanitizing error messages and exceptions to display only file names instead of complete server paths. | Data Integration |
| INC-C34795 | 958631 | Invalid property persistence resolved | Cases were being created with an invalid pyReportDefinition property persisted on case instances, causing DX API validation failures. Investigation showed this was caused by the pxConvertResultsToCSV activity incorrectly creating classless properties under pyWorkPage when generating CSV downloads through UI links. This has been resolved. | Data Integration |
| INC-C34868 | 946520 | Improved ConvertResultsToCSV backwards compatibility | The pxConvertResultsToCSV activity was automatically appending dots to property names that already contained them, causing property retrieval failures. This was has been resolved by implementing conditional logic to check if property names already start with dots before appending them, ensuring backward compatibility. | Data Integration |
| INC-C35583 | 956588 | Data view API behavior corrected for empty values | After update, custom components were failing to render when clicking Professional IDs from search results. Investigation showed the DX API endpoint /api/application/v2/data_views/{data_view_ID} response data transform behavior had changed, where the Default Automap Empty Behavior switched from Default value to Null, causing empty strings and arrays to be replaced with null values that were not expected by the custom components. This has been resolved by restoring the data view API Default Automap Empty Behavior to return default values instead of null for empty data. | Data Integration |
| INC-C3576 | 928520 | Added handling for exception generated by idle page | Portal pages became unresponsive after remaining idle for approximately 5 minutes, displaying "Contact your administrator" errors. Investigation showed this was caused by thread invalidation during inactivity periods, leading to data page loss and invalid reference errors. This has been resolved by adding handling for an IndexOutOfBoundsException encountered during deserialization of a ChangeList created via a reference-type Autopopulate property context. | Data Integration |
| INC-C40236 | 960091 | Oracle database query limit handling improved | Database operations were failing with "ORA-01795: maximum number of expressions in a list is 1000" errors when retrieving property information for classes with large inheritance hierarchies. This was caused by Oracle's limitation on IN clause expressions when the ancestorAndClassGroupMemberList exceeded 1000 items during property lookups. To address this, an update has been made to detect the use of Oracle and modify the lookupPropertyQueryWithLimitedExpressions() function to build IN clauses with chunking to prevent reaching the restriction level. The original behavior is preserved for other databases. | Data Integration |
| INC-C4043 | 926889 | Performance improvement for schema change tracker | The Schema Change Tracker rule was not opening due to a long-running database query that was taking an excessive amount of time. This has been addressed by optimizing the query for customer added tables. | Data Integration |
| INC-C42476 | 955091 | SOAP header handling improved for optional elements | ConnectSoap rules were failing when optional header elements had no runtime values, generating "Couldn't create OMElement from string value" errors. This has been resolved by adding empty string validation to skip processing of headers with no content values. | Data Integration |
| INC-C46353 | 956866 | Query runner display and performance enhanced | The query runner tool was displaying only 20 columns maximum, showing unformatted text data without word wrapping for XML/JSON content, and experiencing performance issues. This was caused by limitations in the query runner implementation, and has been resolved by implementing an HTML/JS/JSP/Java-based solution that increases the column display limit to 100, adds pagination functionality, enables dynamic table column generation, and improves text formatting with proper word wrapping. | Data Integration |
| INC-C4650 | 918071 | Corrected Obj-Open handling for using system page as step page | After upgrade, attempting to use a system page as step page was failing when using Obj-Open to open the application page to fetch a value and apply it to the access group. This was traced to a missed use case for previous work done on Obj-Open-By-Handle to prevent the access group page becoming corrupted, and has been resolved by modifying the handling for MethodObjOpen. | Data Integration |
| INC-C4768 | 914549 | Embedded pages handling updated for REST Connector wizard | The REST Connector Wizard was generating Data Transforms that failed to properly map nested JSON objects to embedded page properties. This was traced to the handling of embedded page structures which called UpdatePage methods without child steps, and has been resolved with an update to ensure that nested JSON objects are correctly mapped to their corresponding embedded page properties in the generated data transform. | Data Integration |
| INC-C47722 | 958822 | Resource management improved | Resource management handling has been updated for CMIS, REST, and HTTP connectors using try-with-resources blocks in the connector activities to ensure resources are properly closed. | Data Integration |
| INC-C5094 | 917593 | Additional table map clearance logging added | Table mapping is established at node startup and generally only updated when there is some change to a particular table. For example, if a deployment modifies a table then the table mapping is invalidated and would need to be regenerated. In some scenarios, deleting a Data-Admin-DB-Table instance in an Oracle database may cause the table mapping to be deleted and trigger regeneration for every table on each node in the environment. In order to assist with diagnosing this issue, more detailed logging has been added which will identify the pzInsKey of the instance causing the clearing and include it in the message "TableMap cleared due to the deletion of non-CDH Data-Admin-DB-Table entry identified by pzInsKey [%s]". | Data Integration |
| INC-C54008 INC-C56834 INC-C7644 INC-B41974 INC-A783 INC-C10527 INC-C55435 INC-B36464 INC-B22849 INC-B20321 INC-C40905 INC-C4263 INC-C5780 |
918047 918052 |
Support added for custom error messaging for data pages | Custom validation error messages were not displayed when data objects were edited via a landing page or savable Data Page in applications using the Constellation UI, instead only returning generic errors when data objects were configured with the Edit Validate rule. This has been resolved by implementing enhanced error handling across data DX APIs that now provides meaningful error messages while also including proper identifiers for internal errors and ensuring 422 validation errors display correctly in Constellation modals. | Data Integration |
| INC-C5761 | 917442 | includeTotalCount logic improved for data_view | The POST data_view_ID API was not returning totalCount values even when includeTotalCount was specified in the request JSON and the count API was limited to 5000 records maximum, preventing proper pagination implementation in custom front-ends where users needed to know the total number of pages available. This has been resolved with an update to the logic for includeTotalCount to calculate and return the total count in the API response. | Data Integration |
| INC-C7132 | 917278 | WebSphere MQ authentication updated | Message Explorer failed to authenticate when connecting to WebSphere MQ 9 instances despite successful test connectivity. This has been resolved by adding code to fetch authentication details when JMS Listener and Connector configured with Resource Reference to ensure proper credential handling in Message Explorer connections. | Data Integration |
| INC-C8337 INC-C10570 INC-C43051 INC-C32924 |
917725 919968 955052 943537 |
Soap service compatibility corrected | After update, attempting to invoke SOAP services failed with NoClassDefFoundError exceptions related to the jakarta/xml/soap/MessageFactory class. This was traced to a compatibility issue with the SOAP JAR files being compiled with Java 11, and has been resolved by degrading the JAR changes to the previous version. | Data Integration |
| INC-C9609 | 917179 | Improved accessibility for delegation dialog | In order to improve accessibility, updates have been made to the MapFieldsUnique function to set column widths such that the table cell text is completely visible and the necessary aria labels have been added for the inputs and the related visible label relationship. For the table using pzMapFieldsInner, the caption/summary of "Field mapping" has been provided, and screen readers will announce "Field mapping table" when the user reaches the table. | Data Integration |
| INC-C9840 | 917346 | Screen reader announces DataRecordsImport validations | Validation alert messages from pzDataImportMessages were not being announced by the screen reader. This has been resolved to improve accessibility. | Data Integration |
| INC-C9941 | 919639 | Logging and tracking added for diagnosing BadStreamDataException | In order to assist with diagnosing issues with SRS, additional logging has been enabled along with a DSS which will allow skipping corrupted properties due to a bad stream exception while generating a DAT file with details. | Data Integration |
Decision Management
24.1.4 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A23778 | 853449 | Dataflow performance improved for Cassandra datasets | After upgrade, dataflows combining RDMS and DDS datasets were experiencing significant slowness when Cassandra datasets were included, while RDMS-only dataflows maintained high bandwidth performance. This was traced to multiple lookup keys in DDS Data Set browse by keys operation being processed sequentially, not in parallel, and this has been addressed by refactoring the dataset handling in dataflow operations to optimize Cassandra performance. | Decision Management |
| INC-B31616 | 916915 | Added handling for converting Numeric to Symbolic data types for categorical bias fields | After configuring the ethical bias policy with "Language" and "GenderCode" fields and configuring them with GenderCode = "1" then GenderCode = "2", no results were shown when running a simulation. This was caused by the GenderCode field being submitted as type NUMERIC when it was configured in the bias policy to be treated as CATEGORICAL. To resolve this, handling has been added to match the source data with the bias field type and convert Numeric fields to the Symbolic data type if marked as categorical bias. Additional logging has also been added to aid with diagnostics. | Decision Management |
| INC-B48810 INC-C37975 |
931549 954839 |
Logging level reset for ignored ADM responses | After update, logs were filling with errors for Adaptive Decision models (ADM) when ADM responses were ignored. This was traced to the logging level being set to "error" when "warn" was expected, and has been corrected. | Decision Management |
| INC-B51876 | 924719 | Accessibility improved for question help icon | Smart Info help icons configured for questions in question pages were not accessible via keyboard navigation. This has been resolved by implementing proper keyboard navigation support for Smart Info help icons to ensure visible focus indications and activation with the enter key. The icon has the semantic role of button and a programmatic label. | Decision Management |
| INC-B52939 INC-C42377 |
906137 955887 |
VBD DataMigration made more robust | Data migration jobs were failing with VBDServiceNotActiveException errors. This was traced to the Visual Business Director (VBD) service not being properly activated during migration job execution, and has been resolved with an update to simplify cluster service, improved detection logic for unavailable nodes, and increased diagnostic logging. | Decision Management |
| INC-C10267 INC-C28097 |
919823 942770 |
Added wrong class loader handling for CassandraQueryLogger | The Customer Decision Hub (CDH) outbound campaign run was intermittently failing with the error "Cassandra database isn't available". This was traced to the CassandraQueryLogger having been instantiated with the wrong class loader. This can occur when the DDS Service is initialized in parallel with the data flow and the DataflowGenerator.generate() method switches the class loader implementation to one that does not support the loading of this class. To resolve this, the class loader will be updated to PRApploader if the initialization of the CassandraQueryLogger is invoked with an incorrect class loader. | Decision Management |
| INC-C10502 | 917252 | Adaptive models documentation updated | The documentation for customizing predictions has been updated to specify that the response timeout in the Prediction must be less than the timeout for delayed learning. | Decision Management |
| INC-C10530 | 941531 | Updated error handling for compose and merge shapes | The same customers that generated leads during ad-hoc batch runs were not producing leads during regular batch campaign execution. While executing a merge and compose branch, a record is translated into a new record consisting of just the keys used to query a secondary dataset source. Investigation showed that if an error occurred in this branch, the corresponding record for the lookup was not always properly identified and records were returned from the secondary source in an incomplete state along with the record that failed. This has been resolved by updating the error handling to not emit the records which failed to execute due to issues such as too many matches in the source. | Decision Management |
| INC-C10530 | 924798 | Updated error reporting for conditional data flow | Offers were not being generated for some customer IDs when running a very large campaign (1 million+). Investigation showed the strategy was not being invoked for these missing customers even though they were part of the segment and no failures appeared in the dataflow or logs. Running the campaign again included the previously missing customers. This was traced to the condition matching between .pySubjectID (from segment) and .CustomerID (from customer dataflow), and has been resolved with an update to ensure dataflow errors are properly reported for compose/merge shapes when too many rows are retrieved, along with introducing additional diagnostics to make compose/merge errors available for analysis. | Decision Management |
| INC-C10999 | 920028 | Updated SavePostMessage handling for very large emails | Email Triage case processing was not working correctly when handling emails containing more than 2000 characters. Investigation showed that during the execution of the pzSavePostMessage activity, the Note page was created and the pxCompleteMessageKey field was set, however, this Note page was prematurely removed within the same activity. Subsequently, the pzProcessPulseNotifications activity attempted to access the Note page, resulting in a reference error and failure to complete the post-creation process.This has been resolved by updating the Page-Remove handling in the pzSavePostMessage activity to ensure proper page reference handling. | Decision Management |
| INC-C1190 INC-C26994 |
919865 939874 |
Data flow commit more robust during shutdown | It is possible that a data run commit could be missed when a shutdown took an excessive amount of time if a slow destination exceeded the timeout and shutdown continued regardless. Previously, the initial shutdown logic waited for at most 60 seconds before it would just exit the data flow event loop directly without checking batching stages, input queue or processing queue states. This has been resolved with an update to ensure input records are counted in the input thread and output records on the processing thread, making it safe to to clear the input queue when the data flow stops (Changes in DataFlowStage). Informative messaging regarding status and progress has also been added. | Decision Management |
| INC-C12268 | 929162 | Memory management improved for interaction history processing | The PxHandleResponses component was generating out-of-memory errors during data flow processing. Investigation showed this was caused by event strategy error handling where the internal memory state was not properly cleared when exceptions occurred, leading to "java.lang.IllegalStateException: Duplicate key" errors. This has been resolved with an update to properly clear internal state during exception processing. | Decision Management |
| INC-C13961 | 922351 | Additional logging added for predictors | In order to assist with diagnosing issues related to account context predictors failing to populate in model management responses despite being visible in pxDR records, additional logs have been added to in the ADM response composition path to understand the configuration used and predictors configured on it. | Decision Management |
| INC-C14095 | 921692 | Cassandra authentication repair frequency updated | Excessive authentication repair operations were being triggered on every pulse when using embedded Cassandra service with Cassandra driver 4. Investigation showed this was caused by the driver not collecting information about system keyspaces by default, resulting in the auth replication updater incorrectly seeing system_auth keyspace replication as 0 every time. This has been resolved by configuring the Cassandra Session Cache Cassandra driver to not filter out system keyspaces, ensuring proper replication visibility and eliminating the unnecessary repair operations. | Decision Management |
| INC-C15147 | 933140 | Default behavior changed for writing interaction history records | The database-based Interaction History aggregation was occasionally missing records during the summarization process. Investigation showed this was caused by customization that explicitly set the pxOutcomeTime to a date in the past. To resolve this, the default behavior when writing Interaction History records to the database has been updated. When applied, the pxOutcomeTime property of Interaction History records will be overwritten if all of the following conditions are met: - The DSS setting interactionHistory/writeToIH is set to true. - The existing pxOutcomeTime value is not empty and not set to a future date (future dates will result in an error). - The new DSS setting interactionHistory/overrideOutcomeTime is set to true. (default) If these conditions are satisfied, the pxOutcomeTime will be updated to the current date, and this action will be logged. To disable this new default, set the DSS interactionHistory/overrideOutcomeTime to false. |
Decision Management |
| INC-C15345 | 922503 | Improved accessibility for pyDisplayNotificationGadgetDetails | Helper text was missing for the gear icon in the notification header. This has been resolved by adding the necessary Helper Text value to pyNotificationHeader. | Decision Management |
| INC-C15468 | 930803 | Globally Optimized Strategy decision table processing corrected | The KnownPages map was incorrectly constructed during Globally Optimized Strategy (GOS) execution when using nested and external strategies. This caused outdated context variables to be used, causing decision table compilation to fail due to incorrect resolution of the Primary page. This has been corrected to ensure proper Primary page resolution during decision table compilation. | Decision Management |
| INC-C1617 | 912480 | Added hardcoded file type for default profile photo | Going into the end user portal and selecting "Use Original" to set a profile photo changed the picture to the default pzdefaultUserPic, but following that change attempting to send a pulse message to another user resulted in the email not being received and the error "FileExtension may not be null or blank for filename" was logged. This was traced to the defaultUserPic not having a file extension, and was a missed use case for this scenario. To resolve this, the pyFileType value has been hardcoded to png in the pzCropImage activity to ensure it is set correctly. | Decision Management |
| INC-C16196 | 929466 | Corrected dataflow handling for linked class instances | After upgrade, ClassCastException errors occurred when running data transforms in data flows, particularly with text properties that auto-referenced other classes via ID. This has been resolved by ensuring linked class instances are properly resolved in dataflow execution. | Decision Management |
| INC-C16222 | 932369 | pyWorkParty class maintained in DataSet operations | After update, pyWorkParty details experienced class changes when being set into data pages using DataSet functionality. Investigation showed this was caused by incorrect class mappings for page groups in DataSet features, and this has been resolved by updating the handling to preserve the original obj-class when copying the page as it may be different than model's class when using inheritance. | Decision Management |
| INC-C16295 | 921089 | Apache Parquet library updated | The Apache parquet-avro library has been updated to the latest version. | Decision Management |
| INC-C17156 INC-C5448 INC-C10984 INC-C14731 |
924539 920580 923096 924329 |
Kafka Admin related operations use Admin Client cache | A very high count of java.util.concurrent.TimeoutExceptions was seen after migration to external Kafka for running the stream service. The exception appeared mostly during lag calculation with external stream, or in environments with a very large number of queue processors. To reduce the number of connections to the external stream node, the Kafka AdminClient connections will be cached to avoid timeout exceptions. | Decision Management |
| INC-C17614 | 929620 | File access security controls strengthened | In some scenarios, it was possible to access a file uploaded by another user. This has been resolved by updating the user authorization validation before allowing file access. | Decision Management |
| INC-C20125 | 925698 | Decimal conversion error messages updated and stack trace added | GOS strategy execution failed with container exceptions when processing decimal conversions, which was caused by null values being passed from property filters to 'when' rules during DollarBalance calculations. To assist in troubleshooting events like these, exception handling has been improved to provide clearer error messages and stack traces for troubleshooting. | Decision Management |
| INC-C20885 | 927607 | Pulse post cursor position maintained after tab switch | When users positioned their cursor in the middle of pulse post content and switched to another browser tab, the cursor position was reset to the bottom of the pulse post instead of maintaining the original position. This has been resolved by updating the focus handling for tab-switching events. | Decision Management |
| INC-C22799 | 937477 | Updated handling to resolve stream data truncation exception | Stream data set truncation operations threw UnsupportedVersionExceptions when the pzExecuteWriteUsageDataFlow activity attempted to truncate records in pzDecisionUsageStream. Investigation showed this was caused by incompatible Kafka API versions during the truncation process. To resolve this, the DataSet-Execute method has been removed for stream truncation and conditional checks have been added in the pxDelayedLearningFlow dataflow to send data to streams only when the repository exists. | Decision Management |
| INC-C22863 | 945934 | Filter added for IH records with SubjectID exceeding 255 characters | The Interaction History database was throwing "Current resilient strategy doesn't own partition" errors when pySubjectIDs exceeded 255 characters, causing partition table corruption. This has been resolved by adding a filter to remove the invalid records. | Decision Management |
| INC-C24259 | 944100 | Keystore refresh synchronization improved | Data flows using Kafka with Avro Schema Registry serialization and External Secret Manager authentication began failing when secrets needed refreshing. Investigation showed this was caused by multiple threads simultaneously writing to the same keystore file during key refresh, leading to data corruption and connection failures. This has been resolved by adding a lock mechanism and handling for a race condition to the keystore file handling to ensure thread-safe access during SSL keystore operations. | Decision Management |
| INC-C25295 | 933600 | Cluster logging synchronization optimized | Large clusters experienced high heap memory utilization and crashes during node startup due to excessive Hazelcast messages from logging synchronization. This has been resolved by updating the query logger level via pulse operations instead of Hazelcast. | Decision Management |
| INC-C27000 | 945589 | Improved performance of DSMClipboardPage encryption | Data flow execution with DSMClipboardPage encryption was taking an excessive amount of time and significantly impacting ingestion performance. This was traced to performing excessive checks during data transform shape execution, and has been addressed by optimizing DSMClipboardPage encryption checks to reduce the frequency and duration of encryption validation operations. | Decision Management |
| INC-C27293 | 936779 | Dataflow service startup delays reduced | Dataflow services experienced significant delays when starting after node restarts, with partition assignments taking up to 15 minutes to complete. This has been resolved by optimizing service registry queries in CheckAssignmentsTask. | Decision Management |
| INC-C27835 | 940062 | Duplicate interaction history records prevented | Duplicate interaction history records with identical details were inserted during node shutdown scenarios when dataflow service threads were created just before shutdown. This has been resolved by implementing enhanced thread context detection and stopping mechanisms during shutdown sequences. | Decision Management |
| INC-C29014 | 938227 | Updated handling for ResponseTimeout settings | Users were unable to save ResponseTimeout settings for Predictions when updating alternate labels in prediction rules. This was caused by a conflict in the rule saving mechanism when duplicate alternate labels were present, and has been resolved by adding the necessary validations to handle the duplicate alternate labels. | Decision Management |
| INC-C31093 | 942591 | Performance improvements for Globally Optimized Strategies (GOS) | GOS compilation was taking an excessive amount of time. To address this, improvements have been made around the handling of optimization references and handling has been updated for complex scenarios where serialization and deserialization could become inconsistent. Other work includes: - Updated context variable handling to resolve Duplicate Key errors in Proposition Filters - Improved strategyresultcount execution performance with early exit conditions, better context management, and detailed validation - Enhanced logging and diagnostics for inlining behavior, component mappings, and execution flow - Introduced stricter validation of program sources before loading mappings - Expanded logging digests with richer component and execution details for better troubleshooting |
Decision Management |
| INC-C32273 | 948341 | S3 repository data flow write handing updated for improved performance | File dataset operations were intermittently failing when writing to S3 repositories due to "SlowDown" errors (HTTP 503) caused by exceeding AWS request rate limits during data flow execution. This has been addressed by removing unnecessary file listing operations when starting data flows, significantly reducing the number of S3 API requests and preventing rate limit violations. | Decision Management |
| INC-C32501 INC-C34292 INC-C10585 |
942953 947983 949548 |
Handling added for dataflow input thread exception | The DelayedItemsDataFlowService was not reprocessing or retrying delayed queue processor items as expected, and the message "Trying to repair item" was logged. This was traced to a missing input thread caused by an exception thrown by the source data set browse operation that prevented calling onCompleted on the subscriber. This has been resolved by adding a completion callback to ensure the input thread is finalized completely. | Decision Management |
| INC-C32564 | 955303 | Data migration bucket assignment handling updated | Data migration processes were intermittently failing during the additional data export stages with the error "VBDException: api.core.service.cache.operations.BucketAssignedException: Bucket '5' is assigned but not yet active [operation='VBDBrowseOperation']". This was caused by timing issues in the Visual Business Director's bucket management system, and has been resolved by implementing Retry for broadcast release events, adding logging for bucket assignment events, and ensuring that missing assignment events are added when bucket is activated and that pulse message sending is delayed until subscription to the event stream is completed. | Decision Management |
| INC-C3268 INC-C23078 |
925810 930237 |
Time-based cache eviction added for DSMClipboardPages | After optimizing ClipboardPages used in data flows and including a cache shared between all data flows, a property which was unavailable on first access of the flow was also unavailable in any subsequent flow. This was traced to the cache handling not correctly accounting for being accessed by multiple applications, leading to a scenario where a property referenced from an app where it doesn't exist being populated in the cache with a null value, and that null being persisted due to the cache not being refreshed. To address this, a time-based cache refresh has been added for DSMClipboardPages to allow model changes to be reflected in data flows. | Decision Management |
| INC-C33052 | 949090 | Kafka null message handling improved | Dataflows became stuck when encountering null values in Kafka messages. This was traced to the handling for tombstone messages (null values used for log compaction in Kafka), causing dataflows to enter infinite loops while repeatedly attempting to process the same erroneous message. This has been resolved by implementing logic to ignore messages with null values in Kafka browse operations. | Decision Management |
| INC-C33586 | 945642 | Event catalog logging enhanced | Event catalog feature failures were not generating sufficient log messages to isolate problems, making troubleshooting difficult when incorrect Cassandra keyspace configurations were used. The logging framework has now been enhanced to provide more detailed diagnostic information for event catalog failures. | Decision Management |
| INC-C33809 | 944215 | Interaction history summary processing improved | Applications experienced out-of-memory errors when processing interaction history summaries due to excessive memory consumption during pre-aggregation runs. Investigation showed this was caused by overly specific keys in the Action Outcomes By Channel Summary Data Set combined with the presence of millions of interaction history records. This has been resolved by enhancing the Decision Data Store API to support backpressure, enabling iterative record loading from Cassandra instead of loading all records at once in order to reduce memory requirements during summary data processing. | Decision Management |
| INC-C34067 | 951364 | Strategy compilation performance optimized for large operations | Very long compilation times were occurring for Globally Optimized Strategy (GOS) operations. This occurred when the context manager contained duplicate context variables with the same name in a Deque structure. To resolve this, Collectors.toMap() has been replaced with a manual loop using putIfAbsent(). This preserves only the first occurrence of each variable name (representing the latest context variable in the Deque) and prevents duplicate key exceptions. In addition, several related areas have been refactored for improved performance and robustness. | Decision Management |
| INC-C35539 | 950063 | Avro schema URL modification enabled | After update it was not possible to modify the URLs of any existing Avro schemas due to the Schema Registry tab appearing greyed out. This was an unintended side effect of work done to introduce support for configuring the schema registry URLs using application settings, and has been corrected. | Decision Management |
| INC-C35621 | 948954 | Rule resolution updated to consider rule type | A NullPointerException was generated for the GOSCentralCompilation class when handling rule updates, causing the container API to return all actions for all customers when the API was utilized from an external system. This was traced to a null value for pub.util.StringMap.getString(String), and was caused by the system performing a rule update system pulse that did not correctly extract the rule name due to the rule it was trying to resolve being of a different rule type. To resolve this, the algorithms analyzing whether any of the changed rules are descendant of inlined rules for the GOS has been refactored to use RuleDescriptors to dynamically resolve rule names according to different rule types. | Decision Management |
| INC-C36046 | 947885 | Updated handling for Shadow challenger model deletion | Attempting to remove shadow models through the Prediction Studio interface generated an exception, and Prediction Studio was failing to load after the failed deletion attempt until the M-branch was manually deleted. Investigation showed the pxSaveStrategy activity was attempting to save the strategy in a locked revision ruleset instead of the appropriate branch ruleset, and handling has been added to resolve this issue. | Decision Management |
| INC-C38064 | 951676 | GOS rule deserialization error handling updated | Container API calls returned inconsistent results across different requestor contexts after action availability time changes, requiring multiple restarts to resolve. Investigation showed this was caused by null pointer exceptions during Globally Optimized Strategy rule deserialization when inlined rules could not be resolved during compilation. This has been resolved by introducing a checked exception RuleNotResolvedException that forces parsers to explicitly handle rule resolution failures and ensuring that unresolved rules are tracked in the inlined rules list for monitoring, enabling automatic recompilation when these rules become available. | Decision Management |
| INC-C38194 | 954279 | Resolved invalid parameter error for eligibility data flow | After update, data flows were encountering InvalidParameterException errors and failing to persist error records to the data flow run error report. Investigation showed that on change of treatment eligibility, the 'when' rule selection was picking up the pylabel, resulting in the decision data rule holding the label instead of the name in the EligibilityConditions property. This has been corrected. | Decision Management |
| INC-C38444 | 956688 | Single action group end date enforcement restored | Actions within single-action groups were being offered to users even after their configured end dates had passed. This was traced to an incorrect optimization in the globally optimized strategies code which resulted in an action being always active if it had a begin date and an end date, was the only action in the group, and it was active at the moment of compilation. To resolve this, an update has been made to ensure the "Is Proposition Active" flag is correctly set to false when the proposition data reaches the end of its defined period. | Decision Management |
| INC-C38765 | 949792 | Real-time data flow status handling improved | Real-time data flows became stuck in failing state and could not transition to in-progress status even after restarts. Investigation showed this was caused by improper status transition logic when partition assignments were missing from the key-value store. This has been resolved with an update to still create an assignment in this case, which will allow unknown pods and terminated pods to be unassigned from the partitions properly. | Decision Management |
| INC-C39003 | 953229 | Improved invalidation for GOS strategy revision management | Custom strategy framework deployments were creating multiple current revisions for single globally optimized strategies (GOS) when release and engine packages were deployed separately, causing revision management confusion. Investigation showed the system not correctly marking the current revision as stale, resulting in multiple active revisions for the same strategy. This has been resolved by updating the logic to ensure the current active revision is invalidated if a new one is created. | Decision Management |
| INC-C3948 | 918565 | Added handling for AVRO union record mapping | It was not possible to publish a message to Kafka using UNION in an AVRO schema as the subschema was not properly resolved. This has been corrected by updating the mapping of AVRO unions that have records by using Pega classes' names to map them to the correct AVRO record type. | Decision Management |
| INC-C42945 | 954045 | Strategy expression null handling updated | After update, strategy expressions containing conditional date formatting operations were throwing null pointer exceptions. This has been resolved by updating the implementation to use Objects.toString() which safely handles null values by converting them to the string "null". | Decision Management |
| INC-C43635 | 955354 | Group DDR section autogeneration corrected | Group-level decision data rules (DDR) sections were not being auto-generated for groups with spaces in their names, causing section rules to reference artifacts rules instead of proper group-specific sections. Investigation showed the pzSetAutoGenerateFlag Data Transform was incorrectly relying on the 'pzIsAutoGenerated' property instead of the 'pzIsAutoGeneratedForm' flag. This has been resolved by updating the data transform to use the correct property flag for auto-generation validation. | Decision Management |
| INC-C45466 | 956974 | Pulse message timestamp display corrected for ReplyDetailsHeader | Pulse messages posted in previous days were displaying incorrect date-time values in the pyReplyDetailsHeader, where the minutes portion was showing as months in the custom date format. This was caused by improper date formatting logic in the pulse message display component, and has been resolved by correcting the "Custom date-time format" field from "MMM dd, yyyy h:MM a" to "MMM dd, yyyy h:mm a" to display minutes correctly. | Decision Management |
| INC-C45865 | 961339 | Kafka serialization handling corrected for empty PageList properties | After update, Kafka serialization was failing when non-null PageList properties were left without values. This was caused by the DSM Clipboard page conversion process incorrectly removing empty properties and lists for optimization, and has been resolved by modifying the process to maintain empty properties and lists as defined on the original page. | Decision Management |
| INC-C4794 | 919299 | Updated strategy rule handling for duplicate names | Attempting to download a Globally Optimized Strategy (GOS) resulted in the process browsing without completing, and the error "failed to scan rule strategy" was logged. This was traced to a custom strategy invoked from the parent strategy, and there was a workaround of saving the strategy under a different name and referencing that strategy in the parent strategy. To resolve this issue, handling has been added for duplicate rule names of different types which will catch and prevent exceptions to ensure reports are generated successfully. | Decision Management |
| INC-C4868 | 920637 | Updated handling for child requestor rule access | Audience count was not being shown in the PDC. This was traced to the child requestors not having access to rules invoked from the parent requestors, and has been resolved with an update to set the pzInheritRulesetList and pzUseCurrentAccessGroupForChild parameters when using the queueBatchActivity() method. | Decision Management |
| INC-C4868 INC-C23915 |
930127 932489 |
Data flow metrics converted to use job scheduler | Previously, the "PegaAESRemote" agent was used to push the data flow metrics, storage and audience metrics to the Pega Diagnostic Center (PDC). In some cases, the agent was not picking properly and the desired data was not captured as expected. To ensure better maintainability and reduce the dependency on the older Agent feature, a new job scheduler "PublishDataFlowMetrics" has been introduced which will be responsible for sending Customer Decision Hub metrics to the PDC. With this change, the existing Agent in the PegaAESRemote ruleset used to send the CDH Metrics to PDC and the data acquisition instance of the Agent in Background node have both been disabled to ensure the counts are not sent twice. | Decision Management |
| INC-C50138 | 960119 | Real-time data grid proxy configuration updated | Actions were failing to load and sessions were hanging when proxy JVM settings were configured, particularly affecting development and test environments. This was caused by real-time data grid (RTDG) communications incorrectly using JVM proxy settings, and has been resolved with an update to use DefaultHttpRoutePlanner instead of ProxySelectorRoutePlanner. The DefaultHttpRoutePlanner will not make use of any Java system properties, nor of system or browser proxy settings. | Decision Management |
| INC-C51864 | 963813 | Security updated for prediction model testing | To improve security, the output property control in prediction model testing has been changed from a Rich Text Editor to a text area, and the text formatting handling has been updated. | Decision Management |
| INC-C52034 | 960910 | Batch dataflow thread setting correctly honored | The data flow thread count environment setting was not being applied for batch runs. This has been resolved by moving the thread count population logic from run creation time to run initialization time, ensuring that environment variables are properly consulted when initializing batch runs. | Decision Management |
| INC-C7402 | 925783 | Updated error handling for S3 file browse | The browse operation was failing when attempting to browse File Dataset directories that contained no matching files in S3 storage. This has been resolved by updating the handling for empty directory scenarios to return empty results rather than throwing access errors. | Decision Management |
| INC-C7775 | 915496 | Added error handling for data flow using data set | A data flow using a data set as input to retrieve work records was only retrieving 600 records even though the table contained 40,000+ records and the failure threshold was set to 1000000. This was traced to the data from BLOB containing an invalid date on multiple records, and has been addressed by adding handling for ExceptionWithInputRecord errors. | Decision Management |
| INC-C7827 INC-C24163 |
921262 932388 |
Proposition Filter updates made more robust | A "PRRuntimeException: Proposition criteria execution failed" error was generated after deploying updated Proposition Filter rules. This was traced to differences in the timing of cache population which caused the Method and Explain Cache and the Condition Cache to go out of sync due to the Proposition Filter rule changing between these two updating. To ensure proper cache synchronization, the loadConditionCache function has been updated to invoke the PZSANITIZELOGICSTRING activity to align with assembly-time behavior, and the logic in loadConditionCache has been modified to use pzInsKey for resolution. In addition, a chunking strategy has been implemented for loadMethodCache and loadExplainCache at compile time to minimize the risk of compilation issues caused by exceeding Java’s 64KB method size limitation. | Decision Management |
| INC-C8550 INC-C39072 |
930968 950997 |
Sub-strategy updated for conditional model | Decision funnel simulation was failing when using the Trigger_NBA_TopLevel strategy (BAU). This was traced to a sub-strategy having no public component named, and has been resolved with an update which will correctly populate pyComponentName in the sub-strategy creation for the conditional model. | Decision Management |
| INC-C956 | 916005 | Documentation updated for group-by keys for Summary Data Sets | The documentation for Summary Data Sets has been updated to clarify that properties that might have unique values for each interaction history record should not be used when selecting group-by keys. Aggregation does not take place when these properties (time properties, InteractionID, pxOutcomeTime, etc) are selected. | Decision Management |
| INC-C9632 INC-C21107 |
916423 927617 |
Updated handling for summary dataset truncation | Aggregation service can unexpectedly truncate the summary dataset during failed Cassandra calls due to timeouts. To resolve this, in case of a Time Out exception an error will be logged but no truncation will be done, and an additional DSS "TruncateEnabled" has been provided to temporarily turn off truncation on aggregation keyspace completely. | Decision Management |
| INC-C9933 | 916653 | Updated migration handling for collection backed up by data sets | The PopulateSPA dataflow was not migrating single-page applications (SPAs) from Prod to Simulation as part of the data migration unless PopulateSPA was manually run. To resolve this, an update has been made to ensure collections backed up by a data set are now migrated using the dataset as the source of truth for any configuration property that was newly introduced. | Decision Management |
Low-Code Application Development
24.1.4 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B16027 | 880036 | Error message updated for expression builder | Testing parameterized data pages in the expression builder threw the error "There has been an issue; please consult your system administrator". This was caused by the expression builder test functionality not supporting parameterized data pages. To address this, a validation warning message has been added informing users that parameterized data pages cannot be tested in the expression builder and the process will exit. | Low-Code App Development |
| INC-B32080 INC-C42818 |
892672 959732 |
Production Level change event logging added | Under some conditions the Production Level property could be changed due to an update or change in the JVM parameters, but no activity for the event appeared in the audit trail. This has been resolved with an update to the EngineLoggingUtils function to capture the necessary information. | Low-Code App Development |
| INC-B51954 INC-C7741 INC-C18603 |
927468 | Updated handling for generating aggregate UVU report | Usage Validation Utility (UVU) reports were showing partial data for aggregate reports even though hourly reports were complete. Investigation showed the aggregation stored procedure had failures due to the size of the hourly files, and this has been resolved by updating the sppr_aggregate_usage and sppr_purge_table stored procedures to better handle larger file sizes. | Low-Code App Development |
| INC-C10427 | 918503 | Added accessibility to table search status message | Results from a search of delegated data tables were not announced by the screen reader. This has been corrected by updating to a dynamic layout and adding the accessibility role type to the component/widget and value to the alert. | Low-Code App Development |
| INC-C11682 | 917025 | Resolved references to removed stylesheets | When using a locale with "right to left" UI settings, the error "Section 'DesktopStyles' execution error on page 'LISTVIEW_pyCoverAllAttachmentList' of class 'Rule-Obj-ListView'... Failed to resolve rule file" was generated. This was traced to code that referred to removed desktopbase stylesheets file, and these references have been removed. | Low-Code App Development |
| INC-C12763 | 942542 | Resolved formulas displaying text instead of calculated values | Excel files containing WORKDAY() formulas were displaying the formula text instead of calculated values after parsing. This was due to the Apache POI library used for Excel parsing not properly evaluating the formulas during file processing, and has been resolved by upgrading the Apache poi version to 5.4.1 which has corrected this issue. In addition, the ExcelUtils.java file has been updated to handle complex formulas which are not supported by poi. | Low-Code App Development |
| INC-C1361 | 926643 | Improved security for URL mapping parameters | Cross-site scripting protections have been updated for URL mapping parameters. | Low-Code App Development |
| INC-C18465 | 928745 | Application login warning message addressed | The error "Required parameter AppPref for data page D_pzUserHasUnlockedRulesetsForApp cannot be blank" appeared in the logs every time users logged in. Investigation showed this occurred when all rulesets in the application structure were locked, and was caused by the AppPref parameter being marked as required when it was not necessary. To resolve this issue, the parameter has been removed. | Low-Code App Development |
| INC-C18609 | 931026 | DevStudio proxy routing corrected | DevStudio displayed blank screens when accessed through reverse proxy configurations using path-based routing. This was caused by incorrect path conversion handling in the pzClientApplicationData HTML fragmentation, and has been resolved by updating sysWebInfo to use the SystemInformationProvider API for getting system information data. | Low-Code App Development |
| INC-C21097 | 949219 | Application version creation deployment error messaging improved | A failure occurred during the 'create application version' task of the revision deployment process despite successful deploy branch completion, resulting in empty output parameters. Investigation showed this occurred if the branch had checked out rules, and has been addressed by introducing a new Pega API error code which includes the message "You must check in all branch rules before merging" along with a fail code to better diagnose and remediate the issue. | Low-Code App Development |
| INC-C2261 | 917923 | Information for generating case documents updated | Attempting to generate a Microsoft Word document using a template with hyperlink-related tags created in Microsoft Word worked correctly. However, the same process did not work properly if the template was created using Google Docs. To clarify the necessary standards, the documentation for generating case documents has been updated to specify that templates created in online or browser-based editors may not be processed correctly by the document generation engine, even if saved in .docx format. For best results, open the generated documents in a word processor with full .docx compatibility. | Low-Code App Development |
| INC-C25714 | 938374 | Hourly usage daemon made more robust | The hourly usage collection daemon was silently disabling itself and stopping data collection when encountering exceptions, particularly when operators had blank or whitespace usernames. An INFO message stating "LicenseDaemon exiting - license tracking has been disabled" was logged. This has been resolved with a check for a blank username along with improved error handling to prevent daemon shutdown and provide better visibility when data collection issues occur. | Low-Code App Development |
| INC-C31754 | 947145 | Copy/Merge RuleSet utility updated for conflicts | The Copy/Merge RuleSet utility was not displaying the list of conflicted rules during ruleset version operations. This has been resolved by updating the refactor utility's conflict detection mechanism. | Low-Code App Development |
| INC-C33268 | 943755 | GetSiblings activity security improved | Cross-site scripting protections have been updated for the GetSiblings activity. | Low-Code App Development |
| INC-C4098 | 911999 | Effective Start Date information updated | The documentation for configuring Ruleset version settings has been updated to clarify that the Effective Start Date field is used to assist with auditing future data and does not prevent the rules in the Ruleset version from being found by rule resolution. | Low-Code App Development |
| INC-C41441 | 953245 | Empty values removed from Operator profile | Operator profiles were accepting and persisting empty skill entries, allowing invalid configuration data to be saved. To resolve this, empty skills will be removed from the operator page during validation. | Low-Code App Development |
| INC-C42580 | 955078 | Decision table header rendering updated | Decision table headers were not rendering correctly when using specific function combinations in property headers. The issue manifested when switching between different function expressions like @startsWith with @substring versus @whatComesAfterFirst. Investigation showed this was caused by improper parsing of nested function expressions in the decision table header rendering logic, and has been resolved by modifying the function used in the decision table to ensure proper rendering. | Low-Code App Development |
| INC-C8184 | 915938 | Updated TLS version for REST Connector rules | Some REST Connector rules were pointing to TLS v1.0, which is deprecated. These have been updated to refer to the latest version of TLS. | Low-Code App Development |
Mobile
24.1.4 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B42467 | 903757 | Corrected mobile radio control validation display | Validation messages displayed incorrectly on mobile modal dialogs containing radio controls, with short messages concatenating instead of displaying properly. Investigation showed the mobile rendering engine was not properly handling multiple validation messages for radio controls within modal contexts. This has been resolved by updating the CSS to use display block for inline errors in the error div of radio buttons. | Mobile |
| INC-C16350 | 921003 | Offline package synchronization time-to-live increased | If a high-latency low-bandwidth network was in use, it was sometimes not possible to complete a Client for Windows synchronization with Pega due to the 15-minute time-to-live limit for continuation of the server-side offline package. During the first synchronization, the server caches the offline package in case the client loses network and the synchronization can continue from the last received data if done within the time limit, but after 15 minutes the server forced the client to restart from beginning and it was possible to become stuck in an infinite synchronization loop. With this update, the offline package time-to-live has been increased to 24 hours to ensure access for a full synchronization on a high-loss low-bandwidth network. | Mobile |
| INC-C17413 | 922332 | Synchronization and performance improvements for Client for Windows | Enhancements have been made in Client for Windows to improve performance by using a sideloading mechanism for handling large data pages and to support delta-sync and force full synchronization functionalities. | Mobile |
| INC-C22746 | 933900 | User consent popup handling updated for touch devices | After update, the Usercentrics (3rd party user consent management) popup was not clickable anymore when using touch devices. This was due to touch event handling changes in the platform, and an update has been made to support the necessary event return. |
Mobile |
| INC-C25264 | 935513 | File selection dialog focus management improved | When touchscreen functionality was enabled, opening file selection dialogs incorrectly placed the initial focus on the close 'x' button instead of the primary "Select Files" action. This was caused by inconsistent modal focus management logic implemented in a previous fix that changed behavior based on input method detection. This has been resolved with the addition of the DSS setting "ModalDialogXIconFocus" to control the behavior, and will set the focus to the close icon when is set to true. | Mobile |
| INC-C3436 | 924377 | Offline queue processing logging updated | Enhanced logging has been added around offline queue processing to provide better troubleshooting insights. | Mobile |
| INC-C42855 | 955891 | Mobile modal button alignment fixed | Modal dialog buttons were incorrectly aligned on mobile devices, with both Submit and Cancel buttons appearing on the left side instead of Submit on the right and Cancel on the left. This has been resolved by adding the necessary CSS code to align pyModalButtons properly on mobile devices. | Mobile |
| INC-C5940 | 915762 | Numeric keypad showing for iPad | The keyboard was behaving differently on iPad than iPhone with regards to Number controls. On iPhone, the numeric keypad was showing, whereas on iPad the normal keyboard was showing. This was traced to the iPad modifying its user agent which resulted in difficulty detecting iPad devices, and has been resolved by updating the pattern used for the navigator.userAgent. | Mobile |
| INC-C99 | 916808 | Touch events respond correctly in Coexistence context | When using the Constellation blended UI, clicking the "Go" button to begin work on the assignment in Dev Studio worked as expected using a desktop browser and a mouse click but touching the "Go" button on a touch-screen laptop or mobile device caused the screen to freeze. This has been corrected with an update to the handling for the pega-embed tag and root-container class. | Mobile |
Project Delivery
24.1.4 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B52885 | 912201 | Search indexing documentation updated | The documentation for Indexing class data has been updated with additional information about indexing attachments. | Project Delivery |
| INC-B53440 | 904058 | Extract rule documentation updated | The documentation for creating and running an extract rule has been updated to clarify that manifest files will be generated by default in CSV and XML extractions in Cloud/Pega Cloud. The option "Include check total property" allows you to enter a property to use as a checksum SQL function for the extraction process. This option will be disabled for CSV and XML extractions for Cloud/PegaCloud since these manifest files will be generated by default, and it will only be available for Database extraction in Cloud/PegaCloud. | Project Delivery |
| INC-C19776 | 933624 | Connect-JMS documentation updated to clarify connection eviction settings | Connect-JMS Rules use a connection pool when creating a new request to reduce the load on the server and improve performance. The eviction parameters are used to prevent connection closed exceptions by ensuring proper eviction of expired connections from the pool, improving the overall stability and reliability of JMS connections in the system. To assist with configuration, the documentation for completing the service tab of the Connect-JMS form has been updated to reflect the default values and recommended ranges for the JMS connection pooling parameters: • MinEvictableIdleTimeMillis: Default value 5000 ms (5 seconds), range: 1000 ms to 2400000 ms • TimeBetweenEvictionRunsMillis: Default value 15000 ms (15 seconds), range: 5000 ms to 1800000 ms These values may need to be fine-tuned based on your actual load characteristics and performance goals. It’s also advisable to include a buffer to accommodate traffic spikes or variability in response time. |
Project Delivery |
| INC-C20312 | 928094 | OAuth documentation updated for services access | The documentation for Defining processing and authentication for service packages has been updated to clarify that any OAuth rule in can be used to authenticate a request to a service package that is configured to use OAuth as an authentication type. There are no configurations for the service rule to map a specific OAuth client registration rule to a specific service package. | Project Delivery |
| INC-C21051 | 927488 | Documentation updated for OAUTH2 token handling | The documentation for configuring an OAuth 2.0 authentication profile has been updated to clarify that the Authorization code grant type for a REST Connector is supported only through the OIDC flow, and that this grant type should be used when the application requires manual intervention to authorize access to the protected resources of the external application. | Project Delivery |
| INC-C3223 | 908954 | Picklist troubleshooting documentation updated | The documentation for troubleshooting a picklist has been updated to note that when a picklist loads progressively and the selected value was available in the first load, it will remain in its original order in the picklist. If the selected value was not available in the first load, the selected value will become the first option in the picklist. | Project Delivery |
| INC-C35084 | 950946 | Data encryption documentation enhanced | The documentation for implementing and using the TextEncrypted property type has been updated with the information that the option to use a custom cipher for data encryption is deprecated as of the Pega Platform 24.2 release. In addition, an article with details to create a keystore for application data encryption has been made available to assist with choosing and applying a standard cipher. | Project Delivery |
| INC-C3745 | 927218 | Asynchronous processing documentation updated | The documentation for defining resource and processing details for a Service REST rule has been updated to clarify that when the REST service is configured in asynchronous execution mode and receives a request, it forwards the request to the queue class defined in the configuration settings. The queue processes messages based on its availability, and processing usually starts immediately. |
Project Delivery |
| INC-C3787 | 912500 | OAuth configuration documentation updated to identify virtual operators | The section regarding client credentials in the documentation for creating and configuring an OAuth 2.0 client registration has been updated to clarify that after a client registration is saved with the Access group option, the system creates a virtual operator for the client application. In audit logs, the virtual operator ID starts with AU followed by a set of numbers. | Project Delivery |
| INC-C41437 | 953181 | SSO best practices documentation updated | The SSO best practices documentation has been updated to note the importance of maintaining basic authentication for administrator accounts as a fallback in case of SSO failure. | Project Delivery |
| INC-C8541 | 913811 | BIX extraction documentation updated | The documentation for BIX extraction overview and for extracting data in batch mode has been updated to clarify that Snowflake database is not supported as the output destination for Extract Rules. | Project Delivery |
Reporting
24.1.4 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B21374 | 953307 | Expanded regex for case IDs in Dev Studio search | Search was not working for case IDs with the pattern XXX-240530-33, though it did work for the string Y-240530-859. This was traced to the pattern of three letters and a hyphen not matching the expected pattern of a single letter and a hyphen, and has been resolved by updating the regex pattern used in the pzSearchResults activity for Dev Studio. | Reporting |
| INC-B25317 | 885768 | Updated timezone handling for monthly case count drilldowns | When viewing a report with a column chart grouping cases by month, the cases count was correct when hovering over the column but drilldown on certain months did not count the cases on the last day of the month. This was traced to the getIntervalStartDate() and getIntervalEndDate() APIs in the FusionChartDataGeneration java file used to generate the start date and end date for the query, and was due to the completion date for a particular record in the table not falling in the range generated by the query due to the timezone handling. To resolve this, DrillDownLogicStringMaker.java has been updated to handle timezone differences for chart drilldowns. | Reporting |
| INC-B52885 | 912197 | Data-WorkAttach-File class correctly excluded from indexing | Search and Reporting Service (SRS) indexing failures were causing a backlog and interruption of indexing. This was traced to the Incremental Indexer incorrectly picking up instances of class Data-WorkAttach-File, and has been resolved by selecting the checkbox "Exclude this class from search" in the Advanced tab of Data-WorkAttach-File class definition to exclude this class from indexing. | Reporting |
| INC-C11917 | 928857 | Report browser property visibility made available | In order to support customizing Report Browser to hide all Page, Page List and Association, the 'when' rule "pyshowonlytoplevelpropsinreportbrowser" has been added. | Reporting |
| INC-C12358 | 917375 | Mixed query data objects shown in application | After creating multiple data pages on the same class where some were queryable and some non-queryable, some of the items were not shown in the dropdown when selecting sources from the Explore Data portal authoring. This has been resolved by modifying the pxExploreDataClasses logic to ensure that only query-enabled data pages appear in the dropdown. | Reporting |
| INC-C14796 | 920094 | Updated filtering for children during parent class re-indexing | A "No document was found" error was generated after performing a re-index for Search. Investigation showed that when an "Index Data" operation was done on a parent class, the existing child class index data was deleted during the process and not recreated. This was a missed use case, and has been resolved by adding the pxObjClass filter in the DeleteByQueryCommand criteria. | Reporting |
| INC-C15050 | 921818 | Accessibility improved for repeating structures view | The Explore Data table was announcing "All" instead of "All Insights" when users navigated with accessibility tools. To improve accessibility, this has been updated to set the aria-label for the table container to be as same as the visible heading on toolbar. The same will be followed for the toolbar action menu-button. | Reporting |
| INC-C15768 | 925195 | Explore data insights category display corrected | After creating a Shared Insight for a Casetype and sharing access with a user and a workgroup, incorrect category details were displayed after reloading Explore Data and trying to expand the Insights. This has been resolved by using count distinct on pyGUID for the insights table to handle the duplicates generated by the permissions. | Reporting |
| INC-C16938 | 928204 | Corrected validation for security event configuration landing page checkboxes | Security event configuration checkboxes were not being honored, potentially causing sensitive data to be exposed in search query logs regardless of the "Search queries" setting. The "Successful logins" event checkbox was also not functioning as expected when deselected. This has been resolved by updating the validation handling for the security event configuration landing page checkboxes and ensuring events are logged as expected. | Reporting |
| INC-C17666 | 932304 | DSS added to chunk large database queries | After upgrade, data synchronization failed on the search landing page during indexing of classes. The Oracle database error "ORA-01795: maximum number of expressions in a list is 1000" was generated. Investigation showed this was caused by SQL queries being generated with more than 1000 expressions in the IN clause when synchronizing relevant records, exceeding Oracle's database restriction of 1000 entries per list. This has been resolved by implementing query chunking that splits pxInsId values into maximum 1000-item segments and joins multiple IN clauses with OR conditions, controlled by a new DSS setting indexer/model/relevantRecordsChunkPropertyRecordsMaxSize under Pega-SearchEngine ruleset. | Reporting |
| INC-C19222 | 930385 | Corrected tenant ID handling for synchronization | Platform Model synchronization failed with Oracle query error "ORA-00904: 'null'.'PZTENANTID': invalid identifier" when attempting to configure OpenSearch for Rule Search in multi-tenant environments. This has been resolved by updating the default search type to SEARCH_SERVICE and adding the class alias name while preparing the SQL queries to fetch the CSPs while synching the data model. |
Reporting |
| INC-C19291 | 926914 | Insights updated to use locale information for Currency | When any currency field was added as a primary field for a case type data model, the currency symbol defaulted to USD in the data Insights even though the locale of the Operator ID and Server were mapped to another country. This has been resolved with an update to check for a currencyCode configured in pyAppDefaultFields and use that value in Insights. | Reporting |
| INC-C19351 | 940050 | Report browser save operation updated | Report Browser Save As operations failed with a "Delete record failed" error after performing consecutive Save As operations on reports. Investigation showed this was caused by improper record handling in the pzRRSaveAs activity, and has been resolved by enabling the WriteNow checkbox at step 22 of the pzRRSaveAs activity to ensure proper record creation. | Reporting |
| INC-C20660 | 927506 | Removed 10 year +/- date restriction for optimized filters | Date filters in optimized tables were restricting date selection to only +/- 10 years from the current date. This was due to a hardcoded date range limitation in the filter panel configuration, and has been resolved by removing that limitation in the pzFilterPanelDateOptions section. | Reporting |
| INC-C20763 | 929220 | Handling added for extracting encrypted data from BLOBless tables | After adding encrypted properties to the mapping in the definition tab and not in the filter, a BIX extract failed and the message "An error occurred during resolving the report definition - Property 'Prop2' is encrypted" was logged. This has been resolved with an update to handle the decryption of encrypted columns for BLOBless tables during extraction. | Reporting |
| INC-C21587 | 933254 | Added check to prevent null pointer exception when Permit Access is empty | A null pointer exception was generated from a report definition if the ABAC policy had a "when" condition which evaluated to true and the permit access field was left blank or empty. This has been corrected by updating the filter logic. | Reporting |
| INC-C21667 | 960418 | BIX manifest count accuracy improved for nested structures | BIX extract manifest files were showing confusing and intermittently inconsistent values in pxTotalInsertsCount and pxTotalInstanceCount properties, with insert counts sometimes unexpectedly exceeding instance counts. Investigation showed this was caused by incorrect counting logic in the manifest generation process for chunked extracts with nested structures, and has been resolved by correcting the pxTotalInstanceCount manifest count calculation to accurately reflect the actual processed records when the extract includes a structure that has pagelist inside a pagelist. | Reporting |
| INC-C22627 | 930340 | Improved accessibility for chart actions menu | Chart actions menus were not providing meaningful context for screen readers when multiple charts appeared on the same page. This has been resolved by adding aria-label attributes with chart titles to provide unique identification for each chart's actions menu. |
Reporting |
| INC-C24513 | 933325 | Corrected scroll bars for ar_MA locale | The Report Browser was not displaying scroll bars for the left-side property list when using the Arabic Morocco locale (ar_MA). This was caused by incorrect CSS positioning rules for right-to-left (RTL) layouts in the report editor styling, and has been resolved. |
Reporting |
| INC-C24841 | 936345 | Security updated for Insights | Cross-site scripting protections have been updated for Insights reports. | Reporting |
| INC-C2516 | 910539 | Report access permission message display fixed | Reports displayed an empty blue box when access permissions were missing. This was traced to the report filter box appearing without proper privilege validation, and has been resolved by adding conditional logic to the RRFilter embedded section and enhancing the when rule validation in pzIsDisplayingInlineSection. | Reporting |
| INC-C27086 | 940563 | Report Menu button contrast improved | To improve accessibility, the color contrast of the Report Menu actions button has been updated. | Reporting |
| INC-C27311 | 936400 | Corrected Summary Report drilldown accessibility | The focus was not moving to the arrow symbols as expected when accessing the drilldown report in the Report Browser. However, the focus behavior worked correctly when opening the same report from Dev Studio. This has been corrected to ensure consistent accessibility across all portal types. | Reporting |
| INC-C27425 | 936384 | Updated datetime handling for Prompted Filter | Prompted filters for datetime fields were not returning correct results when the date part in Explore Data insights was set to seconds. This has been resolved with an update to consider the operator time zone while calculating the datetime values in function aliases. | Reporting |
| INC-C30499 | 946044 | Report filter scrolling improved for high zoom levels | Report filter panels became unscrollable at 150% browser zoom when application headers were enabled, preventing access to filter options. This was traced to CSS layout conflicts between the application header and filter panel at high zoom levels, and has been resolved by adjusting the layout calculations in pyReportEditorStyling CSS to accommodate various zoom levels while maintaining proper scrolling functionality. | Reporting |
| INC-C31207 | 942020 | Updated BIX handling to bypass S3 validation if not available | BIX extraction rules configured for database output were incorrectly checking S3 connectivity and failing when S3 was not configured or had connectivity issues, generating the error "User does not have access to the Output directory: bix". This has been resolved with an update which will bypass S3 bucket validation during BIX database extraction. | Reporting |
| INC-C31709 | 952833 | PDF margin settings corrected to allow zero values | PDF documents were not respecting explicitly set margin values of zero. Investigation showed the PDFUtilsImpl Java file contained a condition that applied default parameters when margin values were set to zero or less. This has been resolved by modifying the logic to properly honor explicitly set zero margin values in PDF generation. | Reporting |
| INC-C32053 INC-C29826 |
940674 938526 |
Modified ExcelExporter compression mode | After update, a Robotic Process Automation (RPA) flow where a bot read an Excel report and extracted the data was failing with the error "File contains corrupted data". This has been resolved by updating the ExcelExporter compression mode to false so the generated Excel is compatible with PowerBI. | Reporting |
| INC-C32508 | 945274 | Updated SearchResultsWorkOptions cloud environment status evaluation | The @Utilities.pzIsPegaCloud() function was returning false in non-production environments, causing controls like case search filters to not display the "Archive Items only" option. This has been resolved by updating the pzSearchResultsWorkOptions UI control condition. | Reporting |
| INC-C33003 | 948978 | KMAuthor access corrected | Users with KMAuthor access group could not use the "Summarize By" dropdown option in Knowledge Management Published Reports, while the same functionality worked for KMSysAdmin users. The access permissions for have been corrected to resolve this issue. | Reporting |
| INC-C33805 | 949358 | Added handling for unexpected characters causing exception | RequestorLockExceptions were occurring on the NativeSQLAPIResolver component, which created thread lock issues on ClassMap operations. Investigation showed this was caused by an incorrect SQL query formed due to an underscore(_) in the data which was excluding descendant classes. This has been resolved by updating the logic for special characters. | Reporting |
| INC-C35809 | 952389 | Corrected report sorting and pagination data accuracy | Report definitions with rank options returned incorrect data when users applied column sorting and then navigated to subsequent pages. This was caused by rank query updates based on sorted columns that interfered with proper pagination. This has been resolved by updating the logic in the pzGridSortPaginate activity. | Reporting |
| INC-C36386 | 955702 | Batch processor queue validation improved | Data was being pushed to the pySASBatchIndexClassesProcessor queue even when automatic updates were disabled. This was caused by DSS validation checks being applied at the processing end rather than when data was initially queued, and has been resolved by modifying the ModelChangeDispatcher to validate the automatic updates setting before queuing data. | Reporting |
| INC-C36544 | 951843 | Report data cleanup removes temporary data pages | The pxRetrieveReportData function accumulated temporary pages over time, leading to memory exhaustion and system instability. Investigation showed cleanup was not working as expected when a data page was involved, and this has been resolved by updating pxretrievereportdata to remove the temporary page in that scenario. | Reporting |
| INC-C37347 | 949462 | Elasticsearch indexing performance improved for multitenant environments | Applications were experiencing slow indexing performance when using agents for batch indexing in multitenant Elasticsearch configurations. This has been resolved by implementing queue processor-based reindexing with proper multitenant support, where the system now finds all classes per tenant, enqueues classes to queue processors with multitenant support, and processes each event through class batch indexer queue processors for improved performance. | Reporting |
| INC-C39205 | 951260 | Database join functionality corrected with ABAC policies | Database queries failed with "invalid identifier" errors when joining classes that had ABAC policies applied. Investigation showed that the SQL generator incorrectly referenced column aliases from the wrong table context when ABAC policy conditions were applied to joined classes. This has been resolved by fixing alias resolution in report queries with right outer join when ABAC policy conditions are applied. | Reporting |
| INC-C4196 INC-C4727 |
915285 | Improved accessibility for Insight legend texts | Insight legend/value text was appearing as truncated in the Constellation portal depending on the length of the legend text. This has been resolved with an update which will show the full text in a tooltip on hove/focus. | Reporting |
| INC-C42154 | 955200 | Content security policy commenting format updated | FusionCharts JavaScript was triggering Content Security Policy violations due to commented localhost URLs in the code. This was caused by single-line comment syntax that CSP parsers were interpreting as active URLs, and has been resolved by converting the single-line comments to block comment format to prevent CSP interpretation as executable content. | Reporting |
| INC-C43821 | 959941 | Chart drill-down functionality restored for date dimensions | Column chart drill-down operations were failing with HTTP 500 errors when date fields were used as chart dimensions. This was traced to the system incorrectly converting date values to epoch timestamps in the filter criteria during drill-down operations, and has been corrected. | Reporting |
| INC-C45896 | 960615 | Excel export consistency stabilized on Constellation for localized list | After creating a landing page in Constellation with a data page as the data source, configuring promote filters, and localizing column headers using field values, the Excel export functionality was producing inconsistent results when performed multiple times on the same list, with variations occurring in column order, column content, column name translations, and promote filter application. Investigation showed this was caused by the pyPageName not being properly maintained during the export process, and this has been resolved by copying the old pyPageName in the pzGetFiltersFromContent activity to ensure stable and consistent Excel export results. | Reporting |
| INC-C6003 | 929837 | Security updated for showHeader | Cross-site scripting protections have been updated for the showHeader parameter in URLs. | Reporting |
| INC-C6985 INC-C7911 |
919810 919757 |
Corrected Pulse notifications for multi-tenant environments | After upgrade, new Pulse notifications were not being displayed as a count on the bell icon within the portals in a multi-tenant environment, and no notifications for new messages were being delivered. Running the tracer showed the error "Execution of SQL statements via NativeSQLBuilder is restricted in MT environments." This issue was an inadvertent side effect of work done on the pySendNotification activity rule which introduced java code utilizing NativeSQLBuilder, and has been corrected by modifying the logic to allow native SQL script execution in multi-tenant environments. | Reporting |
| INC-C7046 | 916322 | Report Widget date filters corrected | Report widgets in dashboards were displaying incorrect filtered data when chart bars were clicked, showing zero records instead of the expected monthly data. Investigation showed the system was filtering by the first date of the month rather than the entire month period when drilling down from chart visualizations. This has been resolved by modifying the date range filtering logic in the dashboard widget implementation to make use of DateUnits to ensure correct ranges. | Reporting |
| INC-C8513 | 918931 | Added handling for calling multiple report definition data pages | Null pointer errors were being generated when filtering a table of report data. Investigation showed that during the filtering, D_SearchAccountsForAccess was being called; because this used data sourced from a report definition, pxRetrieveReportData was called again and the previous report data in the table was being cleared as a result. This was a missed use case, and has been resolved by updating pzReplacePropertiesWithRDFields. | Reporting |
| INC-C936 | 946567 | Exception handling added for addreportdefinitiontodatapage | The pyReportDefinition page was missing from data pages despite enabling the 'datapages/addreportdefinitiontodatapage' DSS setting. Investigation showed this was caused by an exception in the report definition tracer post-successful execution, and handling has been added to resolve this issue. | Reporting |
| INC-C9927 | 918022 | Updated report scheduling radio button controls | Radio buttons in report scheduling configuration were not selectable when setting up monthly recurring tasks. This was traced to a deprecated control, and has been resolved with an update to the radio button control implementation in the scheduling interface. | Reporting |
Security
24.1.4 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-C38451 |
950657 | OIDC dynamic parameter processing supported | The dynamic parameters for the OIDC authorization endpoint were not getting passed. Investigation showed the dynamic parameters were treated as literal strings instead of being processed as parameter references, and this has been resolved by implementing proper dynamic parameter processing for OIDC authorization endpoints. | Security |
| INC-B42474 | 901524 | Corrected handling for activating keystore after client secret update | When using data encryption with Microsoft Azure Key Vault, activating the new key store or forcing a data key rotation were not working when the client secret was updated after expiry. This has been resolved by updating the handling in KeyVaultManagementService and KeyVaultMetadataManager. | Security |
| INC-B53119 | 909608 | The SECU0006 Alert updated to better track brute force login attempts | The Security Alert frequency based on the "Failed login attempts before employing authentication lockout penalty" setting in Lockout policy has been updated. Previously, the message was sent once based on reaching the configured threshold. With this update, alert messages will be shown based on the number of attempts. When the policy number is reached, the alert "PRPC detected excessive failed login attempts for the user:XXXX from IP: Proprietary information hidden. Brute force attack prevention measures were invoked" will be generated. Then for every X number following, the alert will be "PRPC detected excessive failed login attempts for the user:XXXX from IP: Proprietary information hidden. Brute force attack was detected and the same has been prevented." | Security |
| INC-C12767 INC-C23551 |
923199 929948 |
HTTP Strict Transport Security header implementation updated | To improve security, an update has been made to ensure HTTP Strict Transport Security (HSTS) headers are included in the initial /prweb call response. | Security |
| INC-C13472 | 921673 | PDF library version information display made configurable | Generated PDF files expose the exact PD4ML library version in document properties. To improve security, a "when" rule pyHidePD4MLVersion (Boolean) has been added to control whether or not the version number information is included in the properties of the generated document. The default is to include the library version number. | Security |
| INC-C13496 | 921705 | OIDC scope selection control updated | Reviewing the viewXML rule of the OIDC Auth service showed discrepancies between the scope defined in the rule form and the indexes present in the OIDC XMLView. Investigation showed the multi-select control used for the Scope in Authentication Service rule was saving duplicate values for scopes. This has been resolved by updating the handling in the Data-Admin-AuthService class to avoid this behavior. |
Security |
| INC-C16146 | 929332 | JWT token processing documentation updated | The documentation for creating a processing JSON web token profile has been updated to clarify that if a processing token profile is created alone without a generation token profile, the truststore name must match the name of the alias/public key inside the truststore to prevent the error message "Unable to retrieve JWK public key". | Security |
| INC-C17675 INC-C46454 |
942704 958148 |
Corrected application alias URL redirection | Application alias URLs were incorrectly redirecting to the authentication screen selector page instead of the basic Web-Login page when SAML/OIDC authentication services existed in the environment. This occurred even when the authentication service was not associated with the specific application being accessed. This has been resolved with an update to ensure accessing prweb/app/appalias will redirect users to Web-Login.HTML. | Security |
| INC-C20976 | 928542 | Authentication Security Improvement | After updates were made to prevent accessing certain activities in an unauthenticated context with pzAuth=guest, downloading the mobile app using a QR code was not working. This has been resolved by adding authentication logic for pzAuth=guest and pyActivity & pyStream combinations. | Security |
| INC-C20976 | 928851 | Improved authentication security | In some scenarios, it was possible for guest access to bypass authentication and execute select activities. This has been resolved by enhancing the authentication mechanisms to block unauthorized access attempts and return appropriate error responses. | Security |
| INC-C21025 | 954105 | URL error message security updated | In order to improve security, the ShowMessage HTML rule in @baseclass and Code-Pega-List has been updated to remove requestor and operator details. | Security |
| INC-C22149 | 928470 | Documentation updated for BLOB encryption data key creation | The documentation for encrypting the storage stream (BLOB) has been updated to clarify that the BLOB encryption process cannot generate a new Pega Platform data encryption key and uses the existing CDK. Information is provided to assist with manually generating a new data encryption key. | Security |
| INC-C22611 | 949049 | Null check added to correct authentication validation error | After update, custom authentication services experienced unexpected system errors when processing incorrect PIN validation requests. Investigation showed this was caused by a NullPointerException that occurred if the PIN was invalid, and has been resolved by adding a null check. | Security |
| INC-C23008 INC-C1804 INC-C26193 |
929812 949292 934301 |
Updated cross-site scripting protections related to calendar creation | Attempting to create a calendar instance failed with the error "Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate". This has been resolved by updating the pyXSS_Prevention_Validate rule logic. | Security |
| INC-C23350 | 929155 | Improved regex algorithm for masking logic | Users were unable to login when DEBUG logging was enabled for the HttpUtilities class. This was due to complex pattern matching operations exceeding the regex processing capacity in the requestor ID masking logic and causing PatternSyntaxException errors. The regex algorithm has been updated to improve performance. | Security |
| INC-C23867 | 954126 | SiteCipher decryption handling updated | Application creation from Blueprints was failing with "Decryption with SiteCipher is not supported" errors when site cipher encryption was enabled, causing the wizard to become stuck. This has been resolved by updating the siteCipher encrypted password validation. | Security |
| INC-C25230 | 934938 | File upload security validation enhanced | Security has been updated by improving the logic checks to prevent the upload of malicious files. | Security |
| INC-C25712 | 935043 | Mobile JWT authentication session handling corrected | JWT Bearer grant type authentication failed for mobile applications when configured to use JWT assertions from active SSO sessions. Investigation showed the pxRequestor page properties pointed to Mobile Token Credentials instead of the OIDC authentication service. This has been resolved by enhancing the design to properly identify OIDC authentication services for mobile users. | Security |
| INC-C27076 | 940776 | Security checklist API names corrected | Security Checklist API response contained task names that did not match the corresponding names displayed in the studio interface, including several typographical errors. This has been corrected. | Security |
| INC-C28714 | 949998 | Email listener token refresh mechanism updated | Email listeners using Microsoft Graph API (Outlook integration) were intermittently failing with "token is expired" errors, showing running status but not processing emails. This was caused by a failure in the automatic OAuth token refresh mechanism within the MS Graph Email Client, and has been addressed by modifying the purge access token logic and adding additional logging to assist with diagnostics. | Security |
| INC-C28826 INC-C6968 INC-C19693 INC-C31107 INC-C29509 INC-C36468 |
939898 923695 928895 940001 940193 947388 |
Updated content-type handling for REST authentication | The error "Access token endpoint invocation failed : {statuscode=200, ErrorMessage=Token endpoint response doesn't contain access token}" was seen during the OAUTH2 token invocation of a REST connection. This was traced to the header containing the content-type of application/x-www-form-urlencoded or text/html instead of application/json, causing an authentication mismatch. To resolve this, an update has been made to ensure the response header is correctly populated with content-type as "application/json" when an access token is available. | Security |
| INC-C29028 | 945853 | Password security policy enforcement standardized across authentication methods | In some circumstances, inconsistent security controls were seen for SSO-authenticated administrators. This has been resolved by updating the password policy validation logic to consistently enforce security policies regardless of the administrator's authentication method. | Security |
| INC-C30503 | 947346 | preventXSSInLabel documentation updated | The documentation for the preventXSSInLabel DSS setting has been updated to outline the use and security risks involved in the decision to prevent or allow HTML injection into a Label control. | Security |
| INC-C30763 | 950507 | Security alert accuracy improved for whitelisted activities | SECU0003 security alerts incorrectly triggered for the pyOnbeforeWindowClose activity despite being included in the allowed activity list. Investigation showed this was caused by the whitelist checking activity names without considering class context. This has been resolved by updating the security validation to properly match activities using their full class-qualified names. | Security |
| INC-C32672 | 944373 | Security improved for WebLogic error messages | WebLogic servers were displaying detailed error messages in the browser when processing malformed requests. To improve security, error sanitization has been implemented to return generic HTTP 400 responses for malformed requests. | Security |
| INC-C3298 | 924784 | CSRF token validation updated | GET requests were not properly validating CSRF tokens for non-AJAX requests, potentially allowing unauthorized changes to be committed. This has been corrected. | Security |
| INC-C34123 | 947376 | Work item access security errors eliminated | Opening existing work items generated 403 errors with security alerts about unregistered requests for the showstream activity. This was caused by improper request validation in the Pega_Desktop_DocGadgets.JS file for whitelisted Action Launch Harness operations, and has been resolved by correcting the BAC validation logic for deprecated WorkList operations. | Security |
| INC-C35686 | 948371 | Enhanced URL security | In some scenarios, there was a potential to execute unauthenticated activities by manipulating parameters. This has been addressed by introducing an attribute to identify tampered or malformed URL requests so they cannot bypass validation. | Security |
| INC-C36852 | 954633 | Report definition class hierarchy handling updated for use with Access Control Policies | Report definitions were failing with pxObjclass exceptions when Access Control Policies (ACP) were defined on parent data classes in complex inheritance hierarchies. The issue occurred specifically when data classes served as parents to abstract platform classes that contained report definition subclasses, and was caused by improper class resolution when ACPs were present in the inheritance chain. This has been resolved by adding handling to prevent .pxObjClass exceptions in the subclass report definition when an ACP exists on the top Data-class. | Security |
| INC-C39151 | 953627 | Delegation security token handling corrected | Applications were experiencing SECU0019 "The mashup is not consistent with the latest security enhancements" alerts and blank screens when attempting to edit data type rules from delegated landing pages in blended UI environments. This was traced to the system incorrectly adding an active CSRF token (pzCTkn) to URLs when the signature token was already present, and has been resolved by modifying the UI logic to prevent duplicate token parameters from being sent. | Security |
| INC-C39718 | 965650 | Operator profile security updated | Cross-site scripting protections have been updated for operator name fields. | Security |
| INC-C41015 | 953483 | pxDefaultSecured updated to work with Chrome 139 | The Live UI tool failed to load due to Content Security Policy errors introduced by Chrome 139 browser updates which affected CSP-blocked worker error events. To address this, the Content Security Policy rule pxDefaultSecured has been updated. | Security |
| INC-C46073 | 958763 | Handling updated for proxy authentication password decryption | Email accounts configured to connect to Microsoft Graph API through corporate proxies requiring basic authentication were failing with "407 Proxy Authentication Required" errors. Investigation showed this was caused by the system sending encrypted password values directly to the proxy instead of decrypting them first, resulting in authentication failures. This has been resolved by ensuring proper password decryption occurs before sending credentials to proxy servers during OAuth 2.0 authentication flows. | Security |
| INC-C47134 | 965629 | Mashup page security updated | Cross-site scripting protections have been updated for the pzLoadMashupPage activity. | Security |
| INC-C52309 | 961505 | CSRF validation security enhanced for DX APIs | CSRF validation checks have been updated for hybrid apps DX APIs. | Security |
System Administration
24.1.4 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B23797 | 949447 | Added handling to avoid requestor destroyed error | The error "java.lang.InterruptedException: Requestor has been destroyed or recycled" was observed in the logs. A RequestorLockException occurs when the system tries to access or interact with a requestor object that is no longer available, either because it has been destroyed, recycled, or is otherwise locked due to concurrent access or timing conflicts, and generally occurs when deferred or queued events are triggered just milliseconds after a user logs off. This error is known to occur under certain timing conditions and does not have any functional impact on the system. To address the issue, an update has been made to manage exceptions more effectively by ensuring that all beforeunload event listeners are removed during logoff, preventing unexpected triggers after the requestor is recycled. | System Administration |
| INC-C13310 | 935883 | Debug logging added for ERR_PROPERTY_TYPE_CHANGED | In order to assist with diagnosing issues where indexing operations failed with "ERR_PROPERTY_TYPE_CHANGED" errors for count properties, enhanced debug logging has been added to capture oldProperty, newProperty, and mergedProperty details. | System Administration |
| INC-C13337 | 920362 | Markdown library update | The markdown library has been updated to the latest version. | System Administration |
| INC-C14319 | 924772 | Exception handling improved for REST service authentication | REST service connections were experiencing a high failure rate during stress testing. This was traced to the system attempting to handle an exception that did not have an error message, causing it to throw a null pointer exception on top of the original error. This has been resolved by adjusting the DSS settings to enable stack trace logging during JWT processing. | System Administration |
| INC-C15356 INC-C35725 |
926972 948238 |
Corrected logic for queue processor context | The queue processor was routing items to an incorrect queue processor instead of the intended target, causing RuleNotFound exceptions when the system attempted to execute activities in the wrong class context. This was traced to the page change class method used to establish proper class context for queue processor execution and has been resolved by updating the logic to ensure correct routing. | System Administration |
| INC-C20603 | 935440 | Handling updated for international number formatting | A currency code starting with 'X' was not visible at the Inquiry Amount Field under the workcase details UI. This was due to changes between Java 8 and Java 11, and. has been resolved by updating the es_CR (Spanish Costa Rica) currency symbol and creating new APIs to load the currency,decimal, grouping separator symbols from locale XMLs. | System Administration |
| INC-C21581 | 959020 | Performance statistics table bloat prevented | Application requestor metrics for Customer Decision Hub applications were generating excessive data in the pr_perf_stats table despite configured retention settings, requiring manual table growth management and causing failure events for ClusterAndDBCleaner. This has been addressed by improving the performance of the pyClusterAndDBCleaner which is responsible for purging data from the pr_perf_stats table. | System Administration |
| INC-C25621 | 945830 | Added locales | Locale support has been added for Ireland ('ga', 'ga_IE' ), Sweden ('en_SE'), and Norway ('nb','nb_NO'). In addition, logging has been enhanced in datetime to better determine if a locale is invalid or missing if an IllegalArgumentException is generated in the PDC. | System Administration |
| INC-C25875 | 946584 | Added check for file processing before removal | The queue processor was deleting repository files before successful processing completion when case locks were held during inbound email processing of attachments larger than 5MB. This has been resolved with an update to ensure that large message content is only removed from the repository upon successful processing, and the snapshot cleanup post handler has been removed. | System Administration |
| INC-C25895 | 939739 | Date format pattern compatibility added for en_BE locale | After upgrade from Pega 8.8 to Pega Infinity 24.1 and from JDK 8 to JDK 17, applications encountered IllegalArgumentException with "Illegal pattern character" errors. Investigation showed date format patterns for the en_BE (English Belgium) locale were incompatible with the newer JDK version. This has been resolved by updating date format pattern handling to ensure JDK 17 compatibility. | System Administration |
| INC-C30907 | 940233 | Queue processor updates | Queue processors experienced latency when writing records compared to stream datasets. Investigation showed this was caused by the default Kafka acknowledgment strategy requiring confirmation from all brokers. This has been resolved by implementing support for ACK=1 acknowledgment strategy. In order to address a related issue where Kafka will throw the exception "Must set acks to all in order to use the idempotent producer" when enable.idempotence=true is used for anything else except acks=All or acks=-1, the delivery strategy has been updated to AtMostOnce. | System Administration |
| INC-C31356 INC-C36685 |
946545 948650 |
Queue processor lag calculation corrected | Queue processor lag metrics displayed inaccurate values when processing high-volume Kafka messages. Investigation showed this was caused by a race condition where delays in committing queue processor offsets to the database table led the system to incorrectly use Kafka's end and start offsets instead of the correct queue processor offset for lag calculations. This has been addressed by correcting the lag calculation logic to properly handle timing delays in offset commits. | System Administration |
| INC-C36448 INC-C36734 INC-C36789 INC-C36801 INC-C36941 INC-C37168 INC-C37236 INC-C37237 INC-C37276 INC-C37353 INC-C37566 INC-C37624 INC-C37824 INC-C37994 INC-C38285 INC-C38376 INC-C39213 INC-C40100 INC-C41015 INC-C41020 INC-C41029 INC-C44165 INC-C45714 |
957416 | Live UI functionality restored for Chrome/Edge browsers | Live UI was failing to load when using the default Content Security Policy (CSP) configuration 'pxDefaultAllowAll' in Google Chrome and Microsoft Edge browsers version 139.X.X and later. This was caused by a Chrome 139 update which introduced a change that fires an error event when CSP blocks a Worker script, preventing Live UI from functioning properly. The issue may be addressed with a local workaound by adding "blob:" to the list of allowed websites in the Child Frame-Source section. This has been resolved by updating the platform to handle the new browser behavior and ensure Live UI compatibility with the latest Chrome/Edge versions. | System Administration |
| INC-C37758 | 952531 | PropertyDataPageWrapper log message refactored | The Autopopulate loggers have been updated to create the necessary additional objects when debug mode is active. | System Administration |
| INC-C38015 | 948897 | Data flow query performance optimized | Scheduled record processing experienced significant performance degradation in DelayedItemsDataFlowService data flows. This has been resolved by implementing query optimization improvements to eliminate the performance bottleneck. | System Administration |
| INC-C39326 | 955501 | History added for operators automatically disabled by security policies | When the Operator disablement policy was enabled with the "Number of days of inactivity," the DisableDormantOperators Agent would run at the appropriate time and invoke the pzDisableDormantOperators activity without any audit trail or history records being maintained. This was caused by the DisableDormantOperators agent's pzDisableDormantOperators activity lacking logic to update operator history records, and has been resolved by adding history tracking functionality to the operator disablement process. | System Administration |
| INC-C40021 | 953848 | Apache Parquet library updated | Apache Parquet has been updated to the latest version. | System Administration |
| INC-C41005 | 951295 | Made queue processor more robust when encountering corrupted items | Queue Processors were failing to process items after encountering corrupted messages in the queue. This has been resolved with an update that adds an isDebugEnabled check before logging values in the queue processor flow to allow the system to skip corrupted messages and continue processing. | System Administration |
| INC-C47204 | 960042 | Axios updated | The Axios library has been updated. | System Administration |
| INC-C57042 | 965980 | Apache Tika updated | Apache Tika libraries have been updated. | System Administration |
| 917358 | Corrected large heap issue in PegaBroadcasterCache class | Web nodes were going down due to high heap utilization. Investigation traced this to the size of PegaBroadcasterCache, which overloaded due to a large number of verifydisconnectedRequestor push messages sent by the server whenever the client was idle for 40 seconds. To resolve this, an update has been made to stop caching the push messages unless a disconnection is detected. | System Administration |
User Experience
24.1.4 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-C18864 | 925823 | Embedded pagelist autocomplete restored | Embedded pagelist autocomplete functionality was not working after upgrading from Pega 8 to Infinity 24.2 when using DX API. This was traced to the FUA flag handling during the upgrade process, and has been resolved. | User Experience |
| INC-A23056 | 838242 | Corrected accessibility for Rich Text Editor controls | When using Rich Text Editor controls with the JAWS 2022 screen reader, the control announced a generic "Rich Text Editor, PEGACKEDITOR" label instead of the descriptive field label. This was due to a missing aria-label attribute and has been corrected. | User Experience |
| INC-A29326 | 948852 | Focus corrected after modal dialog is closed on the utility pane | When users refreshed pages or launched cases and navigated to the utility pane gear icon, closing the “Followers" widget caused focus to be lost instead of returning to the gear icon. This was a missed use case and has been resolved by correctly setting the focus after section refresh. | User Experience |
| INC-A29636 | 921701 | Configurable time limit set for PDF generation | PDF generation processes were running for excessive periods and causing threads to become stuck, impacting system performance. This has been addressed by implementing configurable timeout settings through the pyPdfSettings data transform to automatically terminate PDF generation after a specified time limit. | User Experience |
| INC-B26622 | 879692 | Corrected Custom DX Component publishing with locked ruleset | Custom Constellation DX Component Builder publishing failed when the application ruleset specified in the task.config.json file was locked. This has been resolved with an update to handle locked ruleset scenarios properly. | User Experience |
| INC-B31175 INC-C15021 |
886372 923066 |
Updated accessibility visibility handling for autocomplete carrot dropdown | After creating an Autocomplete and checking the "Display as combo box (field and button)" in presentation, the focus moved to the caret icon which did not contain any accessible text. To improve the accessible experience, pzpega_ui_template_autocomplete.js has been updated to implement the aria-hidden="true" attribute for this icon. | User Experience |
| INC-B51509 | 903540 | Corrected error icon covering checkbox | The field level error message icon was covering the checkbox, causing difficulty with checking/unchecking the checkbox. This has been corrected by updating the CSS. | User Experience |
| INC-C10206 | 917971 | Tabbed layout displayed correctly in Semantic UI | Tabbed layouts were automatically switching to stacked layout after enabling the Semantic UI. Investigation showed the markup was incorrectly generated when the layout was configured with a visibility on embedded section and Semantic UI, and has been resolved with an update to ensure Semantic details are handled for the pxvisible template. | User Experience |
| INC-C10332 | 915749 | Improved accessibility for delegated table Edit buttons | Descriptive alternate text was missing from the Edit buttons aligned with items on a list of delegated tables in the configuration tab. This has been corrected by adding a field value of type pyCaption for Edit buttons in the pzDelegatedRulesGrid section. | User Experience |
| INC-C10374 | 922763 | Added check for empty DX API activity | Numerous IllegalArgumentException alerts were seen after upgrading from Pega version 8.7 to Infinity 24.1, impacting PDC and PEGA alert logs. This has been resolved by updating pzDXAPICreateTempNewRow with a condition to check whether activity name is empty or not, and then proceed if not empty. | User Experience |
| INC-C10418 | 927769 | Refresh action correctly triggered on change | After update, an autocomplete action set with a refresh section was not being invoked as expected. This was an inadvertent side effect of previous work done to correct an unexpected reload after search, and has been resolved by ensuring the popover is marked as active so the onchange will be triggered. | User Experience |
| INC-C10511 | 921574 | Assignment persists after browser refresh | Assignments disappeared and showed blank screens when browsers were refreshed after case creation and assignment opening. Investigation showed that during 'loadDeferredDocument' function call, the 'displayOnPage' action was overriding the 'openWorkByHandle' action. This has been resolved by including openAssignment in the metadata for microDCRenderer. | User Experience |
| INC-C10615 | 919749 | Accessibility updated for Case Manager dashboard | In order to improve keyboard accessibility, the role link has been added to the dynamic layout in Case Manager, and focus styling has been added to the Recent, Following, and Team Member links/buttons. | User Experience |
| INC-C11030 | 918169 | Highlight corrected for double-digit rows in embedded config | After creating an embedded table with modal editing and adding server side validation, errors in the 10th row were not highlighted as expected. This has been corrected by updating the regex function. | User Experience |
| INC-C11122 | 921124 | Custom filter section link role updated | In order to improve accessibility, the role for a custom filter section link in a report definition has been changed from document to link. | User Experience |
| INC-C11202 | 921343 | Radio button tooltip displays multiline content | Radio button help text tooltips failed to display when field values contained multiple lines or line breaks. This has been corrected. | User Experience |
| INC-C11253 | 919887 | Added check for corrupted flow action | A flow action rule was being deleted when a user attempted to open it, UI distortion occurred when activities were opened, and instances could not be opened from the Record explorer. Investigation showed it was possible to have a corrupted state in which attempting to open a flow action instead opened up a section rule, causing invalid section live preview logic to be triggered. If the section rule was templated, logic in the Preview runs created a temporary section and then deleted it. To address this, handling has been added to hide the live design view preview when there are no available rulesets available to ensure no assets are deleted. | User Experience |
| INC-C11271 | 929044 | Modified embedded property rendering for table column dropdown | A column included in a table with dropdown control set to read only initially showed the prompt value in the Constellation UI, but showed "Standard value" instead of prompt value after switching to other tab with another table and returning. This was traced to issues with PagePropertyRenderer, and has been resolved by modifying the function to use dxComponents directly for page properties to ensure the correct metadata is passed. | User Experience |
| INC-C11507 | 921845 | Corrected layout group tab labels visibility | Layout group tab labels disappeared when the Rich Text Editor was opened in full screen mode within modal windows. Investigation showed the ResizeHarness function was positioning the RTE with absolute positioning without properly resizing the harness container. This has been resolved by correcting the harness resizing behavior when RTE is maximized. | User Experience |
| INC-C11797 | 919477 | Skip links accessibility navigation corrected | Tab navigation was bypassing the skip links target element when initially loading the user portal. This was caused by improper focus handling during initial page load, and has been resolved by updating the handling for pyIsWindowStealFocusInIEAllowed to ensure skip links are properly accessible on first navigation attempt. | User Experience |
| INC-C11819 INC-C19019 |
919771 925139 |
Cross-site scripting filtering updated for resaving rules | After update, attempting to save-as the existing Paragraph rule to new ruleset version generated a syntax error. This was related to the handling of cross-site scripting filters on the Rich Text editor while resaving, and has been resolved by updating the handling to allow Pega JSP tags and related attributes which are already secured. | User Experience |
| INC-C12168 | 917234 | Corrected redundant "Title" labels in operatorID | In Dev Studio, the Operator ID ruleform showed two "Title" fields. This was due to the second "Title" field's property, pyPosition, undergoing a change from previous versions: earlier, the pyPosition property was labeled "Position / job title" and was sourced from Pega-RULES, however, in higher versions, while the pyPosition property was still used, the pyPosition from Pega-UIEngine, which was labeled as "Title", replaced it. This has been resolved with an update to display the second title field as "Position / job title" to avoid confusion. | User Experience |
| INC-C12171 | 926344 | Localization works correctly with Data Page Flag | Data Page List filters were not displaying translated field values correctly when the "Allow querying any Column" checkbox was enabled. The filter overlay was picking field values from the base class instead of the appropriate localized context, while the column values themselves displayed correctly. This was due to the system inconsistently handling field value resolution between the main table display and the filter overlay, and has been resolved with an update to make this resolution consistent. | User Experience |
| INC-C12345 | 917815 | Updated Reports buttons for accessibility | In order to improve accessibility, the role of the expand/collapse icon for the report definition in Dev Studio has been updated from link to button. | User Experience |
| INC-C12790 | 921835 | Rapid menu clicks will open subsequent panels | Clicking rapidly on different items in the left navigation bar under throttled network connections resulted in the menus being opened with all text visible and stacked. To resolve this, if more than one menu item is clicked, each of them will be opened but panels will replace each other instead of overlapping. | User Experience |
| INC-C12872 | 925822 | Updated field value handling when using FUA flag | After upgrading from Pega 8 to Infinity 24.2, DX API issues were seen with label creation when field values ended with dots and FUA flag was enabled. This was caused by the (.)dot in the label value being treated as property reference when combined with the FUA flag, and has been resolved by adding a condition to handle label value with (.) in this scenario. | User Experience |
| INC-C13096 | 923028 | Corrected change event actions for table operations | Editable table configurations with change events triggered system administrator consultation errors when clicking outside the work area after data entry. This has been resolved by updating the handling of change event action sequences in non-optimized table contexts. | User Experience |
| INC-C13355 | 921100 | Corrected className handling for clickable link to details | After enabling a field/column as link to open the details view, the view only opened the first time the link was clicked and failed on subsequent clicks. This was traced to the calculation logic of className, and has been resolved by updating the handling so it is reliably accessed. | User Experience |
| INC-C13693 | 920253 | Corrected accessibility for optimized table with no first column menu | After adding an optimized table to the UI and only allowing sorting for a column, then using the keyboard to sort the column, tabbing out of the optimized table and then pressing Shift + Tab keys did not return to the last table cell in the optimized table that had keyboard focus. Instead, focus moved to the tabbable element before the optimized table. This has been resolved with an update to correctly focus on the last focussible element. | User Experience |
| INC-C13714 | 922699 | Corrected arrow key accessibility for hybrid Constellation | Arrow key navigation was not working as expected in Explore Data tables when running in Constellation hybrid mode. Investigation showed the accessibility utilities were using document.activeElement which is incompatible with the hybrid application as Constellation in rendered within shadow DOM. This has been resolved by updating to domElement.getRootNode().activeElement which will work both in normal and hybrid applications. | User Experience |
| INC-C13832 | 927434 | Dirty dialog behavior corrected for case sections | Browser alert dialogs appeared after clicking OK on dirty popup dialogs when using buttons placed in CaseActionHeader and CaseDetails sections. This has been resolved by correcting the dirty dialog dismissal logic. | User Experience |
| INC-C13969 | 922469 | Field alignment with empty values corrected | Field alignment became distorted when field values were empty, particularly affecting the Todo Section display where subsequent elements appeared below instead of inline. This has been resolved by correcting the CSS styling to use inline-block display for proper field alignment when values are empty. | User Experience |
| INC-C14334 | 921840 | Operator menu accessibility improved | After opening the user portal and opening the screen reader, clicking on the operator menu read the menu only and did not read the operator name, and the operator menu button could not be reached. This was traced to a mismatch between the operator menu aria-label and button label, and has been resolved by synchronizing the labels to include both the operator name and menu designation. | User Experience |
| INC-C14758 | 921906 | Updated accessibility for hidden case icon | After the child work object was resolved, navigating back to the parent case displayed a hierarchical table listing all work objects, including any parent-child relationships, in a tabular format with an expand/collapse icon to allow users to view or hide child cases when they are present. The child work object correctly did not show the expand/collapse icon when the case was resolved, but the screen reader continued to interpret and read the expand/collapse functionality even though it was hidden. This has been resolved by adding aria-hidden ='true' so the expand/collapse icon will not be read by the screen reader when it is not visible. done | User Experience |
| INC-C15007 | 931819 | Corrected focus after refresh with hidden modal buttons | When performing refresh actions within modal dialogs where the standard modal buttons were hidden, keyboard focus was incorrectly moving behind the modal instead of staying within the dialog container. This was traced to the lastFocusable element not referring the actual DOM element after performing the "Refresh-Section" action, and has been corrected. | User Experience |
| INC-C15010 | 922633 | Smart Tip closes inside grid on focus change | Smart tips were not dismissing when focus changed away from table elements in Constellation hybrid mode. This occurred when using an optimized table and Link control with Actionset Focus and Smarttip with plain text. To resolve this, focus detection has been updated so the Smart Tip closes correctly on focus change for this configuration. | User Experience |
| INC-C15432 | 924631 | Logoff timeout dialog accessibility fixed | The logoff timeout dialog button was missing accessibility attributes in the timeout dialog implementation. This has been resolved by adding the necessary handling for it to receive focus. | User Experience |
| INC-C15819 | 924901 | Swiss French currency formatting corrected | Currency fields displayed incorrect "sFr" symbols when using the fr_CH (Swiss French) locale. This has been resolved by updating the fr_CH locale with the correct currency symbol mapping. | User Experience |
| INC-C15899 | 927344 | Updated accessibility for Anypicker clear icon | The "clear selection" icon in the Anypicker control was not being properly announced by screen readers when users hovered over selected values. This has been corrected by adding the aria label for the close icon and updating the aria label when the dropdown values change. | User Experience |
| INC-C15959 | 931274 | Screen reader documentation updated | The documentation for Configuring Links and Best Practices for Accessibility has been updated to clarify that the screen reader does not announce special operations for standard link controls, such as opening the link in a new window, and that no screen reader support is provided for custom controls used as links. | User Experience |
| INC-C16050 | 922535 | Localization enhanced for SimpleTable controls | Applications experienced untranslated "Add" button text and row labels in SimpleTable controls when using non-English locales. This was traced to missing localization entries for these UI elements in the pygenericfields resource bundle, and has been resolved. | User Experience |
| INC-C1635 | 916402 | Help icon helper text localized | The text phrase "Help for" which appeared as part of the helper text overlay triggered by the Help icon was not being translated. This has been resolved by creating a field value for the "help for" text so that it can be localized. | User Experience |
| INC-C16407 | 923972 | Disable condition validation fixed | Forms with input controls using "Disable when" conditions were showing "Invalid request data" errors when submitted, preventing successful form submission. This was caused by incorrect validation logic that checked editable fields using raw configuration data where disability status was present with annotations. This has been resolved by adding a check for disabled status of field. | User Experience |
| INC-C16881 | 927354 | Corrected accessibility for Anypicker control being read twice | The NVDA screen reader was announcing the Anypicker control button twice when users navigated to it using keyboard controls. This has been corrected by updating the roles for input element and search results panel. | User Experience |
| INC-C17018 | 928571 | Localization updates | Several localization issue have been addressed, including items on the duplicate case search screen such as assignment names, table headings, column headers, and status values not being properly translated. | User Experience |
| INC-C17078 | 925719 | Visibility conditions fixed for view refresh operations | Autocomplete fields with data references were not refreshing properly after update, particularly when used in table modal edit scenarios. This has been resolved by correcting the handling for the mapping of item visibility to state of the list. | User Experience |
| INC-C17092 | 935363 | Updated handling to prevent case context switching | Opening Details/History tabs on different cases caused context switching, displaying data from previously opened cases instead of the current case. Investigation showed the pzINSkey was not being consistently cleared from redux when opening new cases. This has been addressed by updating the handling to check for pyID in redux first, then fallback to pzINSKEY. | User Experience |
| INC-C17245 | 926732 | Corrected accessibility for Anypicker down arrow | The down arrow button in the Anypicker control was missing the necessary aria-label attributes for accessibility. This has been corrected. | User Experience |
| INC-C17362 | 929596 | Updated handling for forming semantic URL after browser refresh | Pages were incorrectly redirecting to self-service-main-page after an inactive period. This occurred when custom pyHome or pyHome1 views were configured, and was traced to an incorrect semantic URL formation that launched standard views instead of custom ones on browser refresh. This has been resolved with an update which will consider page class when forming the correct semantic URL for showPage. | User Experience |
| INC-C17545 | 930748 | Corrected AM/PM handling for Morocco | Date time controls were displaying AM/PM indicators in English instead of Arabic when using the Arabic Morocco locale (ar_MA), and subsequent refresh actions were throwing validation errors. This has been resolved by providing locale-specific AM/PM values for the ar-MA locale. | User Experience |
| INC-C17807 | 926763 | Multiselect readonly display corrected | Optimized table multiselect controls configured as readonly were displaying as editable. This was caused by inconsistent handling in the renderControl function where multiselect controls did not follow the same readonly logic as other control types due to it being a a page-list type property. This has been resolved by implementing consistent readonly handling for multiselect controls in an optimized table. | User Experience |
| INC-C18216 | 927278 | Date range control dirty check corrected | Form dirty checking did not trigger when users modified datetime controls configured with date range options. This has been corrected. | User Experience |
| INC-C18593 | 931364 | Preview button on last notification made focusable | The preview button on the last notification in a series was not accessible via keyboard navigation. This has been resolved by updating the focus management in the notification UI rendering logic. | User Experience |
| INC-C18767 | 925968 | Smart Tip keyboard navigation corrected | Using the Enter key to close a Smart Tip overlay via the X icon during keyboard navigation resulted in the overlay immediately reopening. This was traced to the keyup/keydown handling combined with the focus shift on close, and has been resolved by correcting the keyboard event processing. | User Experience |
| INC-C18782 | 928593 | Dialog close button accessibility resolved | The dirty check popup close button was not accessible via keyboard after focus had moved to the Cancel or Submit button when working in the perform harness. This has been corrected with an update to ensure focus on the close icon when ModalDialogXIconFocus is true. | User Experience |
| INC-C19466 | 925553 | Corrected datetime handling for Costa Rica locale | When using the operator locale es_CR (Costa Rica Spanish), opening the History tab of any rule in Dev Studio after logging out and logging back in displayed corrupted datetime values for "Last Added By", "Last Updated By", and "Last Moved By". This has been resolved by updating the locale configuration for es_CR in the datetime formatting module. | User Experience |
| INC-C19770 | 929496 | Accessibility improved for calendar controls | Calendar controls have been updated to address accessibility issues including hidden elements and insufficient color contrast that prevented proper screen reader access and visual identification. | User Experience |
| INC-C19779 | 927106 | Constellation flowaction options restored | UIKit applications with constellation-enabled case types could not access certain flowaction customization options, specifically the save button label customization. This was caused by the pyIsConstellationUI 'when' rule returning false for UIKit applications, and has been resolved by updating the when rule logic to properly recognize UIKit applications with Constellation features enabled. | User Experience |
| INC-C19790 | 930486 | Improved accessibility for server-side validation error banners | When using server-side validation, the banner at the top of the screen listing fields with errors was displaying the messages using markup which was not easily interpreted by screen readers. This has been resolved by updating HarnessErrorList. | User Experience |
| INC-C19950 | 925653 | Tooltip option added for radio button helper text | Radio button controls lacked the tooltip helper text option that was available in other form controls. This has been added. | User Experience |
| INC-C19973 | 929504 | Improved accessibility for Calendar icons | Calendar icons were displayed with insufficient color contrast (opacity 0.5) making them difficult to see for users with visual impairments. This has been corrected by setting the iconCalendar opacity to 1 in the pzbase-control-icon.css rule. | User Experience |
| INC-C20466 | 931772 | Date picker calendar icon accessibility updated | Date time controls in dropdown mode had calendar icons that were not accessible to screen readers and could not receive keyboard focus. This has been resolved by adding proper aria-label and role=button attributes to make the calendar icon fully accessible. | User Experience |
| INC-C20897 | 932626 | Corrected mobile popover closing | Tooltips remained visible on mobile devices after closing full-screen results. Additionally, when results were configured inline, the results overlay was not opening on subsequent attempts. This has been corrected by updating the multiselect control to generate CSS classes without trailing spaces and properly reset the isPOOpen flag when overlays are closed. | User Experience |
| INC-C21062 | 940811 | Accessibility improved for field validation error announcement | JAWS screen reader failed to announce field-level validation error messages when client-side validation was triggered on required fields. This has been resolved by implementing proper focus management and accessibility attributes for validation error announcements. | User Experience |
| INC-C21248 | 929108 | Child case overlay keyboard accessible | Child case overlays were not accessible via keyboard navigation. This has been resolved by adding keyboard event handlers in the overlay interface. | User Experience |
| INC-C21440 | 930091 | Thousand separators correctly hidden in read only table | Thousand separators were displaying in read-only table cells when they should have been hidden. This was caused by incorrect formatting logic for read-only table display, and has been resolved. | User Experience |
| INC-C21724 | 932715 | Corrected missing user reference data | User reference properties in editable table rows were losing their data when rows were deleted from the top of the list, causing selection values to disappear. This was traced an issue with data handling during row deletion operations in embedded page lists, and has been resolved by correcting the data preservation logic to maintain user reference values when table rows are manipulated and re-rendered. | User Experience |
| INC-C21855 | 942082 | Browser refresh assignment error resolved | An assignment error was generated on browser refresh while a Constellation case was displayed in a traditional portal. This error did not occur in a pure Constellation portal. This was traced to the state management during browser refresh in mixed portal environments, and has been resolved by updating the Rule-Utility-Function pzFindAndUpdate to better handle the blended UI. | User Experience |
| INC-C21926 | 929879 | Mobile create menu positioning corrected | The create menu overlay was displaying in incorrect positions when accessed from mobile footer navigation, sometimes overlapping with the footer or extending beyond screen boundaries. This was caused by forced width styling conflicting with dynamic position calculations, and has been resolved by updating the CSS positioning logic. | User Experience |
| INC-C21938 | 941912 | Corrected handling to maintain view data | Data on the main page was disappearing after submitting information through a modal window, requiring a page refresh to restore the content. This occurred because additional properties and readonly view data were not being maintained in separate objects during payload preparation, and has been resolved by storing the additional properties in separate objects. | User Experience |
| INC-C22028 | 932475 | Modal title styling corrected | Modal dialog titles were applying Heading 2 mixin styles instead of the specified custom styles when configured in the application skin. This has been corrected. | User Experience |
| INC-C22151 | 933842 | Bootstrap configuration loading performance improved | Applications were experiencing extreme slowness when generating routing tables, particularly in lower environments where the D_pxBootstrapConfig data page was taking excessive time to load. Investigation showed this was caused by inefficient Report Definition calls being used instead of more performant Engine API methods. This has been resolved by replacing the Report Definition approach with direct Engine API calls to generate the routing table, significantly improving application performance. | User Experience |
| INC-C22254 | 932548 | Validation error focus corrected | Focus was incorrectly shifting to the case header title instead of the field with the validation error in caseworker portal forms. This has been resolved by correcting the focus behavior. | User Experience |
| INC-C22554 | 929801 | Close icon accessibility improved | Modal overlay close icons were not accessible via keyboard navigation and did not respond to Enter key presses. This has been corrected by adding focus ring styling and Enter key event handling to enable full keyboard accessibility for modal overlays. | User Experience |
| INC-C22706 INC-B48169 |
932069 910580 |
Updated handling for section rule live preview | After opening section rules through the Live UI tool, adding an entry in the list of deleted rules as a preview did not delete the section rule. This issue occurred when the preview section was generated in a locked ruleset in an application without checkout enabled on the operator. This was a missed use case for a live preview rule save when no proper ruleset was available, and has been resolved with an update which will only provide a section rule live preview if a proper ruleset is available, and otherwise will show a status message indicating "No ruleset versions available". | User Experience |
| INC-C23064 | 934921 | Summary panel tab accessibility improved | Clicking on Pulse or Details tabs in the summary panel failed to move focus to the respective tab content when multiple sections were present in the work area. This has been resolved with an update to address focus movement between summary panel tabs. | User Experience |
| INC-C23418 INC-C29128 INC-C26706 INC-C27462 INC-A5862 |
941837 | Landing pages correctly opening on portal load | Logging in to the Constellation Work Portal displayed the message "TypeError: Cannot destructure property 'routeKey' of 'this.appRoutes[n]' as it is undefined." instead of the expected landing page, and the page was unresponsive. This was traced to a missing valid route in the routing table caused by stale routing table data due to cache invalidation. To resolve this, the engine API is now used to read routing table data directly from the database instead of the previous report definition data page. | User Experience |
| INC-C23461 | 932037 | Corrected decision table calendar handling | When working inside a decision data table, the calendar was not shifting as expected when using the up or down arrows to change the month. This was caused by missing mouseup event handlers in the ui_spinner component, and has been corrected. | User Experience |
| INC-C23710 INC-C25525 |
934472 935619 |
Added null check for pop-up window show harness | After update, pop-up window actions configured as "Click → Harness → Target: Pop-up Window" in the Admin portal stopped functioning due to "Uncaught TypeError" JavaScript errors. This was traced to previous work done to escape special characters in the window name parameter of the Show Harness action when the target is a popup, and has been resolved by adding a null check. | User Experience |
| INC-C24373 | 934542 | Focus indicators added to time picker footer links | Apply and Close links in the DateTime time-only popup calendar lacked focus indicators when accessed via keyboard navigation. This has been resolved by adding the CSS focus styles for these footer links to improve accessibility. | User Experience |
| INC-C24596 | 931740 | Week start day made consistent in datetime picker | Date time picker controls were displaying inconsistent week start days between different picker components (some starting Monday, others Sunday). This was caused by inconsistent locale configuration between UI components, and the handling has been updated to resolve this issue. | User Experience |
| INC-C24609 | 943324 | Form refresh handling updated | Form refresh data was not persisting when users clicked the next button in a screenflow, causing previously set data properties to reset when navigating back to previous screens. This has been resolved by updating the handling for both 'refresh' and 'refreshFor' calls. | User Experience |
| INC-C24677 | 947229 | Portal development sections open correctly in Designer Studio | After upgrade, error messages were generated when attempting to open ArtifactViewTemplate, ArtifactSection, and AssistedArtifactSection rules in Designer Studio. This was due to missing class definitions, and has been resolved by adding the class $none definitions for sections in 'for' loops to restore proper section opening functionality. | User Experience |
| INC-C24882 | 935400 | Updated accessibility for multi-select properties | When using a search screen with a property configured as a multi-select drop-down the errors "Elements must only use supported ARIA attributes" and "ARIA attribute is not allowed: aria-multiselectable="true" were generated. This has been resolved by updating the aria-multiselectable attributes in the control and template files. | User Experience |
| INC-C25152 | 949546 | Corrected special characters in multi-select email addresses | Email addresses had special characters displayed in multi-select fields. This was due to incorrect encoding by the cross-site scripting filter, and has been resolved by replacing the filter with DOMPurify in the "htmlForNewTokenCapsule" function within the multi-select control JavaScript. | User Experience |
| INC-C25271 | 951496 | Email template security updated | Cross-site scripting protections have been updated for the Customer Decision Hub email correspondence rule template selection. | User Experience |
| INC-C25417 | 932743 | jQuery library updated | jQuery has been updated to the latest version. | User Experience |
| INC-C25516 | 933651 | Added error handling for change tracker | User actions were becoming stuck when modal dialogs contained fields with client-side disable conditions that remained in the change tracker after modal closure. This was traced to the change tracker attempting to resolve client conditions for properties that were no longer available in the current thread context. This has been resolved with an update to properly clear change tracker entries when modals close. | User Experience |
| INC-C25734 | 938712 | Localization updated for "My Work" heading | The "My Work" heading was not displaying localized text. This has been resolved by updating the localization rule of pyWorklist. | User Experience |
| INC-C26056 | 938031 | Authorization error page refresh handling improved | Refreshing the browser after receiving unauthorized access errors resulted in 403 Forbidden errors instead of proper error messages. This has been resolved by updating the dynamic container loading logic to handle unauthorized refresh scenarios properly. | User Experience |
| INC-C26510 | 937163 | Window name display documentation updated | The documentation for available UI actions has been updated to clarify that the windowName parameter is not used as the title of the window or the name displayed on the tab. Instead, it acts as a target identifier and is an internal name used to identify and potentially reuse the same window or tab. If a window or tab with that name already exists (and was opened by a script), the browser will reuse that window instead of opening a new one. The actual title displayed on the tab comes from the title tag of the loading page defined by the server response, and not from the window.name. | User Experience |
| INC-C26682 | 938939 | Case theming made available for coexistence | Previously, a case type created using Constellation architecture in the Cosmos application was rendered in the Constellation authoring styles and there was no option to inherit the Cosmos built-on application branding. With this update, support has been added to create and apply a specific theme for the Constellation cases when rendered inside the traditional UI, allowing the Constellation UI to render with customer branding and align with traditional portal styles. | User Experience |
| INC-C26736 | 937880 | Corrected scrollbar focus management | The scrollbar was not automatically returning to the top of the page after form submission, causing users to remain at their current scroll position instead of being repositioned to view the top of the updated content. This has been resolved with an update to ensure the assignment heading receives focus and the page scrolls to the top of the form when moving between steps. | User Experience |
| INC-C26776 INC-C26775 |
940138 942303 |
Corrected pxSessionTimer popup handling | The pxSessionTimer popup was closing unexpectedly when focus moved away from it, and the close ("X") button was not displaying when modal dialogs were already open. This has been resolved by updating the handling of overlay interactions and focus management in the session timer popup component. | User Experience |
| INC-C27085 | 939089 | Ellipsis hover shows localized field value | After update, the pzEllipsis control hover functionality was displaying raw property values instead of localized field values. This has been resolved by updating the localization logic in the hover display mechanism to add a "pyAddTitleForEllipse" condition set to true by default which will restore the title attribute to display localized field values in hover text. | User Experience |
| INC-C27329 | 936117 | ViewEditing / MetadataTranslator logic updated for section saves | When saving the pyCaseMainInner section, the error "Exception creating / saving View rule into the DB" was generated during the pzGenerateView activity. This has been resolved by updating the view rule generation for UI-Kit based applications during section saves to skip non-autogen / non-design templated sections. | User Experience |
| INC-C27931 | 941032 | Corrected premature validation error messages | Error banners were appearing during field changes when using the Pega_Extensions_ActionableButton component in local actions, rather than only appearing on submit as expected. This was traced to the incorrect validation timing, and has been corrected. | User Experience |
| INC-C28719 | 953261 | Session timer dialog accessibility improved for screen readers | The session timer dialog was not being properly identified by NVDA screen reader software, reading as a normal dialog instead of a timer dialog. This has been resolved by adding the necessary accessible name attributes. | User Experience |
| INC-C28836 | 940613 | Modal close button accessibility behavior corrected | Modal dialog close buttons were unexpectedly activating on mouse down instead of mouse up when using pzModalTemplate, though it did not occur with the close icon in pyFlexModalTemplate.pzModalTemplate. The event handling inpzModalTemplate has been updated to correct this issue. | User Experience |
| INC-C28840 | 939407 | Updated logic to match labels for assignment instructions | Assignment instructions (pyInstructions) were not displaying in Theme-Cosmos when the Assignment flow label and Flow Action label did not exactly match. This was due to overly strict label matching logic, and has been resolved by updating the condition for displaying instructions. | User Experience |
| INC-C28918 | 954874 | Case locking notifications restored | Case locked messages failed to display to end users after system updates. This was caused by error handling that prevented message display when errors occurred before assignment opening, and has been corrected so the message appears as expected. | User Experience |
| INC-C2894 | 917474 | Validation errors correctly displayed in delegated tables | Validation error messages were not displaying in delegated data tables as expected. This was traced to the report definition flushing the error message on the result page, and has been resolved with an update to the error handling to ensure validation error messages are properly displayed for delegated table interfaces. | User Experience |
| INC-C29242 | 939231 | Improved localization for table components | The "Add" button in SimpleTable components and the Edit and Delete action labels in table components were not being correctly localized. This has been corrected. | User Experience |
| INC-C30656 | 947595 | Image upload controls properly enforced in Rich Text Editor | The Rich Text Editor was accepting drag-and-drop image uploads even when the image upload option was explicitly disabled in the toolbar configuration. This has been corrected. | User Experience |
| INC-C30672 | 943065 | Localization consistency improved for UI elements | Default UI elements including Yes/No field values and Next/Previous buttons were not correctly localized due to trailing spaces in button names and missing translation mappings for specific UI components. This has been corrected. | User Experience |
| INC-C30714 | 943798 | Added question mark handling for multiselect | Multiselect controls were throwing JavaScript errors when users entered a question mark as the first character, causing all page actions to hang. This was due to the character was not being properly escaped in the multiselect control's regex pattern, and has been corrected. | User Experience |
| INC-C30858 | 948250 | Combo box accessibility enhanced for keyboard navigation | Clear icons in autocomplete combo boxes were not accessible to keyboard users or screen readers. This has been resolved by adding proper keydown event handling and accessibility attributes. | User Experience |
| INC-C31047 | 943894 | Optimized grid focus retention fixed | After closing modal dialogs launched from optimized grid rows, the focus indicator was not returning to the originating row. This has been resolved by updating the handling for the display border on the focused grid cell when modal is launched and closed from that cell. | User Experience |
| INC-C31089 | 942793 | Security improved for preview activity | Cross-site scripting filters have been updated for the selectivePreview activity. | User Experience |
| INC-C31140 | 943038 | Corrected error highlighting for calendar input | Property labels were incorrectly displaying in red (error state) after correct values were entered in calendar input fields with validation. Investigation showed the error message class was not being properly removed when the data-value matched the updated value after navigation from table configuration flows, and this has been resolved with an update which will remove the labelError class on the label when values are corrected. | User Experience |
| INC-C31159 | 943152 | Rich Text Editor dirty state detection improved in modals | Modal dialogs closed without displaying unsaved changes warnings when Rich Text Editor fields were modified and focus remained in the editor. Investigation showed this was caused by the dirty state detection not triggering immediately upon content changes in the editor. This has been resolved by improving the focus and change event handling for Rich Text Editors in modal contexts to ensure a dirty event is fired on change. | User Experience |
| INC-C31252 | 948857 | Pulse notes loading extended | Pulse sections in blended applications were limiting display to only 10 posts when Constellation cases were launched from UI Kit portals. Investigation showed pagination was not functioning correctly in the blended UI environment, and this has been resolved. | User Experience |
| INC-C31852 | 944145 | Channel menu navigation displays correctly | Channel configuration menus failed to display submenu options when hovering over outbound Email or SMS options. Investigation showed an indexOf function was being called on a non-string value, and this has been resolved by adding a check for string in the control menu javascript. | User Experience |
| INC-C31931 | 951275 | Updated class handling for embedded properties | SECU0001 security errors occurred when nested data reference objects were used in views with multiple keys. Investigation showed property information retrieval was limited to work class context, missing nested object properties. This has been resolved with an update to ensure the embedded properties resolve to the correct class to retrieve any further parameters when given a page. For the scalar properties, the flow remains the same. | User Experience |
| INC-C32058 | 947171 | Tooltip sizing corrected in modal | Tooltips expanded to excessive size on first interaction with case lifecycle stage elements. Investigation showed the Reveal with Animation feature on embedded sections was causing tooltip rendering issues. This has been resolved removing the animation checkbox in the local action for modal. | User Experience |
| INC-C32635 | 943004 | Case summary follow button focus behavior corrected | When clicking the star icon to follow or unfollow cases in the case summary header, keyboard focus was being lost, requiring users to press tab again to regain focus indication on the button. This has been resolved by updating the button state change event handling so focus consistently remains on the button when activated. The screen reader announcement also reflects the label changing upon follow/unfollow. | User Experience |
| INC-C32722 | 943107 | Case summary panel has accessible label | After upgrade, the case summary panel expand/collapse button no longer had an accessible label, causing screen readers to announce only "button" instead of the descriptive label. This has been corrected. | User Experience |
| INC-C32864 | 945366 | Corrected layout positioning for email notifications | Email notification settings were displaying outside the dynamic layout box in the Theme Cosmos User Portal notification preferences screen. This has been corrected. | User Experience |
| INC-C33310 | 944648 | Table filter clear behavior corrected | When users clicked the "Clear Filter" option in table columns, the page automatically scrolled to the top. This was caused by an additional href="#" attribute added to the clear filter link in the pzGridFilterPanel section, and has been resolved. | User Experience |
| INC-C33387 | 943642 | Updated handling for operations on nested pageList structures | Dynamic forms were throwing "Expecting input data of type PageList" errors when performing screen flows that involved changing product names and saving. Investigation showed the system was receiving JSON data instead of the expected PageList format when processing form refresh settings with "Remove" operations on nested pageList structures during recursive traversal. This has been resolved with an update which will create a a state machine if one is not found during traversal and ensure that all nested levels of the pageList are properly handled so the associated content and page instructions are preserved and processed as expected. | User Experience |
| INC-C33676 | 946485 | Review harness heading structure updated | The "To do" heading in the Review harness was configured as an H3 element instead of H2, which is not correct for accessibility compliance. This has been resolved. | User Experience |
| INC-C33994 | 950358 | Web mashup login screen documentation updated | An article has been added to the documentation for troubleshooting mashup issues which covers that multiple tabs are not supported for mashups with anonymous authentication. The proper configuration should use only a single tab. If multiple tabs are used and each has session timer, the tab which times out first will see the expected log in screen with anonymous login, but additional tabs will display the login screen which asks for credentials. | User Experience |
| INC-C34448 | 948696 | Added check to permit some local actions on offline mobile | After upgrade, local actions were not opening on mobile harnesses in offline mobile apps. This was due to work done to block local actions outside case context, and has been addressed by adding a null-check for pyWorkPage to allow execution of some specific scenarios for some local actions. | User Experience |
| INC-C35183 | 949415 | Report table header focus accessibility corrected | Report table headers received focus but did not display visual focus indicators, creating confusion for keyboard navigation users. This has been corrected by adding the necessary focus border styling on table header elements with data-read attributes. | User Experience |
| INC-C35239 | 954150 | Corrected radio button selection issue | Radio buttons marked as mandatory were not getting selected on the first attempt when they were the first field on a form. Users had to make a second selection for the radio button to register. This has been resolved by correcting the focus and blur behavior. | User Experience |
| INC-C35485 | 952162 | Mitigation available for Notes protocol links blocked in Rich Text Editor | After upgrade, Rich Text Editor was not processing notes:// protocol links. This is due to the implementation of DOMPurifier, which restricts certain custom protocols, specifically the 'notes://' links due to security concerns. In order to support backwards compatibility, an update has been made which will support adding specific code in the UserWorkForm to permit the desired tags. This a mitigation mechanism for backward compatibility issues that might have been introduced by limiting tags. However, reintroducing the blocked tags carries the risk of creating security vulnerabilities for XSS and HTML injections. Please refer to the documentation for Security in Rich Text Editor for additional information. | User Experience |
| INC-C35808 | 950899 | Unauthorized access error messaging corrected | "Unauthorized Access" error messages were not being displayed when users attempted to perform actions without the necessary permissions. This has been resolved with an update to ensure HTTP and page messages are presented in assignments as expected. | User Experience |
| INC-C36543 | 948689 | Accessibility improved for autocomplete controls | Screen readers could not properly identify autocomplete dropdown buttons due to missing aria-hidden attributes on the autocomplete caret button. This has been corrected. | User Experience |
| INC-C36767 INC-C36932 |
949900 949875 |
Embedded data handling corrected during grid editing | Editing a grid which used embedded data resulted in incorrect results. This was traced to an issue with the refresh data transform and the merge data API, and has been resolved with an update to improve the logic and handling for mergeListChanges during mergeData and clean up page instruction when the array length is different. | User Experience |
| INC-C36982 | 960541 | Constellation tab count refresh control added | Tab counts in landing pages were not refreshing when underlying table data changed, causing user confusion as displayed counts remained stale even after bulk actions modified record quantities. This was due to the behavior of thread-level data pages: when a data page is configured to reload once per interaction, it may not always refresh as expected during complex interactions or when navigating between different views. Additionally, if the UI is not set to refresh automatically upon returning to the tabbed view, the count will remain unchanged until a manual refresh of the browser is performed. In order to address this limitation, the setting "pyAutoUpdateLandingPageTabCounts (Boolean)" has been added which will cause the TabbedPage template to refresh the tabCount when case/process events have been triggered. | User Experience |
| INC-C3740 INC-C34213 |
910717 947730 |
Picklists include associated localization rule and locale reference | Associated localization rules were missing for picklists after update. This has been corrected with an update which will pick the correct class during the upgrade rules process. This ensures the correct locale reference is generated in the view metadata configuration so the view rule's localization references and view upgrader's generated locale references will be in sync. | User Experience |
| INC-C37533 | 949812 | Button alignment corrected in consent screen | Buttons in the authorization consent screen were misaligned. This was caused by incorrect CSS centering applied to the reject button, and has been corrected. | User Experience |
| INC-C38028 | 951866 | Date picker accessibility improved for labels with apostrophes | Date picker controls were displaying incomplete alt text when labels contained apostrophes. This has been resolved with an update to encode the apostrophe symbol as HTML Hexadecimal code in the date picker template so the full alt text is present. | User Experience |
| INC-C38047 | 954097 | Timezone conflict handling updated in datetime controls | When operators had specific regional timezone settings that differed from a datetime control timezone configured through a property, the control was showing time according to the operator's timezone rather than the specified property timezone. This has been resolved by updating the handling in the calendar JavaScript rule. | User Experience |
| INC-C38112 | 955109 | Table pagination accessibility enhanced | Accessibility issues were seen with unoptimized table pagination controls. This has been resolved by adding the necessary focus elements. | User Experience |
| INC-C38186 | 953444 | Modal button accessibility announcement corrected | Screen readers incorrectly announced "collapsed" when navigating to buttons configured to launch modal dialogs or overlays. This has been resolved by adding an aria-haspopup attribute for modal/overlay. | User Experience |
| INC-C38550 | 951435 | Task manager correctly shown when service case cancelled | The Constellation task manager was disappearing from the user interface after cancelling service cases and clicking "Done". This was traced to the required key value not being passed correctly and has been resolved by modifying the finish assignment to include a confirmview check specifically for multidoc mode, ensuring the necessary key value is sent. | User Experience |
| INC-C38782 | 951463 | Corrected handling for saving views with 'disable when' | Applications were experiencing save failures when attempting to configure 'disable when' conditions on cascading dropdown fields within embedded data tables in editable mode. This was traced to an issue with the context metadata generation, and has been resolved by updating the comparison check for only valid type(String). | User Experience |
| INC-C39135 INC-C32401 |
949975 942500 |
DOMPurify updated | The DOMPurify library has been updated to the latest version. | User Experience |
| INC-C40436 | 953551 | Decimal column sorting corrected | Decimal columns in Constellation grids displayed incorrect sorting behavior when values contained similar digits before the decimal point such as 24.01, 24.03, and 24.10. This has been corrected by updating the sort.js file to correctly handle decimal values. | User Experience |
| INC-C4059 | 913344 | Localization added for text in save view dialog | When saving a custom view for a table (for example from the My Followed items widget) some text in the dialog was not being localized as expected. This has been corrected. | User Experience |
| INC-C40602 | 953433 | Nested view name length validation handling updated | Nested views could not be saved when the combined parent and child view names exceeded 64 characters due to automatic name generation. This was due to insufficient length validation during nested view name creation, and has been resolved by adding the pyLabel property to Rule-UI-View. | User Experience |
| INC-C4070 | 917765 | Data source references made consistent | Some sections referencing data pages were missing from the Index-References. Investigation showed this was due to a missing entry under pxRuleReferences for Anypicker source inside a section, and was due to the anyPicker assembly not appending the data source reference in the same way as the multiselect control. This has been corrected. | User Experience |
| INC-C40887 | 952504 | Rich Text Editor resizing constrained in multi-column layouts | Rich Text Editors in two-column layouts were expanding beyond their designated column boundaries when resized, overlapping adjacent fields and disrupting form layout. This was caused by insufficient boundary constraints in the resize functionality for scenarios with multiple Rich Text Editors, and has been resolved. | User Experience |
| INC-C41013 | 952523 | Personalized view display corrected for image columns | Image columns configured as always visible disappeared from personalized views after removing unused columns from the interface, disrupting user customizations. Investigation showed this was caused by the system incorrectly associating image columns with common property references that were affected by column removal operations. This has been resolved by improving the column reference management to maintain always-visible image columns independently of other column changes. | User Experience |
| INC-C41181 | 951966 | Accessibility updated for report table expand/collapse | Keyboard users could not see focus indicators on expand and collapse icons in report tables within dashboard charts. This has been resolved by adding tabindex attributes in the HTML rendering for expandable table elements. | User Experience |
| INC-C41281 | 951959 | Corrected case reload navigation issue | When opening a case for the first time in the Theme Cosmos DevStudio portal, performing a browser reload navigated to the home page instead of remaining on the case page. Investigation showed this occurred due to multiple portal names being created on browser refresh, and has resolved by updating the portal name handling when sessionCount is not empty. | User Experience |
| INC-C41340 | 951570 | Hijri calendar support added | A comprehensive Hijri calendar control has been added to support Islamic calendar dates. | User Experience |
| INC-C41479 | 960825 | Dynamic questionnaire UI refresh corrected | When switching picklist options in dynamic questionnaires, the next question would load on the backend but the UI would continue displaying the previous question instead of refreshing to show the new content. This has been resolved. | User Experience |
| INC-C41755 | 958750 | Refreshed blank value updated on UI | After update, cascading dropdowns on the UI which had a refresh data transform configured whenever the first picklist value changed were not being updated as expected. Investigation showed the parameters for the second autocomplete were not being rendered in the UI if the value in redux was [], and this has been corrected to ensure state synchronization between cascading dropdowns. | User Experience |
| INC-C41858 | 954552 | Modal resize handle updated with aria label | The resize handle for a modal dialog was being announced by screen readers as "clickable" without further context. This has been addressed by adding an aria-label to to the draggable button with the text "Drag to resize modal". | User Experience |
| INC-C43193 | 956066 | Japanese error message display corrected | Error messages in Japanese were displaying vertically instead of horizontally in error banners when multiple error messages appeared on screen. This was caused by CSS text orientation issues specific to Japanese character rendering in the Constellation UI, and has been resolved by updating the CSS to address banner text wrapping. | User Experience |
| INC-C4344 | 912945 | CaseNavigation correctly announced by screen reader | When initially loading a work object, the "details" panel was selected and loaded but not announced by a screen reader. This has been corrected by setting aria-current as true on the Case Navigation tab. | User Experience |
| INC-C440 | 910777 | Corrected fixed collapsed summary pane display handling | When the summary panel was collapsed, the fixed summary pane region's content overlapped with the main case region and covered the section. This was an issue with handling the browser resizing, and has been resolved by updating the handling for the top margin for a case view with collapsed summary. | User Experience |
| INC-C4464 | 917335 | Added null handling to pushimagetoc11nservice | When using a custom activity to upload an image in the operator profile and save it, the exception "Attempting to map data from property .imageContent with unsupported mode: UnknownFrom" was intermittently generated and the image was not saved. This has been resolved by adding handling for null ImageContent to pzpushimagetoc11nservice. | User Experience |
| INC-C45205 | 957533 | Scrolling in autocomplete combo box mode corrected | Autocomplete controls which were configured to display results as a list with combo box mode enabled were not showing scroll bars when more than the maximum configured results (5) were returned, and clicking the dropdown arrow was displaying all results instead of respecting the limit. This has been resolved by modifying the autocomplete control to enable scroll bars in combo box mode and properly limit results when the dropdown arrow is clicked. | User Experience |
| INC-C45450 | 957860 | 24-hour date format selection enabled for non-optimized grids | It was not possible to select 24-hour date format for calendar controls within non-optimized grids. This has been resolved by adding the necessary support to the editable date time picker controls for non-optimized grid configurations. | User Experience |
| INC-C45450 INC-C36335 |
955322 955841 |
24-hour date format added for localized calendar controls | Support has been added for a 24-hour date format in the editable date time picker controls when using localization. | User Experience |
| INC-C45593 | 960602 | Screen reader accessibility improved for audit attachments | Screen readers were announcing and focusing on a hidden attachment data frame in the audit tab, causing confusion during navigation. This has been resolved by adding aria-hidden='true' and tabindex='-1' attributes to hide the frame from screen readers so that the iframe label and contents are not announced by screen reader when navigating case history dialog. | User Experience |
| INC-C45733 | 959523 | Modal dialog error message properly cleared | Error messages in flows running within modal dialogs were persisting even after screen refresh and control value changes. This has been resolved by ensuring error messages are properly cleared when control values change or screens refresh within modal dialog flows. | User Experience |
| INC-C46266 INC-C19472 |
956301 929916 |
Session timer popup duplication prevented | Multiple session timer warning popups appeared simultaneously when session timeout approached. Users received duplicate or multiple logout warning messages instead of a single notification. This was caused by improper session timer event handling in the user interface. This has been resolved by correcting the session timer popup management to prevent duplicate warnings. | User Experience |
| INC-C4721 | 917224 | Blended UI loading message localized | The message "Loading content" was not localized in Constellation Blended UI. This has been corrected. | User Experience |
| INC-C47263 | 958709 | Helper text focus corrected | Focus was not working for the helper text if there there was a space or line break in the field value for "Help icon with overlay on focus". This has been resolved by adding a check for overlay on focus helper text. | User Experience |
| INC-C4733 | 920127 | Cases and Data from "Explore data" dropdown menu localized | Localization support has been added for class labels and field labels in the Explore Data section of the user portal and to the values in a picklist type of field backed by local source in a table. | User Experience |
| INC-C4733 | 917255 | Explore Data menu items localized | Case Types and Data Object Names were not being localized in the Constellation Explore Data menu. This has been corrected. | User Experience |
| INC-C47590 | 960217 | Skin rule preview functionality restored | After update, preview panels were displaying blank content when opening skin rules. This was traced to the cross-site scripting filters which passed the converted ascii value for the parenthesis and blocked the Preview from loading, and has been resolved by replacing this ascii value with parenthesis in the pzSelectivePreview activity. | User Experience |
| INC-C4770 | 913350 | Table focus navigation improved | Non-optimized tables with inline editing experienced focus issues where users could not tab back into the table after editing a row and moving away. This has been resolved with an update to ensure correct focus on the table row when "Click row to edit" is enabled. | User Experience |
| INC-C48945 | 958225 | Bulk action record limit error addressed | Bulk actions were failing with "Narrow the query to 5000 records" error messages even when selecting fewer than 250 records from datasets containing more than 5000 total records. This has been resolved by refreshing the list view after bulk action execution. | User Experience |
| INC-C50741 | 961538 | DX API payload handling corrected after upgrade | After upgrading from Pega 8.7 to Infinity 24.1, multi-select dropdown values in DX-API assignment/action/refresh calls were showing index values replaced with characters in the payload. This has been resolved. | User Experience |
| INC-C50833 | 960782 | Datatype edit view enabled | Previously, the pyEdit view could not be created directly in the Views tab for datatypes in Cosmos theme Constellation landing pages. With this update, pyEdit has been added to the Section rule in Data- so that it can be overridden into a data type's class and edited for List page table column editing purposes. | User Experience |
| INC-C5115 | 917531 | Updated required asterisk handling for multiple required field conditions | The asterisk (*) next to a field indicates that the field is marked as 'Required' in the system. However, the asterisk was also visible in cases where a 'Required When' condition was applied whether or not the 'Required When' evaluated to true for the field, causing it to be visible due to the global 'Required' setting even if the requirement was false. To address this, the handling for the asterisk has been updated to be visible on the column header only when all the cells are required. Additional work to refine this handling is planned for a future release. | User Experience |
| INC-C51191 | 960673 | 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-C5817 | 927181 | Insight Checkboxes localized | Localization support has been added for Checkbox in Insights. | User Experience |
| INC-C6049 | 926305 | Security field mapping for embedded properties fixed | The security fields map was not populated with data reference fields from embedded properties when no records were present. This has been resolved by adding dataRef multiselect properties to the security fields map. | User Experience |
| INC-C6804 | 918916 | Corrected Constellation blended UI assignment refresh | An assignment opened in a hybrid application was not refreshed as expected. This has been resolved by updating the handling for publishing the websocket message in the blended UI. | User Experience |
| INC-C6921 INC-C22775 INC-C15030 |
914109 933699 928402 |
Corrected container context and handling for blended UI | Previous case data was reflected on opening a new case that was created in a hybrid application, and some tabs and tables were not loading in interaction portal. Views/fields which had a visibility 'when' condition on them were not showing even if the condition was satisfied, and bulk actions were not working as expected. These issues have been resolved by updating the container item loading and handling for blended UI. | User Experience |
| INC-C7227 | 912822 | Cases and Data from "Explore data" dropdown menu localized | Localization support has been added for class labels and field labels in the Explore Data section of the user portal and to the values in a picklist type of field backed by local source in a table. | User Experience |
| INC-C7456 INC-C13418 |
917959 922644 |
Corrected special characters shown as ASCII in filter | After configuring an optimized table sourced with a data page and adding column data with special characters such as "Begun#$%&* Asiya()*23", the values were being converted to ASCII values in the filter. This was due to the system returning the encoded cross script filtered string, and has been resolved by restoring the string back to the original to show special characters as well, and reapplying the cross-scripting at a later point. | User Experience |
| INC-C8551 | 917577 | Localization added for multiselect keyboard instructions | The instructional text for keyboard on multi-select controls contained hardcoded non-localized text that was picked up by the screen reader. To improve accessibility, field values have been created for for the following texts: "Arrow down to open. Start typing to search" "Suggestions are available. Use up and down arrows to select" "Reached the end of the list" "Reached the beginning of the list" |
User Experience |
| INC-C8612 | 917568 | Localization support added for filter comparator options | When using a list view with a column filter, the condition operator select field dropdown options were not localized. This has been resolved by introducing new translation keys in the pyGenericFields localization rule. To implement this change, language packs must be regenerated to contain the newly created entries. | User Experience |
| INC-C9110 | 916053 | Create Case focus highlight added | The UI Kit Create Case button was missing a visible focus indicator. This has been resolved by updating the CSS for greater accessibility. | User Experience |
| INC-C9119 | 921956 | Multi-tab session management synchronized | Session timeout warnings appeared inconsistently across multiple browser tabs, and logging out from one tab affected active sessions in other tabs. This was caused by inadequate session state synchronization between browser tabs, and has been resolved. | User Experience |
| INC-C9199 | 928547 | Updated token handling for SSO session termination | SSO session termination was not functioning properly in certain mashup scenarios and spinning progress indicators did not resolve. Investigation showed the authentication logic which relied on checking the global PCore object to determine bootstrap completion status was not able to reliably track dynamically manipulated embed elements. This has been resolved with an update to use instance-specific flags instead of global PCore checks to properly track bootstrap completion and handle re-authentication scenarios. | User Experience |
| INC-C9263 | 927751 | Corrected empty Phone Number field defaulting to mandatory | After starting to enter a phone number and then erasing it, a validation error occurred on submit. This was traced to the Country Code being initiated but not getting cleared, and has been resolved with an update which will clear the Country Code if the Phone Number is removed. | User Experience |
| INC-C9516 | 919553 | Accessibility list structure corrected | Applications were displaying incorrect list structures for case ID text elements, affecting screen reader accessibility. This has been resolved by correcting the list structure generation MetaList configuration in the accessibility framework to ensure proper accessibility. | User Experience |