Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
Low-code Application Development
Case Management
24.1.1 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A19066 | 857213 | Corrected process model export | Exporting a process model to an external format such as XPDL or BPEL was generating an empty export.xml file. This was traced to an error in checking the type of the parameter sResultXML, and has been resolved. | Case Management |
| INC-A21365 INC-A15775 |
842665 828072 |
Failed status correctly announced in BPNotes | JAWS was not announcing Failed status in the pzBPNotes section. This was traced to a missing focus event for the icon and has been resolved by replacing the Skipped and Failed label with a button to display pyTempText instead of the smart tooltip in the pyBPNotes Section. | Case Management |
| INC-A23925 | 865644 | Improved security for potential cross-site scripting | Cross-site scripting protections have been updated for the case type rule name. | Case Management |
| INC-A27598 | 846860 | Attachments documentation updated | The documentation for Extension points and supporting Rules for attachments has been updated to specify that when using pzMultiFilePath control along with pyMaxDragDropAttachSizeMB setting, it is required to have section pzAttachFileDDFileList in the UI. | Case Management |
| INC-A28485 | 865665 | Updated handling for pyFlowData clipboard with Tree Navigation | When using TreeNavigation7/ TreeNavigation in screenflow, navigating the case generated clipboard errors from pyFlowData. This has been resolved by updating the parameter handling in pxShowSubFlowData and adding the local variable flowStepPage. | Case Management |
| INC-A28980 | 848773 | Updated logic for SaveAllAttachmentsDD | When using an Attach File button configured to call the pyAttachContent local action followed by a refresh of the current section, the optimistic locking refresh message was not shown as expected and the transaction committed stale data to the database. The section contained a table to display the attachments based on a property that refers to D_AttachmentList, and investigation showed that the file upload component pzSaveAllAttachmentsDD was updating the pxUpdateDateTime property to currentdatetime. This was traced to previous work done in pzSaveAllAttachmentsDD, and has been resolved. | Case Management |
| INC-B11685 | 868348 | Pulse notification link description read by JAWS | When a JAWS user selected the notifications link on the main navigation menu using the keyboard, the notifications that were listed in the sub-menu were not read. This has been resolved by changing the role type to component/widget and the value to Link in the pzShowNotificationDefaultWrapper section. | Case Management |
| INC-B1330 | 853746 | Display customized error messages on attachment widget | Support has been added to show customized error messages on the attachment widget if the upload fails. The following activities have been updated: CallVirusCheck - to include MessageOnUploadFailure parameter pySaveFileContent - to include MessageOnUploadFailure parameter pzUploadAndSaveFile [Data-WorkAttach-File-Temp] - updated to send a parameter MessageOnUploadFailure to messages pyVirusScanFail / pyUploadFailed |
Case Management |
| INC-B147 | 868230 | Handling added to avoid incorrect cover count value | While working on and resolving child cases, a validation error on screen was intermittently causing the pxCoveredCountOpen value to be decremented by one. Handling has been added to address this issue and maintain the correct count. | Case Management |
| INC-B1539 | 857414 | Corrected multiple SLA instances after problem flow | Given a screenflow which had a flow level SLA defined, if an error was encountered when trying to enter the final assignment step and the SLA was started, the SLA did not reset when the issue was fixed and the case restarted using the Restart flow action. After restart, the system created an additional entry for the SLA problem flow while not removing the old SLA entry. This has been resolved by updating the flowfua flowmethodbody function so that if the pyCompanionFlow property is not empty on pxFlowPage(currentFlowpage), the SLAtoUse variable will be set to null to avoid the creation of multiple SLA queue instances. | Case Management |
| INC-B15400 | 866421 | Work-Cover-SimpleCase updated to use ResolveAndCloseCase | Cases were not being cleaned up as expected when using the Resolve Case action in the Actions menu. Investigation showed the flowaction was calling the UpdateStatus activity, which updates the resolution status but does not clean up the open assignments. This has been resolved by updating the case wide action in "Work-Cover-SimpleCase" case type(pyDefault) from pySetStatusResolved to pyResolveAndCloseCase. | Case Management |
| INC-B18712 | 870678 | Aria-labels updated for icons on Case Type Questions View | When creating a case type as a questionnaire, some icons were missing the accessible helper text aria-label in the edit/add questions view of App Studio. This has been resolved by updating the helper text value defined in the pzEmbeddedSurveyQuestion and pzSurveyQuestionTemplate sections. | Case Management |
| INC-B3565 | 858161 | pxIconShowReopenScreen rule deprecated | The Show Reopen control (pxIconShowReopenScreen) was generating a 403 security alert for an unregistered activity. As there are workarounds and other controls available which can be used to achieve the same functionality, the pxIconShowReopenScreen control has been deprecated. | Case Management |
| INC-B4211 | 865672 | Improved performance for GetAssociatedTags | The report definition pyGetAssociatedTags had a performance warning. This report uses a join on the "Data-Social-Tag" class with the "pxLinkedRefTO" column of the "pr_link_work_tag" table, but no index was being used. This has been resolved by adding an index to the table pr_link_work_tag for the columns pxLinkedRefTo and pxLinkedRefFrom. | Case Management |
| INC-B4796 | 857203 | Repaired Disqualify this action from bulk processing | After update, using "Disqualify this action from bulk processing" was not working. This was an inadvertent side effect of work done to the pzPreBulkProcessModal activity to consider context, and was caused by the pyGetRelevantActions activity hardcoding the class as Work- when adding the Transfer Assignment flow action. This has been resolved by removing the hard-coding and modifying the pzPreBulkProcessModal activity condition to check the hierarchy of the class. | Case Management |
| INC-B4827 | 857867 | GetStageList activity updated for improved backwards compatibility | After upgrading from Pega 7 to Pega Infinity '23, using the activity method@pxExecuteAnActivity(CaseTempPage,"pzGetStageList") to get a case stage list did not return all of the stages defined in a case type as expected, but instead current stages were skipped and stages were returned without the case current stage. This was traced to a difference in handling due to the introduction of the pyIsInitializationStage property in Pega 8 which is used to retrieve the stages list. In order to improve backwards compatibility, the 'when' condition param.skipCurrentStage==true has been added in step 7 of the pzGetStageList activity to check if the current stage needs to be skipped. | Case Management |
| INC-B4850 | 868345 | Accessibility added for selected radio button on Question Page | When navigating the 'questions' with a screen reader, the user was not made aware of their selected radio button once they've completed the action. This has been resolved. | Case Management |
| INC-B5511 | 855877 | Invalid file uploads correctly removed from server | When performing a file upload through the profile picture on the user portal configured on Theme Cosmos, the file was uploaded to the server's temporary location despite failing validation and throwing an invalid file error message on the screen. This has been resolved by passing the necessary parameter as true to the uploadFile function to remove the invalid file from static content storage once the file information is read. | Case Management |
| INC-B597 | 865829 | Corrected reassignment issues for flow with dash in the name | Routing cases or assignments was not working correctly if the flow name contained a dash "-" character. This was a missed use case for SaveAs, and has been corrected. | Case Management |
| INC-B7407 | 871129 | Corrected reference for child cases in collapseModal function | Creating a child case in a modal window and then deleting or minimizing it before finalizing it caused an incorrect reference to be used for other actions, leading to other child case confirmations being displayed with an unexpected size and placement. To resolve this, an update has been made to set a value for the variable _openCaseOnCreate in collapseModal function. | Case Management |
| INC-B8440 | 860653 | Link attachment handling updated for Constellation | The save timestamp was modified by the attachURL activity while adding a link as an attachment, causing an error when the timestamp did not match the eTag. To resolve this, a condition has been added to the skip saveAttachment activity in the AttachURL activity if the case is Constellation. | Case Management |
| INC-B8651 | 863958 | Updated createdBy field handling for bot attachments | When a case was created from an email with an attachment, attempting to check the attachments section showed the file but indicated its status as "Loading..." and the attachment was not accessible. Investigation showed the DX API response for get attachments did not contain createdBy and createdByName for files which were attached by the system/bot. This meant the files were not accessible as the Attachments widget link to download the attachment is based on those two fields. To resolve this, an update has been made to set the createdBy and createdByName fields in the DX API response when the attachments are attached by system/bot. | Case Management |
| INC-B9875 | 863568 | Ensured duplicate key exception for customized GenerateID | After upgrade, a customized version of the GenerateID activity reused an existing ID and overwrote an existing case. This scenario did not generate a duplicate key exception as expected during the case creation process (AddWork), which was a behavior change from Pega 7. This was traced to a difference in handling for newObject value, and has been resolved by updating the RecalculateAndSave activity to set newObject to true if pzInskey is not present on the work object. | Case Management |
Cloud Services
24.1.1 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B8226 | 859446 | Updated DDL generation to remove view comments | After creating a custom package and installing it to a higher environment, the DDL for automatic Installation did not work in DB2. Investigation showed that if a view is created prefaced with a comment, DB2 will return that comment as well when the view's select query is requested and the export process will include that comment in the metadata. There is a step in the export to check that the select statement includes a "create view as" statement at the beginning, and if it is missing, it is appended. This causes an invalid query as shown in the schema export. This has been resolved by filtering comments out of the view statements. | Cloud Services |
Conversational Channels
24.1.1 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B16449 | 867463 | Updated HistoryIndex property handling for migrated cases | After update, emails were not being properly attached if the related case was created before the update. This was an issue with the method used to set the pyHistoryIndex property on the workPage, and has been corrected. | Conversational Channels |
| INC-B17182 | 872741 | Added explicit websocket close for Robot activities | Robot activities were not being invoked by data pages after a prolonged (several hours) period of working stability. This was traced to the websocket sessions not getting closed properly, causing the connection limit to be reached. This has been resolved with an update to explicitly close the session after the message is received from the message service. | Conversational Channels |
| INC-B4724 | 860569 | Updated CTI connection handling | A user was intermittently not automatically connected to the Computer Telephony Integration (CTI). This has been resolved with an update to add the element to activesub map if activesubscriptionnew is undefined. | Conversational Channels |
| INC-B949 | 858122 | ParseReplyMail regex updated | When a plain text email reply matched the regex from ParseReplyMail in the body, the message was truncated unexpectedly from that point. This has been resolved by modifying the regex. | Conversational Channels |
Data Integration
24.1.1 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A12208 | 865635 | Added null pointer handling for external database table mapping | A runtime error was generated while trying to map PEGA class with view in an external database using a JDBC connection. This was traced to a null pointer exception caused by data.internal.access.mssql.SQLGeneratorMssql.getSchemaName, and has been resolved with an update which handles the null pointer exception and logs an informative error message indicating the absence of the default schema. |
Data Integration |
| INC-A13499 | 838929 | Added condition to prevent incorrect rule creation on Index class | In some scenarios it was possible to create declarative rules on the Index class. This is not an intended usecase, and a condition has been added to prevent this process. | Data Integration |
| INC-A13631 INC-A10142 |
851005 846591 |
Additional tools added for diagnosing BLOB issues | Additional tools added for diagnosing BLOB issues In order to assist with diagnosing corrupted BLOB issues which are not recoverable with the PegaCBU tool and fixBLOB utility, additional DSS settings have been added to the Pega-Engline ruleset with default value of false: - validateOrphanPageListIndexEncoding: When true, avoid adding orphaned page list indexes which are referred from a page and print DirectStreamEncoderV7SkipTargetedEncoding. - skipTargetedEncoding: when true, skip targeted encoding. Try to re-encode if any exception is encountered during encode process and correct the issue only if the debug logger StorageStreamCommonImplDiagnosis is enabled and the DSS has the value true. Log additional information only when DirectStreamEncoderV7Diagnosis debugger is enabled. |
Data Integration |
| INC-A16756 | 871238 | Added handling for pxUpdateRecord failure during save | Intermittent issues were seen with pxUpdateRecord failure when attempting to update the database table record by using a savable data page, causing cases to need reprocessing. The exception "Job Scheduler [ClaimCreation2] activity [CreateCC] execution marked as failed with message [pxResults (class:" was generated. This was traced to an invalid value for a PageList, and has been resolved by adding a retry mechanism along with a check for property mode before generating an InvalidParameterException. | Data Integration |
| INC-A19931 | 862363 | Handling added for tenant URLs registered with Microsoft Azure | The Multi-Tenant Hash IDs generated by the Open ID Connect Setup contained wild cards which were disallowed by Microsoft Azure during the URL registration. This has been addressed with an update to remove the '*' and '!' characters from the redirect URL based on the boolean DSS setting "ignoreAsteriskAndBangSymbolInMT". | Data Integration |
| INC-A21896 | 860641 | Extra logging added for session timeout issues | Additional diagnostic logging has been added to trace changes to the redirectURI in order to investigate issues with session timeout not working and reporting "Redirected too many times". | Data Integration |
| INC-A22151 | 865646 | Support added for multiple apostrophes in the name fields | If more than 1 apostrophe was given in the First name and Last Name parameters, every subsequent apostrophe after the first was getting converted to "'".This has been resolved by updating pzhandlebars_helpers.js to prevent the ANCI format. | Data Integration |
| INC-A23729 | 845172 | Dev Studio security updated | Cross-site scripting protections have been updated for Rules and Ruleforms in Dev Studio. | Data Integration |
| INC-A2376 | 864231 | Passivation handling updated for data page serialization | A very high count of ClassCastException errors were generated in the Pega Diagnostic Center (PDC) when trying to passivate an editable D_GetRequestType data page which has a backlink to an autopopulated property on a read-only datapage. This has been resolved. | Data Integration |
| INC-A24588 INC-A28040 |
853647 862884 |
Corrected clipboard context for append and map | The mapping of a page list was incorrect when placed under a single page. This was traced to an error in the way the clipboard context was being formed in case of append and map to steps, and has been resolved by updating the order in which clipboard context is saved. | Data Integration |
| INC-A25591 | 840671 | Support added for migrating Oracle optimized index with Primary Key | When upgrading from Pega 7 to Pega Infinity '23, the error message "ORA-00955: name is already used by an existing object" was generated. This can occur when Oracle data pump is used to move the schemas in earlier versions of Oracle 18 or 19, and is caused by parallel threads optimizing the primary key (PK) index while another thread is simultaneously adding the PK index, and has been addressed by adding support for this edge case. | Data Integration |
| INC-A26110 | 868318 | Corrected extra column label incorrectly shown | A delegated data type was unexpectedly displaying the "Delete" column header label. The delete functionality was correctly not shown. This has been resolved by updating pzrecordEditor to have the same condition for the Delete label as for the Delete icon. | Data Integration |
| INC-A26215 | 869993 | Handling added for SP Rebuild Indexes on database name with dashes | When databases are named with dashes as per Microsoft Azure recommendations, executing the stored procedure sppr_rebuild_indexes generates the error "Unable to execute sql query: EXECUTE PegaRULES884.sppr_rebuild_indexes 'stats'; com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '-' ". This has been resolved with an update to handle the stored procedure execution error when database objects containing dashes ‘-‘ in their names are encountered. | Data Integration |
| INC-A27098 | 868099 | Corrected UI Accessibility_ Filter application with ESC key | When using a table list, clicking on the filter to investigate the required value and hitting ESC to exit resulted in unexpectedly applying the filter as if "Apply filter" had been clicked instead. This was traced to the filter popover passing 'reason' as an empty string in this scenario, and this has been resolved by adding a check. | Data Integration |
| INC-A2788 | 811938 | Corrected header layout accessibility | JAWS was not reading Heading tags for the Param.ShortDescription value in pzDataTypeKeysAndDescription. This was traced to the ShortDescription being set as a label instead of part of the dynamic layout header, and this has been resolved by modifying the section to include the header with h1 tag. | Data Integration |
| INC-A28634 | 865670 | 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-B1010 | 864071 | Added catch for notification thread exception | A notification configuration was working in the development and production environments, but was not working in the pre-production environment. Investigation showed there was an uncaught thread exception, and handling has been added to resolve this issue. | Data Integration |
| INC-B10336 | 870637 | Additional logger added for archival exclusion | Additional logging has been added to assist with diagnosing issues with ABAC security configuration filter conditions which cause classes to be mapped to a different table while running queries using nativeSQL. | Data Integration |
| INC-B11885 | 862429 | Added handling for system pulse race condition on startup | A newly scaled-up batch node did not pick up new Next Best Action rules. This was traced to a race condition, and has been addressed by reloading the class map into the system pulse module. | Data Integration |
| INC-B1193 | 862269 | Corrected exception generated when expanding a property | Datapages were not working correctly, causing case creation to fail. This was traced to a ReadOnlyException that was generated when opening a workobject using ReadOnly Datapage, and this has been corrected. | Data Integration |
| INC-B12438 | 868450 | Updated country codes | In order to meet ISO-3166-1 standards, the following country codes have been added: AX ALA Åland Islands BL BLM Saint Barthélemy CD COD Congo (the Democratic Republic of the) CW CUW Curaçao GG GGY Guernsey IM IMN Isle of Man JE JEY Jersey ME MNE Montenegro MF MAF Saint Martin (French part) PS PSE Palestine, State of The code for Romania was previously incorrectly listed as ROM. This has been updated. RO ROU Romania |
Data Integration |
| INC-B1278 | 869006 | File Listener retry logic updated | File Listener was not moving the file to the error folder as expected after failing to read it three times, but instead was continuing to retry. This has been corrected with an update to properly set the processing status error message so the process continues as configured. | Data Integration |
| INC-B13217 | 868313 | REST connector socket timeout made consistent | The socket timeout value given on the REST connector rule form was not consistently applied, causing the observed timeout to exceed the configured timeout in certain situations. This was due to the timeout being calculated as a max time between packets, and has been addressed by setting the timeout to be a fixed value. | Data Integration |
| INC-B13561 | 868295 | DSS added to control descendant class lookups | In some use scenarios, system performance can be severely impacted by thread blockage around ClassMapImpl when there are saves of the Rule-Obj-Class records and Rule-ClassMetadata records linked to the data tables. To address this, the DSS useClassMapForDescendantClasses has been added to allow modifying the behavior of descendant class lookups and use the Classmap in memory instead of the Database. The default for this DSS is false, which directs lookups to use the database. | Data Integration |
| INC-B14091 | 872861 | Logging added for terminate requestor | Additional logging has been added for the terminate requestor function in order to assist with diagnosing problems where the queue processor becomes stuck with "Ready to process" items. | Data Integration |
| INC-B14380 | 864599 | Corrected handling for Malaysian date/time | When using the ms_MY locale in an Operator profile, setting the date/time or performing a section refresh generated an error indicating the date/time was not valid. This has been resolved by adding formatting for the values PG (pagi) and PTG (petang) for Malaysian (ms_MY) uses. | Data Integration |
| INC-B14835 | 869413 | Error handling updated for connections using setClientID | The error "ConnectorException: Couldn't establish connection: Method setClientID not permitted" was generated when attempting to establish a connection using Connect-JMS. This has been resolved with additional handling for setClientID() runtime exceptions. | Data Integration |
| INC-B15023 | 870820 | Corrected handling for editable list with recursive embedded page list properties | When presenting an editable list in Constellation that was created from a case type with an embedded page list property which itself contained another embedded page list property, accessing the form to edit a parent list entry to add, remove, or modify entries within the child list intermittently caused rows from the child list to disappear. This was traced to the interestPage handling for the modal dialog and has been corrected. | Data Integration |
| INC-B1548 | 850875 | JavaBeanViewer updated to remove browser invocation | In order to ensure potentially sensitive information is not accessed without authorization, the 'allow invocation from browser' option for rule "RULE-OBJ-ACTIVITY DATA-ADMIN-IS-JAVABEANVIEWER" has been disabled. | Data Integration |
| INC-B1584 | 864673 | en_PH locale added | The en_PH locale file has been added to support the Philippines. | Data Integration |
| INC-B16409 | 869692 | Logging added for diagnosing socket timeout issues with S3 | An IOException was frequently generated when loading bulk data all at once, leading to corrupted clipboard data and a parsing exception. To assist in diagnostic work, logging has been added to track SocketTimeOut and Connection Time to Live. | Data Integration |
| INC-B17158 | 867153 | Corrected duplicate data page from API | When using the v2 data_view/{data_view} API, the GetDataPage step was making two copies of the page. This has been corrected. | Data Integration |
| INC-B1736 | 866063 | Updated Pega Cloud File Storage (PCFS) handling for duplicate attachments | When migrating attachments to Pega Cloud File Storage (PCFS), attempting to move a file with a duplicate name failed. This has been resolved by updating the pzuploadattachment activity to handle duplicate attachments. | Data Integration |
| INC-B1756 | 872607 | Updated Purge query handling of clipboard | The purge function was not working as expected. This was traced to queries in one of the steps in the purge activity not being handled correctly Oracle version 19 and passing empty strings as rulesetlisthashes, and has been resolved by improving the Select purge query method of storing the result to clipboard. | Data Integration |
| INC-B18729 INC-B17679 |
870906 871569 |
Diagnostic logging added for PegaArchiver | Additional logging has been added to assist with diagnosing issues around excessive run time for the Archive function. | Data Integration |
| INC-B19847 | 871877 | Additional logging added for Lake Gen 2 configuration exceptions | Logging has been added to collect the HttpResponse exception generated when attempting to configure a Microsoft Azure Data Lake Gen2 repository. | Data Integration |
| INC-B20863 | 871715 | RequestorLockException logging updated | The logging level for RequestorLockException has been changed from infoForced to debug. | Data Integration |
| INC-B3098 | 855804 | Corrected table edit for parameterized datapage | After creating a table view with a read-only data page, adding a column in the edit view and then editing that column in the table resulted in the new value being replaced with the old value after clicking outside the area. Investigation showed that the fetchData function of DataAPI did not have the dataViewParameters parameter when using a table sourced from a parameterized datapage, causing the call to fail and the table to display the old values. This has been corrected. | Data Integration |
| INC-B3711 | 858655 | Modified flow save functionality | Clicking the save button on any screen in the Quote Flow that had a blank required field was triggering the client side validation even though the flow was not submitted. This has been resolved by modifying the save functionality so the validation error is only triggered if there is an attempt to continue without completing required fields, and saving is permitted at any point in the application process, including the Convert Stage. | Data Integration |
| INC-B5284 | 859687 | Corrected thread pool not terminating at shutdown | The Pega application was not shutting down gracefully following Apache Tomcat shutdown. This was traced to a thread pool that generated non-daemon threads not closing properly, preventing the JVM from termination. This has been corrected. | Data Integration |
| INC-B5709 | 859359 | Corrected flow rule edit 'when' logic | The "configure view" button was unexpectedly being offered in Dev Studio after reopening a submitted screen flow, and clicking on it generated the error "Only one modal dialog can be opened at a time". This was traced to an error in the 'when' rule logic for the property panel of assignment pyOutcomes which caused it to become initialized in the flow rule form when it should only be initialized in Case Designer. This has been corrected. | Data Integration |
| INC-B6098 | 861337 | Corrected validation behavior for append and map to step | When a new data transform was created with save as, an existing validation removed elements if a new child element was added to an append and map to step. This was a missed use case, and has been resolved with an update to the 'when' condition for the JSON data transform appendMapTo validation rule such that all elements remain intact when a new child element is added. | Data Integration |
| INC-B6471 | 856973 | Updated DateTime control for locale th_TH | When using the DateTime control for the th_TH (Thai) locale, attempting to select 29/9/2567 (2024) resulted in the correct property in the clipboard value after Save, but the UI displayed 28/02/2567 instead of 29/02/2567. This has been resolved by updating pzpega_ui_formatDateTime to improve the calculation of isThaiSolarAndLeapYear and also consider 28th Feb and 1st March. | Data Integration |
| INC-B6802 INC-B19202 |
866913 872004 |
Corrected AccessGroupSwitch handling | Attempting to open a case belonging to another application without manually switching to the application generated a Login screen and the case was not opened. This has been resolved by updating the handling for the application switch cookie paths. | Data Integration |
| INC-B6997 INC-B11585 |
858319 861417 |
Correction for en_ZA currency separator | When using the “en_ZA” locale with boolean properties mapped to currency control on screen, the decimal separator “,” was displayed as “.” at runtime, and refreshing the screen increased the value by adding a zero. This was traced to the java 8 version picking up "." instead of "," even though the platform engine layer was using ",". Due to this inconsistency the additional zero was added for every refresh. This has been resolved by updating the handling for the en_ZA currency conversion issue in JDK 8. | Data Integration |
| INC-B730 | 864822 | Corrected code for dynamic operator time zone | After configuring a date control in a grid, attempting to change the operator timezone resulted in the values appearing in the filter in GMT format. This has been resolved by updating the code for Central European Standard Time (CEST) to be Central European Time (CET) as CEST represents Summer Time (Daylight Time). | Data Integration |
| INC-B753 | 856087 | Datefield maintained correctly during XML parsing | reverted?'0101' was appended to the date field while importing an XML file, making the datefield invalid. Investigation showed this was caused by the Apply-Parse-XML step being called on the same page multiple times, and occurred when multiple files were uploaded and processed at the same time. The issue was not seen when the Parse XML rule was run alone. This has been resolved with an update to ensure the correct parsing. | Data Integration |
| INC-B7715 | 859124 | Accessibility corrected for using enter key to edit table | When a keyboard user navigated to a row in a delegated table and hit the enter key to edit the inputs, a new line was created instead. This has been resolved by modifying the section in such a way that pressing the enter key will edit the existing record rather than creating a new row. | Data Integration |
| INC-B791 | 864556 | Updated Archived-shared records handling | Cases in Archived-Shared status were not being cleared from the pr_metadata table, increasing the table size. Investigation showed that when using the pxLinkAttachmentToCase activity, attachments were only marked as Archived-Shared status when they occurred in the same batch. This led to marking the shared attachments as regular attachments when they were not part of same batch while running the archival jobs, and caused the shared attachment to only be accessed by the case that was archived, leaving the unarchived case not able to access it. This was a missed usecase, and has been resolved. | Data Integration |
| INC-B7923 INC-B2525 |
860267 857095 |
Corrected authentication request at startup | After update, the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS PZGETALLCHANNELS" appeared at startup. This was caused by an unneeded attempt to authenticate and has been resolved. | Data Integration |
| INC-B8067 | 871688 | Corrected handling for generating nested JSON elements | When using a data transform to create a REST connector in clipboard and subsequently transform it into a JSON text for Amend to Map, the JSON data transform did not work in cases where the clipboard structure was more complex (for example a pagelist containing a page list). This has been resolved by updating the logic of the mapping order of elements between clipboard and JSON. | Data Integration |
| INC-B9025 | 870966 | CreateConnection correctly passes JNDI credentials | Connection issues were seen when authentication was enabled on the JMS broker side and JNDI credentials mentioned in the JNDI server rule form were not being passed as expected. This has been corrected by updating the activities called in the JMS explorer functionality. | Data Integration |
Decision Management
24.1.1 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A19934 | 833082 | DecisionTable made consistent after eligibility column removed from optimized strategy | After an entire column of a decision table referenced in an eligibility condition was removed because the validation was no longer required, the globally optimized strategy was not returning offers and behaved inconsistently. Investigation showed that Trigger_NBA_TopLevel had the correct results, however GOS_TOP_Level had results only in Normal execution results and not in Optimized execution. While there was a workaround of restoring the deleted column, an update has been made for the DecisionTable to take "Primary" from the calling Strategy to correct this issue. | Decsion Management |
| INC-A20027 | 868327 | Predictive model monitoring updated | Campaign runs were failing, indicating issues utilizing data from predictive models. This was traced to issues in retrieving data from the clipboard, and has been addressed with an update to gather the required properties at design time instead of runtime and by refactoring predictive model monitoring to use the static data. | Decsion Management |
| INC-A24708 | 859853 | Updated partition handling to resolve thread contention | A contention lock was occurring in the Postgres database after a campaign run in the second wait dataflow. This has been addressed by improving the partitions assignment mechanism including shuffling. | Decsion Management |
| INC-A25749 | 840886 | Performance improvements for Value Finder | Very large runs of Value Finder were becoming stuck, generating errors, and causing the dataflow heap to be overwhelmed. To address this, updates have been made to improve the performance and memory requirements of the Value Finder activity including reducing the number of columns for customer group discovery, improvements to core group discovery algorithm, decoupling stage statistics and customer group discovery, down-sampling for customer group discovery, and minor improvements to the Value Finder simulation post-processing activity. | Decsion Management |
| INC-A28311 | 858457 | Bind markers correctly used for TTL | When the time to live (TTL) was configured through a property, the related prepared statement issued by the Decision Data Store (DDS) dataset was not using bind markers and specified the actual TTL value in the statement. This caused unnecessary duplicate prepared statements in Cassandra and led to performance issues. This has been resolved by updating the Decision Data Store software development kit to a version that corrected bind markers used for TTLs. | Decsion Management |
| INC-A29620 | 849932 | Updated Interaction History error logging to assist debugging | The Decision Funnel simulation returned empty reports. Investigation showed that the data flow used to synchronize simulation data to the database was failing due to an incorrect Interaction History (IH) configuration. When the IH configuration contained duplicated entries, the Visual Business Director (VBD) browse failed with a cryptic stack trace. To resolve this, the IH Data Transform configuration problem will be properly logged so the Decision Funnel VBD -> database synchronization data flow is evident and can be restarted if needed. | Decsion Management |
| INC-B11219 INC-B15312 INC-B18598 INC-B18714 |
861555 864948 870267 870245 |
Decision simulation batch size made configurable | Data migration was failing at the export phase while processing the pyRemoveDuplicatesFromSimulationDataSet data flow run. This was traced to a Cassandra read and write timeout exception, and has been resolved by adding a batchable feature to the data set with size configured with a prconfig setting. Create the below DSS only on Production: * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/deduplication/batchsize - Setting value: 50 * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/deduplication/requestors - Setting value: 1 Create the below DSS on both Production and BOE: * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/requestors - Setting value: 3 * Owning ruleset: Pega-Engine - Setting name: prconfig/dnode/dds_partitioner_class/default - Setting value: com.pega.dsm.dnode.impl.dataset.cassandra.TokenRangePartitioner * Owning ruleset: Pega-Engine - Setting name: prconfig/dnode/cassandra_use_extended_token_aware_policy/default - Setting value: true |
Decsion Management |
| INC-B12153 | 868801 | Corrected and improved GOS report generation | Attempting to download the globally optimized strategies (GOS) report was not working. This has been resolved with an update to ignore startDate and endDate when pyIsPropositionActive is not Date, show a better error message when a SSA doesn't have a direct component, and generate the GOS report faster. | Decsion Management |
| INC-B13604 | 864413 | Improved validation logic for revisions | Clicking on "Current Revision" from the Revisions Management landing page caused an extremely large requestor clipboard page of over 2.7GB to load, leading to performance and memory issues. The size of this page was a result of the system handling more than 200 ChangeSet requests in one revision along with detailing the validation checks for 8500 rules. This validation check is no longer needed due to current handling processes for the change requests, and has been removed to improve performance and the clipboard page size. In addition, pagination logic has been added for displaying the change requests in a revision. | Decsion Management |
| INC-B13759 | 866437 | Corrected handling for click of Operator image | After creating a case and routing it to a work queue, clicking on the operator image refreshed the case and no content was displayed on the UI. This was an unintended side effect of work done to correct an accessibility issue with the operator icon, and has been resolved by updating the div tag handing for role="img", tabindex="0" in the pxInitials control. | Decsion Management |
| INC-B14031 | 863716 | Corrected event strategy logic for HandleResponses | After update, the pxHandleResponses dataflow was generating a different number of output properties in its event strategies. Investigation traced this to the updated configuration of the pxWaitForResponses and pxWaitForResponseExpiry strategies; the addition of the new property pyOutcomeWeight had the unexpected result of clearing the state of the pxHandleResponses data flow run, where both Event Strategies are used. This has been resolved by correcting the event strategy logic to add the property while preserving the data for pxWaitForResponses and pxWaitForResponseExpiry. | Decsion Management |
| INC-B14451 | 866705 | Corrected ADM snapshot truncation | The data import case in Data Migration was failing with a "Rule not found" error. An audit trail showed there was a failure in the ADM datamart table truncation prior to ADM data import; this has been resolved with an update to only truncate the ADM snapshot data if ADM import is enabled. | Decsion Management |
| INC-B1476 | 857423 | Instruction text rendered in a Questionnaire page | After developing a Questionnaire with some introduction text on each page, the introduction was not shown when running the Questionnaire. This was due to difference in handling for the Question page in Constellation, and has been resolved by adding a new parameter to the pzQuestionPageScr flow and setting it when saving the Questionnaire case type so the introduction text is included. | Decsion Management |
| INC-B14837 | 868054 | Scenario Planner displays top N for Projected Reach | Scenario Planner was displaying only the top 1 for Projected Reach, causing the Scenario Planner simulations to be off when inbound slots have multiple offers per slot, not just the top 1 in rank. This has been resolved with an update to ensure the top N actions are considered for Scenario Planner. | Decsion Management |
| INC-B15053 | 864771 | Updated logic for ADM case resolution | When there were multiple Adaptive Decision Manager (ADM)-based predictions in a case type, some decisions made by predictions were missed when the cases were resolved. Investigation showed that during case resolution, the make decision and set response call were concurrent and could result in some data loss. This has been resolved by changing this to sequential queue processing. | Decsion Management |
| INC-B15096 | 872133 | Batch sizing made available for Cassandra queries | When a Decision Data Store (DDS) dataset BrowseAllRecordsOperation was executed there was no method to pass the batch size to use for the Cassandra page size. This caused the default datastax driver page size of 5000 to be used in queries, potentially leading to out of memory conditions for datasets with large records. To address this, the feature class BatchableFeature has been added to the data flow for BrowseAllRecordsOperation to allow limiting the number of records received by each Cassandra query per dataflow run. | Decsion Management |
| INC-B15704 INC-B18598 INC-B20996 |
865576 870175 871633 |
Truncate operation improvements | In order to support a variety of different database engines and avoid truncation failures of the pyADMFactory data set during the data migration import process, the implementation of the truncate function has been updated to better handle external and internal tables and tables mapped to more than one class. | Decsion Management |
| INC-B15792 | 872386 | Updated handling for Customer/DSM aliases | If the strategy changed the alias Customer to a Decision Strategy Manager (DSM) page and tracked the original Customer page for resetting later, during the enrichment of aliases, if Customer was included, it was reassigned to a DSM page and the previous page (now the DSM page set in step 1) is tracked again. As a result, the oldAliases list contained both the original Customer page and the DSM page from the initial change. When resetting the aliases, Customer remained associated with the DSM page from step 1. Consequently, this alias was visible to the parent activity, leading it to incorrectly use the DSM page for Customer instead of the intended original page. To address this, the reset order has been reversed to the alias order to ensure the correct page on the final reset. | Decsion Management |
| INC-B16495 | 867488 | ADMPredictorsFilter limit increased | Model predictors were not properly populated in the predictors monitoring screen. This was due to the limitations in the pyADMPredictorsFilter Report definition which was set to retrieve a maximum of 500 records at a time. To resolve this, the limit for maximum records to retrieve in pyADMPredictorsFilter has been increased to 99999999. | Decsion Management |
| INC-B17441 | 868570 | Resolved permission error in pyProcessCaseEvents | The queue processor encountered report definition permission issues related to process AI calling a Strategy, resulting in an exception while invoking the Interaction History summary top-up queries. This was related to the handling of the complex field type used by the context page copy that is sent as an input page to the prediction strategy, and has been resolved with the addition of an extensible 'when' rule to allow skipping the desired properties while executing prediction. | Decsion Management |
| INC-B17807 | 870558 | Corrected file data set Preview file filter | In any file type data set, selecting Preview File next to the export showed a different file than the one expected. This was traced to Preview in the file data set picking the first file in data set directory even if it did not match the file pattern, and has been resolved with an update to correctly filter out files not matching the pattern even if they are in the same directory. | Decsion Management |
| INC-B17974 INC-B21582 |
871406 872100 |
Corrected button access for decision revision management | Attempting to remove treatment attributes from Action Decision Data was not working due to an incorrect state for Add field and other buttons in the form tab of the decision data rule. This has been corrected. | Decsion Management |
| INC-B20239 | 872836 | MVEL library deprecated and replaced for PropositionFitler explain mode and simulation mode | Simulation runs were not returning counts in CDHSample even though the counts were populated as expected if the proposition filter was run individually. This has been resolved by replacing the MVEL library with a simple expression evaluator for PropositionFitler explain mode and simulation mode. As part of this work, the DecisionDataExpressionEvaluator class has been deprecated and will be removed in a future release. This class uses MVEL library and is only used in PropositionFilterTemplate Rule-Utility-Functions. | Decsion Management |
| INC-B20390 | 872536 | Updated handling for recursive Prediction references | Page type predictor values were not being displayed on the prediction widget. This was traced to a configuration where Prediction execution could result in infinite recursion for complex data structures if case reference and data reference properties referred to case and data classes containing case predictions. This has been resolved with an update which sets the useOptimized flag to false so that prediction execution considers Clipboard page and not just DSMClipboard page. | Decsion Management |
| INC-B21171 | 871484 | Session and message usage metrics enabled | CDH Session and message usage metrics were not enabled in any environment. This was traced to the channel name or application name being created with the character '-'. While doing context switch, the App name was captured and a Page Group created with Subscript as the name of Application. This caused the app name to be "-", which caused the issue to the form page group. To resolve this, an update has been made to strip special characters from the string. | Decsion Management |
| INC-B2228 | 872187 | Decision Funnel query activities log proper stack trace | In order to improve debugging, Decision Funnel query activities have been updated to allow logging a stack trace. | Decsion Management |
| INC-B4317 | 860364 | Updated visibility condition for Pulse | In a configuration where internal Pulse and external Pulse messages are displayed separately, if a case was kept open by a user who needed access to only external comments and another user worked on the case in parallel and typed in internal comments, those internal comments were visible to external users. To resolve this, the pyCanPublishC11nMessage 'when' condition has been added in the pzPublishC11nMessage declare trigger rule, and should be set as .pyIsPrivate != true. | Decsion Management |
| INC-B5879 | 861176 | Made DDS availability datacenter-aware | The Data Distribution Service (DDS) SDK version has been updated to enable DDS availability check being datacenter-aware. | Decsion Management |
| INC-B6548 | 857384 | IH Summaries made resilient to Stream C2K migration | In some cases following C2K migration of Managed Streaming for Apache Kafka (MSK) to the Instaclustr environment, Kafka offsets were being reset to 0. As Stream-based Interaction History summaries and event strategies rely on source offset, this may lead to records being incorrectly ignored after Kafka migration. To resolve this, special handling has been introduced to summaries and event strategies that detects Kafka change to ensure records are correctly processed after the migration. | Decsion Management |
| INC-B6752 | 857773 | Updated handling for Decision Data Store table consistency level | After changing the Decision Data Store table consistency level to Strong, the dataset operation started failing after restart with the exception "InconsistentTableSchemaException: Table with different schema is already registered in [data] table group". Investigation showed that when instantiating the DDS data set, the consistency level of the table was retrieved from the schema repository if the table was already registered. To resolve this, an update has been made to use the consistency level from the Data-Admin-DDS-Table record instead of a default value if the table schema is already registered for use. | Decsion Management |
| INC-B7423 | 863672 | Updated handling for reading files from S3 repository | When attempting to read files from a custom S3 repository, the directory was visible but it was not possible to list subdirectories or read the files. This was traced to an issue with access to view files that were created or uploaded by other operators, and has been resolved with an update to the file data set to work with non-explicitly created directories. | Decsion Management |
| INC-B7952 INC-B9183 INC-B9606 |
858479 863013 868670 |
DSS added to control data flows for Data migration pipeline | Data migration processes running in parallel with all data flow runs triggered at once can take some time to complete with high volumes of data (customer samples or interaction history) and may fail with out of memory errors. One way to pace resource utilization is to sequentially run the individual data flows involved in data migration. To that end, the DSS dataMigration/numberOfConcurrentRuns has been made available to set the number of threads per data flow when the migration pipeline is running. Further work is planned for a future release to improve, simplify and stabilize the data migration pipeline. | Decsion Management |
| INC-B8811 | 865039 | Improved backwards compatibility for GOS | While trying to create a globally optimized strategy (GOS), providing the top level strategy and then trying to save the rule generated the error "Optimization failed to parse ".RecoPilotFlag!='Y'" using IL parser because the type CHARACTER is not supported in this context." The type CHARACTER has been deprecated but is still used. In order to support this usecase and maximize backwards compatibility, an update has been made to convert CHARACTER to a string value whenever possible so the GOS will run. | Decsion Management |
| INC-B8855 INC-B12414 |
860354 863028 |
Adaptive Decision Manager (ADM) configuration updates | In order to improve Adaptive Decision Manager (ADM) model migration, updates have been made to batch size, thread count, and partitioning. - Batch size on the ADM Migration data flow has now by default been set to 5 - This batch size is also configurable through the DSS 'decision/adm/service/migration/batchSize' if required - pyADMFactory data set now has a partitioning key defined which will allow the export data flow to run across the tier (as opposed to only on one node) |
Decsion Management |
| INC-B9189 | 860542 | Updated Lz4 jar for Kafka Topics | After update, using Kafka Topic to send and receive messages generated the error "org.apache.kafka.common.KafkaException: Received exception when fetching the next record". This has been resolved by updating the lz4-java version. | Decsion Management |
| INC-B9208 | 862280 | Security updated for edited Pulse messages | Cross-site scripting protections have been updated for editing Pulse messages. | Decsion Management |
Low-Code Application Development
24.1.1 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A24726 | 843942 | Application Wizard security updated | Cross-site scripting protections have been updated for the Application Wizard. | Low-Code App Development |
| INC-A25634 | 868713 | RecordAPI logging added | Additional diagnostic logging has been added to track context and decisions made for the RecordAPI. | Low-Code App Development |
| INC-A30185 | 850455 | Updated handling for masked PII data | After creating a Connect Generative AI rule type with a Mask Sensitive data filter to mask any identified PII data in the user prompt, the response data did not unmask the PII as expected. This has been corrected. | Low-Code App Development |
| INC-B11364 | 868334 | Function pxIsInListOfValues updated for improved backwards compatibility | After update, a function which previously evaluated to true when certain values were empty changed behavior to evaluate to false under the same condition. This discrepancy stems from a change from the previous regex method for splitting the listOfValues to using Apache Commons CSVParser logic. In this particular scenario, this update changed the behavior of the function @pxIsInListOfValues() thereby causing the when rule to return false and thus all the offers were filtered out by one of the proposition filters that used this when rule. In order to support backwards compatibility, an update has been made which will return true when listOfValues is empty and value is blank. | Low-Code App Development |
| INC-B11552 | 864328 | Extension added for custom triage class | After update, the SLA was not being applied to a custom class used for email-based triage cases. Investigation showed the OpenAndLockWork step was failing, causing the process to exit the Establishcontext activity and preventing the ProcessEvent activity from running. To handle this use case, the extension pyCheckAndMigrateInteractionCases_Ext has been added to set the objclass of the email triage case; this defaults to "Work-Channel-Triage" and can be modified as needed. | Low-Code App Development |
| INC-B12444 | 864835 | Corrected chat transcript migration for authenticated events | After update, chat transcripts for older cases were not visible. This has been resolved by updating the migration mechanism used by pyHistory for outbound authenticated events. | Low-Code App Development |
| INC-B13711 | 863550 | Corrected issue with cases license category | The classification of the cases to Dispatch disappeared from the PowerBI dashboard and cases appeared to be wrongly classified as Execution. This was traced to an issue with the cases license category and has been resolved. | Low-Code App Development |
| INC-B15287 | 868503 | Corrected two pyEmails created on OEML cases | After creating a case and sending an email to a customer, the customer reply on the same thread created another pyEmail on OEML correspondence case. This was a missed usecase for "New outbound email" and has been resolved with an update to pzCreateInteractionReply. | Low-Code App Development |
| INC-B16631 | 869695 | Corrected truncated error message text display on hover | When using the Expression Builder and there is an error on the test, the error message was truncated and the full text was not visible on hover as expected. This was traced to an error in the pzEllipsis control, and has been resolved. | Low-Code App Development |
| INC-B19826 | 872415 | Corrected date format issue in Configuration Sets | A configuration type "Date only" used as part of a configuration set was not updated when changed in the Admin landing page. If the default locale was deleted then the change to the date control was recognized. This has been resolved by updating the data transform Pega-Configuration.pzPreAdministrationSave to consider locale while copying the value. | Low-Code App Development |
| INC-B20714 | 872616 | docx4j library updated | Values were not populating in a Microsoft Word template using Pega property references, and opening a document created from a Word Template with Pega property references generated a popup with the message "Word found unreadable content in <File Name>. Do you want to recover the contents of this document? If you trust the source of this document, click yes". This has been resolved by updating the docx4j library. | Low-Code App Development |
| INC-B335 | 861884 | Corrected branch development handling for Production rulesets | After adding a production ruleset to the application definition and access group, a test branch was created and then all rulesets were locked. It is expected that the branch will only be for the top ruleset of the current application, but in this scenario branches were created even for the Production rulesets. When branch development was enabled through the Branch Development Toggle icon on the top right corner of the screen, the Production ruleset was being populated as default. Attempting to change that to some other value reverted back to the Production ruleset value. This is incorrect behavior as Production rulesets should not appear in the list. These issues have been corrected. | Low-Code App Development |
| INC-B3467 | 855565 | Security updated for showGrid | Cross-site scripting protections have been updated for showGrid. | Low-Code App Development |
| INC-B3573 | 857915 | Improved backwards compatibility for decision tables | After upgrading Pega 7 to Pega 8, a null pointer exception occurred when evaluating a decision table. This was traced to the engine rule classes expecting the parameter page in a different format, and has been resolved by updating the @Utilities.pxEvaluateDecisionTable() function to add a new parameter page with the existing data and call the rule engine file for the data transform execution. | Low-Code App Development |
| INC-B6162 | 856162 | DSS added for AllowMissingProperties functionality | A goal seek error occurred after update when using the Property-Map-DecisionTable method when the AllowMissingProperties option was not checked. This was due to the system looking for the property referenced in the decision table and returning false. Beginning with Pega 8, allowMissingProperties must be checked to handle any missing properties in the decision table. This is a change in behavior from Pega 7 where the functionality worked even though AllowMissingProperties was not checked. For better backwards compatibility, the DSS "DecisionTable/ObtainValue/AllowMissingProperties" has been added in the PEGA-RULES ruleset. When true, this DSS will have the same effect as having AllowMissingProperties checked. | Low-Code App Development |
| INC-B6698 | 858695 | CheckFieldSecurity updated to handle custom Transfer Assignment | After update, a Transfer Assignment local action for transferring an assignment to an operator or a workqueue was no longer working and the error "One or more inputs are invalid" was generated. This was traced to work done as part of the page instruction field security which was failing in this use case due to the added pyAssignment page properties on the content copy page, and has been resolved by updating the logic for the pzCheckFieldSecurity activity. | Low-Code App Development |
| INC-B7822 | 860121 | Code added to break infinite loop related to AssignedToMyStaff | Agents were getting stuck suddenly. Investigation showed that this was due to pxAssignedToMyStaff, which when called while listing operators reporting to the current operator can cause long running interaction including a scenario where a manager reported to themself, generating an infinite loop. This has been resolved with an update which will break the loop if a manager reports to themself or if there is a recursion in the team structure. | Low-Code App Development |
| INC-B8351 | 862182 | Appstudio overview screen color contrast improved | The background color for the Appstudio overview screen has been updated in the pz-app-dashboard CSS file for improved accessibility. | Low-Code App Development |
| INC-B9321 | 859619 | Support added for custom assignment name with TaskLabel | After update, a configuration of the Assign-Worklist Data Transform that used pxTaskLabel to set a custom value for the assignment name and override the one set in the flow process for the assignment shape was no longer working. This was due to changes in the system to use pxFlow from work to fill Assignments details in the response. To resolve this, the pzSetAssignmentsList activity has been modified to use assignment page pxTaskLabel if it is not null, and otherwise use pyWorkPage.pxFlow().pyLastFlowStepLabel. | Low-Code App Development |
Mobile
24.1.1 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A21383 | 835391 | Updated logging for invalid case types | The presence of a bad/missing case type causes an error to happen in case-related processing logic. This error is caught but a bad step status was still set with the "Failed to find a 'RULE-OBJ-CASETYPE' message, and this message was not being logged. This has been addressed with an update so that Validation for Applications flags invalid case types. The runtime case logic will gracefully handle the error situation and clearly notify the application owner of the problem. | Mobile |
| INC-B12407 | 870536 | Corrected multiselect display for iOS | The multiselect list was not working as expected on iOS. Investigation showed the calculation for height and top position in mobile were not correct when mobile height is small and the results were shown in a specific fullScreen scroll container. This has been resolved with an update to fix the gap and input visibility issues of multiselect and autocomplete in this scenario. | Mobile |
| INC-B12458 | 862126 | createPDF action updated for QR codes in offline mobile | Preview was not working for offline mobile when a QR code was included in the PDF. This has been resolved by adding base64 image field support for the PDF generator in Client for Windows. | Mobile |
| INC-B1391 | 861449 | Offline mobile app skips pre-processing | Pagelist contents were not stored to the Pega server when using an offline mobile app even after synchronization. This was a missed use case for not needing to perform pre-processing activities configured in the flow action when the assignment is submitted from an offline mobile client, and has been resolved by modifying the offline mobile app code to send an extra boolean parameter "skipPreProcessing" as true. This parameter works with the added 'when' condition to skip the pre-processing flow when the assignment submit action is performed from the offline mobile application. | Mobile |
| INC-B19829 INC-B19548 |
869914 869096 |
ZIP files correctly packaged for offline mobile | ZIP files were not correctly packaged as BINARY when using offline mobile. This has been resolved by adding zip and bin extensions to the binary files list. | Mobile |
| INC-B2102 | 865630 | Generic error message in offline mobile now translated | The "PleaseCorrectErrors" field value was not correctly resolved in the offline application.This was traced to a missing field value definition in the offline packaging configuration, which has now been resolved. | Mobile |
| INC-B9657 | 863580 | Updated handling for autocomplete cancel button in mobile | When using an autocomplete control in a mobile screen with full screen enabled, navigating to the autocomplete, clicking on it to launch it in full screen, and clicking cancel without entering any characters did not close the autocomplete as expected and the screen froze. This was traced to a javascript error caused by the system expecting a popup from the autocomplete which was not generated, and has been resolved. | Mobile |
Project Delivery
24.1.1 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A30085 | 854709 | Get next work supports fetching cases from multiple application | The documentation regarding the logic for selecting the next work assignment has been updated to clarify that the Get Next Work functionality retrieves assignments from all the applications to which the user has access. | Project Delivery |
| INC-B5790 | 860628 | Local Actions in offline mode documentation updated | The documentation for Local Actions in offline mode has been updated to make special note of the need to define the Flow Action Rule on the same class as the Case Type. If the Flow Action Rule is defined on a different class, the Offline Processing Engine cannot find the rule at runtime. | Project Delivery |
| INC-B9218 | 867658 | Clarification for keyboard shortcuts instruction | The Text Editor keyboard shortcuts instruction in Knowledge Management article creation has been updated to clarify that "use keyboard shortcuts Alt+F10" applies only when inside the Rich Text Editor body. | Project Delivery |
Reporting
24.1.1 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-269550 | 801431 | Resolved UserDashboardContainer not displaying correctly | When using an AJAX container and navigating to other tabs while inactive, the screen/sections were showing blank or not rendering as expected. This was an issue related to using positioning absolute for the section, and has been resolved by modifying the py-dashboard-personalization CSS to remove position absolute and adjust the column-2 position. | Reporting |
| INC-A11826 | 825228 | Corrected datatype for Report Definition datetime | It was not working to specify a symbolic condition such as [Today] for a datetime property in a report definition [Date and Time] interval. This was caused by the datatype being saved as "DATE TIME" instead of "Date Time" when created from UserPortal, and has been resolved by updating the pzGetSelectedValues Activity to correct the datatype. | Reporting |
| INC-A15578 | 827993 | Corrected button visibility for inline custom filter section | When using a report definition with an inline custom filter section, performing a refresh caused the inline section's apply and clear buttons to disappear. This has been resolved by removing a second visibility condition on the dynamic layout in the pyDefaultCustomFilterApplyCancel section. | Reporting |
| INC-A21986 | 859195 | Corrected security registration for Report Next Page | Report Next Page was not working when clicked.This has been resolved by registering pzdoGridAction in the pzBACActivityRegistration section. | Reporting |
| INC-A22659 INC-B7687 |
835684 858568 |
CountOfCases activity added to collect secondary storage statistics | The pyCountOfCases activity has been added to the Work- class of the Pega search executor to count distinct instances for archival and live data. | Reporting |
| INC-A24184 | 860831 | Custom search with pagelist functions with SRS | After migrating to the Search and Reporting Service (SRS) from Elastic search, the old implementation of a custom search was no longer working. This has been resolved by adding the DSS "enableOrInFilterValue" to control processing OR in the search filter value. | Reporting |
| INC-A26127 | 852924 | Adjusted handling for archival purging | Running the ArchivalUsingPipeline process to archive data to secondary storage was generating the error "Exception occurred during purge attempt for live indexes" in the purging phase of Archival. When an case type hierarchy has parent case type and child case types, the search and reporting setting for a child case type in the case type rule is disabled. Due to this, the purger phase in the case archival job was failing when it tried to delete an index on the work class of child case type which did not exist. To resolve this, an error filter has been applied to ignore the error code ERR_INVALID_ENTITY_NAME from the deleteIndexes search API. | Reporting |
| INC-A4701 | 823045 | Updated logic for embedded search | Embedded search was not working for ABAC(one of + Page group). This was traced to the open-work-by-handle failing the Access Control Policy, and has been resolved. | Reporting |
| INC-A7619 | 865636 | Added null pointer check for IncremenatlIndexer | Search index was not working and items were moved to the broken items queue due to null pointer exceptions seen in the pyFTSIncremenatlIndexer queue processor. This has been resolved by adding a null check to the RemovePOIFiles method to avoid exceptions during delete. | Reporting |
| INC-B10322 | 867029 | Handling added for embedded properties in a sub-report | After update, reports containing a specific sub-report could not be saved and an error was generated related to two columns present in the sub-report. Investigation showed the Propinfo had a null value, and this has been resolved by adding logic to handle embedded properties and validate them. | Reporting |
| INC-B10344 | 861727 | Correct column name shown when exporting Grouped results | An incorrect column name was being shown when exporting Grouped results to Excel. To resolve this, if a column is 'Grouped by' and is a column in the table, export to Excel will ignore the column in the table so its header label should not appear and cause misalignment. | Reporting |
| INC-B10398 | 861474 | Resolved unregistered Report Explorer request | A 403 error was displayed when clicking on select values for datetime properties in Report Explorer when pyblockunregisteredrequests is true. This has been resolved by registering pzGetCustomPropsForTreeGrid in pzBACActivityRegistration. | Reporting |
| INC-B10661 | 861213 | DSS added for indexing timeout to prevent node restart | It was possible for a bulk reindexing process on a class with millions of records to time out and cause a node to be marked as unhealthy and be restarted. Because processing was not completed, the utility nodes would attempt to reprocess the same items and the duplicate entries in the pySASBatchIndexProcessor queue could cause the stream service's disk space to become full. To address this, the DSS indexer/srs/bulkGenerationTimeoutInSeconds has been created to set the timeout for bulk generation. If it will take longer then the limit, then bulk generation will be stopped with an error. With the timeout, nodes will not be marked as unhealthy and termination will not occur. The type of error will identify the need to use the DSS indexer/srs/partitioningConfiguration to make indexing possible. | Reporting |
| INC-B10861 | 865685 | Improved security for DisplayReport | Cross-site scripting protections have been updated for the DisplayReport activity. | Reporting |
| INC-B12870 | 868133 | When condition updated for Live UI button | After update, the Live UI button was being populated in reports for end users. This has been resolved by updating the when condition of pyEnableUIInspector in code-Pega-list. | Reporting |
| INC-B13389 | 864586 | Report name with special characters displays correctly | After update, a report name containing special characters showed the ASCII values in the tab names. This has been resolved by updating the RDWinTitle control. | Reporting |
| INC-B17668 | 867689 | Support added for disabling SRS Incremental Indexing before migration | In order to improve the process of migrating to externalized search, an update has been made which will disable the Search and Reporting Service (SRS) incremental indexer when SearchCapability.SRS_ALLOW_INCREMENTAL_INDEXER is not activated. This capability should be deactivated only in the following scenarios: 1) environments with SRS and the migration in the state 'Ready'; and 2) environments without SRS. | Reporting |
| INC-B18313 | 872431 | Restored date format for report prompt filter | After upgrade, the date format in the report prompt filter was displayed as a timestamp value such as '20240609T045800.000 GMT' instead of the previous format of 'June 9, 2024'. This was traced to an incorrect behavior in pzResolveCopyFilters for DateTime and has been corrected. | Reporting |
| INC-B23105 | 872628 | GetPropsForTreeGrid registered with BAC | A 403 Forbidden error generated by the Report browser has been resolved by registering pzGetPropsForTreeGrid in pzBACActivityRegistration. | Reporting |
| INC-B3603 | 859201 | Worklist Counts enabled for non-Theme Cosmos applications | Worklist Counts were not updating on the Dashboard. This was due to a property which pointed to a Theme Cosmos Declare Expression that was not in the ruleset stack for UI-Kit, and has been resolved by creating a WorklistOpenCount Declare expression which is accessible for non-Theme Cosmos applications. | Reporting |
| INC-B4697 | 866586 | Copy/Move Report Definition Shortcut behavior updated | When trying to copy a report shortcut to the same category of the Report Browser, the error message “Category name: This report shortcut already exists in this category. Please select a different category.” was displayed. However, in the backend, the report shortcut was created in open rule set version and deleted from the existing locked rule set version. Investigation confirmed that for Copy to Same Category, the error was shown but it still created a new record in an open available ruleset and deleted the original one. For Move to Same Category, no error was shown but a new record was created and the old one was deleted. To resolve this, for Copy to Same Category, an error will be generated and the new record will not be created. For Move to Same Category, an error will be generated and the record will not be created. A check has been added to ensure that pxCreateRecord should happen only when the Category is not the same. | Reporting |
| INC-B5040 | 860477 | Corrected Search for 'show results in new window' | When using the search bar in PQM, the "Show results in a new window" function opened a new window opens but returned results unrelated to the search. For example, searching for COM-24172948 returned "1000 results found for 'COM24172948'" and the results were follow up cases instead of the actual complaint record. This has been resolved by updating the preferences from Searchtext to Searchstring for 'Show results in new window'. | Reporting |
| INC-B7368 | 861677 | Max records override for Export to Excel | Exporting to Excel from an Insight was capped at 5000 records for export. To address this, an update has been made to override max records in pzUpdateSystemSettings in case of export to Excel. | Reporting |
| INC-B7958 | 865464 | Corrected distortion while scrolling fixed header alignments | When the "Do not scroll header" checkbox was enabled, the report column headers were becoming jumbled at run time. This has been resolved by updating pzPega_ui_grid.js and adding the necessary CSS for a fixed header to pyReportEditorStyling. | Reporting |
| INC-B9236 | 859658 | Performance improved for SQLParser class | The SQL auto parser has been updated to decrease performance impact during report definition execution. | Reporting |
| INC-B9677 | 867354 | Bix CSV extract files for child cases include headers | When the "-c" option for BIX was used in Pega Cloud to include child case data in the CSV extracts, the child extracts were produced in files separate from the parent cases and contained only the data lines while the parent extract also included the column headers. This has been resolved by adding the necessary support for the headers to be included in the child data file. |
Reporting |
| INC-B9729 | 869268 | Updated empty value handling for validation of custom filters in reports | In some specific scenarios when the validation failed for a report with filters in a custom section using multiselect controls, the system displayed a Pega internal error screen instead of displaying the expected error message and a java error was logged. Investigation showed the Filter Operation in pyContent of the pzValidateCustomFilterSection had the value IS NULL at the initial point of the report definition, and this was carried over into the later process. This has been resolved with an update to pass the value as = instead of IS NULL to match the filters in the pyBody of the RD. | Reporting |
Security
24.1.1 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A24541 | 866155 | Updated handling for custom browser CSP | After introducing a separate application for handling the unauthenticated browser context (requester type Browser) with a very strict Content Security Policy configured as blocking, attempting to log in to an application in the platform failed when authentication was passed in context of the local access group. Investigation showed that after configuring different CSP policies for unauthenticated context at the application level and user-specific application level with varying CSP modes, users were receiving both CSP headers after logging in. To ensure that only one CSP header is present at any given time, updates have been made to remove both CSP headers from the response headers map before replacing the values with the new policy. | Security |
| INC-A2894 | 856620 | Rule-Obj-Access-Deny replicated to all nodes | An update has been made to ensure the Rule-Obj-Access-Deny rule is synced to all nodes in a multi-node environment. | Security |
| INC-A29484 | 855138 | Cross-site scripting protections updated | Cross-site scripting filters have been added for dynamic layout sections. | Security |
| INC-A3941 | 836304 | Stacktrace suppressed when OAuth2 token is expired | Numerous errors related to JSON Web Tokens (JWT) were logged, including messages that the JWT was rejected during signature verification due to a bad signature or being expired. This has been resolved with an update to suppress the stacktrace in logs when the OAuth2 access token is expired and only print the error message. If log level is debug, a complete stack trace will be printed. | Security |
| INC-B10230 | 863326 | Security improved for autocomplete | Cross-site scripting protections have been updated for autocomplete. | Security |
| INC-B12748 | 865817 | ABAC policy conditions updated to include descendant classes | When running a report definition on a case class which has class specialization on it, the report returns rows (cases) from all of the specialized classes as expected when the “Report on descendant class instances” option is checked. If an ABAC policy is implemented for this case type to enable row level security and the policy condition uses a property on the case itself, the report eliminates the rows that do not meet the condition as expected. However, if the policy condition used an association rule to join with a data class (or another case class) to perform the check, the report failed to fetch any of the case instances from specialized classes even when the policy condition was satisfied. This was caused by the ABAC policy conditions that use associations not including descendant classes, and has been resolved by updating the file PolicyConditionActionAssembler class with the new entries. | Security |
| INC-B12824 | 863463 | Security update for Smart Tip | Cross-site scripting protections have been added to the 'Show Smart Tip' feature. | Security |
| INC-B15155 | 870184 | Diagnostic logging added for logout issue | Additional logging has been added to assist with diagnosing issues related to pxStopPending causing unexpected logout. | Security |
| INC-B17248 | 867778 | Trim added to authentication key construction scope | Trying to make API calls using an OIDC token from an active SSO session generated the exception "Unable to obtain access token for client details in authentication profile configured for connector." Investigation showed there was a scope issue while constructing the key, and this has been resolved by implementing trim during this process. | Security |
| INC-B20163 | 873711 | Improved error message security | Protection against injection attacks has been updated for error messages. | Security |
| INC-B423 | 851165 | Corrected iOS SAML SSO handling | A blank screen was being shown after successful authentication using SAML SSO on an iOS device. This was traced to the iOS Safari browser sending the CSP report starting with "type":"csp-violation" instead of "csp-report", and has been resolved by updating the CSPReport method in CSPUtils.java. | Security |
| INC-B5310 | 857911 | Database save stack trace added | StackTraces_DBSaveOperations has been added to debug logging in order to enable printing a stack trace for database save operations. | Security |
| INC-B5680 | 855468 | Added temporary context for CDK rotation | When the Customer Data Key (CDK) expired, trying to rotate the key during non-admin user session context generated the error "You are not authorized to create, modify, or lock instance SYSTEM-DATAENCRYPTION-CDK". This was due to the user role not having access for CDK class, and has been resolved by temporarily assigning System-DataEncryption-CDK access to non-admin user to acquire the lock successfully. | Security |
| INC-B6072 | 859620 | Logging added for userClaims | Additional logging has been added in order to assist in debugging issues with "derive operatorId from claim". | Security |
| INC-B6306 | 858237 | Resolved runtime exception for OAuth2 | A runtime exception was generated when trying to log in with OAuth2, specifying "Unable to fetch token page using key ac_pega-authorizationcode-openid profile email". Investigation traced this to an additional space character added after email in the key, and it has been resolved by adding trim to the scope while constructing the key. | Security |
INC-B7968 |
861646 | Observability increased for SAML WebSSO request | In order to assist with troubleshooting the logged error "Caught Exception while validating SAML2 Authentication response protocol : SAML token security failure", the observability has been increased to identify what attribute in SAML Assertion is causing validation failure. | Security |
| INC-B8872 | 865593 | Corrected NoInformationRecognized code for PRauth | The field value "NoInformationRecognized" is available for updating the error message associated with incorrect login credentials, but the updated error message worked only if requests contained "/prweb". The configured error message was not shown for requests with /PRAuth. This was traced to a typo in the PRauth code which caused it to not override the value from the NoInformationRecognized field; this has been corrected. | Security |
System Administration
24.1.1 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A5927 | 822047 | Corrected SOAP Service outbound message signing | The system was signing the body element of outbound messages for the SOAP Service despite the specified outbound signing elements. This has been corrected. | System Administration |
| INC-B1033 | 855349 | Agent runs on correct day after restart | When an agent was configured to run daily on one background node at a time using America/New York timezone, if the scheduled run time was after 7pm EST time and there was a restart the agent was instead scheduled for the next day. This has been resolved with an update to ensure an agent in a different time zone is not skipped. | System Administration |
| INC-B11448 | 866872 | Made message processing flow more robust against heavy loads | During periods of heavy system load, the data flow thread might receive the Kafka confirmation slightly later than usual and overlap with the queue processor thread reading the message and starting to process it. If this occurred during the queue processor's thread experiencing an issue and re-queuing the message for another attempt, the data flow thread removed the message from the database while it was still being processed by the queue processor thread. This race condition has been addressed by modifying the database query for removing the message. | System Administration |
| INC-B12042 | 866875 | Some sites have a limitation of creating Kafka topics only in lower case in the external enterprise Kafka cluster for the stream service. To better support moving to Kafka externalization, a DSS has been added to change how the queue processor's Kafka topics are named (lower vs upper case). Set the value to the desired strategy; allowed values are: UPPERCASE - for pzStandardProcessor queue processor the stream name will be PZSTANDARDPROCESSOR and Kafka topic name will be: pega-PZSTANDARDPROCESSOR - this strategy is used as the default; LOWERCASE - for pzStandardProcessor queue processor the stream name will be pzstandardprocessor and Kafka topic name will be: pega-pzstandardprocessor; To apply the configuration naming convention all nodes need to be restarted simultaneously (not a rolling restart), then stale Kafka topics must be manually removed as these are not removed automatically. |
System Administration | |
| INC-B12578 | 865610 | Additional passivation logging available | In order to assist with diagnosing an intermittent issue with data loss when submitting from one screen to another, additional logging has been made available for the passivation APIs. | System Administration |
| INC-B17068 | 868691 | Markdown library update | The markdown library has been updated to the latest version. | System Administration |
| INC-B18402 | 871090 | Updated logger handling for PRPulseDispatcher class | The campaign process program run status was not progressing to the completed state, and error were generated indicating "Invalid value for aClassName passed to .createPage:Failed to get column mapping for property Data-BatchOutPR132.pySubjectType". This has been resolved by modifying the logger for the PRPulseDispatcher class to continuing pulse processing even after pre-processing failure. | System Administration |
| INC-B2470 | 861915 | 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-B5470 | 867556 | Optimized APIs added to improve lag calculation for external Kafka | When an enterprise-level Kafka cluster is hosted in multiple regions with multiple Kafka racks and many Kafka brokers, Pega's partitions can be stored anywhere in the cluster. This can drastically impact the network latency for the Kafka API calls that perform the lag calculation process to render the "Ready to process" values in the Queue Processors landing page, as the underlying mechanisms used for lag calculation need to complete the entire process within 30 seconds to avoid a timeout exception with the error message "Unable to calculate lag for <QP-stream-name>". To address this need, new stream SPIs/APIs have been added which provide significant optimization in obtaining offsets in a faster fashion with reduced total number of Kafka API calls. | System Administration |
| INC-B5743 INC-B2491 |
855812 855146 |
System pulse logging updated | After deploying a ruleset versioning update, the new rules were not being picked up by the queue processor and the system runtime context continued to be the previous ruleset version. This type of issue occurs when the SystemPulse fails to propagate the latest version of the rule to all nodes in the cluster, leading the system to utilize the existing version of the rule. In order to capture whether the deployed rules are propagated to all the nodes in the cluster, additional diagnostic log messages have been added. These loggers handle defined rule update pulse types for diagnostic information, CACHE, RFDEL, IMPRT, CLDEC, PURGE, DSMST, and are based on the environment's production level and DASS: systempulse/rulesUpdate/logAcknowledgement/enabled. Logging has been enabled by default for production level >= 4 (i.e. PRE-PROD or PROD) and disabled by default for lower environments. | System Administration |
| INC-B5791 | 861687 | Processed count data type updated from integer to long data | The records processed in last hour count was always shown as 0 in Admin studio for a queue processors handling an enormous number of records each day. Investigation showed the queue processor had more than 6 billion processed records, which exceeded the allowed limit for integer. This has been resolved by changing the integer data type to long data type. | System Administration |
| INC-B6892 INC-A11374 |
859160 831400 |
Added null partition value handling for DelayedItemsDataFlowService | After upgrade from Pega 7 to Pega 8, ORA-00936 "missing expression" errors were generated by DelayedItemsDataFlowService. This error occurred while reading delayed items from the database, and was due to there being more than 25 nodes splitting the work and the additional partitions having a null value. To resolve this, the condition has been updated to avoid generating an SQLException for null partitions during processing. | System Administration |
| INC-B7039 | 865512 | Additional logging information added for purge agent | In order to assist with diagnosing issues with the purge agent not cleaning up instances as expected, more detailed log statements have been added to the RAPurge function. | System Administration |
User Experience
24.1.1 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-251607 INC-246272 |
772994 772992 |
Updated accessibility for text area character count | JAWS was reading the remaining character count of a text box multiple times before all other content on the tab. This was due to the attribute aria-live="assertive", and has been addressed by updating webwb_pzpega_ui_template_textarea.js to add a new condition in the template to handle aria-live and aria-atomic attributes for Macintosh and Iphone devices. | User Experience |
| INC-270228 | 853797 | Corrected user portal harness issue for Cosmos | The user portal was not correctly rendering in Theme Cosmos when set as a single page. This has been resolved by updating the handling for the Show-Harness and Show-Property activities. | User Experience |
| INC-A14835 | 830560 | Updated scroll handling for flow in modal window | When a flow was used in a modal action event, refreshing the modal window or moving the flow to the next task resulted in the modal window itself moving when a scroll was performed in the main page. This has been resolved by updating the modal container handling of the overflow scroll for this usecase. | User Experience |
| INC-A15251 | 835002 | Interaction remains open after submitting task | After opening the email reply dialog of an incoming email interaction and then minimizing the dialog again, adding a task from the task menu and submitting it would close the task but also unexpectedly closed the email interaction. This only happened if a single task was added; adding multiple tasks or showing the confirm harness after submission did not close the entire interaction on submission. This has been resolved by updating the code in the AutoClose section. | User Experience |
| INC-A18620 | 833830 | Resolved table layout validation | The UI was becoming distorted when validation was triggered for a property added to a column inside an optimized table layout, and it was no longer possible to add anything in the table due to the the text-input field disappearing. An error icon was seen. This has been resolved by updating the pzbase-grids CSS. | User Experience |
| INC-A20262 | 867369 | Added handling for special characters in KM article titles | Attempting to open a Knowledge Management article in the Customer Service application failed to load the content in the popup window if there was an apostrophe in the article title. This has been resolved by escaping the special characters in the window name parameter of the Show Harness action when the target is a popup. | User Experience |
| INC-A20684 | 868917 | Lists option correctly displayed in UI Gallery | After upgrade, the list option was not visible in the Rich Text Editor UI Gallery. This was an unintended side effect of security work, and has been resolved. | User Experience |
| INC-A23866 | 838647 | Updated accessibility for Rich Text Editor keyboard icon | A label has been added to the Rich Text Editor keyboard icon with an associated tooltip to improve accessibility. | User Experience |
| INC-A24366 | 842946 | Background color maintained when spellchecker is called on-change | If a section had one or more text areas and a Rich Text Editor configured with a spell checker action on change, an incorrect spelling caused all text areas on that screen to become yellow. Investigation showed the repaintTextArea function was incorrectly being called by spellcheckerscript.js for all text areas in the document, and this has been corrected. | User Experience |
| INC-A25025 | 846331 | Decimal value properly rounding on Mobile | Decimal values in a number UI control were not rounding properly for offline Mobile. This was a missed use case, and has been corrected. | User Experience |
| INC-A26464 | 865668 | Hierarchical table control click handler updated | After navigating to 'Hierarchical table' in UI gallery, repeatedly expanding and collapsing different rows intermittently caused the expand and collapse to stop working for some of the rows. In hierarchical tables, rows are reused from a pool based on pagination size. Because of this reusing, the click handler, which is removed from a row used as a lowermost child, is not reattached upon reuse, causing the expandable icon to freeze. To resolve this issue, the clickHandler has been re-attached in the updateStyle method, which is triggered by onAllocatePathForDomObjects. | User Experience |
| INC-A27036 | 846452 | Corrected decimal handling for read-only | For properties of type Decimal set with read-only format in the UI-Control and decimal point set to Auto, entering a 15-digit value returned an invalid result with an extraneous decimal point. On the clipboard, the 15-digit integer was set correctly. This has been corrected by updating pzpega_ui_formatNumber.js. | User Experience |
| INC-A27074 | 842657 | Upload file hover shows selected filename | When using the Upload functionality to upload the files, the Filepath control still showed the message 'No FIle Chosen' after choosing the file and hovering on the selected file using the mouse. This is a difference in behavior from Pega 7, where the mouse hover showed 'Filename' after selecting the file. To restore the previous behavior, a setTitle function onchange has been added to dynamically set the title based on the value for the filePath control. | User Experience |
| INC-A27168 | 848164 | Opening a Case ID in Theme Cosmos report made consistent | Clicking on a row inside of a report will open the case in the same tab, but the case will open in a new tab if the Case ID is the primary column. Investigation showed the "oafunc" attribute can have values such as "openAssignment" which was not handled for reports. To resolve this, openAssignmentInNewTab functionality has been implemented in the pz-cosmos-ui-utils.js file for openAssignment action. This is used as the value for the "oafunc" attribute to open work objects in a new tab that are rendered as children in a tree in summary type reports. In addition, the handling has been updated for the "pzRDWinTitle" control file for openAssignment action | User Experience |
| INC-A27311 | 868100 | Page number field made editable | The page number field could not be edited in a table in the dashboard portal. This has been resolved by updating the handling in the GridActivePage control to allow an onchange of the pageNumber field. | User Experience |
| INC-A30118 INC-B20999 |
856485 872295 |
Validation error banner made accessible | JAWS was not reading the server level validation error messages generated by pyCaseErrorSection. This has been corrected. | User Experience |
| INC-B10764 | 870801 | Corrected attribute handling for custom report definition filter | Opening a report and clicking on "other navigation" caused a pyDirtyCheck popup to appear even when no changes were made. Investigation traced this to the use of a form containing a date field that had text entry disabled that was used in a custom report definition filter rendered in non-template mode. This has been resolved by updating the handling for the "data-initialvalue" attribute so it renders as expected in both template and non-template mode. | User Experience |
| INC-B10809 | 868535 | Spell checker styles removed on Rich Text Editor section refresh | When an incorrectly spelled word like "test mesage" was entered into a Rich Text Editor control, clicking on spell check highlighted the error, but clicking outside of the area did not remove the highlight during the refresh section action. This was a change in behavior from previous Pega Platform versions, and the regex has been updated to restore the expected clearing of the highlighting. | User Experience |
| INC-B1089 | 853156 | Corrected anchor alignment during scroll | The smart info anchor icon or tip icon was misaligned when scrolling on the main page. This has been corrected. | User Experience |
| INC-B11529 | 868349 | Application is accessible at 150%+ zoom | When the portal was rendered at 150% zoom or more, there was no option for keyboard users to close the navigation menu until a mouse click was performed or an option was selected from the menu. This has been resolved by adding the necessary handler. | User Experience |
| INC-B12101 | 862714 | Added setting for allowcustomtags in Rich Text Editor | After update, custom style tags were being removed when using the Rich Text Editor. This was an unintended side effect of work done to enhance cross-site scripting protections for the Rich Text Editor control, and has been corrected. | User Experience |
| INC-B12446 | 872573 | Corrected container loading order for hybrid applications | When attempting to open Constellation cases in the Cosmos portal of a hybrid application, app/primary containers were reset and trying to call "open work by handle" resulted in empty details and an error on the screen. This was traced to an error in the container order of events and has been corrected. | User Experience |
| INC-B12956 | 863839 | Updated focus order for modal dialog buttons | The focus order of cancel and submit buttons in the modal dialog was not consistent between @baseclass and Work class. The default order has now been set set to first move focus to the cancel button and then to the submit button. This is handled in a new py section "pyModalButtons" which is used inside pzModalTemplate, and the button focus order can be customized by changing the button order in pyModalButtons. | User Experience |
| INC-B12999 | 862954 | Optimized table has correct row values | An optimized table was showing showing Pega property names as row values after update. This was traced to an issue with resolving the parentPage if the pageList was referenced as a property, and has been corrected. | User Experience |
| INC-B13349 | 866729 | Accessible filter dialog role corrected for optimized table | When using JAWS with an optimized table, navigating to the menu button on the column header and opening the Apply Filter caused the screen reader to announce both the aria-label and the role. This has been corrected by updating the aria-label for the column filter modal dialog from 'Column filter popover' to 'Column filter'. | User Experience |
| INC-B1362 | 857263 | Corrected Rich Text Editor generating dirty pop-up without changes | When Rich Text Editor was present in the section and the first editable field, clicking the Close button generated a dirty pop-up asking to save the work object even though there were no changes made. Investigation showed this was caused by the cancel/close process adding a new line to the Rich Text, and has been resolved by adding trim to remove the unwanted spaces. | User Experience |
| INC-B14356 | 868821 | Corrected portal rendering after resize | The top navigation window was not rendering correctly after launching the Provider manager portal and resizing the window to a smaller size. This has been resolved. | User Experience |
| INC-B14995 INC-B13626 |
870599 866598 |
Corrected multiselect and autocomplete handling for touch screens | The multiselect and auto complete controls were not loading the data when a touchscreen was used and the source for the control was a data page. The data loaded as expected when using a mouse. This has been resolved by adding the needed target element in the success function in Control_multiselect.js. | User Experience |
| INC-B15209 | 870798 | Corrected multiselect item delete | Attempting to remove a selected value from a multiselect field within a live interaction by clicking on the cross icon was not working. This was traced to a div focus issue and has been corrected. | User Experience |
| INC-B15506 | 871968 | Datetime validation message displayed with java edit validate rule | A date time control with "allow text entry" set to No did not display the validation message in the UI even though it was in the clipboard. Investigation showed the div responsible for showing the error was not available in the dom if "allow text entry" is No and the java edit validate rule is used. The same configuration worked as expected if the existing standard validate rule IsFutureDate was used. This has been corrected. | User Experience |
| INC-B15574 | 869927 | Corrected overlapping columns in Export to PDF | The column that contains the currency property was overlapping with the column to the right of it when exporting a report as a PDF. This has been corrected by updating the pyReport_ExportToPdfStyles.css file. | User Experience |
| INC-B16253 | 869223 | Corrected CSS for Rich Text Editor border | Adding a border-radius of 10 pixels caused the border to cut off at the bottom of the Rich Text Editor space. This has been resolved by adding the CSS for overflow hidden. | User Experience |
| INC-B16320 | 870815 | Corrected tooltip overriding control label | JAWS was no longer reading the label of a control after an inline tooltip was added. This was due to the control label being overridden, and as has been resolved by providing an ID for the helper text div and giving it to aria-described-by instead of aria-label. | User Experience |
| INC-B16345 | 866725 | Clear filter focus outline appears for non-optimized table | An update has been made to correct a missing focus outline on Clear Filter by adding a selector specifically for a non-optimized table filter. | User Experience |
| INC-B16594 | 870956 | Corrected label default for afternoon period of current date and time | An error in the date/time widget for the current date and time default was evaluating the period between 12:00:00 PM (12 noon) and 12:59:59 PM as AM instead of PM. This has been corrected. | User Experience |
| INC-B16894 | 868684 | Date showing on hover for mobile view | When using a Touch laptop, the date was missing on hover after selecting it in the calendar gadget. This has been corrected. | User Experience |
| INC-B17397 | 871479 | Removed hard-coded aria-label interfering with localization | When adding a date time control to a section or applying a date time column to a non-optimized or optimized table, the date time calendar icon picker had an aria-label of "Date Picker" which was not translated. This was caused by the aria-label being hard-coded for this field; as the aria-label is not required here, it has been removed to resolve this issue. | User Experience |
| INC-B1797 | 858556 | Corrected flow container context handling for error messages | Error messages related to validation were not removed automatically during screen refresh and carried over from one screen to another screen even after the validation was corrected and the case was successfully submitted from the previous screen. This was due to all of the cases (tabs) being rendered in a flow container which resulted in page messages being pushed to the FlowContainer context (ex. app/primary_3) instead of the active container item context. This has been resolved with an update to populate page errors in the activecontainer context. | User Experience |
| INC-B18193 | 868151 | Calendar date picker contrast improved | The background color of the date picker has been updated from #0089ec to #076bc9 for improved accessibility. | User Experience |
| INC-B19773 INC-B20656 |
869537 870257 |
Corrected display of readonly hyphen | After update, the "--" for readonly with no value was misaligned for Inline labels in dynamic layouts. This has been corrected by updating the width to 2px for no-value-span. | User Experience |
| INC-B2079 | 860218 | Constellation preview pane updates correctly after action | When using Constellation, hovering over a case ID in worklist and clicking preview opened the preview slider with all the actions, but the preview pane was not refreshing after using the withdraw local action to resolve the case. As a result, local actions were still available and the additional tabs based on status were not displayed. This has been resolved by adding a deleteCaseSummary action for updating the assignments. | User Experience |
| INC-B20809 | 872121 | Stakeholder widget visible in Constellation | A stakeholder widget with an added visibility condition for embedded section was not displaying as expected in Constellation. This has been corrected. | User Experience |
| INC-B21180 | 871596 | Corrected activity registration for FieldHistoryCustomAction | Attempting to download the Field History from a case was generating a SECU0019 alert. This was traced to pyExportFieldHistory not being correctly registered when using BAC, and has been resolved by updating the registered activity for the download button in the pyFieldHistoryCustomAction section. | User Experience |
| INC-B3093 | 858365 | GetNextWork opens traditional case directly | GetNextWork was unexpectedly opening a case in a popup. This was traced to the case being created in Theme Cosmos and displayed in Constellation, and was caused by pzCreateDetails not being able to get the needed component to render traditional iframe. To resolve this, an update has been made to override pzCreateDetails for traditional cases to get the proper component details for display. | User Experience |
| INC-B3472 | 857116 | Handled overflow for maximized toolbar display | Content screens and the text rich toolbar were overlapping when the content toolbar was maximized. This has been resolved by adding handling for the overflow of the rich text editor. | User Experience |
| INC-B3745 | 855111 | Updated Traditional UI Coexistence handling for migration | After creating a casetype in Theme Cosmos and referring to the same in Constellation using Traditional UI Coexistence, the data portal was not launched until the assets for the traditional UI were generated again. This was traced to an issue with the key name check, and has been resolved. | User Experience |
| INC-B4356 | 858241 | Removed redundant PDF file extension on download | When a PDF was generated and added using PDF smart shape, a redundant extension was added when the PDF was downloaded from preview. This was traced to pxcreatepdf adding the extension to the filename when it already existed, and has been resolved. | User Experience |
| INC-B4596 | 856232 | Updated attribute on Preview button | The Preview button seen when focusing/hovering on a case ID would intermittently not activate the Preview Panel when the Enter key was pressed, for example after being previously closed with the cancel button. This has been resolved by adding a "type='button'" attribute to Preview button element. | User Experience |
| INC-B4761 | 859243 | Corrected section grid alignment for To Do | After performing the case action "Save to my worklist" and assigning the case to a logged-in user, the To Do section grid alignment was not correct. This was traced to the showHideAssignmentGadgets function which was attempting to show/hide the hierarchical table sections on some actions. As the hierarchical table section was marked as display: none, the height was not correctly calculated while refreshing the section. This has been resolved with an update to the widget row heights on show of the pxAssignmentView section when the assignment block is visible. | User Experience |
| INC-B4773 | 859138 | Restored Rich Text Editor plugin | After update, an error was thrown in the browser console indicating CKEditor was missing two plugins, causing the form to be corrupted from the end user's side. This was an unintended side effect of security work, and has been resolved by restoring the needed plugin. | User Experience |
| INC-B4844 | 857426 | Overflow correctly applied to optimized grid in popup | When there were more than 15 columns in a optimized table displayed in the overlay, scrolling the page up and down caused the column names to come out of the overlay and become disorganized. This issue Issue only occurred when the pop-over was displayed above the grid and contained enough columns to trigger a scroll bar, and was caused by the overlay container with id ="po0" on the first load not having the overflow CSS applied. This has been corrected. | User Experience |
| INC-B4878 | 861843 | Search string clears correctly after use | After entering a search string on the user portal, the entered string persisted on the results page and when returning to the home page. This has been corrected. | User Experience |
| INC-B5095 | 858437 | Cancel button corrected for temporary mode | The Cancel button was not functioning on the case worker area when the case was opened in temporary mode. This has been corrected with an update to pycaseactionareabuttons. | User Experience |
| INC-B5845 | 858833 | Corrected time picker error in right-to-left locales | When using a 24H time format in a right-to-left locale such as Arabic or Hebrew, once a time field contained a value that value could not be changed using the time picker and a javascript error appeared in the console. This has been corrected. | User Experience |
| INC-B6212 | 855562 | Corrected duplicate view generation | If the Configure View button was clicked for a step in the workflow tab when there was already an existing view by that name, the fields in the view were not updated. Instead, a new view and flowaction were generated for each click, using the original step name appended by "_1" / "_2"/ etc each time. Investigation showed the view created in the UX tab of the casedesigner was given the pyViewType "embeddedform", while the pzViewEditorPreProcessing activity which ran when clicking 'Configure View' ignored these views. This has been resolved by revising the pzViewEditorPostProcessing activity to update the FlowActionName to use the backing flow's pyExpression / pyActionName instead of the ViewPage's pyRuleName. | User Experience |
| INC-B6613 | 859053 | Function onGridFilterClose added to improve performance | In an optimized table, enabling a filter for columns having unique data caused the filter overlay itself to contain thousands of records. Once the filter overlay was opened, subsequent interactions took significantly more time than required. This was traced to the filter body not being removed and the results having an extremely large markup which stayed in the DOM, and this has been addressed with a new onGridFilterClose function. | User Experience |
| INC-B6680 | 859906 | Updated handling for negative integer in field label | If a negative integer value was entered in a field label, the HTML formatting showed special characters when it was used in a dynamic layout. This has been corrected by updating the HTML handling. | User Experience |
| INC-B7021 | 871231 | Alert announced by Android/iPhone | VoiceOver in iPhone/Android was not announcing 'Alert' for the error icon on a page level error message. This worked as expected for desktop. Investigation showed the page level validation message on the alert icon was being picked as "center panel region landmark" instead of "alert", and this has been resolved by adding the Alert word in py-cosmos-helper-classes.css so it is read as expected. | User Experience |
| INC-B777 | 860225 | Updated secondary button validation message handling | When attempting to submit without filling in a mandatory field, the error message was appearing on the field but also intermittently on the top of the screen.This has been resolved by updating the handling for validation errors shown for secondary button actions. | User Experience |
| INC-B7857 | 860314 | Corrected screen reader announcing \"angle bracket\" in navigation pane | When navigating the left navigation pane, highlighting "create case" resulted in the screen reader announcing "〉" as "closed angle bracket". This has been resolved by adding aria-labels for menu item elements so the screen reader will read only the label. | User Experience |
| INC-B8352 | 862196 | Added accessible name for iframe | Aria label has been added for the live composer iframe name in App Studio for improved accessibility. | User Experience |