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
| INC-A28652 | 859177 | Always-On Insights enabled | The Always-On Insights feature is available in this version, introducing several additional features to optimize strategies and improve monitoring capabilities: 1: Globally Optimized Strategies Monitoring: introduces new profiling capabilities for globally optimized strategies enabling users to monitor the performance of strategy components. A globally optimized strategy revision is used to track changes in the strategy structure and is assigned after various events such as modifications to the globally optimized strategy rule, sub-strategy, or referenced strategy rule. The Revisions window provides a list of strategy revisions, including a STALE revision and a CURRENT revision. 2: Performance Profiling: Users can configure globally optimized strategy profiling on the Decisioning: Strategy Optimizations landing page. This allows them to open the Performance profile or download a full diagnostics package. The Performance profile UI and downloadable CSV report offer aggregated data for a specific revision and for every component of the strategies included in the strategy rule including average run time and the number of processed output records. The Performance Profile table entries are unsorted, providing insights into the performance of each component. 3: Background Persisted Cached Compilation: This compilation mode allows nodes to reuse the published program stored in the database and pause globally optimized strategy execution until compilation is complete in non-production environments. This mode helps optimize performance by leveraging cached compilations and reducing the overhead of strategy execution during compilation. These enhancements collectively aim to improve the efficiency, monitoring, and performance optimization of globally optimized strategies in Pega Platform. |
Special Note |
Case Management
8.8.5 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A15741 | 833063 | Resolved case date/time shown correctly after actions menu | After returning to a resolved case, clicking on Actions for the available case showed the case update date/time as "A minute ago" even though no action was taken. Opening the case again restored the correct value. This has been resolved by updating the handling for the "pxUpdateDataTime" property in the pzPrepareInternalAssigmentForResolvedCase activity. | Case Management |
| INC-A18362 | 834103 | Select File(s) button accessible using Nuance Dragon | Nuance Dragon was unable to open a file selection dialog when given the command "Select File(s)". In addition, when using the "Click button" command for buttons which were assigned numbers, the "Choose two" command for the Select File(s) did not open the dialog. This was due to the select file button having been created as a overlay button which did not have any action on it, and has been resolved with an update to the pzMultiFilePath control to add role="button" and aria-label="<%=buttonName%>" to the input element to improve accessibility. | Case Management |
| INC-A19066 | 848291 | 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-A20218 | 837201 | Application case local actions working with Mashup | After update, local actions for previously created cases were not working with Mashup. This has been resolved by updating the openAssignment function. | Case Management |
| INC-A20546 | 834822 | Corrected post-cancel Create focus | After navigating to create a case using the Create Menu, selecting Cancel and Delete on the confirmation modal dialog did not return the focus to the Create menu as expected. This has been corrected. | Case Management |
| INC-A21365 INC-A15775 |
842664 829305 |
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-A2171 | 840610 | File Upload shows correct icons after file deletion | After uploading several valid files of different file types (e.g. png and pdf), deleting one of the files caused the preceding file to get the icon of the deleted file so the file and the icon no longer matched. There was previous work done to resolve this which added an ID property to the element to keep the type and icon aligned. This update addresses a casing difference where the frontend FileInput component uses "id" but "ID" is being passed in DX components by passing a redundant "id" property to keep the IDs in sync. | Case Management |
| INC-A22781 INC-B2703 |
840712 852719 |
FlowDependency page handling updated | In Activity pxCheckFlowDependencies step 16.5, a call to System-Queue-FlowDependency.pzSpawnQueueItemForFlowDependency is used to create and then remove a page named pyQueuePage of context System-Queue-FlowDependency. However, since the name of the primary page during the QP Execution is also pyQueuePage, the Page-remove step does not remove the page because it has the same name as the primary page. This has been resolved by replacing all the references to pyQueuePage with pyFlowDepQueuePage in the pzSpawnQueueItemForFlowDependency activity so the FlowDependency page will be created and removed as expected. | Case Management |
| INC-A23925 | 839192 | Improved security for potential cross-site scripting | Cross-site scripting protections have been updated for the case type rule name. | Case Management |
| INC-A23928 | 839044 | Improved security for PDF generation | Cross-site scripting protections have been updated for dynamically generated PDFs. | Case Management |
| INC-A26232 | 840735 | Added missing property for case opened by inbound email | A runtime error was seen on the dispute transaction page of a case created via inbound email indicating an undefined property, pyWorkPage.pyRelatedWorkList(1).pyRelatedWorkClass. This has been resolved by adding the property pyRelatedWorkClass for the Java step of GetRelatedWork. | Case Management |
| INC-A27598 | 846861 | 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 | 848579 | 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 | 848772 | 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-A4335 | 822966 | Handling updated for security alert on case submission | A section included on a data page which was flushed and recreated on click of a button reloaded correctly in the UI, but the PDC registered a SECU0001 alert. This has been resolved by modifying the newAssignPage.pyCurrentActionLabel property from hidden control to Text input to mitigate these alerts. | Case Management |
| INC-A8610 | 834034 | Added missing property for Access control policy | Adding an Access control policy on Assign-WorkBasket class caused an issue with visibility of flow actions and the "GO" button was hidden. Investigation showed the AssignPage, which is passed as the argument to the have haveAccess method, did not have the needed pxApplication property which is used in Access control policy condition. This has been resolved by adding the pxApplication property to assignPage in the pxCreateAssignmentFromFlowPage function along with updating the pyPopulateAssignmentContents and pyPopulateCaseContentsWrapper activities to add the pxApplication property onto the D_CaseAssignments page. | Case Management |
| INC-B11685 | 862939 | 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-B1539 | 857417 | 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-B3565 | 858162 | 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 | 853838 | 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 | 857206 | 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-B4850 | 862670 | 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 | 855880 | 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 | 853722 | 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-B8440 | 860652 | 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 |
Cloud Services
8.8.5 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A15258 | 833032 | Logging added to assist in diagnosing import issues | Additional diagnostic logging has been added to assist with tracing issues related to serialization during the import of RAP or third party jar using a client-specific application other than the PegaRULES application. | Cloud Services |
| INC-A1823 | 830593 | Default classpath mode updated to avoid class conflict on import | Import using prpcUtils in hybrid mode was failing in one environment with a class conflict issue between versions of classes on the file system and in the database. This has been resolved by updating the default classpath mode to database for prpcUtils and static assembler. | Cloud Services |
| INC-A21157 | 838678 | Updated authorization handling for reindexing requestors | The execution of a column population job was stuck and not progressing. Investigation showed the required authentication for the reindexing requestors was missing for the use case of an imported archive containing a class that contained an externally mapped property that was the target of a declarative expression whose value was retrieved from a Data Page load activity. This has been corrected. | Cloud Services |
| INC-B8226 | 859447 | 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
8.8.5 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A10994 | 842379 | Email manager supports rich text | Rich text support has been added for the email manager. | Conversational Channels |
| INC-A14561 | 839910 | Updated handling for removing inline images | While reading email cases with inline images, an inline image with pdf extension was not handled correctly for pyAttachContentId by the pyGetHtmlMessage activity. This was a missed use case, and has been resolved by updating the 'when' rule to remove inline images based on the pyAttachEncoding value. | Conversational Channels |
| INC-A15747 | 831712 | Support added for special characters in email address | An email address was detected as invalid if it included special characters in it such as "+" or "-". This has been resolved by modifying the Reply / Reply All logic to allow special characters in a customer email address. | Conversational Channels |
| INC-A21364 | 834220 | Mandarin added for messaging widget | The Digital Messaging widget now supports replies in Mandarin. | Conversational Channels |
| INC-A21693 | 845713 | Inbound email handling updated for disabled NLP | An OutOfBound Exception was being thrown during the InboundEmail interaction case creation. This was traced to a customization of CPMSetDataEntities which removed the reference to the data transform SendFeedbackToNLP used to execute the activity CSSendFeedbackToNLP. Because natural language processing analysis was skipped, TASummaryID was not present and the history record fetch failed. This was due to the system assuming NLP is always enabled, which is not a valid assumption. To resolve this, an update has been made to check for pyMode (Inbound/Outbound) instead of of pyTASummaryID to determine inbound emails. | Conversational Channels |
| INC-A25002 | 845064 | Corrected attachment visibility property handling for deferred load | The email interaction flow was going into an error state when wrapping up an Interaction case. This was traced to the pyPostEmailContent for attachments visibility using an auto-populated property value instead of the correct data page value when pyDeferLoadEmails was true. This has been resolved by changing the visibility condition to 'always' for the attachments dynamic layout in pyPostEmailContent and pyPostEmailContentV2. | Conversational Channels |
| INC-B8799 | 859813 | Blank value handling added for CreateInteractionReply | When Email Listener moved a case from one Workbasket to another Workbasket, the error "Unable to load data page D_pxUserFromChannel. Required parameters : Identifier. cannot be blank" was generated. This was a missed use case for a blank value of D_pxUserFromChannel in step 6 of pzCreateInteractionReply, and has been resolved. | Conversational Channels |
| INC-B949 | 858123 | 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
8.8.5 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-237044 | 744186 | Documentation updated for manually generating and applying the DDL | The Deployment documentation has been updated to clarify steps for generating and applying DDL for an upgrade if you do not want the upgrade to automatically apply the changes. | Data Integration |
| INC-267735 | 830292 | Resolved PageCannotBeSerializedForPassivationException error | Non-serializable java object values were being left behind on the thread parameter page as a result of parsing the SOAP response XML. This caused a PageCannotBeSerializedForPassivationException when the requestor attempted to serialize the parameter page. To correct this, code has been added to the Rule-Connect-SOAP Invoke and InvokeAxis2 activities and the ParseRuleUtils java module to clean up the parameter page after executing the connector or parse rule. | Data Integration |
| INC-A10091 | 830305 | Updated pxConvertPageToString for converting JSON | Discrepancies were seen in the output of pxConvertPageToString depending on whether the CasePage was JSON or XML when there were “Ref” properties that referenced data pages. Investigation showed there was an issue the prevented page properties that used "refer to data page" from showing in JSON. This has been resolved with the addition of a new pxConvertPageToString function to accept the parameter if reference properties should also be expanded to support JSON references to datapage. | Data Integration |
| INC-A11983 | 826908 | Null handling added to CFW snapshot | Client for Windows (CFW) was failing while attempting to execute snapshot[name].pxSubscript. In some scenarios the snapshot can be null, and the logic has been updated to handle this condition. | Data Integration |
| INC-A12214 | 826258 | Resolved timeout errors when using MSGraph | Sites which upgraded to MSGraph and blocked the default SMTP host smtp.office365.com were experiencing extraneous connection timeout notices related to the SendEmailNotification and SemSImpleEmailMessage activities due to an unused legacy connection call made by the JavaEmailClient constructor during the process of converting MSGraph messages to MimeMessages. To resolve this, the variable JavaEmailProfile::skipConnect has been introduced to skip the call in the JavaEmailClient constructor for sites configured to use MSGraph. | Data Integration |
| INC-A13631 INC-A10142 |
851006 846592 |
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-A14410 | 836507 | URLs in archived cases can be opened | A URL attached to a case could not be clicked to open after the case was archived. Investigation showed the Link-Attachment instance of Note and URL were archived so attachments were visible, but the Data-WorkAttach-Note and Data-WorkAttach-URL instances were not moved to file storage so the attachments of those types could not be opened. This has been corrected with an update to support archival attachments of type Data-WorkAttach-Note & Data-WorkAttach-URL. | Data Integration |
| INC-A1570 INC-A25696 INC-A18106 |
832943 844707 839071 |
Archived pegasocial-document display as expected | Attachments were not displaying for pegasocial-document archived cases. This has been corrected. | Data Integration |
| INC-A16919 INC-A15380 |
839469 839971 |
Documentation updated for REST API date format conversion | Effective with Pega version 8.8, DX APIs started emitting date/time in ISO format and the Clipboard started supporting ISO date/time formats. Information about this behavior change has been added to the ISO date/datetime API documentation for the Clipboard behavior. | Data Integration |
| INC-A17736 | 830588 | Security updated for debug logging | Potentially sensitive information could be logged when Debug was enabled for the RestConnector class. This has been addressed with an update which will mask the information. | Data Integration |
| INC-A19283 | 841128 | Added condition for pagelist mapping | If a pagelist already had a page, attempting to use a JSON data transform to map a pagelist using "Append and Map to" in manual mapping mode resulted in the mapping failing at runtime with the error "The property was of mode Page List while ClipboardPropertyImpl.getPageValue() was expecting Page mode." If auto map was used for the same pagelist, then the mapping worked. This was traced to a "wrong mode" exception when trying to retrieve the value from an empty pageList, and has been resolved by adding an if/else condition to retrieve the value when pageList is not empty. | Data Integration |
| INC-A19576 | 835370 | References to pzGetLocaleListSeperator updated to pyGetLocaleListSeparator | After update, extracting data for 3rd party stopped working. This was traced to the comma having been replaced with a semicolon in the locale list separator, and has been resolved by changing the outdated references to pzGetLocaleListSeperator to the new pyGetLocaleListSeparator. In order to preserve backwards compatibility, pzGetLocalSeperator will be utilized as a wrapper that calls the new pyGetLocaleSeparator. | Data Integration |
| INC-A20585 | 834410 | DevStudio Resources help query updated | The file rule pxJsAPI, used for opening the help document "Javascript API" from DevStudio Resources menu, has been updated to use pzpega_jquery_latest. | Data Integration |
| INC-A20809 | 837407 | Corrected Date Range control change event timing | When a Date Range control was configured with a refresh section or post action on change, three separate network requests were sent to the server. If there was an attempted interaction with the Date range control while waiting for a response from the server, the date range control stoped functioning. On clicking the date input, the calendar opened and closed right away. This has been resolved with an update which will fire the change event on the start and end dates only when the value changes, and the extra change event on StartInput which is causing the third network call has been removed. | Data Integration |
| INC-A20996 | 840040 | REST connector supports lax redirects | Support has been added to allow enabling lax redirecting for the REST connector by adding handling for a blank or null host for lax redirects and corresponding tests. | Data Integration |
| INC-A21896 | 860640 | 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-A22030 INC-A26836 |
845498 846728 |
Additional time zones supported for GMT conversion in en_US localization | Support has been added for converting the Singapore, Auckland, and Sydney time zones to GMT through the FormatDateTime(strDateTime, strPattern, strTimeZone, strLocale) function when using the en_US locale file. | Data Integration |
| INC-A22454 | 843849 | Corrected en_NL localization issues | After update, the DateTime field with calendar and decimal field were not working in the case manager portal when using the "en_NL" locale. This was traced to a change in the underlying JDK version used, where discrepancies in data returned are seen with JDK 8 and JDK 11. To resolve this, a locale XML file has been added, en_NL.xml, which returns the needed data irrespective of the underlying JDK version. | Data Integration |
| INC-A23729 | 845173 | Dev Studio security updated | Cross-site scripting protections have been updated for Rules and Ruleforms in Dev Studio. | Data Integration |
| INC-A2376 | 842777 | 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-A23783 | 841220 | Corrected parsing error for create case with special characters | The API was failing with a 400 error code when there was a special character such as "/" present in the create case request. Investigation showed the DX API was incorrectly recognizing escaped double quote, and this has been resolved by updating the switch case to handle strings. | Data Integration |
| INC-A24163 | 838214 | Case Archival documentation updated | Documentation has been updated to specify that Case archiving is available for on-premises and Cloud Choice clients for only the following databases: PostgreSQL, Oracle, and MS SQL. | Data Integration |
| INC-A24248 INC-A19517 |
837697 833717 |
Made debug logging conditional for Parse XML | Performance issues were seen when downloading an attachment. This was traced to previous work connected to debug logging for the Apply Parse XML rule, and has been resolved by wrapping oLog.debug calls with condition to check if debug logging is enabled and only then calculate parameters for logging. | Data Integration |
| INC-A24319 | 862517 | UpdateDataTypes activity cleared if data object missing | When attempting to merge a branch, if there was another branch with data object and that branch was removed from the application stack, an error was generated. As part of the branch merge process, an application save occurs and the app metadata is saved. Since the data object is there in the branch, when the application is saved it will check in the ruleset and fail due to the missing object. To address this, the step status in the pzUpdateDataTypes activity will be cleared if there is a failed step status after step#6: Call pzAssociateClassWithApp. | Data Integration |
| INC-A24646 | 843338 | Corrected check in error for Connect-JMS | After checking out the Connect-JMS rule, checking it in generated the error "CheckIn was unsuccessful. Original Instance does not contain Lock Information. Original Instance Handle : RULE-CONNECT-JMS @BASECLASS". This has been resolved by modifying the when rule pzSaveRefresh of @baseclass to be set to true for private edit so the latest rule set is picked up and the check in will be allowed. | Data Integration |
| INC-A24930 | 843344 | Corrected attachment delete after switch to new repository | View/Download actions were working after switching to a new repository, but deleting attachments failed. Investigation showed pzDeleteFromRepository was using application settings instead of fetching the repository information from the work/link attach tables, and this has been resolved. | Data Integration |
| INC-A25464 | 849690 | Expunger updated for use with CloudK environments | Archived cases were not deleted from secondary database as expected, and the error "Skipping expunge, environment is not running in the Pega Cloud." was generated. This was caused by Expunger using a validation logic which was only valid for Cuttyhunk-based environments. This has been resolved by updating Expunger validation for use in CloudK environments. | Data Integration |
| INC-A26110 | 849726 | 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 | 841065 | 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-A26768 | 843356 | Improved Client for Windows sync performance | The delta sync in Pega Client for Windows was very slow when posting multiple cases to the server. Investigation showed there was an SQL query being called twice in each delta sync, and this has been corrected to improve performance. | Data Integration |
| INC-A27036 | 846453 | 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. | Data Integration |
| INC-A27233 INC-B3280 |
849754 853311 |
Added failsafe to Redux ClipboardPage for missing reference | A context switch generated the exception "Caused by: external.clipboard.StacklessUnsupportedOperationException: Because lightweight clipboard mode is enabled, execution has failed. Message : Property is a reference or autopopulate property and is currently not supported by redux. on property reference". This has been resolved by adding support to Redux ClipboardPage so it sets a value for the reference property when one is not present. | Data Integration |
| INC-A2788 | 811939 | 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-A28040 INC-A24588 |
848514 847169 |
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-A28382 INC-A27118 |
851461 863520 |
Pega-Social attachment retrieval updated | An update has been made to recover Pega-Social documents which were not archived properly by using a hybrid approach to fetch the Rich Text attachment from the primary database if it is not present in secondary storage. | Data Integration |
| INC-A28696 INC-A11557 |
844495 828720 |
Updated data transform to use correct context for embedded properties | When using a JSON data transform to output an object with a property Page List, the properties were not being correctly mapped after encountering embedded pages. This has been resolved by popping the clipboard context after Append and Map to action. | Data Integration |
| INC-A29202 | 849707 | Support added for retrieving archived Data-Corr-PhoneText attachments | After archiving a case, attempting to open attachments of type "Phone text" generated an error. This has been resolved by modifying the activity pzDownloadArchivedFile to show Data-Corr-PhoneText attachments. | Data Integration |
| INC-A3880 | 812962 | Date field usage clarified | To avoid input issues, the usage details of the pxDateTimeisPastOrFuture function have been updated to explicitly state that 0000 is not a valid year for the input. | Data Integration |
| INC-A3999 | 831137 | Defer load logic updated for continuation of queue | The add criteria button was not bringing up autocomplete when configuring the engagement policy. This was traced to having multiple defer loads set for a section, and was caused by navigating to the home page before all of the deferred sections were loaded. The deferload queue is locked first, and when the defer-loaded section/layout is loaded, the queue is unlocked and proceeds to process the next item in the queue. In this case, one of the deferload-section network calls returned an error response on switching to the Home tab, and the queue did not unlock. To resolve this, an update has been made to unlock the defer load queue if the DOM is stale due to thread/context. | Data Integration |
| INC-A9470 | 840638 | Updated time zone handling for pyGetStartOrEndDate | The pyGetStartOrEndDate function gave an incorrect result when triggered at 11:00 AM. This was identified as an issue with the date formatting function formatInternalDate in the function pyGetStartOrEndDate which considers the GMT timezone for formatting the date. The output was correct for @DateTimeUtils.pyGetStartOrEndDate("currentmonth",false,true), but @DateTimeUtils.pyGetStartOrEndDate("currentmonth",true,true) returned the last day of the previous month instead of the 1st of the current month if the expression was tested before 11AM AEST. This has been corrected. | Data Integration |
| INC-A9934 INC-B11385 |
828445 862303 |
Extension of Pulse classes archived correctly | On enabling the Archival strategy, classes created under PegaSocial-Post were not indexed and purged as expected. This has been resolved with an update to archive Pulse messages which are descendants instances of PegaSocial-Post. | Data Integration |
| INC-B1130 | 861789 | Additional email processing logging added | Additional logging has been added to assist with diagnosing a NullPointer exception which was generated in a scenario where some emails were processed in the dev environment but not in the production environment. | Data Integration |
| INC-B11585 | 861416 | 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-B1193 | 862267 | 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 | 863010 | 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-B14380 | 864597 | 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-B1584 | 864667 | en_PH locale added | The en_PH locale file has been added to support the Philippines. | Data Integration |
| INC-B1736 | 854720 | 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-B3046 | 854537 | Added logging for Rule exceptions | Additional logging has been added to assist with diagnosing Rule Not Found exceptions. | Data Integration |
| INC-B3711 | 858657 | 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 | 859688 | 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-B5671 INC-A24457 |
858589 853301 |
JSch updated | The JSch (Java Secure Channel) library has been updated to the latest version. | Data Integration |
| INC-B6098 | 861336 | 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 | 856976 | 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-B6895 | 860371 | Corrected Mashup context when both applications are in the same domain | Inline assignment processing with Mashup was not working after update. This was traced to a context issue when both applications were on the same system. When a mashup is embedded in the same domain (within another application), the action within the mashup considers the parent window for actions within it. This results in setting null to cookies, which causes the session to be ended abruptly. To resolve this, changes have been made to consider the application name for validating isSafeToAskParent. | Data Integration |
| INC-B730 | 864630 | 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-B791 | 864554 | 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 |
Decision Management
8.8.5 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-249416 INC-A26195 |
766171 839825 |
Corrected handling for case completion prediction | The set response mechanism was not working for the case completion prediction. Analysis found that the properties "pxDecisionResults(1).pxDecisionTime" and "pxDecisionResults(1).pyGroupID" from the convert shape of the dataflow "pxDelayedLearningFlow" were causing the issue, which has been resolved with updates to StrategyStageProcessor. | Decision Management |
| INC-A11680 | 839843 | Updated handling for empty PropositionCache | No offers were delivered to customers as Strategy was not importing any offers. Investigation showed the Proposition cache was being refreshed from two different classes which resulted in an empty cache. This has been resolved by checking if cache data is empty or not, and if so, the cache will be refreshed with the correct application context. | Decision Management |
| INC-A12433 | 826434 | ADM node threads set to max 10 | Previously, the number of ADM node threads was auto-populated based on the calculation "CPU count * 2 - 1". However, in some environments this allowed as many as 200 threads. While the higher number of threads can help ADM in reducing the archiving job processing time, there were scenarios where memory issues were seen. To address this, the calculation now has an added ceiling of 10 threads set in the availableProcessors variable in AdmServiceConfiguration. This value may be configured locally. | Decision Management |
| INC-A12911 INC-B3007 INC-B899 |
829352 854257 852881 |
ADM model queuing criteria updated | Model Factories were being updated continuously without any changes to the ADM model or when there were no model responses to update. Due to the continuous update, table space was filling and performance issues were seen. This was traced to the Factory table not showing data for the model keys but there were records in the scoring table on Cassandra side, causing unwanted queries to be issued for these 'phantom' models. To resolve this, an update has been made so models are only queued for update by the ADM service when both the time interval is met and new training data is found. | Decision Management |
| INC-A1479 | 833875 | Ignore case option enabled for Pulse operator search | Operator search in Pulse was not working for SRS elastic search but worked as expected with an embedded elastic search configuration. This was caused by the SRS elastic search system using a case-sensitive query. There is a workaround of extending the rule 'pySearchContextPosts' RD from 'PegaSocial-Message' class, and in filter condition, selecting the 'ignore case' check box for 'pyActor', but this has been resolved by enabling the ignore case option from the setting in report filter for pysearchcontextposts report of PegaSocial-Message. | Decision Management |
| INC-A16047 | 832887 | Corrected query handling for non-UTC timezone | When a server was using a non-UTC timezone, discrepancies were seen for operators in other timezones. This has been resolved by updating the query "group by time" implementation to always use UTC-based time boundaries that align with the system's UTC-based partitions. | Decision Management |
| INC-A16902 INC-A24383 |
838618 839594 |
Corrected Globally Optimized Strategy emitting stale offers | After update, the Next-Best-Action (NBA) run was emitting stale offers for very first run after activating/deactivating any offers. This was an inadvertent side effect of work done to resolve latency seen in inbound API calls during Globally Optimized Strategy recompilation, and has been resolved. | Decision Management |
| INC-A18248 | 842174 | DSS added for expressionCompatibilityMode | After upgrade, expression conditions which checked for blank values were failing. This was due to a change in behavior in the more recent Pega releases where blank and 0 are evaluated as different values for properties such as TrueFalse, Decimal and Integer. In order to improve backwards compatibility, the DSS "decision/strategy/expressionCompatibilityMode" has been added. When set to "true" expressions are handled by SSA programs so that they work similarly to the previous behavior of evaluating blank as equal to 0. When set to "false" or unset, the expression evaluation will use the current behavior. | Decision Management |
| INC-A18449 | 842358 | Case statuse reflected accurately on data migration pipeline | The data migration pipeline showed import case creation failed despite it being created successfully in the candidate environment. This was traced to the service to create the import case returning a time-out error, which was caused by the work object not being committed until it encounters an assignment or a wait shape in the final stage. To resolve this, a wait shape has been added at the beginning in the first flow of the data import case so that the work object is committed as soon as it is created and the service signals the successful creation of the case back to the caller. | Decision Management |
| INC-A19109 | 831793 | Conflicting validation dependencies in ADM resolved | After update, the d-node could not be started. This was due to conflicting validation dependencies in the Adaptive Learning core library and the WebLogic internal module, and has been resolved by updating the version of the Adaptive Learning core library. | Decision Management |
| INC-A19934 INC-A28604 |
833081 844448 |
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. | Decision Management |
| INC-A20027 | 857500 | 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. | Decision Management |
| INC-A20145 | 837292 | Correct null pointer error for nested decision strategies | Decision Funnel simulation was failing in the Strategy execution when the source was a data flow that included another decision strategy as part of its logic. This was traced to a null pointer error when building decision strategy parameter page, and has been resolved. | Decision Management |
| INC-A21199 | 846501 | Check added for CDH instance | A PEGA0161 Adaptive Models alert was generated when there was no CDH instance involved. Investigation showed this was related to checking whether the pxHandleResponses dataflow was up because the javascript was placed into the Pega-DecisionScience ruleset. To resolve this, a check has been added to determine whether a DDS node is available for decisioning along with validating if the system has at least one prediction. | Decision Management |
| INC-A21243 INC-A24206 INC-A27923 INC-B14538 |
835120 838630 844361 865342 |
Handling updated for DDS service shutdown | If a node scale down happened while a resumable batch dataflow run was in progress, the DDS save operation failed with the error "dsm.dnode.api.ExceptionWithInputRecord: java.util.concurrent.ExecutionException: DdsPrpcConversionException: java.lang.IllegalStateException: Shutdown in progress". This was traced to an explicit check for shutdown in progress in the DDS save operation, and has been corrected. | Decision Management |
| INC-A21605 | 833184 | Updated handling for node partitions check | When performing a batch run, records could be processed multiple times if a scaledown happened during the process. In a batch run, the system will periodically go through all partitions assigned to a node and verify if they are still alive. Partitions assigned to dead nodes are unassigned so that another node can pick them up. However, if a node is STOPPING or LEAVING, it was be considered dead even though it might still be processing, and might therefore be considered unassigned. If another node picked up this partition before the first node finished, duplicate processing could occur. To address this, an update has been made to properly consider all node states that can still be doing the processing as alive, i.e. consider LEAVING and STOPPING states as alive. | Decision Management |
| INC-A22043 INC-B232 |
836165 846599 |
Conditional DSS added to skip S3 metrics | The D_pxListFiles utility can cause high memory consumption and lead to an out of memory condition when PegaAESRemote-Interface-CDHMetricsInfo is enumerating files on cloud storage. To resolve this, the DSS SKIPS3STORAGEMETRICSCOLLECTION has been added to allow configuration of this behavior. | Decision Management |
| INC-A22506 | 836044 | Updated SanitizedLogicString hash for InstancesCount | Given two actions where each had a specific criteria using a HasInPageListWhen function but with different comparison operator (> 0 vs = 0), only one function was generated in the internal method cache. This produced incorrect results for legacy execution / explain mode and decision funnel due to the result being the same for both actions, and has been resolved by updating the pzSanitizedLogicString hash by including pyInstancesCountValue. | Decision Management |
| INC-A22995 INC-B8955 |
838396 860970 |
Performance improvements for compiling globally optimized strategies | Compiling changes to the GOS_NBA_TOPLEVEL optimized strategies was taking an excessive amount of time. This has been addressed by implementing ForEach SSA compile time optimization. | Decision Management |
| INC-A23959 | 837848 | Corrected StringLength return type | An error in libraries/ssa/ssa-core/src/main/java/com/pega/decision/compute/ssa/function/functions/StringLength.java caused the return value to be string instead of the expected int . This generated the runtime exception "class java.lang.Integer cannot be cast to class java.lang.String". The function StringLength return type has been corrected to resolve this issue. | Decision Management |
| INC-A24131 | 839588 | Top-up can be turned off for browse operation | The browse operation for the Interaction History data set did not work when the Top-up DSS was enabled. When using the interaction history database as a source, the Summary dataset browse operation will get the list of IDs from either the _ih_customer_v2 table or by executing distinct(pysubjectid) on the fact table and then iterating over each key. This implementation was designed to support Top-up, but even when Top-up was turned off the behavior was the same. This is incorrect behavior: when Top-up is turned off it should just browse the summary dataset storage. This has been corrected. | Decision Management |
| INC-A24246 | 838172 | Decision session count shows correct value | There was a mismatch in session counts when capturing decisions and sessions. Investigation showed the Channel Group was not pushing to the PDC due to a property name mismatch, and this has been resolved. | Decision Management |
| INC-A24708 | 859851 | 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. | Decision Management |
| INC-A25200 | 843994 | Overhead of DSMClipboardPage size and keySet methods reduced | The DSMClipboardPage implementation was using the keySet method which utilized a ConcurrentHashMap iterator each time to walk through all the key properties defined in the class, regardless of whether they were actually assigned or not, in order to figure out how many of them were actually present in the actual page. To improve performance, an update has been made so that keySet walks only assigned properties and avoids creating an extra iterator. | Decision Management |
| INC-A25668 | 840996 | Corrected decision data reference validation | Strategy Validation was missing for the decision data reference on strategy save. This has been corrected. | Decision Management |
| INC-A25749 | 840887 | 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. | Decision Management |
| INC-A26904 | 846310 | Updated access check for Private Post attachments | Attachments were not visible or available for download when using the “Private Post” option. Investigation showed the GetAttachmentReference activity was failing when calling pzIsPrivatePostAccessCheck, and this has been resolved by changing the parameter handling for the access check. | Decision Management |
| INC-A27229 | 849879 | Updated Prediction Studio email digest generation | After configuring Prediction Studio to send an email digest, notifications appeared but the email was not sent. An AccessDeniedException error was generated. Investigation traced this to insufficient permissions to create a file in the environment, which was due to the system attempting to create a CSV file as part of the email generation process. To resolve this, the activity has been updated to use only stream to generate the notification and not create the file. | Decision Management |
| INC-A27774 | 844426 | Updated error handling for record parsing | If an invalid record was found and then a connection error was encountered during file browsing, the file data set failed during parsing of the records during retry. This was traced to an error in the file dataset implementation where the dataset retried the previous failed record instead of skipping it, and has been corrected. | Decision Management |
| INC-A28311 | 858442 | 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. | Decision Management |
| INC-A29495 INC-B7304 |
846299 864457 |
Sharable link security updated | Cross-site scripting protections have been updated for sharable links. | Decision Management |
| INC-A29620 | 849933 | 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. | Decision Management |
| INC-A29641 | 849295 | Added conditional rule handling and exception catch for Globally Optimized Strategies | While saving the GOS strategy, the exception "StrategyParserRuntimeException: Optimization failed to parse "XXXX" using IL parser because The type ILListType<ILPageRecordType[pageClass=XX-Data-Customer, typeRoot=BASECLASS]> is not supported in this context" was generated. This has been resolved with an update which will ignore unresolvable descendants rules when parsing an external-sub-strategy component. If the SSAUnsupportedExprException error is encountered, the system will catch it and fall back to legacy execution. | Decision Management |
| INC-A5643 | 826765 | Migrated ADM Rule saves correct ruleset details after edit | After update, privately editing an ADM rule or checking it out and checking it in again resulted in incorrect ruleset details. Investigation showed the migrated adaptive model had different predictors and the adaptive models adjusted the predictors as per the old configuration. To handle this missed use case, an update has been made to sync model configuration to the back-end using rule resolution in all editing scenarios. If needed, the activity Rule-Decision-AdaptiveModel.pySyncModelConfigurations has been made available to manually trigger a complete sync-up using rule resolution. Additionally, a banner has been added to the Adaptive Model rule form to inform that private checkout changes are not synced to the back-end service. | Decision Management |
| INC-A8663 | 819139 | Null check added to Interaction History initialization | During initialization of the Interaction History cache, a list of both empty and populated subject IDs was included. This led to the Interaction History failing to load when it tried to process a record with a empty ID for the subject, which then created an issue with the data flow run. To resolve this, a null check has been added to the initialization so Interactions with empty subject IDs will not be included. | Decision Management |
| INC-B11305 | 863514 | ModelSnapshots partitioning key modified | The partitioning key for pzModelSnapshots was initially set as pzInsKey. However, this had a negative impact on the batch data flow performance. To resolve this, the partitioning key for PzModelSnapshots has been modified to be ModelID. | Decision Management |
| INC-B11364 INC-B11973 |
860724 | Proposition cache properly refreshed | No campaign offers were delivered to customers. This was traced to the cache not being refreshed and the system pulse of type PROP not being not triggered, and was caused by previous work done to correct the proposition cache being refreshed from incorrect context. This has been resolved by updating the handling in pyReloadPropositionCache to remove a 'when' condition so the cache is properly refreshed. | Decision Management |
| INC-B12153 | 864334 | 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. | Decision 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. | Decision Management |
| INC-B14440 | 864311 | Updated handling of authenticated anonymous user in FUA | A globally optimized strategy compilation for Customer Decision Hub was failing on first use assembly (FUA) due to an authentication error when using OAuth 2.0. The errors "operator does not exist" and "UnauthenticatedThreadException: Could not authenticate thread with access group" were generated. To resolve this, an update has been made so than an anonymous user session (e.g. request from a REST call) which is already authenticated will skip the step to also verify the user ID in the database. | Decision Management |
| INC-B14837 | 865301 | 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. | Decision Management |
| INC-B14960 | 865466 | Support added for bulk contacts in BOE | Attempting to add bulk contact policies and save the constraints tab in the Business Operations Environment (BOE) was not working. This has been resolved by updating the pxManageBulkPropositionRecords function in order to allow addition of multiple contact policies at a time without issues in certain cases. | Decision Management |
| INC-B15053 | 864769 | 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. | Decision Management |
| INC-B1559 | 854683 | 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. | Decision Management |
| INC-B2027 | 849276 | Libraries updated | The spring-core and netty libraries have been updated to the latest versions. | Decision Management |
| INC-B2518 | 864502 | DSS added for VDB thread management | Visual Business Director (VBD) queries were not returning any result. This was traced to distributed operations (node -> node) reaching their time to live (TTL) thresholds, and has been addressed by introducing new dynamic system settings to manage the rest server and rest client thread pools. The DSS settings vbd/restServerWorkerThreads and vbd/restClientProxyThreads aer used to ensure the VBD-embedded REST server uses enough resources to be able to handle remote bucket operations in a timely manner. In addition, the retry mechanism of the bucket operation service has been improved. | Decision Management |
| INC-B4799 | 853562 | Condition label supports hyphen | Support has been added for non-standard labels such as "E-1" or "C-23" attached to condition rows in proposition filters. | Decision Management |
| INC-B4904 | 854715 | Corrected context for nested data transform | After update, data ingestion failures failed for a dataflow with a data transform shape which internally called data transforms based on embedded properties. Investigation showed that the context was not getting set correctly for the embedded data transform dataflow when it referenced a nested data transform, which was traced to the platform clipboard taking the class of the step page by default and only falling back to the class name from the argument when it's not available. This was a missed use case for resolving a data transform in DSM clipboard, and has been resolved. | Decision Management |
| INC-B5879 | 861175 | Made DDS availability datacenter-aware | The Data Distribution Service (DDS) SDK version has been updated to enable DDS availability check being datacenter-aware. | Decision Management |
| INC-B6754 | 861819 | Service limits pushed to PDC | The Service health limits tab was not available in the Customer Decision Hub (CDH) and Decisioning Usage landing page of the Pega Diagnostic Center (PDC). Whenever the CDH application is created, the SR class is automatically created in the format (AppId-SR). In one of the when conditions, there is a check whether the first part of the SR class == AppId; If true, the metrics are collected, and if false they are skipped. In this issue, the SR class was in different format. This has been resolved by updating the 'when' condition to proceed with the data collection. | Decision Management |
| INC-B7952 | 858480 | 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. | Decision Management |
| INC-B8811 | 865037 | 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. | Decision Management |
| INC-B9208 | 864463 | Security updated for edited Pulse messages | Cross-site scripting protections have been updated for editing Pulse messages. | Decision Management |
Low-Code Application Development
8.8.5 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-267156 | 834477 | Improved security for signatureData parameter | Handling for the signatureData parameter has been updated for improved security. | Low-Code App Development |
| INC-270434 | 821787 | Duplicate attachment check updated for iOS | In work done previously, a change was made to append a UUID to the attachname when the device = mobile and browser = Apple Safari. This was done to prevent photos captured through the camera app from being treated as duplicates when being attached to a case and was in response to the iOS default of naming all of the camera uploads as "image". As a side effect of this, UUID was also added to the images/photos uploaded through the gallery/library of an iOS device with the result that uploading a previously taken photo called 'image_205589' became a unique filename with the UUID added which was able to bypass a check for duplicate uploads. To address this, an update has been made to only add the unique ID when the filename is exactly equal to "image" and the upload is from an iOS device. | Low-Code App Development |
| INC-A17989 | 832061 | Corrected logic for conditional validations | A When rule should be used in a Validate rule that requires a combination of conditions such as "A AND B OR C". The When rule will also allow you to choose how the condition should be evaluated - "(A AND B) OR C" or "A AND (B OR C)". When multiple conditions are added directly in the Validate rule, they should use all ANDs or all ORs. In some scenarios the validate rule form allowed a combination of AND/OR conditions to be configured even though it is not a supported configuration, creating unexpected results. To address this, an update has been made so the validate rule can only be created with all ANDs or all ORs, and not a combination. When modifying one condition then all conditions will be updated. | Low-Code App Development |
| INC-A19242 | 835342 | Added check for pyInterestPageClass during validation | Given subflows executed on an embedded page of a different class which had some assignments displayed through the front end using DXAPI, a PEGA_API_001 / HTTP 400 error was generated on submit of the screen. A trace showed that the page data was being validated against pyWorkPage, which was a different class to where the embedded subflow/assignments was defined. This has been resolved by adding logic to check for the pyInterestPageClass and consider it while opening the flow action. | Low-Code App Development |
| INC-A23480 | 849331 | Rule actions updated for Siteminder compatibility |
Attempting to discard private edits on a rule generated a "403 Forbidden" error. This was caused by an interaction with Siteminder, and has been resolved by updating a number of actions including checkout rule, discard rule, expression builder and open rule within rule so as to not trigger Siteminder. | Low-Code App Development |
| INC-A23804 | 844379 | Post-upgrade decision table correctly shows horizontal scrollbar | After upgrading from Pega Platform Version 7 to Pega Platform version 8, the horizontal scrollbar was not visible for a decision table with a large number of columns and rows unless the page was scrolled all the way to the bottom. This has been corrected by adding grid CSS to the pZDecisionTable section. | Low-Code App Development |
| INC-A24726 | 843941 | Application Wizard security updated | Cross-site scripting protections have been updated for the Application Wizard. | Low-Code App Development |
| INC-A25287 | 848377 | Updated service export directory access for download | After update, the Usage Validation Utility (UVU) reports were generated but could not be downloaded. A 404 error was generated. This has been resolved by updating the access to the service export directory. | Low-Code App Development |
| INC-A25488 | 841101 | Logic updated to find unique rules for summary | When a branch had two rules of different types with the same name and same class, the API returned the wrong number of rules without unit tests. This was due to pxInsName being considered while finding out the number of rules that have Pega units. Since there can be multiple rules in a branch with same pxInsName but different type(pxObjClass), the logic has been enhanced to consider type along with pxInsName to identify a rule uniquely. | Low-Code App Development |
| INC-A26750 | 845999 | DSS expanded to allow missing properties for @when rules | Beginning with Pega version 8, the way properties are read off of legacy clipboard pages in the context of declaratives was changed. The current behavior is that an empty property is defined as missing and will throw the MissingPropertyException. This was a change in behavior from Pega version 7, where MissingPropertyExceptions were only generated when the property was not present on the page. In order to better support backwards compatibility for upgrades, the DSS "DecisionTable/ObtainValue/AllowMissingProperties" has been added. When this is set to true, decision tree processing will continue even if a referenced property is not present on the clipboard. To expand the use of this DSS, the ObtainValue function has been updated to allow missing properties for decision table @when rules based on the DSS value. | Low-Code App Development |
| INC-A30094 | 847622 | Increased record count returned by ConfigurationsForSet | The maximum number of records retrieved by the ConfigurationsForSet report used to fetch the list of configuration settings has been increased from 500 to 9999 to ensure all settings are listed. | Low-Code App Development |
| INC-B12671 | 862300 | Security improved for exporting CSV | The Export to Excel function has been updated to improve security when handling CSV files. | Low-Code App Development |
| INC-B13711 | 863548 | 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-B1439 | 854178 | Test case count logic updated | After update, incorrect test case numbers were shown in the summary of test case reports when compared to the drill down. This was an inadvertent side effect of work done regarding test cases from removed rulesets, and has been resolved by updating the logic. | Low-Code App Development |
| INC-B3467 | 855568 | Security updated for showGrid | Cross-site scripting protections have been updated for showGrid. | Low-Code App Development |
| INC-B3573 | 857916 | 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-B4251 INC-B6712 |
854404 856895 |
Modified case usage data agent | The execution of PushDailyCaseData was returning more than 3 million rows which were then attempted to be added to clipboard in a report. This caused memory to get full and cause node instability which resulted in cases being carried over to the next day. This has been resolved by updating the group-by clause for a report definition to improve the handling. | Low-Code App Development |
| INC-B6162 | 856165 | 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-B7822 INC-A18210 |
860122 829740 |
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 | 862169 | 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-B8353 | 860797 | EntityRelationshipDiagramNavigation search button made accessible | pzEntityRelationshipDiagramNavigation contained a search button that was missing an accessible label, resulting in JAWS announcing “button, to activate press enter. This has been corrected. | Low-Code App Development |
Mobile
8.8.5 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A13899 | 829880 | Sync error message properly displayed on mobile | An empty message was shown on mobile if there was a sync error. Investigation showed this happened when the work object was being processed in the browser at the same time as on the mobile device, and was caused by the ErrorSync record being assigned an empty value. This has been resolved by updating the handling to preserve the error and display it. | Mobile |
| INC-A21383 | 835081 | 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-A25025 | 846332 | 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. | Mobile |
| INC-A26432 | 844848 | Corrected signature capture for offline mobile app | After update, the signature capture in the Pega Infinity Mobile Client (PIMC) worked on the first offline use, but subsequent uses were not capturing the signature correctly. Investigation showed the drag gestures were not received by the control but rather passed to the outer UI controls after the first use, and this has been corrected. | Mobile |
| INC-A9285 | 828230 | Unchecked "Allow use as reference property" for MinHCVersionIOS | The pyMinHCVersionIOS property was being set on Application page that was being verified or accessed during certain clipboard operations even when no mobile-based config was being used. Per property definition, the property used the "Allow use as reference property in activities" checkbox. Some of the clipboard operations were then interfering with the Application page in clipboard, resulting in the error "Property is a reference or autopopulate property and is currently not supported by redux. on property reference : .pyMinHCVersionIOS". To resolve this error, "Allow use as reference property in activities" has been unchecked on the pyMinHCVersionIOS property rule-form. | Mobile |
| INC-B1391 | 849160 | 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-B2102 | 865045 | 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 | 863578 | 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
8.8.5 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-216135 | 710294 | Documentation updated with BIX extract ORA-00942 error resolution | The documentation for the extract rules overview has been updated with information about how to resolve the ORA-00942 error by updating the privileges granted to the platform Oracle database user. | Project Delivery |
| INC-A24094 | 841766 | DX API documentation updated for preserving special characters | Documentation for the DX API has been updated to clarify that when using special characters like '%3D' (which are not be escaped) in query parameters, encodeURIComponent must be used in order to prevent escaping the characters when building a request. | Project Delivery |
| INC-A26631 | 843037 | Documentation clarified for MS Graph configuration | The documentation for configuring OAuth 2.0 authentication for sending and receiving emails by using Microsoft Graph has been updated to clarify that the permission type must be Application. | Project Delivery |
| INC-B5790 | 860627 | 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 |
Reporting
8.8.5 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-180408 | 833106 | Handling improved for BIX 'Use last updated time as start' filter | A runtime error was seen when processing BIX extract rules if the BIX filter "Use last updated time as start" was selected. Investigation showed that this was caused by a socket timeout error related to the filter's use of pxCommitDateTime causing a full scan of the interaction table which contained more than 10 million records. This has been resolved by updating the extraction rule to use pxSaveDateTime instead of pxCommitDateTime for the incremental extraction. | Reporting |
| INC-250429 | 769343 | Report editor pagination link made accessible | JAWS was not correctly reading the report editor pagination link. This has been resolved by updating the page link to include aria-label with "Page #" and the href to enable tabbing through page numbers. | Reporting |
| INC-263976 | 807240 | Corrected unneeded decimal localization for Dutch locale | When using the Dutch locale (nl_NL), the progress chart in a section showed 100% complete as "1,0". Investigation showed the chart control center label "percentage" setting was localized too early during the pxFormatValue -> pxFormatNumber call. This transformed "1.0" to "1,0" which then failed to be converted to a percent. This has been resolved by updating the appendFormattedString in AbstractJsonDataGenerator to avoid localizing for this specific situation as the final percentage value will be localized afterward. | Reporting |
| INC-269550 | 801426 | 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-270198 | 801460 | Improved handling for SRS outages | When the Search and Reporting Service was down for a period which exceeded the set retry limits, items went into a broken state. To resolve this, queue retry attempts have been increased to 6 for SRSUnavailableException and PurgeLogicResponse.unavailableSRS() in order to avoid broken items when a status 503 response is received during SRS snapshots. The DSS indexer/srs/maxInitialRetryAttempts can also be used to change the default maximum 3 retry attempts for connection problems and responses with HTTP status codes other than 200 or 503. | Reporting |
| INC-271384 | 809592 | Invocation from browser enabled for report filter actions | After update, dragging and dropping columns to the report filter area to add a filter condition was not working, and an error indicated the activity could not be called directly: "You lack access required to execute Rule-Obj-Report-Definition.pzDropNewFilterFromColumn. Attempting to reorder the columns in the report table display similarly failed with the error "This activity may not be called directly from input: RULE-OBJ-ACTIVITY CODE-PEGA-LIST PZREORGANIZECOLUMNSWRAPPER". After examining the security implications, an update has been made to enable the "Allow invocation from browser" check box in the security tab for Activity pzDropNewFilterFromColumn and pzReorganizeColumnsWrapper. | Reporting |
| INC-A15578 | 827994 | 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-A20600 | 837572 | SRS indexing handling updated for pattern inheritance turned off | After update, SRS indexing failed with the error "Unknown property: MemberID" when pattern inheritance was turned off. This has been resolved by updating the inheritance algorithm name in the indexing request from patternAndDirect into flatParentHierarchyList which was previously calculated by the indexer and contains the correct inheritance order. | Reporting |
| INC-A21986 | 859196 | 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 |
835685 858570 |
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-A23823 | 842757 | Permissions updated for Landing Page | The Show Data option was generating a "403 Forbidden" error after performing a refresh in the Chart Actions drop down of the Landing Page. This has been resolved by adding the needed registration code in the pzBACActivityRegistration section. | Reporting |
| INC-A24184 | 860830 | 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-A24184 INC-B1888 |
852584 859919 |
DSS added to support indexing data page retrieved automatically | After migration to Cloud services, a nested custom data page was not being indexed. Investigation showed the data was stored in the ClipboardPage but SRS was not trying to check it. To resolve this, a DSS has been added to enable/disable indexing data retrieved automatically from a data page. This setting is available during serialization to JSON in the MetadataCollectorSettings field 'indexDataRetrievedAutomatically', and the default value is 'false' to disable this feature. | Reporting |
| INC-A24283 | 838833 | Updated date range picker filters in Insights | After configuring an Insight with Date or DateTime as a filter, using the Date Range picker type to narrow down the results retrieved with the preselected date values was not working. This has been resolved by updating the DateRange picker condition to use the BTW function to calculate the dates. | Reporting |
| INC-A24595 INC-A27741 INC-B5459 |
838038 848059 857460 |
PD4ML updated | PD4ML has been updated to the most recent version to correct layout issues and improve security. | Reporting |
| INC-A26127 | 852925 | 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-A27657 INC-A25829 INC-A26791 INC-A25829 INC-A22348 |
842821 842754 843248 842737 836523 |
Report display corrected | Display issues were seen after update when viewing reports, including the "Review Report" table not being properly placed in the white box. This has been resolved by modifying the format of the container to noHeader in the DisplayReport harness. | Reporting |
| INC-A28875 | 847771 | Corrected SRS serialization error | During the serialization process for external search and reporting, the stack trace error "java.lang.IllegalArgumentException: [Indexer][Data model] Cannot find data model for entity" was generated. This has been resolved by removing an unnecessary conditional check | Reporting |
| INC-A29777 | 858185 | SASIncrementalIndexer alert default raised to 250,000 items | The pySASIncrementalIndexer queue processor was configured to generate a PEGA0134 error at 100,000 items in its queue. As there are large sites which may encounter circumstances where there will be more than 100,000 items awaiting index update, the default value has now been increased to 250,000 items for triggering an alert. This setting is customizable if a different value is desired. | Reporting |
| INC-A4701 | 823044 | 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-A6961 | 832581 | Updated BIX creation in branch | When BIX was created in a branch with filters added, merging the same rule to the base application and trying to Check out and save generated the error "Filter Name—This is not a valid property, or this is a property that cannot be used here.". This was traced to an issue with ruleset context. Internally, BIX makes use of a report definition. When the BIX rule is created in a branch, then the ruleset is a branch ruleset for the report definition as well. Merging a BIX rule to the base application moved the BIX ruleset but not the hidden report definition ruleset. To resolve this, the ruleset of the report definition will be updated in alignment with BIX to ensure the proper context. | Reporting |
| INC-A7619 | 822612 | 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-A9770 INC-A30100 |
822465 847779 |
Sort works in portal reports | Sorting alphabetically did not work in portal reports when a specific category was selected. This was an inadvertent side effect of previous work done to allow sorting when using a data page, and has been resolved. | Reporting |
| INC-B10398 | 860912 | 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-B10861 | 860890 | Improved security for DisplayReport | Cross-site scripting protections have been updated for the DisplayReport activity. | Reporting |
| INC-B2629 | 850885 | Corrected custom report display for "right to left" locales | When using an Arabic locale, the columns section did not appear for custom reports and the UI was not displaying correctly. Investigation showed the application styling was not correctly considering the "Right to Left" settings, and this has been corrected by updating the pyReportEditorStyling CSS. | Reporting |
| INC-B3466 | 851646 | Report Editor security updated | Cross-site scripting protections have been updated for the Report Editor. | Reporting |
| INC-B4356 | 858242 | 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. | Reporting |
| INC-B4697 | 861761 | Copy/Move Report Definition Shortcut behavior updated | 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 | 860478 | 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 |
Security
8.8.5 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A19870 INC-A30017 |
832239 847031 |
Signature algorithm made case-insensitive | The error "Signature algorithm is null" was seen in the engine class . This was traced to the signature algorithm being identified as 'SHA256WITHRSA,' while in the signature map, the key is maintained as 'SHA256withRSA.' Due to this case mismatch, the signature algorithm was recognized as NULL, resulting in a failure of the SAML login. This has been resolved by modifying the map to accept case-insensitive keys. | Security |
| INC-A24541 | 864623 | 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-A3941 INC-A17472 |
836303 836171 |
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 | 863324 | Security improved for autocomplete | Cross-site scripting protections have been updated for autocomplete. | Security |
| INC-B423 | 851166 | 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 | 857912 | 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 | 855471 | 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-B6306 | 858238 | 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 | 861645 | 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 | 864320 | 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
8.8.5 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A12381 INC-B914 |
832386 852236 |
Improved job scheduler rescheduling | A job scheduler configured to run every day except Sunday at 19:00 hours displayed unexpected behaviors such as not scheduling a job for a specific Saturday, or missing a run which then had to be manually triggered. Investigation showed the job scheduler which was run on all associated nodes (no locking) multiple times a day had an activity which was processed really quickly (e.g. empty activity). This caused other jobs to start running a couple of milliseconds before schedule. After the mechanism detected that the job scheduler execution was triggered too early (ex 18:59:59,994) it decided to recalculate the execution launch time again and reschedule. Usually it gets rescheduled to couple of milliseconds later, but in this case rescheduling took place at 19:00:00,005, which generated next runtime for the next day. This has been resolved by adding verification before job execution. | System Administration |
| INC-A13505 | 840455 | Updated handling for calculating externalized Kafka lag | After moving to External enterprise/centralized Kafka, the Ready to Process column did not show how many records were still to be processed by the queue processor. This was traced to the lag calculation process timing out due to an increased latency when fetching offsets from all Kafka data centers/racks, and has been resolved by introducing a new mechanism to calculate lag. | System Administration |
| INC-A23287 | 838602 | MonitoredShutDown thread close added | Shutdown tasks are sometimes unable to shutdown the executorServices (which hold executing threads for Agents, Job Schedulers and Async Services Executor) within the 5 minute time limit, causing system hang. To address this, an executor pull shutdown has been added to mitigate hanging threads after shutdown is completed and a thread dump will be generated. | System Administration |
| INC-A27908 INC-239397 INC-B9531 INC-B11862 |
862491 814346 862000 862017 |
Corrected property handling in Rule Assembly | A large number of Rule Assembly alerts were being generated which were affecting performance. This was traced to the assembly not being correctly saved to the database due to the value of the ExplictMetadataIsReliable property being set as false for one DependentRuleInfo. This value handling has been corrected. | System Administration |
| INC-B1033 | 855351 | 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-B1862 INC-A5927 |
851204 822045 |
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-B2813 | 857474 | Handling updated for MessageContent exception logging | In order to ensure pzMessageContent does not include potentially sensitive information when a queue processor queue throws an exception, an update has been made to sanitize the XML and JSON before sending to the log. | System Administration |
| INC-B5743 INC-B2491 |
855815 855148 |
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 | 861686 | 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-B6613 | 859054 | 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. | System Administration |
| INC-B6892 INC-A11374 |
859161 831399 |
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-B9892 | 859873 | Revised handling for Queue Processor loading | In order to ensure application logic is correctly applied to messages based on the order in which items are processed after node shutdown or restart, an update has been made to sort by timeforprocessing in ascending order when reading from the data.pr_sys_delayed_queue. | System Administration |
User Experience
8.8.5 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-243030 INC-A30138 |
757695 849941 |
Focus Indicator shows for Expand/Collapse Headers on skin | Changes to the onFocus of Expand/Collapse Headers on the skin rule were not reflected on the Case Manager portal. This has been resolved with a modification which will change the tab index for the main div instead of the inside div. | User Experience |
| INC-244187 | 756161 | Image annotation registered with BAC | Annotation of an image not working in the user portal, but did work when the user had access to Developer Studio. This has been resolved by registering the activity in the pyAnnotateArea section for BAC. | User Experience |
| INC-248981 | 764954 | Screen reader correctly announces accordion button status | When a layout group(accordion) was overridden in the application skin and the checkbox was checked for "Collapse all panes on load", the panes were collapsed on load but the screen reader was announcing the state of a button as expanded even though it was collapsed. This was traced to the aria-attribute handling, and has been resolved by adding a multi-accordion identifier and updating the logic in layout group js to toggle multi-expand accordion independently. | User Experience |
| INC-251607 INC-246272 |
772996 772990 |
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-268337 | 800890 | Semantic tab headers read by JAWS 2023 | Tabs including a heading element were skipped by JAWS 2023. This has been resolved by adding role presentation for semantic tabs. | User Experience |
| INC-270184 | 798076 | Corrected Iframe UI appearance | After update, the UI in Iframes was displaying at a reduced size. This has been resolved with an update to set the proper mashup height. | User Experience |
| INC-A10466 | 831291 | JAWS correctly announces OperatorImage icon | When the work object was assigned to a work basket / work queue and not a specific operator, JAWS did not narrate the operator icon correctly. This has been corrected by updating the tags. | User Experience |
| INC-A13846 | 827802 | JAWS correctly announces null read-only fields | When using arrow keys to navigate read-only fields with JAWS 2022, JAWS was reading "ndash ndash" for read-only fields which had null values. This has been resolved by adding accessibility support for no value so JAWS will announce the field is blank. | User Experience |
| INC-A14098 | 831403 | Corrected accessible labels on controls when using autocomplete | Using an autocomplete with "additional field set" configuration was preventing other controls such as text input or dropdowns from getting accessibility names. This was caused by hidden fields that were generated from the autocomplete control based on the "additional field" configuration. Since ID generation is based on the property name, these hidden fields had the same ID as the manually-added other control for the same property and resulted in an empty accessible name. This has been resolved by removing the ID for hidden fields. | User Experience |
| INC-A14548 INC-A24703 INC-A30073 |
831347 843639 855153 |
Corrected section assembly error | Loading sections was generating the message buildWhitelist_1();pzSectionBody_1() on UI. This was traced to pzAssemblepreprocessor becoming corrupted, causing an issue with stream assembly. This has been resolved by adding a check to the section generation and log a warning while also correcting the generation code to run down the auto-generated path. | User Experience |
| INC-A14647 | 831390 | UI accessibility improvements | To improve accessibility, the “Preview” button in the Notifications panel has been enhanced with a soft light border to make it more visible on a dark background. Universal focus styling which works well with both light and dark backgrounds has been added to Theme Cosmos to improve contrast in the left navigation panel. Additional tuning was done on the focused bookmark icon button color and the “Preview” button opacity in Notifications when the link is focused. | User Experience |
| INC-A14978 | 832782 | Focus moves to alert message as expected when tabbing | An alert message that obscured a portion of the screen unexpectedly required tabbing multiple times to be able to access the close button. This has been resolved by updating the pxhamessage-script-wrapper function to bring focus on close button. | User Experience |
| INC-A15224 | 845733 | Google Map reuse flow updated | After update, the Marker Info section map control was not loading. This was traced to a local configuration which was reusing the Google Map object, and has been resolved by updating the pypega_map_googlegis and pzpega_ui_addressmap files to better support the Google Map reuse flow. | User Experience |
| INC-A15251 | 835003 | 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-A15272 | 830865 | Defer load inside Dynamic layout group updated | After upgrade from Pega Platform version 7 to Pega Platform version 8, defer load inside a dynamic layout group was not working, and the contents were loaded at the time loading the screen itself. This has been corrected by updating the logic for isDeferloadDLG from DynamicLayoutTemplateCell.java. | User Experience |
| INC-A15284 | 831587 | Support added for Checkbox control for property with declare expression | The checkbox control was not displaying the true/false text configured for the control in section when using a property with declare expression. This has been resolved by adding the logic necessary for this use case. | User Experience |
| INC-A15513 | 832400 | Added handling for empty caseNavigation menu | The Summary Panel was not expanding after being collapsed on the Case View when the caseNavigation menu item was empty. This was traced to a customization for CaseNavigation which selected "Separator" as the type. In this scenario, when toggleSummaryPanel executed on click of the icon to toggle the summary panel, an undefined error was generated due to navList resolving to an empty array. As using CaseNavigation without a navigation item is not supported, an update has been made to handle this configuration by overriding the template and removing the existing menu. | User Experience |
| INC-A15879 | 832788 | Case navigation menu displays details tab by default | The Details tab on the left summary pane was not shown as default tab when switching between cases. This was traced to the caching key handling, and has been resolved by adding workID to the menuID. | User Experience |
| INC-A16652 | 829402 | Run time content reflected in Rich Text Editor | As part of a local action which sends email from a case, an email template is selected from a dropdown list. The view uses a property "Body" of type Text (Paragraph) with RichTextEditor as "Display As" option, then the data is dynamically populated using a pyRefreshData data transform. The Body property was properly set with the email source stream on the Content Page, but while all simple properties were displayed, the template was not. This has been resolved with an update which automates Rich Text Editor content assertion on assignment refresh. | User Experience |
| INC-A16713 | 838131 | Corrected duplicate header announcement | The accessibility popup dialog was announcing the heading twice. This has been corrected by changing aria-labelledby to aria-describedby in the modal wrapper Dialog_Title. | User Experience |
| INC-A16740 | 834703 | AJAX tab names display special characters correctly | Tab names containing special characters were not displayed as expected when using an AJAX container. This has been resolved. | User Experience |
| INC-A16975 | 837511 | Handling added for data pages with parameters containing ampersand | A 400 HTTP error was generated when using the getPageDataAsync PCore API to retrieve a page type data page by passing a data page parameter value containing an ampersand (&). A 500 HTTP error was generated when using the getPageDataAsync PCore API for retrieving a page type data page by passing a data page parameter value containing ampersand URL encoded. This has been resolved by updating the handling for decoding the input/parameter value to avoid error codes 400 & 500 when the URI contains encoded values. | User Experience |
| INC-A17145 | 832670 | Modified check-in for Helper Text configuration in Sections | Checking out any section which has Helper Text Configuration as 'Help icon with overlay on focus' and then checking it in without making any changes to the Helper Text configuration caused the Helper Text configuration to change to 'Tooltip (not recommended)'. This was traced to pyModes() being in an unexpected state which caused the pzUpgradeOnOpenHelperText activity to reset the pyHelperTextType property incorrectly. This issue was limited to Pega Platform patch version 8.8.3, and has been resolved. To ensure the issue does not occur on higher release versions, the pzUpgradeOnOpenHelperText activity has been modified to prevent this issue. | User Experience |
| INC-A17190 | 833582 | Corrected table focus issue for primary column | When tabbing into a table with select all checkboxes, the focus was not on the intended checkbox element and the table was able to be navigated via the tab key. If a column was marked as primary and one of the cells contained an item that could receive focus, it was possible to tab to that as an element. This has been resolved by correcting the focus issue when a column is marked as primary. | User Experience |
| INC-A17474 INC-A5981 |
831673 844590 |
Home screen correctly loads when skipDocsRecreation is true | When pega.u.d.skipDocsRecreation was set to true, the harness only displayed a white screen. This has been resolved by adding code to load the home screen when skipDocsRecreation is true. | User Experience |
| INC-A17551 INC-A23866 |
829872 838648 |
Toggle added for resize Rich Text area button availability | The option has been added to toggle the availability of the resize button on a Rich Text Editor area using the enableResize setting. The default for this is =true to make the resize available. | User Experience |
| INC-A17922 | 836584 | Handling updated for case in review mode | When moving a case from one stage into another where the target stage contained a process which was not executed by the operator, the local actions at stage level could not be selected anymore and the message "Uncaught TypeError: m.caseInfo.assignments[0].actions is undefined" appeared. Investigation showed that in the failing case, the actions were not present in the openLocalAction API with the result that the local action modal did not appear on the screen. To resolve this, a condition has been added to the openLocalAction API so that if a case is in review mode, the step to save the assignment will not be executed. | User Experience |
| INC-A17974 | 833240 | Mobile check added for autopopulate control | After update, a screen using an autopopulate dropdown control worked on the desktop application but did not work on mobile. This has been resolved by adding a check for !isMobile before calling the setXY function. | User Experience |
| INC-A18376 | 834739 | Corrected preview panel close button focus | When Preview Panel was launched from the Notifications list on the left-navigation bar, focus did not stay in the preview panel after it loaded. This has been resolved by removing an unintentional focus action. | User Experience |
| INC-A18620 | 833831 | 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-A18659 | 833603 | Revalidate and Save handling updated for Design Template-based sections | Revalidate and Save was failing due to locked rulesets not being available to accept the pzGenerateView output, the final stage of Rule-HTML-Section.Validate. To address this, the Rule-HTML-Section Validate activity has been updated to only generate a view if the section being validated is in an unlocked ruleset. | User Experience |
| INC-A18916 | 832539 | Added Iframe registration to support upgrade | After upgrading from Pega Platform version 7 to Pega Platform version 8, the flow action was submitting instead of only saving when using a save button or control in the flow action. Investigation showed that when trying to click on Save in the perform harness, the case is moving to the review harness and the background Finish assignment was getting triggered from Work- .ActionHTML of Pega-EndUserUI. This occurred due to the use of the deprecated Iframe-based action area, and has been resolved by registering the activity. Note Iframes is a deprecated functionality, and it is recommended to update to use pyActionArea. | User Experience |
| INC-A19025 | 836169 | Logo appears in Constellation | After uploading the logo from the channels, the logo was not visible in the staging and production environment. This has been corrected. | User Experience |
| INC-A19409 | 831467 | Added handling for locales with multiple underscores in the name | Singapore-based users were unable to use Google Chrome to access an EMEA-hosted Pega Cloud Constellation application when the locale in the profile was left blank so the locale was taken from the browser. Investigation showed that when Google Chrome is set to "English (United Kingdom, Oxford English Dictionary spelling)", the locale code sent from server is "en_GB_oxendict". In environment-info > setLocale function, only the first underscore (_) was replaced with dash (-) so the locale value became "en-GB_oxendict", which is invalid. There is a workaround of setting the locale, for example "en_SG", or changing the Chrome browser language to English (United Kingdom), but this has been resolved by adding handling for a locale which contains multiple underscores. | User Experience |
| INC-A19688 | 834231 | CaseID correctly displayed as Tab title when case is opened in new Tab | When case was opened in a new tab, the case ID was not displayed in the Tab title. Instead, the portal name "User portal" was displayed. When case was opened in the same tab, the case ID was correctly displayed as Tab title. This was a missed use case in actionrouter.js for the portalCategory when a case was opened in a new tab, and has been resolved by updating the condition to check for formFactorIframe. | User Experience |
| INC-A19993 | 834324 | Conditional check added for validation | Client-side validation failed to trigger for an autocomplete field after selecting from the list. This occurred when the autocomplete option was selected using keyboard, and was due to calling the "gridmousedownhandler" two times (onkeydown, onKeyup). This caused the second time to add tempvalidation as "null", leading to validationtype being null. This has been resolved by adding a conditional check for validation. | User Experience |
| INC-A20921 | 834473 | Corrected empty view after performing process action assigned to WorkQueue | When using Pega Constellation, triggering the optional process (included in a particular stage of a case type) to transfer an assignment to another user using the three dot action menu either resulted in the screen loading without any value or loading without any button to take action. Performing a browser refresh reset the screen. This was traced to an issue with invoking pzSetAssignmentInfo for loading nextAssignmentInfo and navigation details (actionButtons), and has been resolved. | User Experience |
| INC-A20951 | 853546 | Updated pyCompactStylesforPDF to ensure expected font handling | Adding font families for Chinese characters in PDFs was not generating the expected results. This was traced to pyCompactStylesforPDF not picking up the correct font family due to PD4ML ignoring the first CSS from the file, and has been resolved by adding "#{}" in the beginning of this file to get the styles/fonts picked in the generated PDF. | User Experience |
| INC-A21115 | 836183 | Insights returns correct day data | After defining the cases, Custom insights was picking up data cases created in the following day. However, drilling down and selecting 'View data' displayed the correct data. This was traced to a date handling issue, and has been resolved by updating the ConditionBuilder handling of the Z offset for UTC dateTime. | User Experience |
| INC-A21269 | 833268 | Corrected validation message display in two column layout | The validation message generated from the date control was overlapping the other controls the Theme Cosmos when the date control was embedded in a dynamic layout designed as two columns or 2 columns layout. This has been resolved by adding a separate "white-space" styling to the error div so it can wrap as expected. | User Experience |
| INC-A21302 | 837799 | Added apostrophe handling in locale strings | Creating a home field property that contained ' (apostrophe) resulted in a blank screen when converted to the French locale. This has been resolved by sanitizing variables that are used for string values in the file. | User Experience |
| INC-A21970 | 839358 | Corrected manually entered date handling for ko_KR | Manually entering a calendar date in the "ko_KR" locale generated an error indicating it was not a valid date value. Selecting a date from the calendar picker worked as expected. This was caused by the handling for the separator and has been resolved. | User Experience |
| INC-A22151 | 839795 | 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. | User Experience |
| INC-A22304 | 844747 | Added check for Mashup field values | After upgrade, gadget file contents were executed during Mashup but nothing happened after that call. This has been resolved by adding an undefined check for field values list. | User Experience |
| INC-A22337 | 835528 | Corrected focus issue when link control is present in table | When an optimized table contained a link element, hovering over the link changed the tab-index to 0 which incorrectly allowed the link to be focusable by tab. When a link was not present, the cells were correctly only able to be navigated to via the arrow keys.This has been corrected by adding a condition to prevent changes of tab-index inside the table. | User Experience |
| INC-A22549 INC-B13424 |
836031 863093 |
Updated handling for temporary page used by Notifications | The Notification preference settings page from the Notifications bell icon was not loading and the error "There has been an issue; please consult your system administrator" was generated. Investigation traced this to an improper Page-remove in pzGenerateMessageSubscription, and this has been resolved by renaming the temporary page name to TempNotificationChannelPage in the pzGetChannelByName activity. | User Experience |
| INC-A22887 INC-A28410 |
837058 845760 |
Modal heading coding corrected | Visual headings in modal dialogs were coded as 'span' instead of the HTML heading. This has been corrected by changing span to the h2 tag for modal heading in pzmodalheader, and modifying aria-labelledby to aria-describedby in the template form for improved accessibility. | User Experience |
| INC-A22948 | 838972 | Localization corrected for pyStatus work value with special characters | The pyCaption value for an optimized grid was not being localized when the pyStatuswork value contained parentheses. This was due to special characters in table cell values being encoded using the crossScriptingFilter stringUtils API, and has been resolved by using restoreFilteredString to restore the encoded characters and use the result to get the localized string. | User Experience |
| INC-A23541 | 840064 | Updated text color styling for Create menu | After clicking on the Create menu in a portal, the menu was expanded but the "Create" menu item became hidden due to the text color being white on a white background. This was an unintended side effect of work done previously around preventing color changes for submenus from spreading to the expanded Create item, and has been resolved by removing hardcoded CSS and instead us mixins for styling for the Create menu. | User Experience |
| INC-A23582 | 839333 | Optimized grid filter works when sorting disabled | After update, attempting to perform filtering of the columns across all tables of an optimized grid with the 'enable sort' option in the column disabled was unexpectedly showing the funnel icon instead of setting icon (3 dots). This was due to design changes in table filters and sort, and has been resolved with an update to pzpega_ui_template_grid_helpers which will show the filter icon in the menu item for an optimized grid. | User Experience |
| INC-A23674 | 840620 | Improved accessibility for expanded/collapsed My Worklist | In order for the pyWorkItemOwnerDropDown section to function like a menu and allow JAWS to read the expand/collapse state of the "menu", myWorkListWidgetExpandCollapse has been added to the section to handle the aria-expanded attribute on the My Worklist widget header. | User Experience |
| INC-A23976 INC-A29658 INC-A27981 INC-A23976 |
843309 846645 851950 845886 |
Rich Text Editor security updated | Cross-site scripting protections have been updated for the Rich Text Editor control. | User Experience |
| INC-A24244 | 841166 | "Today" flag in DateTime picker set to local time zone | The default date in the DateTime picker was displayed based on the timezone configured in the operator profile, but the flag and Today option was showing based on GMT. This has been corrected with an update to show the triangle on Today's date based on the user selected time zone. | User Experience |
| INC-A24973 | 845797 | Handling added for default attachments category | When the default FILE category for attachments was deleted and custom attachment categories were present, no default category was selected even if there was only one category. To resolve this, an update has been made to set the default category to be the first category in the categories call response if the 'File' category is not present in the response. | User Experience |
| INC-A25293 | 841839 | Resolved MashUp URL issue | Cross-site scripting filters have been updated to add validation for context URL when using MashUp. | User Experience |
| INC-A25324 | 854652 | JAWS reads property label along with help button | In order to improve accessibility, a field label value has been added inside the aria-label to support adding helper text to the "Help icon with overlay on focus" option. | User Experience |
| INC-A25458 | 844990 | Localization corrections and Update Wizard enhancements | Missing localizations were causing HTTP 400 network errors. In versions of Pega prior to this release, the Upgrade Wizard created the localization rule for associated properties and the JSON was user-generated. With this update, the Upgrade Wizard has been improved to make sure the associated properties (i.e. local list) will have their localization rule created with JSON containing its values and this JSON will be generated by wizard itself. In addition, the "Quick links" and "My Tasks" labels were not localized in the self-service portal. This was due to an error in the locale reference for pyHome1 in pxDependencies, and has been resolved. | User Experience |
| INC-A25899 | 844604 | Clear validation errors before submit | After update, when the validation failed for an IBAN field defined on a view, the error message string was being appended with the message text every time the "next" button was clicked. This has been resolved with an updated to ensure error messages are cleared before submit on Constellation. | User Experience |
| INC-A25954 | 849141 | Corrected Constellation localization for zh_CN | When using the Simplified Chinese locale (zh_CN) in Constellation, the ruleset was localized but the system was still displaying in English. This was traced to an issue where the userLocale and baseLocale evaluated as the same due to a condition failure, and has been corrected. | User Experience |
| INC-A26261 | 846447 | Corrected window focus when using escape key | Focus was lost on any control when the escape key was pressed. This was caused by an error in the handling of keyboard accessibility for the left navigation panel, and has been resolved by updating the listener for the "Esc" key so it is only implemented on the sidebar and not on the entire window. | User Experience |
| INC-A26464 | 850098 | 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-A27074 | 842656 | 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-A27098 | 842791 | 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. | User Experience |
| INC-A27168 | 848162 | 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 | 843689 | 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-A27482 | 842098 | AddContainerItem handling updated | The Constellation UI was not loading. Investigation showed the deferload tab was considering the resourceType as 'CASE' when the correct value should be 'PAGE'. To address this, an update has been made to set resourceType as 'PAGE' when calling addContainerItem from loadPortalView. | User Experience |
| INC-A27720 | 842345 | Corrected accessibility for Create Menu focus | When using keyboard or JAWS, the initial focus was not on the intended element when creating a case using the Create Menu. This was traced to the busy indicator stealing focus, and has been resolved. | User Experience |
| INC-A27891 | 844347 | Updated missed use case for dirty check pop-up | A dirty check pop-up window was shown on the screen even if no changes had been made when there was a date control set with display mode as dropdown list. This was an inadvertent side effect of previous work on the dirty popup, and the missed use case of the dropdown date input has now been added to resolve this issue. | User Experience |
| INC-A28881 INC-A21162 |
844538 840839 |
Updated context handling for drag and drop in repeating dynamic layout | After update, adding a new list Item in a repeating dynamic layout and reordering it with drag and drop only reflected the changes after save. This has been resolved with an update to ensure the proper harness context on drag in the webwb_pzpega_ui_rubaxa_sortable js file. |
User Experience |
| INC-A28933 | 846178 | Focus corrected for Assignment title | After update, when an assignment launched the focus briefly went to the Assignment Title and then immediately moved to the top of the DOM instead of remaining on the title even though pySetFocusOnAssignmentTitle was set to 'true'. This was a missed use case in previous work done to set focus on the header text when harnesses are launched which allowed the focus on the assignment title to be overridden, and has been resolved. | User Experience |
| INC-A30118 | 856488 | 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-B10809 | 864661 | 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-B10846 | 862420 | Updated dirty popup handling | The dirty dialog popup was intermittently appearing with the "you are about to discard your unsaved changes" message even though all changes were saved to the operator ID. This has been resolved by adding an input number for loop in pzruleformtoolbar to prevent the alert while closing the tab. | User Experience |
| INC-B1089 | 853157 | 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 | 863321 | 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-B1362 | 857266 | 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-B1415 | 849383 | Corrected index update on table row deletion | When a table row was deleted in Constellation, the data in the rows below the deleted row was cleared and replaced with default values. This was traced to the ref index of the row being incorrectly updated, and has been corrected. | User Experience |
| INC-B1528 | 849164 | Corrected handling for visibility expression | A client-side visible expression was not working as expected if a when condition or custom condition with multiple fields was used. This was traced to an issue with the isReadable check from the IS_NULL/IS_NOT_NULL condition in getExpressionText function, and has been corrected by updating the expression logic used for comparisons to an empty string. | User Experience |
| INC-B1980 INC-A28455 |
852504 846237 |
Corrected ConfigManager text wrap | After update, table headers were wrapping when the filter icon was visible on the optimized table column header in the ConfigManager even when there was empty space available for the text. This has been resolved by removing the width :100% from pzColumnFilterIcon div. | User Experience |
| INC-B2079 | 851904 | 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-B4596 | 856235 | 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-B4658 | 856927 | Support added for user reference field in embedded data | After configuring a user reference field as one of the fields in an embedded field displayed as a table, the user reference field data did not persist with save and submit. This was traced to the user reference field missing from pxContextMetadata, which was a missed usecase. This has been resolved by updating context metadata generation for embedded user reference properties within a multirecord. | User Experience |
| INC-B6680 | 859907 | 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-B7857 | 860315 | 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 | 862194 | Added accessible name for iframe | Aria label has been added for the live composer iframe name in App Studio for improved accessibility. | User Experience |