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
23.1.5 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B13456 | 868991 | Parent case correctly updated when child case is resolved | When using a parent-child relationship case type where the parent has a dependency on the child case being resolved, in some scenarios the parent case was not getting updated with the expected Withdrawn status if an alternate stage was followed. This has been resolved by introducing logic to explicitly update DependentPage when the object to update is a parent. | Case Management |
| INC-B20720 | 889325 | 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-B27412 | 902407 | Updated logic for archival case ID | After the Case Archival process was completed, some of the archived cases still appeared in the global search even though the Archival search filter was not included. Investigation showed live cases were not removed from indexes due to missing letter-case matches caused by the pyID being derived from the pzInsKey. This was a missed use case, and has been resolved by updating the logic to send the exact value of pyID by getting it from the respective tables so live cases will be deleted from indexes. | Case Management |
| INC-B29899 | 882472 | "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 | 890264 | 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-B33540 | 886935 | 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 | 927902 | 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-B41088 INC-B38253 |
892401 889771 |
Lock released on case with optimistic lock when error occurs | The lock was not released when an exception occurred during case processing in Constellation on a case using optimistic locking . This has been resolved by adding logic in the pzPerformActionErrorHandle activity and the pzJumpToStep activity to check if the case locking is optimistic and release the lock on the case if an exception is encountered. | Case Management |
| INC-B42463 | 895502 | Constellation preprocessing documentation updated | The documentation for Constellation has been updated to clarify that preprocessing is run on submit and refresh of assignment and case actions. | Case Management |
| INC-B43058 | 911702 | 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-B44082 | 902554 | Updated error message display handling | When dictionary validation failures occurred during navigation attempts it was not possible to navigate back from forms and no validation error messages were seen. This was due to HTTP 400 responses being received with multiple error messages, and has been resolved by adding handling for displaying multiple error messages with a single code in the Constellation UI framework. | Case Management |
| INC-B44819 | 901217 | 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-B46243 | 908989 | Corrected stack overflow for archive process | The archival process was failing with a StackOverflow error when executed in pipeline mode. This has been resolved by updating caseHierarchy.toString() . | Case Management |
| INC-B49246 | 902496 | Corrected attachment class handling after cancelled delete | After attaching a document, previewing it, and clicking delete from the 3 dots menu, clicking the cancel button to stop the deletion resulted in the attachment being removed from the Link-Attachment class and it was not able to be previewed again. This was a missed use case and has been corrected by adding a wrapper activity to prevent deleting the Link-attachment instances on cancel or close actions. | Case Management |
| INC-B51419 | 903736 | Usage and documentation updated for pyBulkProcessing operator ID | The documentation for bulk processing has been updated to clarify proper steps for "Troubleshooting errors with Assignments stuck with pxAssignedOperatorID=pyBulkProcessing". This covers the needed information to avoid or correct a scenario where cases became stuck because an agent or node went down and assignments were moved to the Assign-Worklist of the pyBulkProcessing operator ID but the pyBulkProcessing operator profile was not valid. The usage section of the rule BULKPROCESSINGID has also been updated with more detail, and reads "During bulk processing exceptions, Cases will be routed to the operator specified in this Application Setting. Save this setting to the current application Ruleset and update the value with the operator ID to which Cases should be routed. Ensure no other operator or Work Queue in the system uses this ID." | Case Management |
| INC-B52085 | 916074 | 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-B52231 | 904263 | Accessibility added to application icons | The application logos/icons used in the pzDeferLoadApplicationLogo control were missing the alternative text for accessibility. This has been resolved by adding the alt attribute with appName for the logo image. | Case Management |
| INC-B53300 | 908819 | Corrected Cancel button label for better accessibility | The Cancel button n the attach content pop up had extra information when it received focus, speaking "cancel button Click here to cancel work". This was a missed use case, and has been resolved by updating the pyMessageLabel Cancel field value to announce "Cancel". | Case Management |
| INC-C12121 | 920034 | 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-C14218 | 930232 | 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-C15065 | 923213 | 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-C16631 | 923352 | 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 | 924449 | 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-C20468 | 927703 | DSS added for RecalculateAndSave backwards compatibility | After update, a service call which updated the parent case and created a child case was generating the error "ORA-00001 Unique Constraint". Investigation traced this to the child case creation method being customized to use obj-save with write now, which was not working with recent changes to the RecalculateAndSave activity to add insert queries. To support this customization, the DSS SkipInsertQueryUponCaseCreation has been added to skip the add insert logic and restore the previous functionality of merge/update. | Case Management |
| INC-C20644 INC-C33988 |
944753 946023 |
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-C22363 INC-C33988 |
929771 945751 |
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-C24316 | 946697 | 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 | 917957 | 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-C3734 | 919104 | 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-C3802 | 913337 | 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-C4509 | 915944 | 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-C5329 | 913329 | Popup appears for empty required field submission | Given a screenflow with a required input in Theme-Cosmos, clicking Submit without entering any value triggered field validation but the expected dirty popup indicating "Please correct flagged fields before submitting the form!" did not appear. This has been corrected. | Case Management |
| INC-C6160 | 913787 | 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-C9640 | 915851 | 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 | 947833 | 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 23.1.5 Resolved Issues for Cloud Services
Conversational Channels
23.1.5 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B46032 | 900064 | CreatePostAndWorkPartyFromEmail log level changed | The log level in pzCreatePostAndWorkPartyFromEmail has been updated from "LogInfoForced" to "Error" to prevent potentially capturing sensitive data. | Conversational Channels |
| INC-B46226 | 900928 | Logging added for operator presence issues | An intermittent issue was seen where all customers waiting in chat queues were suddenly removed. Due to the volume of requestors and interactions on the environment, targeted logging has been added to avoid impact on system performance. The setting OPERATORS_TODEBUG uses operator IDs to track the activity of few selected CSRs to facilitate debugging operator presence issues. | Conversational Channels |
| INC-B49985 | 904760 | Added null check to TreatIncomingText | When a plain text format email contained special characters, the pyTreatIncomingText activity in the email listener was generating a null pointer exception. This has been resolved by adding a check. | Conversational Channels |
| INC-B50303 | 901672 | Updated handling for very large inbox in Constellation | The UI component of the Constellation Email Manager Portal was failing to load the next set of cases after the first 150 items. This was seen due to the progressive loading of a very large inbox (over 2.6k in this scenario) using continuous scrolling which was repeatedly invoking the loadMore method and calling the API with the same loadedEmailCount twice. This has been resolved with an update to handle this usecase. | Conversational Channels |
| INC-C1208 | 912060 | Email case load optimization | When there were a lot of email cases in in-flight mode and if all emails in that case are pre-loaded in one single request (on screen load), a requestor lock exception occurred that caused the requestor pool to be exhausted. This has been resolved with an update to use deferred load of emails on demand so that emails that are not seen on screen are not loaded on clipboard. | Conversational Channels |
Data Integration
23.1.5 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B10618 | 904621 | Logging added to diagnose insights issue | Additional logging has been added to DictionaryCacheImpl.java to assist with diagnosing issues with imported insights intermittently not loading in the portal page. | Data Integration |
| INC-B27282 | 881113 | 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-B29170 | 903049 | Corrected parent keyword resolution error | While adding DDS as destination to a data flow, the error "Please consult your system administrator" was generated. Investigation showed the "Parent" keyword for HiddenInput was not correctly resolved to the parent reference which caused a field security issue. This has been corrected by updating HiddenAssembly.java to resolve the "Parent" keyword to the proper reference. | Data Integration |
| INC-B29673 | 903830 | Debugging logging added for Tomcat servers | Enhanced logging has been added to assist with diagnosing issues with the Tomcat server shutdown. | Data Integration |
| INC-B30143 INC-B11802 |
886847 887678 |
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-B32976 | 901927 | Corrected file extension for Smart Dispute | When using the Pega Smart Dispute Framework Application, the .pdf extension was missing for the generated PDF file, causing the CreateCB service invocation to fail. This has been corrected. | Data Integration |
| INC-B34410 | 899782 | DSS added to use lower TLS protocol for MSGraph | After upgrading from Pega 6 to Pega 8, sending email attachments larger than 3MB using the Microsoft Graph API was not working and the error "Blocked by tenant configured AppOnly AccessPolicy settings" was logged from from SENDEMAILNOTIFICATION. In Pega 8, an enhancement was introduced to use proxy configuration for MSGraph which included integrating trustStore and keyStore details into the HTTP client. By default the native protocol settings are used, which in this case was expected to be TLS 1.3. However, since outlook.office365.com does not support TLS 1.3, this error occurred. To support this use, the DSS "getSupportedLowestTLSVersion" has been added to fetch a lower supporting protocol and configure the same value in the HTTP client. | Data Integration |
| INC-B35087 | 903367 | closeIdleConnections() tuned | Slow response was seen for Rule-Connect- SOAP/REST service calls, and application performance was impacted. Investigation showed there was a HTTP network close handshake delay causing unused SOAP connectors to not be promptly closed. To address this, the connection pool cleanup code to has been moved to the queue processor. | Data Integration |
| INC-B35227 | 934868 | 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-B36659 | 889409 | Added handling for numerical filename in eForm upload | After upgrade, uploading a file with the eForm rule was generating an error if the file name began with a number. This was traced to a clipboard page creation limitation, and has been resolved with an update which will add a prefix to the page name for the createPage function. | Data Integration |
| INC-B41381 | 901656 | Changed logging level for missing meta data | The error "Page D_GetReceiveFileTargetFilesList in Thread TABTHREAD1 in Requestor is missing meta data. Skipping this page for passivation" was repeatedly generated and filling up logs. Investigation traced this to a custom D_GetReceiveFileTargetFilesList data page which did not contain the expected meta data. Missing meta data does not have any functional impact and there will be no loss of business logic. To prevent the excess logging, this has been addressed by downgrading the log level from error to warn. | Data Integration |
| INC-B46095 | 901427 | Added stagingloc support for DataManifest listener pzuploaddataactivity | The DataManifest listener pzuploaddataactivity was not working as expected. This has been addressed by adding repository API support for a staging location. | Data Integration |
| INC-B46174 | 896069 | Ondemand Passivation remote node timeout duration made configurable | Users of Pega Call were being unexpectedly logged out or had clipboard page issues. This was traced to websocket timeouts related to passivation as well as network, VPN, and other types of connection breakage from server to client. To address this, the Ondemand Passivation remote node timeout duration has been made configurable to allow more tolerance for connection interruptions. SettingName: ondemandpassivation/timeout/duration/seconds Description: specifies the maximum time, dynamically fetched from prconfig settings, for a remote task (Ondemand passivation) to complete before timing out. Only supports prconfig. Minimum value allowed is 10. DefaultValue: 10 RecommendedRange: 10 |
Data Integration |
| INC-B46704 | 900444 | SearchTerm value correctly reset for delegated data type | After making a data type delegated and displaying the delegated table in the user Portal under configuration, searching for a value in the table records showed the filtered records. However, after a refresh was performed the filtered values were reset to their normal state but the value entered in the search box still appeared instead of being reset to empty. This was traced to the input value of the search field not being properly reset at the clipboard even after refresh, and has been resolved with an update to explicitly flush clipboardpage. | Data Integration |
| INC-B49232 | 922476 | 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-B50652 | 914360 | Corrected validations for UploadCSVResults flow action | Validations were inconsistent when using pxUploadCSVResults flow action to upload files. If an invalid filetype (other than csv) was uploaded, clicking submit displayed a success screen. Clicking submit without uploading any file generated a runtime exception error on the screen. This was traced to missing validation on the pxUploadCSVResults flowaction, and has been resolved. | Data Integration |
| INC-B50929 INC-B51325 |
901095 903471 |
DSS added to modify rule resolution handling for Customer Decision Hub | Proposition rules were sometimes missed during rule resolution. This was traced to an inconsistency in the rule cache: the rule cache is dependent on the system pulse for invalidation, and if any rule is created after the cache initialization and the system pulse is missed or the rule is created before the system pulse module is loaded, then the cache is not updated and there is a "hitnotfound" error for the rule during resolution. According to the default logic, if a proposition rule is not found from the cache, a new rule is created. This may potentially cause issues if the intended rule has already been created but isn’t present in the cache due to the race condition. To resolve this, a DSS has been added to specify the behavior when this error is encountered. Setting CACHE_RRALIAS_SKIPHITNOTFOUND_ENABLE to true will result in the change that if a specified rule is not present in the cache, the system will search the database and add the entry into the cache. The default condition is false. Enhanced logging has also been added for the rule not found error which will print the request data and database query in order to better diagnose underlying issues. | Data Integration |
| INC-B51773 | 914644 | 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-B52975 | 906041 | Attachment Migration wizard updated for backwards compatibility | While upgrading from Pega 7, cases with attachments were migrated to Pega Cloud and stored in the database. When the Attachment Migration wizard was run to move the files to the repository, the file names included the Service Export full path and the extension was missing. This was due to the attachment name handling difference, and has been addressed by adding logic to handle attachment names when upgrading from Pega 7 versions by extracting the name from the full path. | Data Integration |
| INC-B53303 | 913470 | Corrected secBaseRef calculation | Opening any case from Worklist/Get Next next work and performing an onChange-> Post Value action for any field resulted in a "Rule not found" exception. This was due to the parent context being loaded instead of the clipboard page/current page context and was traced to secBaseRef being calculated incorrectly in the doc_domutils.js file. This has been resolved by adding a set- and reset-context wrapper around the calculation. | Data Integration |
| INC-C13830 | 918553 | 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-C21278 | 948885 | 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-C2192 | 910647 | PreActivity security improved | Cross-site scripting protections have been updated for PreActivity. | Data Integration |
| INC-C22889 INC-C13308 |
930085 928047 |
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-C22902 | 942797 | 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-C27762 | 942778 | 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 | 938673 | 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-C28599 | 940493 | 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-C30214 | 948439 | 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-C3256 | 913445 | 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-C34868 | 946519 | 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-C35034 | 948441 | 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-C4043 | 926890 | 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-C4650 | 918072 | 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 | 914546 | 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-C5094 | 917594 | 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-C5307 INC-B38572 |
911394 888500 |
Handling added for DateTime transform error | After update, the date was changed by one day while mapping a property of the type Date (in connectREST) into a DateTime. This was traced to the DateTime losing a day during the JSON transform and has been corrected. | Data Integration |
| INC-C5761 | 917443 | 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-C9840 | 928014 | 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 | 919636 | 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 |
| 921063 | 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 |
Decision Management
23.1.5 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B34347 | 893861 | Added configurable VBD dataset system tools | Data migration was failing with a heap space exception encountered during ADMFactory export when running the pipeline during VBD Actuals export. This has been addressed with several updates which will perform an internal retry when the bucket is busy during BrowseOperation of the VBD Dataset to isolate the DataFlow retry and any potential DataFlow failure, enable HTTP response compression, and Introduce a new behavior for VDB dataset partitioning which will create a partition for a day to reduce memory consumption. Enhanced diagnostic logging has also been added. 1. DSS short description: VBD Response compression Enable HTTP response compression if configured. Owning Ruleset: Pega-DecisionEngine Setting Purpose: vbd/restServerCompressionEnabled Value: true 2. DSS short description: VBD Dataset browse partition size Owning Ruleset: Pega-DecisionEngine Setting Purpose: vbd/dataSetBrowsePartitionSize Value: 1 (day) Configuration is applicable to VBDDatasets with HOUR, DAY granularity. Configuration is not applicable to VBDDatasets with WEEK granularity. 3. DSS short description: VBD Diagnostics logs Log response when longer than threshold; Log process time when longer than threshold; Log pending tasks if above threshold. Create scheduled task. Owning Ruleset: Pega-DecisionEngine Setting Purpose: vbd/restServerPendingTasksLogInterval Value: 60 |
Decision Management |
| INC-B38638 | 894450 | SkipCreatePost parameter made available | In order to support a configuration that skips adding the Pulse attachments on email cases, the SkipCreatePost parameter has made available and has been modified from Boolean to be "True or False" in both the CreateWorkFromMail and pyCreateAndManageWorkFromEmail activities. | Decision Management |
| INC-B42760 | 911249 | Updated GOS_BehavioralLimits strategy invalidation handling | The Contact Policies (CP) were not functioning correctly, sending offers which should have been blocked by the CP after the required number of impressions had been received. This was traced to the contact policies being updated from a lower environment via a RAP file, which did not apply to the GOS_BehavioralLimits strategy. As a result, the old strategy was used, causing the issue. To resolve this, the invalidation logic for the GOS_BehavioralLimits strategy has been updated. | Decision Management |
| INC-B44694 | 902469 | Data flow picks up DefaultWorkingSet properties | When responses associated with Real-Time Containers were captured, the interaction history records were missing certain properties utilized by downstream functionality if the "Output properties" option was set to "Output selected properties". This has been resolved with an update to the data flow handling to pick up properties added to the pyDefaultWorkingSet data transform before starting any strategy component in the data flow. | Decision Management |
| INC-B45373 | 901043 | Improved revision compilation and invalidation logic for Globally Optimized Strategies | When working on a large system with many nodes, several new actions and proposition filter changes were not applied correctly. This was traced to a time window between a Globally Optimized Strategy (GOS) revision compilation finish and the time the revision is committed to the database. Rule changes coming in during this window that should have invalidated the current revision were ignored, creating a race condition. This has been addressed with an update to address revision invalidation in cases where incoming rule changes occur between the time the new revision has been compiled and the revision is committed to the database. | Decision Management |
| INC-B46388 | 900053 | CSV file attachment corrected for Simulations | After creating a decision funnel simulation, attempting to attach the TopLevelView report as CSV was not working. This was traced to Param.CSVProperties in the pzAttachSimReportAsCSV activity appending a property with a "."(dot) , and then another dot was added when it was passed in the pxConvertResultsToCSV activity. This has been corrected. | Decision Management |
| INC-B47916 | 904941 | Added handling for null pointer during data flow shutdown | If an Adaptive Decision Manager (ADM) Single Case run was processing records while an associated service such as a RealTime data flow was stopped, a NullPointerException was thrown which stopped the RealTime service from being terminated and a STOPPING_FAILED error was generated. This was a missed use-case, and has been resolved by updating the data flow to guard against throwing a null pointer error when stopping a data flow service that has a single case run processing records. | Decision Management |
| INC-B51050 | 903697 | Troubleshooting Kafka Data Sets documentation updated | The documentation for Troubleshooting Kafka Data Sets has been updated with information on resolving the "RecordTooLargeException" error by modifying the broker configuration to increase the limit for the message size. | Decision Management |
| INC-B52939 | 906138 | 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-C10530 | 924799 | 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-C10530 | 941530 | 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-C10538 INC-C6360 INC-C3806 |
915683 | Added handling for class loader race condition | A class loader race condition was causing a data flow failure during shutdown with a "NoNodeAvailableException" error. This has been resolved with an update to ensure the system waits for created data flow threads to complete before shutting down a node. Additional handling has been added to prevent s null pointer during shutdown when single case calls are active and corrects potentional missed records during slow stop behavior of the data flow. | Decision Management |
| INC-C10585 | 946297 | 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-C10841 | 922035 | Updated bulk load handling for very large data sets | During a bulk load operation, it was possible for the number of elements in the set to surpass the 10k limit on distinct dimension values with the result of records being saved with missing properties and missing data in tools like Action Performance. The limit was intended to be imposed on a per-partition basis, but in this scenario caching of the streaming ingestion implementation caused the limit to be reached on a per-collection basis instead. This has been resolved by allowing bigger dictionaries for stream aggregation and cleaning them up for each flush window. | Decision Management |
| INC-C1190 INC-C26994 |
919866 939873 |
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-C15147 | 933142 | 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 | 922505 | 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-C1617 | 912478 | 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-C16295 | 921246 | Apache Parquet library updated | The Apache parquet-avro library has been updated to the latest version. | Decision Management |
| INC-C17156 INC-C5448 INC-C10984 |
924540 920581 923097 |
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-C20885 | 927609 | 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-C22863 | 945933 | 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-C2338 | 909571 | Batch node scaling startup services handling modified | After update, exceptions were being generated during node scaling which affected outbound campaign execution. Investigation showed that when a batch node started up it immediately started processing records and established a session to Cassandra before formally initializing DDS Service. After DDS Service was initialized, it acted as if the Cassandra configuration had changed and tried to restart the session, causing errors during the batch run. To resolve this, an update has been made to ensure the DDS SDK only establishes a Cassandra session after DDS service is fully up, and handling has been added to avoid unnecessary Cassandra session restart. | Decision Management |
| INC-C26403 | 942530 | Kafka Avro Schema storage format updated | Attempting to verify the Invitation ID read from Kafka with the invitation ID stored on a case as a check whether to continue case processing was not working. This was traced to the data stored as bytes in Kafka being interpreted as text format by Pega, preventing a match. To support this use case, an update has been made to store Avro Bytes as a base64 string with [ENC:BASE64] prefix. | Decision Management |
| INC-C27000 | 945590 | 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-C31093 | 943210 | 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-C3268 | 925811 | 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-C35621 | 949439 | 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 | 947884 | 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-C3635 | 909629 | Resolved startup issues with embedded stream nodes | When using the DelayedItemsDataFlowService dataflow, the error "Stream service is not initialized" was generated for scheduled items even though the stream landing page showed nodes in NORMAL status. This has been corrected. | Decision Management |
| INC-C3948 | 918566 | 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-C4301 INC-C5795 |
913947 913708 |
Check added to purgedecisondata to skip unrelated files in the repository | Many clipboard.InvalidValueException error messages were being generated indicating "T GMT is not a valid date/time value". The reported error is originated from pzpurgedecisondata activity, and was traced to a file titled as ".directory" in the Customer Decision Hub (CDH) repository which could not be parsed. This has been resolved by adding a 'when' condition to the date check which will skip metadata and folders starting with ".". | Decision Management |
| INC-C4319 | 913185 | Visual Business Director (VBD) diagnostic and error handling improvements | The following updates have been made to enhance the Visual Business Director (VBD) Data Set operations' reliability, logging, and error handling: - Fallback and Retry logic has been integrated into the PartitioningFeature of the VBD Data Set, with the retry logic accounting for elapsed time. The system will revert to the initial state if nodes are empty during VBD client node resolution before or after an HTTP call. - Detailed logging has been implemented at the TRACE level for ServerVBDServiceController, and the exception and log messages have been refined for clarity. Logging for getCollectionConfiguration is performed on both the client and server sides. - Futures that have timed out will be cancelled. The processThresholdTimeout has been decreased, and executor snapshots and log details will be included for TimeoutException. Monitoring has been added for the rtdg-rest-executor. |
Decision Management |
| INC-C4868 | 920639 | 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 | 930129 | 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-C6292 | 913757 | Updated error handling for Customer Profile Viewer (CPV) | The "Explain propensity" function in the Customer Profile Viewer (CPV) was only showing one predictor while the underlying Adaptive Gradient boosting (AGB) model had many more active predictors. This was traced to missed error handling for the CPV propensity implementation (model explanations), and has been resolved with the addition of a null check for the DSMValue type when it's missing in the function that loads the explanation details. | Decision Management |
| INC-C643 | 906125 | Corrected unoptimized properties in pzGetSocialMessages | Attempting to run the report definition pzGetSocialMessages related to the "Social/Pulse posts" search results from case manager and case worker portal generated the error ""Union not applied because properties are not optimized in Work-Cover-Task". This has been corrected. | Decision Management |
| INC-C7402 | 925784 | 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 | 915494 | 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 | 921265 | 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 | 930970 | 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 | 922353 | 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 |
916424 927619 |
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 |
Low-Code Application Development
23.1.5 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B16027 | 880035 | 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-B20714 INC-C4183 |
872855 919805 |
Corrected properties handling for Microsoft Word templates | After update, Microsoft Word templates were not working properly if they included case properties such as pyID, caseStatus, or pzInsKey. This has been resolved by updating the parseAndPopulate function of the docxGenerator API . | Low-Code App Development |
| INC-B23858 | 882449 | Corrected page handling to resolve PEGA0045 alerts | A PEGA0045 PDC alert, which is triggered when a requestor loads a data page that is already loaded, was generated from the node classification tracer when viewed from the Dev Operator login in Dev Studio. Investigation showed this was caused by the loaded D_PZNODESINCLUSTER data page not being used, followed by new request being submitted for the same data page without using the existing one due to the original being marked as reload once per interaction. This has been resolved by updating the page handling in Data-Portal-PegaAdminStudio-ClusterWidget to avoid PEGA0045 alerts. | Low-Code App Development |
| INC-B27950 | 900913 | Corrected handling for URL mapping with SSO | When using URL mapping with SSO to launch the case, the URL did not launch the case on the first attempt but did open the case as expected if the URL was hit a second time. Investigation showed the case was opening from the Standard Thread instead of the AutoThread for the SSO operator, and this has been resolved by introducing new variable pzisRedirectedFromSimpleURL in Code-Pega-Thread class to identify the flow is from SimpleURL, so that UI will use the same variable to open the Case Portal for the first time and subsequent requests. | Low-Code App Development |
| INC-B42296 | 908933 | Product rule save optimized for improved performance | When the ruleset minor and major versions and app context were pre-populated, the saving of the RAP rule form was taking an excessive amount of time. This has been addressed by optimizing the pzGetApplicationByRuleset activity. | Low-Code App Development |
| INC-B44364 INC-C19651 |
899224 934083 |
Endpoint handling updated for prcluster_service | After update, prcluster_service was not providing a response when hitting the endpoint for health checks. This was due to changes in the underlying servlet responsible for providing the response when the given endpoint is hit, and has been resolved by updating the WebStandard servlet method. | Low-Code App Development |
| INC-B48959 | 905140 | Increased QueryTimeoutValue for pipeline test case open | While merging branches, failures were seen with the error "Exception parsing the response from branch summary service". This was traced to SQL timeout while trying to open the Pega units rule table which contained a large amount of data. To address this, the maximum elapsed time in seconds for the QueryTimeoutValue has been increased. | Low-Code App Development |
| INC-B51239 | 908624 | Security updated for context paths | Cross-site scripting filtering has been added for context paths. | Low-Code App Development |
| INC-B51954 INC-C7741 INC-C18603 |
927470 | 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-B53416 | 911118 | Corrected handling of "$" in TracerEvent | The character "$" at the end of a property value was being misinterpreted and converted to "#DIALOGBODYnbsp;" while displaying clipboard pages. Investigation showed this was an issue with the handling in the TracerDisplayPropertiesScripts HTML, and has been corrected. | Low-Code App Development |
| INC-C12763 | 942541 | 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-C2261 | 917924 | 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 | 938373 | 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 | 947144 | 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 | 943754 | GetSiblings activity security improved | Cross-site scripting protections have been updated for the GetSiblings activity. | Low-Code App Development |
| INC-C4098 | 911996 | 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-C8184 | 915936 | 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
23.1.5 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B46675 | 900394 | Calendar spinner corrected for touchscreen laptop | A datetime control configured as spinner was working on iPad but not on a touch screen laptop using Google Chrome. This was traced to the configuration in the touchend event handler, and has been resolved by adding event listeners for touchstart and touchend events to the calendar spinners. | Mobile |
| INC-B52554 | 911720 | Added retry logic for locking during mobile sync | Intermittent sync errors were seen when working on mobile cases, and errors were logged indicating "Unable to open an instance using the given inputs" and "The work object XXX could not be locked: Cannot obtain a lock on instance". Investigation showed an SLA was locking the case while it was being updated from the mobile device; this has been resolved by adding retry logic to ActionQueueProcessor to allow the SLA to complete so that the case can process as expected. | Mobile |
| INC-C1566 | 908807 | Cache-control header added to disable cache | For URL responses that should not be cached, the server will issue the following header: Cache- Control: no-store, no-cache. | Mobile |
| INC-C16350 | 921005 | 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 | 922334 | 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-C20897 | 932628 | 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. | Mobile |
| INC-C22926 | 941605 | Handling added for legacy iOS push library implementation | iOS push notifications were not being received on mobile devices when sent through Customer Decision Hub (CDH). This was traced to the client application using an outdated push notification library. Starting with Pega version 8.5, the platform has adopted the HTTP/2-based APNs provider API. In order to support an application using the legacy library or custom implementation, the closeConnection function has been removed from send() to allow CDH to send multiple batches of the messages. | Mobile |
| INC-C3436 | 924378 | Offline queue processing logging updated | Enhanced logging has been added around offline queue processing to provide better troubleshooting insights. | Mobile |
| INC-C3944 INC-C3365 INC-B48692 |
911141 908758 910731 |
Corrected click handling in mobile app | Unexpected behaviors were seen in the mobile app, including issues with attaching files, skipping days when going to the next/previous day, and issues with collapsible headers opening and closing. This was an inadvertent side effect of work done on dropdown event loops, and has been corrected. | Mobile |
Project Delivery
23.1.5 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B37355 | 909693 | Authentication access group documentation updated | The security documentation for the Authentication Process flow has been updated to clarify the configuration information necessary for setting up an access group for the Browser Requestor. | Project Delivery |
| INC-B44601 | 902133 | Documentation updated for Field-Level Audit | The documentation for Enabling Field-level Auditing has been updated to clarify that Declarative Rules are not supported within data flows, with the result that Field-level Auditing will not work when executed from data flows. | Project Delivery |
| INC-B49938 | 903198 | Documentation updated for property-level encryption | The documentation for property-level encryption when using access control policies has been updated to clarify that encryption is only supported for textProperty and is not supported for embedded properties. | Project Delivery |
| INC-B52358 | 906421 | Dedicated index documentation updated | The documentation for creating dedicated indexes has been updated to clarify that selecting "For specified properties" is optional when creating dedicated indexes. | Project Delivery |
| INC-C20312 | 928096 | 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-C3787 | 912498 | 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 |
Reporting
23.1.5 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B10314 INC-B14636 INC-B15872 INC-B1662 INC-B16662 INC-B17143 INC-B17444 INC-B17472 INC-B1888 INC-B21931 INC-B23691 INC-B24830 INC-B25209 INC-B25495 INC-B25822 INC-B26551 INC-B3032 INC-B32417 INC-B35357 INC-B35525 INC-B38480 INC-B39929 INC-B42285 INC-B42731 INC-B44324 INC-B45715 INC-B48027 INC-B6255 INC-B6956 INC-B7757 |
901696 | ModelDiffCalculator updated for SRS data modal issues | When issues are encountered with the SRS data model, running the pxResetSearchModel activity can help reset the model and fix the issue. However, in some cases this is not a viable solution as it would delete all the indexes from live and archival and require time and effort to create new indexes from scratch. To address this, the latest SRS product version has an updated ModelDiffCalculator to accept class FtsExcluded Properties changes in place of running pxResetSearchModel. This is handled through the use of the hasFtsExcludedPropertiesChanged flag to accept any changes in FtsExcludedProperties. | Reporting |
| INC-B21374 | 876470 | 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 | 885767 | 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-B36882 | 908811 | Corrected AddPropListForClass_TreeGrid handling | When a keyboard user navigated to the Reports tab and created a new report, properties from the Index table either did not have a label in the data explorer page and appeared as blank in the UI or the page property was seen for all embedded properties. This has been resolved by updating the logic for determining inheritance in the pzAddPropListForClass_TreeGrid so properties have the correct label visibility. | Reporting |
| INC-B44237 | 913250 | Corrected handling for spaces in embedded ElasticSearch | When using "one-of" in embedded ElasticSearch, the spaces in the search strings were being removed by a ReplaceAll function, causing inconsistent results and results that did not adhere to ABAC (Attribute-Based Access Control) policy. This has been resolved by updating the logic to trim the search strings instead of replacing the spaces. | Reporting |
| INC-B44668 | 904396 | Modified linked property display for Report Browser | When using the end user Report Browser, the Best Bets versus the All Matches were displayed slightly differently. Investigation showed that a linked property was displayed in the Report Browser Date Explorer as a list instead of as text. This has been resolved by modifying the pzAddPropListForClass_TreeGrid to mark the linked properties as Text properties rather than displaying falsely as a list. | Reporting |
| INC-B46998 INC-B46998 INC-B35177 INC-253507 INC-10191 INC-A15400 INC-222311 |
901833 899932 |
Corrected datetime calculations in function aliases for locale | After migration, the date and time report display in the manager portal displayed in GMT instead of the timezone/locale used in the operator profile. This was traced to handling differences between on-premises installation and Pega Cloud in the pxDay function alias used in the Report Definition, and has been resolved with an update to consider the operator time zone while calculating the datetime values in function aliases. | Reporting |
| INC-B47214 | 901531 | Corrected AnyPicker "undefined" search category | When both AnyPicker and Multiselect were used in the same section and categorization was used for AnyPicker, the results included "Undefined" as part of the results in the search category. Investigation showed this was caused by the pega.c.filterCrossScript function being present in Multiselect and the AnyPicker control with the same name but slightly different implementation, causing AnyPicker to use the Multiselect implementation(overrriden) where undefined is not handled by the method. This has been resolved by updating the Multiselect implementation. |
Reporting |
| INC-B47266 | 899147 | Improved accessibility for Dashboard delete buttons | All of the Delete buttons controls on the Personal Dashboard had the same title/name, "Delete this widget", which was not unique or descriptive and hindered accessibility. This has been resolved by creating a new field value for the Delete icons which will make the buttons unique based on the pyLabel coming from the field value. | Reporting |
| INC-B47566 | 909260 | Added alt text for graph placeholder Image | In order to improve accessibility, pzchartcontrol has been updated to add alternative text for the placeholder image shown in reports where a chart cannot be displayed due to lack of data. | Reporting |
| INC-B51370 | 904877 | Report Definition filter condition shows correctly | Using a function in the report definition filter with "Is null" or "Is not Null" did not display the relationship value when running the report. Other conditions such as "Is equal", "Is not equal", etc, worked as expected. This has been corrected by appending the StrOperation when the Function aliases are used in the RRFilters_Logic Control. | Reporting |
| INC-B51984 | 912073 | Updated logic for sort type in report definitions | After configuring a report definition to get case counts along with the ThresholdPanelSize, the sorting conditions were not being honored. It is expected that the group-by columns are given sorting priority and the aggregate fields handled last in order to avoid the tree view being distorted. However in this case, the sort was given as (n-1) instead of n when saved, which was incorrect. This has been corrected by updating the pzPopulateSortOrder logic to be n when the aggregate fields are present. | Reporting |
| INC-B53440 | 904059 | 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. | Reporting |
| INC-C15050 | 921820 | 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-C1627 | 909860 | Copy Report handling updated | After update, attempting to copy reports to a new or existing category was not working. Copying to the same category is not supported, and an error message indicating "Report already exists in category" has been added to reflect the limitation. Copying to a different category has been corrected by updating pzcopyshortcutpostactivity7. | Reporting |
| INC-C16938 | 928206 | 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-C19291 | 926915 | 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-C20763 | 929222 | 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 | 933256 | 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-C22627 | 930342 | 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 | 933327 | 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 | 936344 | Security updated for Insights | Cross-site scripting protections have been updated for Insights reports. | Reporting |
| INC-C27086 | 940562 | Report Menu button contrast improved | To improve accessibility, the color contrast of the Report Menu actions button has been updated. | Reporting |
| INC-C27311 | 936399 | 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 | 948150 | 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-C31207 | 942019 | 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-C32508 | 945273 | 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-C4726 | 914225 | Insights 3-dot action menu text made accessible | When using a screen reader, the 3-dot action icon for the insights menu in Constellation announced "Insight - actions" but did not specify the actual insight title. To improve accessibility, the aria-label for this has been updated to provide more information. | Reporting |
| INC-C7046 | 916323 | 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-C7803 INC-C8790 INC-C9521 INC-C11151 |
917150 | Updated exception handling to correct UVU report generation | While extracting the case data for the Export Case Counts Per Month report using the Usage Validation Utility (UVU) portal, the process appeared stuck at 100% with a message "Waiting for file to be composed...". No link for downloading the .csv file was generated, and errors such as "FileNotFound" and "DatabaseException" were logged. This was traced to issues related to an abnormal table schema, and has been addressed by updating the exception handling. | Reporting |
| INC-C8513 | 918932 | 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 | 948901 | 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 | 918023 | 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
23.1.5 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B37967 | 908053 | Updated handling for IDP authentication timeout | When using AzureB2c, logging in successfully after a brief timeout resulted in the login screen resetting to display the Pega basic Auth Service Selector login screen. To provide a better experience to mobile application users, this has been addressed by including a check of the IDP response: if there is no requestor and no authentication service details, the system will consider that the temporary requestor has expired rather than fallback to the Pega screen. | Security |
| INC-B39158 | 909315 | Corrected SOAP Service calls failing after update | After update, the DataPower SOAP service was generating the exception "AxisFault: WSDoAllReceiver: security processing failed (actions mismatch)" when decrypting the responses. This was due to previous work done in the prwss4j library which was not carried over into the newer versions, which was to calculate the processing actions validation correctly after the message's security requirements were already processed by the library. This has been corrected. | Security |
| INC-B42474 | 901640 | 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-B42872 | 899630 | SECU0017 alert observability added for Browserfingerprint issue | Additional logging has been added to assist with diagnosing unexpected logout issues related to a browserfingerprint error. | Security |
| INC-B46722 | 901179 | Updated encoding for URL special characters | When using OpenURLinWindow to open a URL in new window from a case, a SECU0019 alert was generated for pzProcessURLInWindow. Investigation traced this to the method used to encode a space character in the parameter, and this has been resolved by using XMLUtils.encodeString instead of URLEncoder.encode for the process. | Security |
| INC-B49938 | 901706 | ABAC policy validation added for embedded properties | Encrypting a property with a declare expression was generating an error. This was due to missing validation: encryption is only supported for textProperty, and validation was properly applied for non-text exposed properties. However, the type was not validated for embedded properties, and embedded encryption is not supported. To address this, a validation check has been added for the Embedded Property type in ABAC policy, and the documentation will be updated to specify that embedded encryption is not supported. | Security |
| INC-B52163 | 905428 | Improved security for alert popup | Cross-site scripting filters have been added for the authentication screen error handling. | Security |
| INC-B52373 | 910750 | Corrected decimal handling for ar_MA | When a decimal value was entered as 4,5 while using the locale ar_MA (Arabic - Morocco), tabbing out and triggering validation generated the error "4,5 is not a valid decimal value". This has been corrected by updating the decimal separator for the ar_MA locale. | Security |
| INC-B52373 | 914506 | Added specialized locale ar_SAS for Saudi Arabia | When the application was localized to Arabic but an English keyboard was used, an exception was generated when checking value > 0. This was traced to the UTF definition for the comma decimal separator in Arabic locales (ex, ar_MA or ar_SA) being different than the comma in an English locale, and has been resolved by adding the specialized locale ar_SAS to support using the regular comma of an English keyboard as a decimal separator. | Security |
| INC-C12168 | 917598 | 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. | Security |
| INC-C17675 | 942703 | 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-C1803 | 914759 | Security updated against java injections | Cross-site scripting protections have been updated for LoadMashupPage and GetURLHashes. | Security |
| INC-C19693 INC-C28826 INC-C36468 |
928897 939897 947387 |
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-C20603 | 935439 | 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. | Security |
| INC-C20976 | 930470 | 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-C21051 | 927490 | 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. | Security |
| INC-C21148 | 929807 | 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. | Security |
| INC-C23008 | 948295 | 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 | 929157 | 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 | 940265 | 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-C29398 | 942414 | 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. | Security |
| INC-C30503 | 947345 | 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-C3298 | 924785 | 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-C35686 | 948370 | 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-C3671 | 910380 | Mobile device correctly terminates session after refresh token expiry | When using an OAuth2 Client Registration configuration on mobile, the user was not being logged out after the refresh token expired. Investigation showed that the authentication flow was looking for a custom authentication type, and a stateful session was not considered. This has been resolved with an update to ensure that when force authentication is exercised in the offlinehttp service package. a reauthentication happens. | Security |
| INC-C372 | 908086 | Security updated for URL hash | Cross-site scripting protections have been updated for fetching URL hashes. | Security |
| INC-C45 | 909178 | User ID recorded in audit for disabled operators | Disabled SAML SSO operators received the error msg "Your account has been disabled, contact your system administrator", but their user ID was not recorded the in the security audit report. This has been corrected. | Security |
| INC-C4503 | 913500 | Updated OperatorID security | Security has been updated for the OperatorID clipboard page. | Security |
| INC-C5199 | 912972 | Updated system name security | Cross-site scripting protections have been updated for system name. | Security |
| INC-C6092 | 914978 | Security updated for CKEditor | Cross-site scripting protections have been added for CKEditor. | Security |
| INC-C6548 | 913398 | Updated security for SAML-based SSO code | Cross-site scripting protections have been updated for web authentication using SAML. | Security |
| INC-C6807 | 913781 | Direct access from URL to Service Export Directory restricted | ServiceExport is a directory used to store files temporarily during file upload and import/export functionalities. In order to improve security, direct URL access to the files stored there has been restricted, and the HTTP error status 404 (Resource not found) will be returned. | Security |
System Administration
23.1.5 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B44630 | 908502 | Job correctly stops after calling DELETE job_schedulers API | The DELETE command to stop the job scheduler reported success with a 200 response and showed as disabled, but the job continued to run. This was traced to an issue with the handling of the nodeID parameter for a multi-node service, and has been resolved by updating the API. | System Administration |
| INC-B50938 | 901056 | External Hazelcast v5 startup updated for use with Oracle use | When the Weblogic server was started using Hazelcast v5 with Oracle, multiple errors were generated including a null pointer error. This was seen with Oracle deployments but was not encountered with tomcat,postgres deployments, and has been resolved by refactoring the Hazelcast v5 initialization flow to mitigate startup failure for the prcluster_service. | System Administration |
| INC-C15356 INC-C35725 |
937523 948237 |
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-C19776 | 933626 | 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. |
System Administration |
| INC-C25875 | 946583 | 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-C7958 | 917359 | 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
23.1.5 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A20794 | 840525 | Updated active layout conditional visibility handling | When using a Dynamic Layout Group to display controls for each element of a tab within a page list, on initial load multiple tabs were selected at the same time, presenting two separate tabs of controls on screen. This did not impact functionality, and selecting a tab reverted it to normal presentation. Investigation showed this issue was linked to the logic used for the conditional visibility, and has been resolved by updating the active layout handling. | User Experience |
| INC-A23056 | 838240 | 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-A24064 | 842584 | Deferload corrected when the previous tab is invisible | Tab contents were not loaded when deferload was on, the active tab had a previous and next tab, and the previous tab was invisible on layout group. This has been resolved by updating the handling for defer load with visibility conditions. | User Experience |
| INC-A24271 | 855130 | Corrected classless Anypicker pagelist on clipboard | When using a screenflow with an Anypicker field on multiple pages, an unexpected classless pagelist appeared on the clipboard. After changing the Anypicker to a textinput the issue was not seen. This was traced to the handling of the control when used in multiple sections which caused a missing reference in the generated HTML. To resolve this, an update has been made to register the property based on runtime instead of using a hardcoded value from design time. | User Experience |
| INC-A29326 | 852791 | 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 | 921703 | 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-B10039 | 874485 | Corrected focus maintenance for left panel tabs | Whenever any new tab was added dynamically to the Constellation left panel based upon the case flow status, the focus moved to a different tab instead of being maintained on the same tab. For example, before changing the case status, the focus was in the second tab. When a new tab was added on top, focus shifted to the center tab instead of remaining on the original tab which was now third. This has been resolved by adding a function in the Control_menu js with "enableLabelBasedActiveMenuState" DSS. | User Experience |
| INC-B12102 | 866003 | Added content skiplink for mobile | In order to improve accessibility, a skiplink for moving to the main content of the page has been added for mobile browsers in the available section pySkipLinksToTarget. Skiplinks for the search bar and the navigation pane are not available in mobile. | User Experience |
| INC-B23258 | 873552 | Corrected error readout accessibility for required multiselect | When JAWS users tabbed into a required multiselect control, the screen reader announced the instructions to navigate the multiselect control. When tabbing out without making the required entry, the client side error message and then the details of the next control were announced. This was unexpected timing due to the span tag associated with the multiselect being concatenated with the error message when reading out, and has been resolved. | User Experience |
| INC-B25480 | 904192 | SetRequestorAsDisconnected updated to resolve logout issue | An authenticated session was getting logged out intermittently even when active. Investigation showed this was due to the operator presence state being updated to disconnected, and has been resolved by updating the pzSetRequestorAsDisconnected activity. | User Experience |
| INC-B26622 | 879691 | 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-B27437 | 878890 | Updated accessibility for button with menu action | A button configured with a menu action was not indicating whether it was expanded or collapsed when using a screen reader. This was due to a missing aria-expanded attribute, and has been corrected. | User Experience |
| INC-B27969 | 888409 | Updated accessibility for tab group close button | The VoiceOver screen reader in Apple Safari incorrectly announced the tab group close buttons as having additional menu items. This has been resolved by correcting the accessibility markup, but it is recommended to migrate to layout groups as tab groups are deprecated. | User Experience |
| INC-B28041 | 881041 | Improved accessibility for modal popup focus | When a pop-up was launched after clicking on a button in a modal dialog, focus was set on the back button instead of the "X" (close) button. This was incorrect behavior, and an update has been made to ensure the modal popup focus order is Cancel > Submit > X button. If there are editable controls in the modal, the default focus is on the first editable control. | User Experience |
| INC-B32015 | 904945 | Improved accessibility for calendar date picker | When using a screen reader, attempting to select the correct date picker using the ‘say what you see method’ was difficult due to all date pickers having the same name. When saying ‘Date Picker’, it automatically opened the first calendar on the page despite other date pickers being on the same page. To improve accessibility, the calendar icon label has been updated to "{field label} date picker". | User Experience |
| INC-B35060 | 895862 | Accessibility corrected for My Application left navigation panel | When navigating to My Applications in the left navigation panel, the focus was not moving to the "Proceed To" drop down and "Go" button for the last application as expected. Instead the focus jumped to the "Close" button at the top. This has been corrected. | User Experience |
| INC-B36109 INC-B50464 |
889437 905911 |
Constellation Case in traditional app opens in correct UI | When reusing a Constellation Case Type from an existing application in a traditional UI application, the case opened in an incorrect UI and the view was not displayed correctly. This has been resolved with an update to ensure the correct harness is generated. | User Experience |
| INC-B36363 | 902078 | Corrected shuffled sorting on refresh of table using sourced datapage | When using a section configured with a table and sourced from a report definition data page, clicking on the refresh link resulted in the data appearing without the configured sorting order. This was traced to the table refresh passing implicit parameters which were different from what was passed on initial load, and has been resolved by including a implicit parameter value which will be synced for the queryable datapage. | User Experience |
| INC-B38645 | 899764 | Case ID icon focus corrected | The Suitcase "Case ID" Icon on the MDC tab was unexpectedly receiving focus. This has been resolved by adding the necessary aria-hidden attribute to correct accessibility. | User Experience |
| INC-B38804 | 904054 | Added null check for portalName | After creating a case from Postman using REST services and executing custom logic to update the pulse data, trying to save the datapage using the pzSaveDataPage activity generated an error indicating "InvalidParameterException: cannot be null or blank". Investigation showed there were attributes missing so the clipboard was not holding the required parameters in the Declare_pyDisplay.pyDisplay page. This has been resolved by adding null/blank checks for portalName in DynamicContainerDataModel.java & pzGenerateMicroDC Rule-Utility-Functions. | User Experience |
| INC-B38837 INC-B44647 |
900048 903343 |
Corrected UI display on tab switch and refresh | When accessing the user portal, right clicking on the Case ID to open it in new tab and then changing the application caused UI rendering issues post-refresh. This was traced to a harness issue when multiple URL mapping links are present which caused the default harness to be executed instead of the expected one, and has been resolved by adding a step in the showDesktop activity to parse and fetch the portal name in case of NewTabthread. | User Experience |
| INC-B3954 | 860586 | Corrected focus on validation fail | After launching the user portal to create/update a case, clicking on the Continue button triggered the validation messages, but the screen focus remained on the area of the Continue button instead of shifting to the error messages at the top as expected. This has been corrected with an update to shift the focus to the ErrorBlock on submit if there are validation errors. | User Experience |
| INC-B40893 | 901821 | Additional TestIDs generated for repeating dynamic layouts using v1DXAPIFUA | When using the Cosmos application with a custom breadcrumb which holds the Repeating Dynamic Layout, the DXAPI client retrieved the JSON data which included the TestID of the layout which was then processed in the Angular application. This was working in Production, but was not working in a lower environment due to the JSON data not having the TestID of the repeating dynamic layout. This has been resolved by updating the vieworpage function in the repeating dynamic layout generation code to include TestIDs for each row. | User Experience |
| INC-B41782 | 896584 | Corrected assignment submission with date field error message | When using a date field that was not required, an invalid or incomplete entry did not prevent the assignment from being submitted in Constellation even when there was an active validation error on the date field inside the table. Investigation showed this was caused by the changeHandler receiving a blank value in this scenario, causing the server validation to not fire, and has been resolved by updating the error state in Redux store for invalid DateTime fields. | User Experience |
| INC-B43663 | 895136 | Resolved QR-code download of Ad-Hoc iOS apps | After creating a provisioning profile with 'Ad Hoc' distribution and building a mobile app, the QR code was not being generated for download/install. Investigation showed the Apple iOS application signing-certificate type was being consumed by Pega as certificate type of 'AppStore' even though the signing certificate was created as iOS Distribution type certificate intended for both purposes. This has been corrected by updating the QR code display for the ad hoc provisioning profile. | User Experience |
| INC-B43827 | 895929 | Corrected pageinstructions handling in nested embedded list | When using a nested embedded data structure in Constellation where the parent embedded data had a field group with different properties and another embedded list data property which was shown as a grid, deleting the first row of parent embedded data did not delete the child embedded list and this child list was then displayed as the first row. Investigation showed the pageInstructions function was not generated correctly for a nested structure while performing a move or reorder operation, and this has been corrected. | User Experience |
| INC-B44040 | 900666 | Create Stage title corrected for new modal window | The modal opened from the ActionsMenu of CreateStage was showing the title as "New Casetype_Name" instead of displaying title as "Edit details" or "Change Stage". Investigation showed when multiple local actions were set up and launched from the create stage, the local actions title display was the new pyID ("New Casetype_Name"). To resolve this, new header title sections have been added so the correct title is shown for modals opened from the actions menu on a work object. | User Experience |
| INC-B44067 | 899649 | Corrected save and close local action in create harness | When using the create harness and trying to abandon a launched flow action process or click of "Save and Close" button, the portal ended in an infinite loading screen which blocked any further tasks until the browser was refreshed. This has been corrected. | User Experience |
| INC-B44300 | 894318 | Corrected date formatting for Swedish locale | When using the Swedish locale, the date was incorrectly formatted as "dd mmm yyyy". This has been resolved with an update to use a date formatted as an ISO string to ensure accuracy. | User Experience |
| INC-B45668 | 901407 | Scrollbar height for menu items updated | When a portal header is used, the scrollbar for the left menu items was not showing all of the items configured. This has been corrected by updating the height to consider the header as well. | User Experience |
| INC-B46310 INC-B44820 |
903909 895971 |
Corrected Datetime value property handling for Arabic locale | After update, using the Arabic locale (ar_SA) displayed date control properties as "undefined" instead of the expected values. This has been resolved by correcting the number conversion and formatting for the necessary values. | User Experience |
| INC-B46513 | 900238 | Improved DynamicFieldName color contrast | In order to improve accessibility, the pyDynamicFieldName color contrast has been modified for the add and modify badges in py-case-manager-header-overrides. | User Experience |
| INC-B46843 | 904614 | Added missing text spacing in calendar icon helper label | When using a Date time control in a section to allow users to select a date range for displaying data in reports based on criteria specified in another section, adding the Refresh Section or Refresh Other Section actions caused the Date time control’s accessibility name tag to not render with the correct text spacing and interfered with accessibility. This has been corrected. | User Experience |
| INC-B46921 | 898942 | Corrected focus accessibility for AJAX container worklist tabs | When using the keyboard to navigate the worklist case tabs in an AJAX container, the close tab icon did not have a focus indication. This has been corrected. | User Experience |
| INC-B47148 | 909682 | Transfer assignment Go button corrected | After performing a transfer, clicking on the Go button to open the assignment did not function until a refresh was performed. This was traced to the empty payload key not being properly removed from the redux container, and has been corrected. | User Experience |
| INC-B47543 | 903246 | Resolved question mark reading as number | After adding Image control, Icon Source: Icon Class, Class: pi pi-help, Helper tet : None, with a click action which opened a overlay or modal dialog, screen readers were reading a question mark Help icon as a number button. This has been corrected by updating the CSS for improved accessibility. | User Experience |
| INC-B47832 | 901558 | Corrected accessibility for dirty dialog in modal | The dirty dialog header was not being announced by the screen reader. This was traced to the modal dialog header on pyDirtyCheckConfirm using a label instead of an h2 element, and has been corrected. | User Experience |
| INC-B48163 | 902238 | Corrected reload issue in locked work object | After upgrade, the Work-Cover!WorkUnlock activity, which was Internally triggered from doUIAction activity, was failing at step 3 to unlock the work object. This caused the case to close abruptly on the UI. Investigation traced this to the handling of the harness refresh for dynamic navigation, and the issue has been resolved by adding a check to the reload function. | User Experience |
| INC-B48218 | 901339 | Improved accessibility for Search Input for Followers modal | In order to improve accessibility, the Search Input for Followers modal window has been redesigned to include a more descriptive search readout for screen reader users along with an updated interface to be more in line with other existing modals. These changes include updating the search input 'Label Value' from "Search" to "Search Followers", removing the place holder text and enabling the label to be shown and read by screen readers to allow the user to better understand what the control is doing, and using more informative layout descriptions. | User Experience |
| INC-B48645 | 905170 | Added accessibility for expand / collapse state of submenu | The expanded / collapsed state of a submenu was not conveyed correctly when using a screenreader, and keyboard focus remained on the parent submenu. This has been corrected by adding and removing the aria label dynamically as appropriate. | User Experience |
| INC-B49172 | 902352 | Corrected overlapping of radio button value in a table | When a property of the type Radio buttons was added as a column in the table with mandatory validation, clicking submit resulted in the radio button value (example - 'Yes') overlapping with the radio button. This has been corrected by updating the CSS for non-optimized grids. | User Experience |
| INC-B49330 | 908293 | "My Worklist" text localized | Localization has been added for the 'My Worklist' text in the Todo widget. | User Experience |
| INC-B49603 | 903102 | Save action announcement added for accessibility | In order to improve accessibility, clicking on the work save button will generate an announcement from the screen reader to let the user know the action has been taken. | User Experience |
| INC-B49607 | 909114 | Corrected case open with URL Mapping | When logging in using URL mapping for the first time, it was not possible to proceed with case submission when the concurrent session feature was enabled. This was traced to the thread name handling, and has been resolved by adding pzisRedirectedFromSimpleURL as an additional check for URL mapping validation. | User Experience |
| INC-B49910 | 903436 | Accessibility improved for case-wide action launched modal | When using a case wide action reopen, the modal launched did not have accessibility attributes consistent with other modals such as announcing the reopened modal title. These attributes were present when opening the modal with a button triggering a local action. This has been resolved by removing the role dialog for dialog headers in pydialogcontainerheader and pynewcaseheaderouter. | User Experience |
| INC-B50105 | 903375 | Corrected screen freeze during validation | Entering incorrect input in autocomplete fields within optimized tables that had row visibility expressions configured was causing the screen to freeze. This was traced to a console error in the tGrid.prototype.updateGrippersHeightIfRequired function, and has been resolved by adding a null check. | User Experience |
| INC-B50162 | 906570 | Corrected save of table records added on change of a dropdown | When using Constellation, attempting to save table rows/records added on change of a dropdown value was not working unless "save for later" was clicked. Without clicking "save for later", after the first record was added, selecting a second dropdown value replaced the first row with the details of the second selection. This has been resolved by modifying the generation of the UPDATE Page Instructions when a pyRefreshData DT adds a new row in the pagelist. | User Experience |
| INC-B50297 | 902428 | Added quotes handling for ReadOnly constant value | After configuring a text area in a section with presentation as "Readonly(always)" and value as "Constant", giving some text with few words in double quotes as the constant value generated an error when trying to save. This has been resolved by adding handling for using double quotes in the constant text value for EditMode: Readonly. | User Experience |
| INC-B50334 | 905663 | Alert attribute handling corrected | When validation was configured through the flow action, the alerts displayed on the UI were causing a failure due to the role of alert being used within a <UL /> element. This was due to the alert being located on the incorrect element, and has been resolved. | User Experience |
| INC-B51382 | 904400 | Corrected Semantic tab Title display | The Semantic tab layout option in Dynamic Layout Group did not display the Title of the last tab correctly when the Title was sourced from a Field Value, displaying the ID of the Field Value rather than pulling from the result of the Field Value. This has been corrected. | User Experience |
| INC-B51609 | 905965 | Updated handling for special characters in label control | When a label control had a special character value such as an equal sign, an at sign, a single quote, or a plus sign ( = @ ` +), the encoding and decoding was affected by the cross-site scripting filters. This has been resolved with a specialized unescape function to avoid such errors. | User Experience |
| INC-B51970 | 910534 | Corrected numerical localization handling for RTL languages | When using the locale "ar-SA" it was not possible to type more than one digit into Currency/Number input due to the value being localized as it was being typed. This has been resolved by disabling the automatic conversion of the input value to non-latin numerals and fixed notation for numbers in right-to-left languages. | User Experience |
| INC-B51994 | 905676 | Case links from preview window correctly open in tab | Attempting to use "Open in tab" for an email triage case redirected the new tab to the Home screen instead of to the case. This was caused by an error in the semantic URL, and has been resolved by ensuring the case key is passed in the resource parameters. | User Experience |
| INC-B52070 | 911624 | Date spinner changes announced by screen reader | After creating a section and adding a datetime control with display as 'text input + calendar' in a presentation tab, the screen reader did not announce modifications to the "Month" dropdown made with the arrow keys in the Calendar icon. This has been corrected. | User Experience |
| INC-B52357 | 906566 | Collapse summary panel helper text made accessible | After opening a theme-cosmos case, the 'Collapse summary panel' button showed the helper text on hover but not if accessed using the keyboard with tabbing. This has been corrected in pxCaseMainPageTemplate. | User Experience |
| INC-B52656 | 906428 | Corrected localization for Arabic locale | Localization was not working as expected for some labels such as the filter dropdown lists in the list view, the SLA, and the new comment label in the Pulse section in Constellation. This has been resolved by adding the necessary format and column options for localization. | User Experience |
| INC-C10206 | 917972 | 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-C105 | 914298 | Corrected session timer spacing | The session timer popup had additional space on the right side. This has been resolved by setting the Iframe width to take full space available. | User Experience |
| INC-C10615 | 919750 | 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-C11253 | 919888 | 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-C1146 | 909987 | Corrected accessibility for CaseActionHeader | The role="menubar" attribute was being incorrectly added in the DOM for the CaseActionHeader section of a dynamic layout. This has been resolved by removing the ARIA menu from CaseActionHeader. | User Experience |
| INC-C11819 | 919772 | 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-C12171 | 926345 | 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-C12790 | 921837 | 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-C13337 | 920363 | Markdown library update | The markdown library has been updated to the latest version. | User Experience |
| INC-C13355 | 921102 | 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-C13418 INC-C7456 |
922645 917960 |
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-C13714 | 922700 | 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-C14758 | 921908 | 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. | User Experience |
| INC-C15007 | 931821 | 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 | 922634 | 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-C15021 INC-B31175 |
923067 886371 |
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-C15899 | 927346 | 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-C16881 | 927356 | 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-C17245 | 926733 | 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-C17264 | 925538 | Portal creation updated for mobile channel | After going to the "Channels and interfaces" tab, selecting mobile under the "Create new channel interface" resulted in the screen being stuck in loading mode. This was traced to an issue with components having null scripts in the template dependency object, and has been resolved by revising the pyModalButtons handling in pzPortalModalTemplate. | User Experience |
| INC-C17362 | 929598 | 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 | 930750 | 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-C17678 | 926295 | Corrected handling for converting relative dates with promoted filters | Promoted filters using relative date time periods were returning incorrect filtering results. Investigation showed the filter conditions were being sent using the end user's timezone values instead of the GMT values stored in the database, and this has been resolved by updating the handling for the relative and complex filter conditions before converting value to timezone. |
User Experience |
| INC-C18593 | 931366 | 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-C19457 | 928435 | Updated handling for read-only tab case reference field | Case-wide actions such as trying to add a new record to an embedded list property were generating "TypeError: Cannot read properties of null (reading 'split')" messages when executed. This occurred when a using a case reference field in a list display in a read-only tab, and has been resolved with an update to add safe checks. | User Experience |
| INC-C19466 | 925554 | 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 | 929498 | 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-C19790 | 930485 | 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-C19973 | 929506 | 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-C20660 | 927508 | 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. | User Experience |
| INC-C21248 | 929110 | 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-C2127 | 912580 | Corrected AM/PM handling for ms_MY locale | When using the Malaysian locale (ms_MY) with an offline-enabled mobile app, a datetime entered as PM was switched to AM on save. This was traced to the time conversion handling which defaulted to AM due to not correctly retaining the locale-specific PG/PTG designation, and has been corrected by updating handleNativeDate (pzpega_control_datePicker). | User Experience |
| INC-C21440 | 930093 | 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-C21605 INC-C5044 |
930290 914327 |
Insights drill down table popup displays correctly | When using Insights functionality in Constellation, clicking on chart elements to drill down into detailed data resulted in the filter options popup window appearing behind other UI elements instead of in the foreground. This was traced to an issue with the z-index layering for the Insights drill-down popup components, and has been resolved with an update to ensure drill-down popups display properly in the foreground. | User Experience |
| INC-C218 | 912052 | Documentation updated for Hide/Show fields in Table/Grid | After clicking on a value that triggered a local action and enabling additional hidden fields in an optimized table containing a modal dialog, the grid columns unexpectedly displayed property names instead of the actual property values. This was due to an implementation issue. To assist with the configuration of this flow, the documentation for Launching Modal Dialog Boxes has been updated to specify that if an optimized table includes a menu that opens a modal dialog, a refresh list action is required upon closing the modal dialog to ensure correct context. | User Experience |
| INC-C21938 | 941911 | 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-C22706 INC-B48169 |
932071 910578 |
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-C22775 | 933701 | 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-C23461 | 932039 | 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-C2435 | 913454 | Corrected success alert message on every step | After update, the message "Successfully Submitted" displayed at the bottom center of the screen for every step in an assignment in the Create stage. This has been corrected so the success message displays once at the end of the stage submit button instead of for every "next" button click. | User Experience |
| INC-C24596 | 931742 | 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 | 943323 | 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 | 947216 | 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 | 935399 | 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-C2505 | 911048 | Improved accessibility for modal dialog | Focus was going behind the modal dialog when the dialog was launched from the menu button. This was a missed use case for the focus shift when the menu button is outside of the table, and has been corrected. | User Experience |
| INC-C25152 | 949545 | 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-C25502 | 944720 | Corrected error clearing and focus handling | Constellation field validation errors were not clearing immediately when valid options were selected from picklists, requiring double selection for the error message to disappear. Additionally, focus was incorrectly moving to the first input field when users corrected validation errors. This was an inadvertent side effect of previous work done on URL handling and has been corrected. | User Experience |
| INC-C25516 | 933653 | 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-C25525 | 935618 | 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-C25734 | 938711 | 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-C26776 | 940137 | 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 | 939088 | 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 | 936116 | 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 | 941031 | 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-C28840 | 939406 | 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-C2894 | 917475 | 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-C30714 | 943797 | 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-C31089 | 942792 | Security improved for preview activity | Cross-site scripting filters have been updated for the selectivePreview activity. | User Experience |
| INC-C31140 | 943037 | 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-C3165 | 910651 | Aria label translated in column header | The aria label of the column header was not localized in a non-optimized table. This has been corrected. | User Experience |
| INC-C3270 | 912406 | Mobile compatibility check added for BroadcastChannel API | Attempting to access a Pega Infinity 24.1+ mobile application from Safari on iOS versions 15.3 or lower displayed a blank screen. This was due to the included BroadcastChannels API which requires iOS 15.4+ to run the pzClientDynamicData function for co-existence / blended UI. Since blended UI is not used on mobile, a compatibility check has been added which will skip loading the co-existence code on mobile devices. | User Experience |
| INC-C32864 | 945365 | 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-C33387 | 943641 | 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-C34213 | 947729 | 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-C34448 | 948695 | 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-C350 INC-B50752 |
908661 906653 |
Accessibility improved for modal dialog components | JAWS 2024 was announcing extra information including the browser tab name when launching a modal. This has been resolved by updating aria-describedby to aria-labelledby so that the tab context is not read by JAWS. In addition, logoff timer dialog for the sessionTimer loaded inside the modal has been updated to be more informative. | User Experience |
| INC-C35239 | 949345 | 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-C3629 | 909816 | Security update for JWT tokens | JWT token handling in the Constellation AppStatic Service has been updated for improved security. | User Experience |
| INC-C3996 INC-C6064 |
910633 913549 |
Corrected currency symbol alignment issue in table | The currency symbol was mis-aligned or obscured in a layout group-table grid. This has been corrected by updating the necessary CSS for currsymbolleft. | User Experience |
| INC-C4059 | 910271 | 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-C440 | 910775 | 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 | 917336 | 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-C46 | 906071 | Attachment icon properly hidden by condition | Attachment icons remained visible in collapsed mode even when configured with "Never" visibility conditions. This has been resolved by ensuring visibility conditions are properly respected for attachment icons in all display modes in Constellation. | User Experience |
| INC-C4721 | 917225 | Blended UI loading message localized | The message "Loading content" was not localized in Constellation Blended UI. This has been corrected. | User Experience |
| INC-C4753 | 919444 | Added check for minute value for AM/PM evaluation | The interval between 12:00:00 PM - 12:00:59 PM was being evaluated as AM instead of PM. This has been resolved by modifying the condition to check if minute >=0. | User Experience |
| INC-C490 INC-C5657 |
910962 912658 |
Required fields validation corrected | Required fields validation was not working as expected after upgrade. In some cases, fields set to required always did not generate a popup to prevent submission. When creating a case without entering any value in a required Rich Text Editor and clicking submit, a browser alert appeared which prevented submission as expected. However, accessing the same case by clicking the Go button from the home screen allowed the case to be submitted without mandatory fields even if no values were entered. If mandatory text field, radio buttons, or date field were left blank on a non-focused tab, submit was allowed without throwing any validation error. This was an inadvertent side effect of work done to correct client-side validation performed on hidden fields, and has been corrected. | User Experience |
| INC-C5115 | 917532 | 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-C6327 | 913227 | Corrected accessibility interaction for virtual cursor | When using the Local Action -> Overlay configuration with JAWS 2022, the user was able to escape out of the active overlay with the UP/DOWN arrow keys and browse the rest of the main content. This has been corrected by updating the aria-label and role of overlay for the non-focusable element. | User Experience |
| INC-C6462 | 913090 | Error message showing in Web Embedq | No error message was generated when an unauthorized user attempted to open a case using Web Embed. This has been resolved with an update to add a rendering mode check to determine the context for errors. | User Experience |
| INC-C688 | 909057 | Date picker calendar labels made accessible | To improve accessibility, title attribute to the month, year, hour, min, and am/pm dropdowns for the combo boxes within the date pickers so they are correctly announced by screenreaders and the browser tooltip will be seen on hover. | User Experience |
| INC-C8350 | 914649 | Attachments section localized | Localization has been added to the add button and attachment button of the actions -> view history section. | User Experience |
| INC-C9110 | 916051 | 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-C9199 | 928549 | 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-C9617 | 914728 | Corrected accessibility for multi-select control | When a multi-select control was configured with a visibility condition, JAWS did not announce the control label when focusing on the input. This has been corrected. | User Experience |
| INC-C99 | 916809 | 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. | User Experience |