Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
Low-code Application Development
Case Management
23.1.3 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A14973 INC-A11043 |
827356 822376 |
FindWorkGadget control deprecated | After upgrade from Pega Platform version 7.2 to Pega Platform version 8.7, searching for a case using FindWorkGadget generated the message "Error 403: SRVE0295E: Error reported: 403". The FindWorkGadget control contains the list view control to view the data, which is a deprecated control. This was a missed use case, and has been resolved by deprecating the FindWorkGadget control. Alternate widgets present in the dashboard such as work list, work queue, and the search gadget may be used to find work in its place. | Case Management |
| INC-A21365 INC-A15775 |
842663 835722 |
Failed status correctly announced in BPNotes | JAWS was not announcing Failed status in the pzBPNotes section. This was traced to a missing focus event for the icon and has been resolved by replacing the Skipped and Failed label with a button to display pyTempText instead of the smart tooltip in the pyBPNotes Section. | Case Management |
| INC-A23925 | 839190 | Improved security for potential cross-site scripting | Cross-site scripting protections have been updated for the case type rule name. | Case Management |
| INC-B11685 | 862940 | 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-B147 | 868231 | Handling added to avoid incorrect cover count value | While working on and resolving child cases, a validation error on screen was intermittently causing the pxCoveredCountOpen value to be decremented by one. Handling has been added to address this issue and maintain the correct count. | Case Management |
| INC-B15400 | 866422 | Work-Cover-SimpleCase updated to use ResolveAndCloseCase | Cases were not being cleaned up as expected when using the Resolve Case action in the Actions menu. Investigation showed the flowaction was calling the UpdateStatus activity, which updates the resolution status but does not clean up the open assignments. This has been resolved by updating the case wide action in "Work-Cover-SimpleCase" case type(pyDefault) from pySetStatusResolved to pyResolveAndCloseCase. | Case Management |
| INC-B17952 | 869513 | Activity and data transform rules updated for Questionnaire property handling | When a field was created for the first time under "Map Answer to Field" -> "Create New" in Questionnaire, entering a value starting with the letter "A" in the modal and submitting it set the value to "zzzz" instead. This was caused by the value not being properly appended to the pagelist, and has been resolved by updating the activity and data transform rules to correct the handling. | Case Management |
| INC-B18712 | 870680 | Aria-labels updated for icons on Case Type Questions View | When creating a case type as a questionnaire, some icons were missing the accessible helper text aria-label in the edit/add questions view of App Studio. This has been resolved by updating the helper text value defined in the pzEmbeddedSurveyQuestion and pzSurveyQuestionTemplate sections. | Case Management |
| INC-B1967 | 855590 | Corrected unexpected Stage rule creation | A Stage rule was incorrectly auto-created in a Production ruleset on save of a privately checked-out Case Type rule. This was traced to a previous change made in the handling for a case type rule with a Stage Rule reference, and has been resolved. | Case Management |
| INC-B19766 | 873685 | Updated ReassignToWorkBasket to correct added history record | When an SLA rule to reassign an assignment after a timer expiration was applied to a case, a History type A record was incorrectly added. This has been corrected. | Case Management |
| INC-B20254 | 871563 | Alternative Stage Name security enhanced | Security has been updated for Alternative Stage Name. | Case Management |
| INC-B21012 | 874365 | Unchecked caching of options checkbox in Map Answer to Field | A new "Map Answer to Field" value was not available in dropdown. This was traced to "enable caching of options" being checked inside Map Answer to Field in the pzSurveyQuestionViewAside section, and has been resolved by unchecking the option. | Case Management |
| INC-B21986 | 874374 | "Map Answer to Field" value retained when switching questions | After a new field was created for a question via the "Map Answer to Field" dropdown while configuring a questionnaire, switching to another question and then switching back cleared the "Map Answer to Field" value. This was traced to a data transform in pzSetQuestionAndFieldNames setting the value to null during the switch, and has been resolved by removing the step. | Case Management |
| INC-B22083 | 873980 | Calendar control registered with BAC | Due to being deprecated, the pxCalendar control was not properly registered with BAC. This has been resolved. | Case Management |
| INC-B24727 | 877881 | Corrected 'previous' button handling for multi-attachment screen | After adding more than one attachment in the multi-attachment screen, clicking on the 'previous' button did not return to the previous screen. This has been resolved with an additional 'workPage' page in the Pages & Classes tab of the pzJumpToStep activity. | Case Management |
| INC-B26685 | 878466 | Deleted attachments cleared on the screen | When using the delete link to remove a document, the UI did not update to reflect the document removal until a browser refresh was performed. This has been resolved by checking the "Reload once per interaction" check box in D_AttachmentFieldInfo. | Case Management |
| INC-B3565 | 858160 | 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-B4850 | 862677 | 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-B8440 | 860654 | Link attachment handling updated for Constellation | The save timestamp was modified by the attachURL activity while adding a link as an attachment, causing an error when the timestamp did not match the eTag. To resolve this, a condition has been added to the skip saveAttachment activity in the AttachURL activity if the case is Constellation. | Case Management |
| INC-B8651 | 863959 | Updated createdBy field handling for bot attachments | When a case was created from an email with an attachment, attempting to check the attachments section showed the file but indicated its status as "Loading..." and the attachment was not accessible. Investigation showed the DX API response for get attachments did not contain createdBy and createdByName for files which were attached by the system/bot. This meant the files were not accessible as the Attachments widget link to download the attachment is based on those two fields. To resolve this, an update has been made to set the createdBy and createdByName fields in the DX API response when the attachments are attached by system/bot. | Case Management |
| INC-B9875 | 863587 | Ensured duplicate key exception for customized GenerateID | After upgrade, a customized version of the GenerateID activity reused an existing ID and overwrote an existing case. This scenario did not generate a duplicate key exception as expected during the case creation process (AddWork), which was a behavior change from Pega 7. This was traced to a difference in handling for newObject value, and has been resolved by updating the RecalculateAndSave activity to set newObject to true if pzInskey is not present on the work object. | Case Management |
Cloud Services
There were no 23.1.3 Resolved Issues for Cloud Services
Conversational Channels
23.1.3 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B11552 |
864329 | Extension added for custom triage class | After update, the SLA was not being applied to a custom class used for email-based triage cases. Investigation showed the OpenAndLockWork step was failing, causing the process to exit the Establishcontext activity and preventing the ProcessEvent activity from running. To handle this use case, the extension pyCheckAndMigrateInteractionCases_Ext has been added to set the objclass of the email triage case; this defaults to "Work-Channel-Triage" and can be modified as needed. | Conversational Channels |
| INC-B16449 | 867464 | Updated HistoryIndex property handling for migrated cases | After update, emails were not being properly attached if the related case was created before the update. This was an issue with the method used to set the pyHistoryIndex property on the workPage, and has been corrected. | Conversational Channels |
| INC-B28596 | 879933 | PostProcessTriageWork updated to pass parameter page | After update, a difference was seen in the behavior of pxCreateAndManageTriageWork due to "pass current parameter page" not being checked. This change in implementation caused some configuration logic to break when parameters created in steps prior to pzPostProcessTriageWork were needed. To resolve this, pzPostProcessTriageWork has been updated to pass the parameter page when calling pyPostProcessTriageWork. | Conversational Channels |
Data Integration
23.1.3 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B13217 |
868314 | REST connector socket timeout made consistent | The socket timeout value given on the REST connector rule form was not consistently applied, causing the observed timeout to exceed the configured timeout in certain situations. This was due to the timeout being calculated as a max time between packets, and has been addressed by setting the timeout to be a fixed value. | Data Integration |
INC-B24386 |
874541 | Updated property name handling for archival SRS migration | A Clipboard WrongModeException occurred during archival SRS migration, indicating the property .JobTitle was of mode Page while ClipboardPropertyImpl.getStringValue() was expecting String mode. Investigation showed the archival reindexer was skipping a loop that performs a check for Page if the property name did not contain multiple parts in the name, i.e. Case.JobTitle. This has been resolved with added checks for the property handling. | Data Integration |
| INC-A1110 | 807374 | Corrected cache handling for link control data | Stale data was seen on the link control if it was referred from an embedded property, leading to information from one case to be carried into another. This has been resolved by updating webwb_pzpega_ui_template_link to get the correct value. | Data Integration |
| INC-A16756 | 871240 | Added handling for pxUpdateRecord failure during save | Intermittent issues were seen with pxUpdateRecord failure when attempting to update the database table record by using a savable data page, causing cases to need reprocessing. The exception "Job Scheduler [ClaimCreation2] activity [CreateCC] execution marked as failed with message [pxResults (class:" was generated. This was traced to an invalid value for a PageList, and has been resolved by adding a retry mechanism along with a check for property mode before generating an InvalidParameterException. | Data Integration |
| INC-A18369 INC-B18082 |
870413 872108 |
Case lock maintained during Connect REST | After upgrade, invoking Connect REST to fetch data from an eternal system as part of case creation resulted in the case lock being released and the database commit failing. This was traced to the getSimulationActivity rule being invoked which reset the access group and rolled back any database transactions associated with the thread. This has been corrected so the correct access context is maintained. | Data Integration |
| INC-A19931 | 862364 | Handling added for tenant URLs registered with Microsoft Azure | The Multi-Tenant Hash IDs generated by the Open ID Connect Setup contained wild cards which were disallowed by Microsoft Azure during the URL registration. This has been addressed with an update to remove the '*' and '!' characters from the redirect URL based on the boolean DSS setting "ignoreAsteriskAndBangSymbolInMT". | Data Integration |
| INC-A23729 | 845171 | Dev Studio security updated | Cross-site scripting protections have been updated for Rules and Ruleforms in Dev Studio. | Data Integration |
| INC-A24646 | 843337 | 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 | 843343 | 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-A25591 | 840670 | Support added for migrating Oracle optimized index with Primary Key | When upgrading from Pega 7 to Pega Infinity '23, the error message "ORA-00955: name is already used by an existing object" was generated. This can occur when Oracle data pump is used to move the schemas in earlier versions of Oracle 18 or 19, and is caused by parallel threads optimizing the primary key (PK) index while another thread is simultaneously adding the PK index, and has been addressed by adding support for this edge case. | Data Integration |
| INC-A26110 | 849724 | 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 | 869992 | 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-A26543 | 873464 | Prepending dot to fetch non-scaler properties in pxConvertResultsToCSV | Calling auto-populated properties or embedded properties without adding "." before them was not fetching their value while preparing the CSV file in pxConvertResultsToCSV activity. While scaler properties can be fetched without the ".", auto-populate properties are not scaler in nature. This has been resolved with an update to append a "." before the properties to fetch their values from clipboard. | Data Integration |
| INC-A27036 | 846451 | 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-A27482 | 842097 | 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. | Data Integration |
| INC-A2788 | 813222 | 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-B1010 | 864072 | Added catch for notification thread exception | A notification configuration was working in the development and production environments, but was not working in the pre-production environment. Investigation showed there was an uncaught thread exception, and handling has been added to resolve this issue. | Data Integration |
| INC-B10307 | 861803 | Corrected OpenWorkbyhandle error in coexistence | When using an OpenWorkbyHandle configuration to launch a landing page using coexistence, a 403 error was generated. This was traced to the OpenWorkbyHandle URL being incorrectly generated with the thread name, and has been corrected. | Data Integration |
| INC-B10336 | 870639 | Additional logger added for archival exclusion | Additional logging has been added to assist with diagnosing issues with ABAC security configuration filter conditions which cause classes to be mapped to a different table while running queries using nativeSQL. | Data Integration |
| INC-B10336 | 877135 | setSecurityEnabled defaults to false when using NativeSQL queries | Adding a security rule to the work class and trying to run an archival exclusion activity on the WO of this work class generated an error indicating pxobjclass did not exist. Investigation showed that when ABAC filters are enabled, the NativeSQL layer was adding additional filter conditions in the 'where' clause of the query which caused the queries to fail. ABAC filters are automatically added to the query by default if EnableAttributeBasedSecurity DSS is enabled and an ABAC condition is defined, and the setSecurityEnabled setting was true by default. In order to correct the added filter issue, the setSecurityEnabled setting has been changed to false to disable ABAC filters in the query. | Data Integration |
| INC-B10764 | 870803 | Corrected attribute handling for custom report definition filter | Opening a report and clicking on "other navigation" caused a pyDirtyCheck popup to appear even when no changes were made. Investigation traced this to the use of a form containing a date field that had text entry disabled that was used in a custom report definition filter rendered in non-template mode. This has been resolved by updating the handling for the "data-initialvalue" attribute so it renders as expected in both template and non-template mode. | Data Integration |
| INC-B11228 | 871069 | Trim and special character handling added to attachment migration | Attempting to migrate an uploaded attachment with a name longer than 255 characters or with characters such as "[", "?", "*", "<", ">", "|", ":"] resulted in an error from the pzAttachmentMigrationProcessor queue processor. This has been resolved with the addition of a java step in pzGetAttachmentContent to remove the special characters as well as trim the attachment name to 90 characters. | Data Integration |
| INC-B1130 | 861792 | 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-B11885 | 862430 | Added handling for system pulse race condition on startup | A newly scaled-up batch node did not pick up new Next Best Action rules. This was traced to a race condition, and has been addressed by reloading the class map into the system pulse module. | Data Integration |
| INC-B1193 | 862270 | 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 | 868449 | 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-B12600 | 865196 | Readonly date control correctly displays custom date | After adding a custom date time control with date property and checking "display value read only formatting" and selecting allow text entry as "no" in configuration panel, the custom format dd/MMM/YYYY was modified to mmm-dd-yyyy after the server side validation was triggered. This modification was occurring due to the date format which was picked up from the browser locale (set to English United States) overriding the custom control. If default locale is not mentioned on the Operator page, the system considers the browser locale. To resolve the custom format being overridden, a check has been added which will format the date accordingly even if the dateTime property is considered to have an error. | Data Integration |
| INC-B1278 | 869008 | File Listener retry logic updated | File Listener was not moving the file to the error folder as expected after failing to read it three times, but instead was continuing to retry. This has been corrected with an update to properly set the processing status error message so the process continues as configured. | Data Integration |
| INC-B14091 | 872862 | Logging added for terminate requestor | Additional logging has been added for the terminate requestor function in order to assist with diagnosing problems where the queue processor becomes stuck with "Ready to process" items. | Data Integration |
| INC-B14600 | 874757 | StakeHolder widget updated to support pagelist properties | The data was not being saved when a pagelist property was used to add multiple addresses to the StakeHolder widget. This has been resolved by adding UI support for pagelist data to the StakeHolder widget. | Data Integration |
| INC-B14835 | 869415 | Error handling updated for connections using setClientID | The error "ConnectorException: Couldn't establish connection: Method setClientID not permitted" was generated when attempting to establish a connection using Connect-JMS. This has been resolved with additional handling for setClientID() runtime exceptions. | Data Integration |
| INC-B15023 | 870822 | Corrected handling for editable list with recursive embedded page list property | When presenting an editable list in Constellation that was created from a case type with an embedded page list property which itself contained another embedded page list property, accessing the form to edit a parent list entry to add, remove, or modify entries within the child list intermittently caused rows from the child list to disappear. This was traced to the interestPage handling for the modal dialog and has been corrected. | Data Integration |
| INC-B15281 INC-B26152 |
865981 876284 |
Added sync check for updated localization pack | Importing an updated localization pack through the App Studio localization tool did not immediately reflect the update as expected. This has been resolved by adding a last modified datetime and operator check in the update locale rule. | Data Integration |
| INC-B1548 | 850874 | JavaBeanViewer updated to remove browser invocation | In order to ensure potentially sensitive information is not accessed without authorization, the 'allow invocation from browser' option for rule "RULE-OBJ-ACTIVITY DATA-ADMIN-IS-JAVABEANVIEWER" has been disabled. | Data Integration |
| INC-B1584 | 864672 | en_PH locale added | The en_PH locale file has been added to support the Philippines. | Data Integration |
| INC-B16148 | 867350 | Corrected handling for SLA on Assign to Robot Queue flow shape | After creating a flow and adding the "Assign to robot queue" shape, the flow could not be saved after adding SLA to the shape. Investigation showed this was caused by an incorrect property referral in the SLA, and has been resolved by updating the property used for configuring the SLA and setting SLA type as 'Use existing'. | Data Integration |
| INC-B16409 | 869694 | Logging added for diagnosing socket timeout issues with S3 | An IOException was frequently generated when loading bulk data all at once, leading to corrupted clipboard data and a parsing exception. To assist in diagnostic work, logging has been added to track SocketTimeOut and Connection Time to Live. | Data Integration |
| INC-B16627 | 868070 | Diagnostic logging added for engagement policy issues | Rule resolution tracer loggers have been added along with a check in the skipHitNotFound item PropositionFilter in order to assist with diagnosing issues with actions missing engagement policies. | Data Integration |
| INC-B17158 | 867154 | Corrected duplicate data page from API | When using the v2 data_view/{data_view} API, the GetDataPage step was making two copies of the page. This has been corrected. | Data Integration |
| INC-B17344 | 875400 | Utility Method available to validate JSON against YAML Schema | The validateJSONAgainstYAML function has been made available in the Utility function of AutomationUtils to validate JSON against YAML schema and return a list of validation messages. | Data Integration |
| INC-B1736 | 866062 | Updated Pega Cloud File Storage (PCFS) handling for duplicate attachments | When migrating attachments to Pega Cloud File Storage (PCFS), attempting to move a file with a duplicate name failed. This has been resolved by updating the pzuploadattachment activity to handle duplicate attachments. | Data Integration |
| INC-B1756 | 872608 | Updated Purge query handling of clipboard | The purge function was not working as expected. This was traced to queries in one of the steps in the purge activity not being handled correctly Oracle version 19 and passing empty strings as rulesetlisthashes, and has been resolved by improving the Select purge query method of storing the result to clipboard. | Data Integration |
| INC-B18729 INC-B17679 |
870908 871571 |
Diagnostic logging added for PegaArchiver | Additional logging has been added to assist with diagnosing issues around excessive run time for the Archive function. | Data Integration |
| INC-B20863 | 871717 | RequestorLockException logging updated | The logging level for RequestorLockException has been changed from infoForced to debug. | Data Integration |
| INC-B2102 | 865629 | 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. | Data Integration |
| INC-B23600 | 876803 | XSD data cleared after error | To improve security, XSD data will be cleared from the Connector and Metadata Wizard if an error is encountered. | Data Integration |
| INC-B25600 | 876931 | Updated response data transform empty date value for GET | If a an empty date/time property was added in in the Insights dimensions, it defaulted to 01 Jan 1970. This was traced to the default automap behavior of the pzTranslateViewPageToJSON data transform, and has been resolved by updating the response data transform for GET request to use "null" as the default. | Data Integration |
| INC-B26697 | 878258 | Control selection correctly saved in screenflow | Radio button selection was not being saved in the screenflow after using the next and previous navigation buttons. This has been resolved with an update to store the correct page reference for the list fields. | Data Integration |
| INC-B4258 | 862216 | Child cases correctly archived when top two parents are of same type | Dynamic Hierarchy support has been added for case archival. This supports the use case of archiving an asymmetric case hierarchy where a parent case type becomes a child case type for one of the child case types in the case hierarchy. This resolves an issue where SuperParent has 4 children and Parent2 has 3 children and SuperParent and Parent2 are of same class, which had resulted in child4, child5, and child6 not being archived as expected. | Data Integration |
| INC-B5709 | 859361 | Corrected flow rule edit 'when' logic | The "configure view" button was unexpectedly being offered in Dev Studio after reopening a submitted screen flow, and clicking on it generated the error "Only one modal dialog can be opened at a time". This was traced to an error in the 'when' rule logic for the property panel of assignment pyOutcomes which caused it to become initialized in the flow rule form when it should only be initialized in Case Designer. This has been corrected. | Data Integration |
| INC-B6802 INC-B19202 |
866914 872006 |
Corrected AccessGroupSwitch handling | Attempting to open a case belonging to another application without manually switching to the application generated a Login screen and the case was not opened. This has been resolved by updating the handling for the application switch cookie paths. | Data Integration |
| INC-B730 | 864636 | 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-B767 | 849389 | Extra validation check for space character added for Service REST | A 502 Bad gateway exception for third-party connectivity was traced to the response header using "request id" instead of "request-id". A validation check has now been added to ensure spaces are not allowed in Service REST response headers during save. | Data Integration |
| INC-B7715 | 859127 | Accessibility corrected for using enter key to edit table | When a keyboard user navigated to a row in a delegated table and hit the enter key to edit the inputs, a new line was created instead. This has been resolved by modifying the section in such a way that pressing the enter key will edit the existing record rather than creating a new row. | Data Integration |
| INC-B791 | 875253 | Added handling for search null pointer error | After creating a case hierarchy with multiple child case types, removing one of those child case types from the ruleset and then attempting to archive the parent cases led to a null pointer error from the search API for the deleted child type. Handling has been added for this use case. | Data Integration |
| INC-B791 | 864557 | Updated Archived-shared records handling | Cases in Archived-Shared status were not being cleared from the pr_metadata table, increasing the table size. Investigation showed that when using the pxLinkAttachmentToCase activity, attachments were only marked as Archived-Shared status when they occurred in the same batch. This led to marking the shared attachments as regular attachments when they were not part of same batch while running the archival jobs, and caused the shared attachment to only be accessed by the case that was archived, leaving the unarchived case not able to access it. This was a missed usecase, and has been resolved. | Data Integration |
| INC-B8067 | 871690 | Corrected handling for generating nested JSON elements | When using a data transform to create a REST connector in clipboard and subsequently transform it into a JSON text for Amend to Map, the JSON data transform did not work in cases where the clipboard structure was more complex (for example a pagelist containing a page list). This has been resolved by updating the logic of the mapping order of elements between clipboard and JSON. | Data Integration |
| INC-B8317 INC-A28696 INC-A11557 |
861974 844493 828721 |
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-B9025 | 870968 | CreateConnection correctly passes JNDI credentials | Connection issues were seen when authentication was enabled on the JMS broker side and JNDI credentials mentioned in the JNDI server rule form were not being passed as expected. This has been corrected by updating the activities called in the JMS explorer functionality. | Data Integration |
| INC-B9435 | 860732 | Added null check for strKey in SafeURL | Opening an existing assignment and then clicking on the cancel button generated a browser alert with the error "NullPointerException in SafeURL.put(key,value) {recordKey}, {undefined}". This was traced to an empty value for strKey, and has been resolved by adding a null check. | Data Integration |
Decision Management
23.1.3 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B14451 |
866215 | Corrected ADM snapshot truncation | The data import case in Data Migration was failing with a "Rule not found" error. An audit trail showed there was a failure in the ADM datamart table truncation prior to ADM data import; this has been resolved with an update to only truncate the ADM snapshot data if ADM import is enabled. | Decision Management |
| HFIX-B799 HFIX-B1043 HFIX-B1313 HFIX-B1332 HFIX-B1703 |
862816 864949 870247 870269 878241 |
Decision simulation batch size made configurable | Data migration was failing at the export phase while processing the pyRemoveDuplicatesFromSimulationDataSet data flow run. This was traced to a Cassandra read and write timeout exception, and has been resolved by adding a batchable feature to the data set with size configured with a prconfig setting. Create the below DSS only on Production: * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/deduplication/batchsize - Setting value: 50 * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/deduplication/requestors - Setting value: 1 Create the below DSS on both Production and BOE: * Owning ruleset: Pega-DecisionSimulation - Setting name: simulation/datamigration/inboundsample/requestors - Setting value: 3 * Owning ruleset: Pega-Engine - Setting name: prconfig/dnode/dds_partitioner_class/default - Setting value: com.pega.dsm.dnode.impl.dataset.cassandra.TokenRangePartitioner * Owning ruleset: Pega-Engine - Setting name: prconfig/dnode/cassandra_use_extended_token_aware_policy/default - Setting value: true |
Decision Management |
| INC-B13083 | 864618 | Improved Interaction History sync performance | Interaction History was very slow when working with extremely large data sets. This has been addressed by refactoring the pxInteractionHistory browse operation for better performance in very big data use cases involving records from a large time range (15 months). This improvement also eliminates the merge shape limit on the number of records and avoids the customer interactions limit. | Decision Management |
| INC-B13604 | 864414 | 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-B14031 | 866753 | Corrected count for HandleResponses | After update, the response count on the event strategy window was not accurate. This was traced to the data in the stores_pxHandleResponses table being unexpectedly removed, which was an unintended consequence of a previous update to the event strategy logic to add the new property pyOutcomeWeight. This has been corrected. | Decision Management |
| INC-B1476 | 857424 | Instruction text rendered in a Questionnaire page | After developing a Questionnaire with some introduction text on each page, the introduction was not shown when running the Questionnaire. This was due to difference in handling for the Question page in Constellation, and has been resolved by adding a new parameter to the pzQuestionPageScr flow and setting it when saving the Questionnaire case type so the introduction text is included. | Decision Management |
| INC-B14837 | 868053 | 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-B15053 | 864772 | 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-B15096 | 872135 | Batch sizing made available for Cassandra queries | When a Decision Data Store (DDS) dataset BrowseAllRecordsOperation was executed there was no method to pass the batch size to use for the Cassandra page size. This caused the default datastax driver page size of 5000 to be used in queries, potentially leading to out of memory conditions for datasets with large records. To address this, the feature class BatchableFeature has been added to the data flow for BrowseAllRecordsOperation to allow limiting the number of records received by each Cassandra query per dataflow run. | Decision Management |
| INC-B15704 INC-B12209 |
865577 865017 |
Truncate operation improvements | In order to support a variety of different database engines and avoid truncation failures of the pyADMFactory data set during the data migration import process, the implementation of the truncate function has been updated to better handle external and internal tables and tables mapped to more than one class. | Decision Management |
| INC-B15792 | 872387 | Updated handling for Customer/DSM aliases | If the strategy changed the alias Customer to a Decision Strategy Manager (DSM) page and tracked the original Customer page for resetting later, during the enrichment of aliases, if Customer was included, it was reassigned to a DSM page and the previous page (now the DSM page set in step 1) is tracked again. As a result, the oldAliases list contained both the original Customer page and the DSM page from the initial change. When resetting the aliases, Customer remained associated with the DSM page from step 1. Consequently, this alias was visible to the parent activity, leading it to incorrectly use the DSM page for Customer instead of the intended original page. To address this, the reset order has been reversed to the alias order to ensure the correct page on the final reset. | Decision Management |
| INC-B16495 | 867489 | ADMPredictorsFilter limit increased | Model predictors were not properly populated in the predictors monitoring screen. This was due to the limitations in the pyADMPredictorsFilter Report definition which was set to retrieve a maximum of 500 records at a time. To resolve this, the limit for maximum records to retrieve in pyADMPredictorsFilter has been increased to 99999999. | Decision Management |
| INC-B17436 INC-B14730 INC-A12911 INC-B3007 INC-B899 |
867396 865858 829353 854257 852879 |
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-B17441 | 868571 | Resolved permission error in pyProcessCaseEvents | The queue processor encountered report definition permission issues related to process AI calling a Strategy, resulting in an exception while invoking the Interaction History summary top-up queries. This was related to the handling of the complex field type used by the context page copy that is sent as an input page to the prediction strategy, and has been resolved with the addition of an extensible 'when' rule to allow skipping the desired properties while executing prediction. | Decision Management |
| INC-B17549 | 875821 | Handling and warnings updated for Next Best Action change requests | After the Next Best Action (NBA) process created the customer journey (with one action and one entry criteria) for each of the stages, some of the stages had stripped off actions/entry criteria after the deployment. This was due to the change request handling. Both standard change requests and ops change requests relied on the backup DDR to revert journey associations changed as part of the change request. A common rule was used for reverting changes made by different types of change requests. As a result, if journey changes were made using both types of change requests within the same revision, reverting any one of them impacted the changes made by the other. To address this, the dependency on the backup DDR for reverting changes made using ops change requests has been removed. Ops change requests now maintain a backup of the original journey associations in the case meta data during case creation and use this backup whenever a revert is performed. This ensures that reverting ops change requests will not affect changes made by standard change requests. In addition, a warning will now be displayed when a user tries to withdraw a change request that is used to perform NBA-related changes, and a warning has been added for situations where a user tries to modify more than one NBA rule as part of the same revision using an OpsMT task or another type of change request | Decision Management |
| INC-B17807 | 870560 | Corrected file data set Preview file filter | In any file type data set, selecting Preview File next to the export showed a different file than the one expected. This was traced to Preview in the file data set picking the first file in data set directory even if it did not match the file pattern, and has been resolved with an update to correctly filter out files not matching the pattern even if they are in the same directory. | Decision Management |
| INC-B18411 | 875084 | Updated date filter handling for proposition eligibility | Inconsistencies were seen in eligibility between customer profile viewer and the Next Best Action (NBA) run and between the strategy trigger and the Globally Optimized Strategy (GOS). Investigation showed this was due to the handling of the date when using a filter component with @pxIsBlank(StatDate) OR @pxIsBlank(EndDate), and has been resolved. | Decision Management |
| INC-B19635 | 876214 | Updated HandleResponses data flow to minimize false alerts | PEGA0161 alerts were being generated indicating "The Adaptive models are not learning as they are not getting responses. The pxHandleResponses dataflow has restarted at 20240425T023357.744 GMT." This was a false alert, as shown by the models page indicating they were being regularly updated and that the pxhandleprocess dataflow was in an in-progress state. To resolve this, an update has been made to pxHandleResponses which will check the restart time and send out alerts only within 3 days from the time the dataflow is restarted. The schedule for the check has also been updated from every 10 minutes to once per day. | Decision Management |
| INC-B20239 | 872837 | MVEL library deprecated and replaced for PropositionFitler explain mode and simulation mode | Simulation runs were not returning counts in CDHSample even though the counts were populated as expected if the proposition filter was run individually. This has been resolved by replacing the MVEL library with a simple expression evaluator for PropositionFitler explain mode and simulation mode. As part of this work, the DecisionDataExpressionEvaluator class has been deprecated and will be removed in a future release. This class uses MVEL library and is only used in PropositionFilterTemplate Rule-Utility-Functions. | Decision Management |
| INC-B20390 | 874085 | Updated handling for recursive Prediction references | Page type predictor values were not being displayed on the prediction widget. This was traced to a configuration where Prediction execution could result in infinite recursion for complex data structures if case reference and data reference properties referred to case and data classes containing case predictions. This has been resolved with an update which sets the useOptimized flag to false so that prediction execution considers Clipboard page and not just DSMClipboard page. | Decision Management |
| INC-B20725 INC-B18063 |
873918 869239 |
Updated parameter handling for dataflow sourced from report definition | After update, a dataflow for processing records with source as report definition and destination as activity was failing with a null pointer exception. This has been resolved with an update ensure parameters are properly handled to support using a report definition in a dataflow, including selecting a nested property mapped to an exposed column, sorting on a property from a joined class, selecting a function alias instead of a property, and sorting on a function alias. | Decision Management |
| INC-B21171 | 871486 | Session and message usage metrics enabled | CDH Session and message usage metrics were not enabled in any environment. This was traced to the channel name or application name being created with the character '-'. While doing context switch, the App name was captured and a Page Group created with Subscript as the name of Application. This caused the app name to be "-", which caused the issue to the form page group. To resolve this, an update has been made to strip special characters from the string. | Decision Management |
| INC-B21582 INC-B17974 |
872102 871408 |
Corrected button access for decision revision management | Attempting to remove treatment attributes from Action Decision Data was not working due to an incorrect state for Add field and other buttons in the form tab of the decision data rule. This has been corrected. | Decision Management |
| INC-B2228 | 867392 | Decision Funnel query activities log proper stack trace | In order to improve debugging, Decision Funnel query activities have been updated to allow logging a stack trace. | Decision Management |
| INC-B24605 | 876279 | Migration pipeline performance improvement | Data migration pipeline comparison runs were taking an excessive amount of time. This has been resolved by updating the DDS Data Set SDK to improve the resuming behavior for compound token ranges. | Decision Management |
| INC-B24750 | 875848 | Support added for rolling back data changes after campaign failures | A campaign run that failed in middle of execution may leave datasets in an unwanted condition. In order to facilitate restoration, this update introduces an AggregateKey setting which will roll back the changes when AggregateCount is set to a negative value. This manual process will use the generated file (created using a data file set) to stage pertinent information for records to be rolled back into a database table, decrement the counts in IH summaries, remove triggered contact policies and reset them for subsequent runs, and decrement the count in VBD reporting datasets. | Decision Management |
| INC-B25391 | 876572 | Corrected truncate handling for file data set with manifest | If the Truncate operation was used on a file data set with a manifest file, then the manifest file was deleted instead of the data files. This was an error in the implementation following other work, and has been corrected. | Decision Management |
| INC-B26433 | 877087 | Added handling for Oracle database lookup for GOS performance profiler report | The Globally Optimized Strategy (GOS) performance profiler report was blank. This was traced to the database handle coming back empty due to the Oracle database lookup being case sensitive. This has been resolved by adding an alias for the selected column so that the case of the key and returned column name match. | Decision Management |
| INC-B27326 | 878683 | VBD supports configurable threshold for Dictionary size | Decision Funnel metrics were cut off due to VBD Dictionary size limit of 10,000 records. To address this, the DSS Pega-DecisionEngine.vbd/dictionarySizeThreshold has been added which makes this limit configurable within a range of 10000 / 100000. | Decision Management |
| INC-B2737 | 852667 | Updated handling for "Not a Number" in predictive models | A model created using a Predictive Model Markup Language (PMML) LightGBM algorithm file was missing output results. This was traced to the model outcomes returning NaN (Not a Number), and has been resolved by updating the handling for missing, undefined or unrepresentable value data in the target field for the Tree Model. | Decision Management |
| INC-B5879 | 861177 | 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-B7423 | 863673 | Updated handling for reading files from S3 repository | When attempting to read files from a custom S3 repository, the directory was visible but it was not possible to list subdirectories or read the files. This was traced to an issue with access to view files that were created or uploaded by other operators, and has been resolved with an update to the file data set to work with non-explicitly created directories. | Decision Management |
| INC-B7952 INC-B9183 INC-B9606 |
858481 863014 868671 |
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 | 865040 | 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 | 868483 | Security updated for edited Pulse messages | Cross-site scripting protections have been updated for editing Pulse messages. | Decision Management |
Low-Code Application Development
23.1.3 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-270434 | 821789 | 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-A21070 | 835263 | Localized Constellation application label character count limit removed | An issue was seen when trying to create a Constellation application with the locale set to "de_DE" (Germany). This was caused by the field value text CosmosReactApplicationTemplateLabel being limited to 200 characters; because the German translation exceeded that count, the creation failed. This has been resolved by removing the character length validation for the localized value from the activity pzValidateApplicationTemplateSettings. | Low-Code App Development |
| INC-A24726 | 843940 | Application Wizard security updated | Cross-site scripting protections have been updated for the Application Wizard. | Low-Code App Development |
| INC-A25634 | 868714 | RecordAPI logging added | Additional diagnostic logging has been added to track context and decisions made for the RecordAPI. | Low-Code App Development |
| INC-A28855 | 874606 | Corrected repeat of ConversationFlow called by Create Case Shape | When a conversation flow invoked using CreateCase shape from a conversation flow was advanced to the end, it started from the beginning of the invoked flow again. If the same flow was started and advanced without using CreateCase, the start over did not occur. This has been resolved by revising the conversational "create case" shape logic to use the create top case functionality instead of a custom function. | Low-Code App Development |
| INC-B11364 | 868335 | Function pxIsInListOfValues updated for improved backwards compatibility | After update, a function which previously evaluated to true when certain values were empty changed behavior to evaluate to false under the same condition. This discrepancy stems from a change from the previous regex method for splitting the listOfValues to using Apache Commons CSVParser logic. In this particular scenario, this update changed the behavior of the function @pxIsInListOfValues() thereby causing the when rule to return false and thus all the offers were filtered out by one of the proposition filters that used this when rule. In order to support backwards compatibility, an update has been made which will return true when listOfValues is empty and value is blank. | Low-Code App Development |
| INC-B12444 HFIX-B991 |
864836 864493 |
Corrected chat transcript migration for authenticated events | After update, chat transcripts for older cases were not visible. This has been resolved by updating the migration mechanism used by pyHistory for outbound authenticated events. | Low-Code App Development |
| INC-B12671 | 862301 | 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-B15287 | 868501 | Corrected two pyEmails created on OEML cases | After creating a case and sending an email to a customer, the customer reply on the same thread created another pyEmail on OEML correspondence case. This was a missed usecase for "New outbound email" and has been resolved with an update to pzCreateInteractionReply. | Low-Code App Development |
| INC-B16631 | 869697 | Corrected truncated error message text display on hover | When using the Expression Builder and there is an error on the test, the error message was truncated and the full text was not visible on hover as expected. This was traced to an error in the pzEllipsis control, and has been resolved. | Low-Code App Development |
| INC-B16799 | 877468 | Engagement policies populate correct data in edit mode | Changes to action engagement policies/when rules in engagement policies were not propagated as expected. This was traced to incorrect rule resolution logic in pzLoadUserFriendlyWhenConditionRows, and has been corrected. | Low-Code App Development |
| INC-B20251 | 871558 | Case data object security updated | Cross-site scripting protections have been added to the case data object creation activity. | Low-Code App Development |
| INC-B20714 | 872617 | docx4j library updated | Values were not populating in a Microsoft Word template using Pega property references, and opening a document created from a Word Template with Pega property references generated a popup with the message "Word found unreadable content in <File Name>. Do you want to recover the contents of this document? If you trust the source of this document, click yes". This has been resolved by updating the docx4j library. | Low-Code App Development |
| INC-B21921 | 872016 | Added handling to avoid duplicate queue creation | When incoming messages were sent rapidly, multiple chats with agent case types were called during the queuing process. This resulted in duplicate conversations being created in the Customer Service layer with a single customer session having multiple conversation IDs created and routed to multiple agents. Some agents received an "Assignment not found" error. To resolve this, an update has been made to suppress the duplicate escalations. The customer will see a system message such as "Your request is already under process" which can be customized in the 'cyDuplicateEscalationMessage' question rule. In addition to this, the 'cyDeleteDuplicateQueuedChat' queue processor has been added to delete the queued duplicate conversation if one is created while one is already in process. | Low-Code App Development |
| INC-B22756 INC-B24711 INC-B3573 |
873822 875470 878950 |
#resolvedissues note: Corrected null pointer error 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 copying the paramPage to another page using copyValues(false) when the param page is instance of ComplexParameterPage, and doing action on this new page and on original page when page is not complex. | Low-Code App Development |
| INC-B23721 | 878559 | Updated image tag handling for downloaded case emails | Email attached to a case using a send email automation step was in HTML format when downloaded and inline images were missing. This has been addressed by adding logic to replace and convert the image tag src attribute value from a relative path to base64. | Low-Code App Development |
| INC-B25455 | 875214 | Logger Category Name correctly marked as mandatory | On creation of a new logger category, the Logger Category Name field was not marked as mandatory. This has been corrected. | Low-Code App Development |
| INC-B26810 | 877753 | Added exception handling for missing LinkAttachmentToCase parameter | Inbound email with an attachment was encountering a null pointer exception due to a missing required parameter, WorkInsKey, which is used by the activity pxLinkAttachmentToCase. This exception has been handled with an added condition to check if the service case is present, and will exit the activity if the parameter has no value. | Low-Code App Development |
| INC-B335 | 861885 | Corrected branch development handling for Production rulesets | After adding a production ruleset to the application definition and access group, a test branch was created and then all rulesets were locked. It is expected that the branch will only be for the top ruleset of the current application, but in this scenario branches were created even for the Production rulesets. When branch development was enabled through the Branch Development Toggle icon on the top right corner of the screen, the Production ruleset was being populated as default. Attempting to change that to some other value reverted back to the Production ruleset value. This is incorrect behavior as Production rulesets should not appear in the list. These issues have been corrected. | Low-Code App Development |
| INC-B340 | 849395 | Added handling for special BranchID value | Unexpected errors were seen on the datapage during validation. Investigation showed the datapage contained an input parameter for “SkipNoBranchOption”; if that is false, the datapage will add an extra result with pyBranchID “---” for the ‘No branch’ option, but these characters were not supported in the edit validate rule on pyBranchID. This has been resolved by adding handling for the value = "---". | Low-Code App Development |
| INC-B8351 | 862181 | 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 |
Mobile
23.1.3 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A21383 | 863721 | 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 | 846330 | 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-B11890 | 869989 | Radio button focus behavior customizable for mobile | The default behavior for radio button focus on mobile devices is to move focus away from where the action was triggered following a refresh event. To enable customizing this behavior, a global flag has been added. Set "pega.ui.bEnableMobileFocus" to true in userworkform to maintain focus on the button after a refresh action on mobile. | Mobile |
| INC-B12458 | 862127 | createPDF action updated for QR codes in offline mobile | Preview was not working for offline mobile when a QR code was included in the PDF. This has been resolved by adding base64 image field support for the PDF generator in Client for Windows. | Mobile |
| INC-B12602 | 879245 | Added handling for iOS scroll issue | When using multiselect or autocomplete on iOS, multiple scroll/swipe motions were needed to be able to scroll up or down in the list. This issue was seen on iPhone when the minimum search character setting was 2, and has been resolved with a check for iPhone so that when the result div is not present, scroll to top executes after the keyboard is open. | Mobile |
| INC-B14995 INC-B13626 |
870601 866599 |
Corrected multiselect and autocomplete handling for touch screens | The multiselect and auto complete controls were not loading the data when a touchscreen was used and the source for the control was a data page. The data loaded as expected when using a mouse. This has been resolved by adding the needed target element in the success function in Control_multiselect.js. | Mobile |
| INC-B19548 INC-B19829 |
869098 869916 |
ZIP files correctly packaged for offline mobile | ZIP files were not correctly packaged as BINARY when using offline mobile. This has been resolved by adding zip and bin extensions to the binary files list. | Mobile |
| INC-B20939 | 871355 | Client for Windows supports custom datapage for PDF generation/download | In order to improve case handling, an API has been added to the PDF generator in Client for Windows which allows generating PDFs from a custom datapage. This supports the use case of a single button to download all attached PDFs within a given Case type as a packaged zip file. For more information about this API, refer to the "What's new in Pega Client for Windows" documentation. | Mobile |
| INC-B7021 | 871233 | Alert announced by Android/iPhone | VoiceOver in iPhone/Android was not announcing 'Alert' for the error icon on a page level error message. This worked as expected for desktop. Investigation showed the page level validation message on the alert icon was being picked as "center panel region landmark" instead of "alert", and this has been resolved by adding the Alert word in py-cosmos-helper-classes.css so it is read as expected. | Mobile |
| INC-B9657 | 863579 | 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
23.1.3 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A30085 | 854710 | Get next work supports fetching cases from multiple application | The documentation regarding the logic for selecting the next work assignment has been updated to clarify that the Get Next Work functionality retrieves assignments from all the applications to which the user has access. | Project Delivery |
| INC-B19849 | 877363 | Documentation updated for testing repository connectivity | The documentation for creating an S3 bucket repository and configuring an authentication profile has been updated to clarify that if the authentication profile is changed, the repository must be saved again to avoid the system testing the cached version and producing erroneous results. | Project Delivery |
| INC-B9024 | 862963 | Constellation documentation updated regarding editing user profiles | An update has been added to the documentation to clarify that the Constellation UI does not support the ability to edit the user profile through the Constellation DX API. As a work around, it is possible to open the user profile harness from a traditional application with Theme Cosmos and provide a link to the page in the Constellation application. | Project Delivery |
Reporting
23.1.3 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A24184 | 860832 | 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-B10322 | 867030 | Handling added for embedded properties in a sub-report | After update, reports containing a specific sub-report could not be saved and an error was generated related to two columns present in the sub-report. Investigation showed the Propinfo had a null value, and this has been resolved by adding logic to handle embedded properties and validate them. | Reporting |
| INC-B12870 | 868134 | When condition updated for Live UI button | After update, the Live UI button was being populated in reports for end users. This has been resolved by updating the when condition of pyEnableUIInspector in code-Pega-list. | Reporting |
| INC-B13389 | 864587 | Report name with special characters displays correctly | After update, a report name containing special characters showed the ASCII values in the tab names. This has been resolved by updating the RDWinTitle control. | Reporting |
| INC-B13561 INC-B24931 |
868296 877719 |
DSS added to control descendant class lookups | In some use scenarios, system performance can be severely impacted by thread blockage around ClassMapImpl when there are saves of the Rule-Obj-Class records and Rule-ClassMetadata records linked to the data tables. To address this, the DSS useClassMapForDescendantClasses has been added to allow modifying the behavior of descendant class lookups and use the Classmap in memory instead of the Database. The default for this DSS is false, which directs lookups to use the database. | Reporting |
| INC-B16714 | 875594 | Hyperlinks open as expected in scheduled report | After enabling "Embed link to output in notification" in a scheduled report, the "please click here to see the output" hyperlink in the generated email did not work. This has been resolved by adding the storageType in the pyActionAttachFileToWO. | Reporting |
| INC-B17668 | 867690 | Support added for disabling SRS Incremental Indexing before migration | In order to improve the process of migrating to externalized search, an update has been made which will disable the Search and Reporting Service (SRS) incremental indexer when SearchCapability.SRS_ALLOW_INCREMENTAL_INDEXER is not activated. This capability should be deactivated only in the following scenarios: 1) environments with SRS and the migration in the state 'Ready'; and 2) environments without SRS. | Reporting |
| INC-B18313 | 872432 | Restored date format for report prompt filter | After upgrade, the date format in the report prompt filter was displayed as a timestamp value such as '20240609T045800.000 GMT' instead of the previous format of 'June 9, 2024'. This was traced to an incorrect behavior in pzResolveCopyFilters for DateTime and has been corrected. | Reporting |
| INC-B22380 | 874334 | Corrected error on reordering of report columns | After update, reordering the columns in the report browser generated a "contact your system administrator" popup error. This was due to previous work done which enabled invocation from browser for report filter actions, and had been corrected. | Reporting |
| INC-B22862 | 874550 | Improved performance for BIX extraction to CSV | BIX extractions to CSV run via job scheduler were taking significantly longer to execute after upgrade. Investigation traced this to a check on the value of the DSS setting enableDefaultDelimiterForMSExcelInCSV which was being run multiple times in a while loop during the execution of the internal.access.ExtractImpl.addCSVData method. To resolve this, the addCSVData method has been adjusted so the DSS check happens once before it goes into the loop and it is not done at all within the loop. | Reporting |
| INC-B23827 | 877819 | Corrected exception for Report Browser column drag/drop/delete | While editing a report in the Report Browser, drag and dropping a column or deleting a column generated an exception. This was traced to a code error in the pzPostReportConfigSection activity which added an additional condition to the 'when', and has been corrected. | Reporting |
| INC-B4697 | 861762 | 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-B6183 | 856596 | Reports clickable on list view | After update, the clickable rows used to access the respective reports were no longer functioning as expected when accessing the reports section and choosing to display all reports in a list view. Investigation showed the pyReportBrowserAllReports section was missing an action set when the Optimize code checkbox was checked, and this has been added for onclick rows. | Reporting |
| INC-B7958 | 865462 | Corrected distortion while scrolling fixed header alignments | When the "Do not scroll header" checkbox was enabled, the report column headers were becoming jumbled at run time. This has been resolved by updating pzPega_ui_grid.js and adding the necessary CSS for a fixed header to pyReportEditorStyling. | Reporting |
| INC-B9677 | 867355 | Bix CSV extract files for child cases include headers | When the "-c" option for BIX was used in Pega Cloud to include child case data in the CSV extracts, the child extracts were produced in files separate from the parent cases and contained only the data lines while the parent extract also included the column headers. This has been resolved by adding the necessary support for the headers to be included in the child data file. |
Reporting |
| INC-B9729 | 869270 | Updated empty value handling for validation of custom filters in reports | In some specific scenarios when the validation failed for a report with filters in a custom section using multiselect controls, the system displayed a Pega internal error screen instead of displaying the expected error message and a java error was logged. Investigation showed the Filter Operation in pyContent of the pzValidateCustomFilterSection had the value IS NULL at the initial point of the report definition, and this was carried over into the later process. This has been resolved with an update to pass the value as = instead of IS NULL to match the filters in the pyBody of the RD. | Reporting |
Security
23.1.3 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B7968 |
861647 | 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-A24541 | 866153 | 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-A28575 | 875282 | Added basic authentication handling for modified API servlet mapping | Changing the default servlet mapping to disable PRBasic authentication or move default /prweb to map to PRAuth authentication caused the API calls that used defined authentication in the service package to stop working. This has been resolved by adding logic to support basic authentication type when basic authentication is selected for services where the * url pattern is mapped to PRAuth. | Security |
| INC-A29484 | 855139 | Cross-site scripting protections updated | Cross-site scripting filters have been added for dynamic layout sections. | Security |
| INC-A3941 | 836302 | 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-B12748 | 865818 | ABAC policy conditions updated to include descendant classes | When running a report definition on a case class which has class specialization on it, the report returns rows (cases) from all of the specialized classes as expected when the “Report on descendant class instances” option is checked. If an ABAC policy is implemented for this case type to enable row level security and the policy condition uses a property on the case itself, the report eliminates the rows that do not meet the condition as expected. However, if the policy condition used an association rule to join with a data class (or another case class) to perform the check, the report failed to fetch any of the case instances from specialized classes even when the policy condition was satisfied. This was caused by the ABAC policy conditions that use associations not including descendant classes, and has been resolved by updating the file PolicyConditionActionAssembler class with the new entries. | Security |
| INC-B13609 | 870915 | Improved accessibility for focused empty labels | The screen reader was announcing ‘space, space, space’ when there was a visible focus on an empty space. This has been resolved by updating the pzMFAForm harness to replace the container with screen layout and embed the section. | Security |
| INC-B15155 | 868913 | Diagnostic logging added for logout issue | Additional logging has been added to assist with diagnosing issues related to pxStopPending causing unexpected logout. | Security |
| INC-B17248 | 867779 | Trim added to authentication key construction scope | Trying to make API calls using an OIDC token from an active SSO session generated the exception "Unable to obtain access token for client details in authentication profile configured for connector." Investigation showed there was a scope issue while constructing the key, and this has been resolved by implementing trim during this process. | Security |
| INC-B17764 | 868629 | Corrected handling for Constellation authorization header | When attempting to invoke an embedded logout method that did not have secureCookie='true', the Service Broker revoke transaction had an incorrect authorization header for the transaction. This has been resolved with an update to avoid using default headers for revoke tokens. | Security |
| INC-B19337 | 877617 | Field values security updated | Cross site scripting filters have been added on Field Value strings. | Security |
| INC-B20617 | 876581 | OpenRule control replaced with OpenRuleAdvanced for BAC handling | After upgrade, the 'skills' & 'availability' item sections pyChangeOperatorSkills and pyOperatorAvailability in the navigation menu pyProfileHeaderMenu were generating a 403 error for end users but not for admin users. This was traced to BAC registration issues with the OpenRule control, and has been resolved by replacing OpenRule with OpenRuleAdvanced which contains pzEncryptURLActionString. | Security |
| INC-B20904 | 872588 | Corrected page render for pxDefaultSecured CSP rule | Executing the rule 'pyStatusResponse' standalone by using the pxDefaultSecured CSP rule in the Reject and Report mode did not load the page as expected. This has been resolved by adding the domain "https://fonts.googleapis.com/" in the style-src directive of the 'pxDefaultSecured' CSP rule. | Security |
| INC-B22806 | 877845 | Improved database table connection testing security | Cross-site scripting protections have been updated related to testing the connection to a database table. | Security |
| INC-B23015 | 874339 | Updated OperatorID security | Security has been updated for the OperatorID clipboard page. | Security |
| INC-B23403 | 875644 | Sanitizing filters added for query parameters | Cross site scripting filters have been added to the URL query parameter input. | Security |
| INC-B2902 | 863155 | Websocket connection handling updated | Security handling has been updated for websocket connections. | Security |
| INC-B7191 | 859927 | Corrected filtering for certificate expiry notifications | The pxfetchRequiredCertificationForNotification report definition was fetching all the available certificates in the platform irrespective of the "No.of.Days" filter condition in the configuration. This has been resolved by adding the parameters daysToExpire and notificationInterval to the filter criteria so only those certificates that are expiring based on the "Send expiration notifications before (days)" value will be retrieved. | Security |
| INC-B8872 | 865595 | 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 |
| INC-B9267 | 874631 | Email work link correctly routes to the case after MFA | Clicking on a work link in an email moved to the MFA screen as expected, but once the MFA authentication was done the user was routed to the dashboard instead of to the case screen. This was traced to the URLRedirection for correspondence email not having the required parameter to open the case when Login Service Selector screen was called, and has been corrected. | Security |
System Administration
23.1.3 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B12578 |
865611 | Additional passivation logging available | In order to assist with diagnosing an intermittent issue with data loss when submitting from one screen to another, additional logging has been made available for the passivation APIs. | System Administration |
| INC-B11448 | 866873 | Made message processing flow more robust against heavy loads | During periods of heavy system load, the data flow thread might receive the Kafka confirmation slightly later than usual and overlap with the queue processor thread reading the message and starting to process it. If this occurred during the queue processor's thread experiencing an issue and re-queuing the message for another attempt, the data flow thread removed the message from the database while it was still being processed by the queue processor thread. This race condition has been addressed by modifying the database query for removing the message. | System Administration |
| INC-B12042 | 866876 | DSS added to change casing for queue processor's Kafka topics | Some sites have a limitation of creating Kafka topics only in lower case in the external enterprise Kafka cluster for the stream service. To better support moving to Kafka externalization, a DSS has been added to change how the queue processor's Kafka topics are named (lower vs upper case). Set the value to the desired strategy; allowed values are: UPPERCASE - for pzStandardProcessor queue processor the stream name will be PZSTANDARDPROCESSOR and Kafka topic name will be: pega-PZSTANDARDPROCESSOR - this strategy is used as the default; LOWERCASE - for pzStandardProcessor queue processor the stream name will be pzstandardprocessor and Kafka topic name will be: pega-pzstandardprocessor; To apply the configuration naming convention all nodes need to be restarted simultaneously (not a rolling restart), then stale Kafka topics must be manually removed as these are not removed automatically. |
System Administration |
| INC-B13493 | 868012 | ZoneDateTime used for dayoffset in Daylight Savings Time scheduler calculations | The Calendar Class was not correctly handling Daylight Savings Time when calculating the next run time if the job was scheduled at the exact time change, for example summer 02:00am in Europe/Warsaw. To resolve this, the Calendar Class has been replaced with the ZoneDateTime class to add dayoffset, which provides correct calculations for DST for a specified time zone. | System Administration |
| INC-B17068 | 873495 | Markdown library update | The markdown library has been updated to the latest version. | System Administration |
| INC-B17182 | 872742 | Added explicit websocket close for Robot activities | Robot activities were not being invoked by data pages after a prolonged (several hours) period of working stability. This was traced to the websocket sessions not getting closed properly, causing the connection limit to be reached. This has been resolved with an update to explicitly close the session after the message is received from the message service. | System Administration |
| INC-B17485 | 871619 | Disabled queue processors filtered from alerts | PEGA0137 Alerts were being reported for disabled queue processors. To resolve this, filtering has been added which will be applied before the alerts are sent. | System Administration |
| INC-B18402 | 871092 | Updated logger handling for PRPulseDispatcher class | The campaign process program run status was not progressing to the completed state, and error were generated indicating "Invalid value for aClassName passed to .createPage:Failed to get column mapping for property Data-BatchOutPR132.pySubjectType". This has been resolved by modifying the logger for the PRPulseDispatcher class to continuing pulse processing even after pre-processing failure. | System Administration |
| INC-B18834 | 872631 | JobSchedulerLifecycle logging warnForced | The warning message "Detected duplicate job scheduler execution. Skipping execution." was being generated unnecessarily for sites running job schedulers on multiple nodes. To address this, the warnForced log line in PersistentJobExecutionFactory has been updated to a debug message. | System Administration |
| INC-B2470 | 861916 | External Hazelcast v5 startup updated for use with Oracle use | When the Weblogic server was started using Hazelcast v5 with Oracle, multiple errors were generated including a null pointer error. This was seen with Oracle deployments but was not encountered with tomcat,postgres deployments, and has been resolved by refactoring the Hazelcast v5 initialization flow to mitigate startup failure for the prcluster_service. | System Administration |
| INC-B5470 INC-B12898 |
867557 876681 |
Optimized APIs added to improve lag calculation for external Kafka | When an enterprise-level Kafka cluster is hosted in multiple regions with multiple Kafka racks and many Kafka brokers, Pega's partitions can be stored anywhere in the cluster. This can drastically impact the network latency for the Kafka API calls that perform the lag calculation process to render the "Ready to process" values in the Queue Processors landing page, as the underlying mechanisms used for lag calculation need to complete the entire process within 30 seconds to avoid a timeout exception with the error message "Unable to calculate lag for <QP-stream-name>". To address this need, new stream SPIs/APIs have been added which provide significant optimization in obtaining offsets in a faster fashion with reduced total number of Kafka API calls. | System Administration |
| INC-B5791 | 861688 | 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-B7039 | 865513 | Additional logging information added for purge agent | In order to assist with diagnosing issues with the purge agent not cleaning up instances as expected, more detailed log statements have been added to the RAPurge function. | System Administration |
User Experience
23.1.3 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-227483 | 775404 | Corrected user portal harness issue for Cosmos | The user portal was not correctly rendering in Theme Cosmos when set as a single page. This has been resolved by updating the handling for the Show-Harness and Show-Property activities. | User Experience |
| INC-A14835 | 830561 | Updated scroll handling for flow in modal window | When a flow was used in a modal action event, refreshing the modal window or moving the flow to the next task resulted in the modal window itself moving when a scroll was performed in the main page. This has been resolved by updating the modal container handling of the overflow scroll for this usecase. | User Experience |
| INC-A15251 | 835004 | Interaction remains open after submitting task | After opening the email reply dialog of an incoming email interaction and then minimizing the dialog again, adding a task from the task menu and submitting it would close the task but also unexpectedly closed the email interaction. This only happened if a single task was added; adding multiple tasks or showing the confirm harness after submission did not close the entire interaction on submission. This has been resolved by updating the code in the AutoClose section. | User Experience |
| INC-A18620 | 833832 | Resolved table layout validation | The UI was becoming distorted when validation was triggered for a property added to a column inside an optimized table layout, and it was no longer possible to add anything in the table due to the the text-input field disappearing. An error icon was seen. This has been resolved by updating the pzbase-grids CSS. | User Experience |
| INC-A20262 | 867368 | Added handling for special characters in KM article titles | Attempting to open a Knowledge Management article in the Customer Service application failed to load the content in the popup window if there was an apostrophe in the article title. This has been resolved by escaping the special characters in the window name parameter of the Show Harness action when the target is a popup. | User Experience |
| INC-A23427 | 849454 | Default application image correctly available in Mobile | When using Switch Application on desktop, the default application can be identified from the image available on the left side of the application. Using the same configuration for Mobile in Navigation – MobileIconBar the image on the left did not appear. This was traced to the pyChecked and pyRadio attributes not being correctly populated as string literals in the mobile configuration, and has been corrected. | User Experience |
| INC-A23866 | 838646 | Updated Rich Text Editor resize and accessible label | 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. In addition, a label has been added to the Rich Text Editor keyboard icon with an associated tooltip to improve accessibility. | User Experience |
| INC-A24366 | 842945 | Background color maintained when spellchecker is called on-change | If a section had one or more text areas and a Rich Text Editor configured with a spell checker action on change, an incorrect spelling caused all text areas on that screen to become yellow. Investigation showed the repaintTextArea function was incorrectly being called by spellcheckerscript.js for all text areas in the document, and this has been corrected. | User Experience |
| INC-A27098 | 842790 | 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-A27311 | 843688 | 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-A30206 | 846623 | Non-actionable Google access errors suppressed in TrackingMap logs | After update, an excessive number of exceptions were being logged when using the pyTrackingMap UI Control. These were related to "isGoogleSupported" and did not impact the control's function. To resolve this, the logging has been addressed with an update to suppress the errors. | User Experience |
| INC-B10225 | 873841 | Required field indicator handling updated for accessibility | The required field indicator '*' was not appearing when tooltip and required were configured on the control. Investigation showed both client side and server side validations were executing after the tab key placed the focus on the next field, causing JAWS and other accessibility tools to either read a control that became disabled/read-only or a field which had become editable was missed altogether. This has been corrected. | User Experience |
| INC-B10230 | 863325 | Security improved for autocomplete | Cross-site scripting protections have been updated for autocomplete. | User Experience |
| INC-B10809 | 864663 | 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-B10814 | 864863 | Header values provided to resolve upload errors | When trying to upload the localization Excel sheet, a 403 error was generated and errors indicating the request had an empty CSRF token and a null BrowserFingerprint were logged. Investigation showed the upload API call was missing the required header values in the post request for X-Requested-With, pzCTkn, and pzBFP. This has been corrected. | User Experience |
| INC-B11290 | 862165 | Updated preserveClientChanges handling for Form Refresh | After performing a Form Refresh and removing values from the fields, those cleared fields popped up again during attempts to enter a value in a different field. This was traced to the redux state still holding the previously entered value due to the handling for preserveClientChanges when combined with dataChanges containing a user-selected start date time, and has been corrected. | User Experience |
| INC-B11529 | 863371 | 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-B11674 | 878303 | Corrected portal rendering when switching applications from new work object tab | When working with two applications, opening a work object in a new tab and then switching applications resulted in the second portal loading only left navigation while the main content remained blank. This has been resolved. | User Experience |
| INC-B12101 | 862715 | Added setting for allowcustomtags in Rich Text Editor | After update, custom style tags were being removed when using the Rich Text Editor. This was an unintended side effect of work done to enhance cross-site scripting protections for the Rich Text Editor control, and has been corrected. | User Experience |
| INC-B12263 INC-B21999 INC-B10802 |
873872 874801 862684 |
Corrected nested layout group tab headers | When multiple layout tabs were present, including nested layout tabs, and there were more than 10 tabs open, selecting the last indexed tab from the dropdown caused the tab headers to scroll back to the extreme left and hide the selected tab. This was traced to an incorrect calculation for the right side navigation control in the "_slideEnoughToBringSelectedHeaderIntoFullView" function in layoutgroup.js, and has been corrected. | User Experience |
| INC-B12407 INC-B12602 |
870538 865473 |
Corrected multiselect display for iOS | The multiselect list was not working as expected on iOS. Investigation showed the calculation for height and top position in mobile were not correct when mobile height is small and the results were shown in a specific fullScreen scroll container. This has been resolved with an update to fix the gap and input visibility issues of multiselect and autocomplete in this scenario. | User Experience |
| INC-B12432 | 868841 | Modal context preserved for Constellation Page-Set-Messages | When running the Search and Select pattern within a modal which included a custom Data Transform to set page messages through page-set-messages activity, these messages were displayed in the review harness but not in the modal itself. This was traced to previous work to not add messages to the work area context and rather do it on the primary context, and has been resolved with an update to ensure context will not be trimmed if it has a modal for an error message. | User Experience |
| INC-B12739 | 865764 | Mandatory field warnings cleared correctly when using RefreshData | When using Constellation, a validation error for a required field was not cleared when a value was set using pyRefreshData. This prevented the screen from being submitted, and the error "Cannot be blank" was displayed for all of the error messages. This has been corrected so the field will be validated as expected irrespective of previous validation state. | User Experience |
| INC-B12766 | 864580 | Corrected button accessibility for close/cancel in case creation | After the case create harness was displayed in a pop-up, the pop-up dialog minimized and the close and collapse buttons were being read as blank by the screen reader (NVDA). Investigation showed the aria-labels inside the header tag were not read properly by screen readers, and this has been resolved by removing the "aria-hidden=true" in the header section. | User Experience |
| INC-B12824 | 863464 | Security update for Smart Tip | Cross-site scripting protections have been added to the 'Show Smart Tip' feature. | User Experience |
| INC-B12956 | 863836 | Updated focus order for modal dialog buttons | The focus order of cancel and submit buttons in the modal dialog was not consistent between @baseclass and Work class. The default order has now been set set to first move focus to the cancel button and then to the submit button. This is handled in a new py section "pyModalButtons" which is used inside pzModalTemplate, and the button focus order can be customized by changing the button order in pyModalButtons. | User Experience |
| INC-B12999 | 862955 | Optimized table has correct row values | An optimized table was showing showing Pega property names as row values after update. This was traced to an issue with resolving the parentPage if the pageList was referenced as a property, and has been corrected. | User Experience |
| INC-B13349 | 866730 | Accessible filter dialog role corrected for optimized table | When using JAWS with an optimized table, navigating to the menu button on the column header and opening the Apply Filter caused the screen reader to announce both the aria-label and the role. This has been corrected by updating the aria-label for the column filter modal dialog from 'Column filter popover' to 'Column filter'. | User Experience |
| INC-B13558 | 867671 | Added accessibility for custom validation error message | A custom validation error message was not read by JAWS when set on a property for a text input. This has been resolved by adding a role alert for the custom message. |
User Experience |
| INC-B13743 | 868372 | Cosmos-react libraries updated to resolve styling errors | A page containing Pega web embed with custom DX components correctly displayed on the first load, but the web embed did not display after navigating to a page in the app which did not have a web embed and then returning to the first page with the custom components. This has been resolved in version 4.2.4 of the "@pega/cosmos-react-*" libraries which contains an additional check to prevent these Styled Components errors. | User Experience |
| INC-B13759 INC-B24969 |
866438 876622 |
Corrected handling for click of Operator image | After creating a case and routing it to a work queue, clicking on the operator image refreshed the case and no content was displayed on the UI. This was an unintended side effect of work done to correct an accessibility issue with the operator icon, and has been resolved by updating the div tag handing for role="img", tabindex="0" in the pxInitials control. | User Experience |
| INC-B14356 | 868822 | Corrected portal rendering after resize | The top navigation window was not rendering correctly after launching the Provider manager portal and resizing the window to a smaller size. This has been resolved. | User Experience |
| INC-B14380 | 864598 | 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. | User Experience |
| INC-B14528 | 875621 | Validation message retained on the UI | A non-mandatory property was validated upon submission of the screen, but messages did not stay on the UI under the Property field. Investigation traced this to the system performing a client side validation on blur event, and this has been resolved by removing the client validation on blur event and performing validation only on change event. | User Experience |
| INC-B14559 | 866545 | Corrected Previous and Cancel button behavior | When there were required fields in the screen, clicking on previous/cancel generated a "value cannot be blank" error. On the second click, the screen moved to the previous screen. This was traced to a validation issue and has been resolved. | User Experience |
| INC-B14617 | 866212 | Timeline list displays sorted events correctly | When using a timeline view in Constellation with Sorting criteria applied in authoring, rendering more than 1000 records did not always display the most recent entries at the top unless the display was scrolled down and back up again. This has been corrected. | User Experience |
| INC-B15113 | 865870 | Added handling for missing display field in Constellation | Using a Picklist property sourced from a datapage in Constellation resulted in the message "An internal error occurred. Please contact administrator." This was traced to an empty 'Display field', and has been resolved with an update to the logic which will set the display field value only when available and will otherwise fallback to use the Identifier field for Dropdown&RadioButton if display field is not configured for the property. | User Experience |
| INC-B15209 | 870800 | Corrected multiselect item delete | Attempting to remove a selected value from a multiselect field within a live interaction by clicking on the cross icon was not working. This was traced to a div focus issue and has been corrected. | User Experience |
| INC-B15506 | 871970 | Datetime validation message displayed with java edit validate rule | A date time control with "allow text entry" set to No did not display the validation message in the UI even though it was in the clipboard. Investigation showed the div responsible for showing the error was not available in the dom if "allow text entry" is No and the java edit validate rule is used. The same configuration worked as expected if the existing standard validate rule IsFutureDate was used. This has been corrected. | User Experience |
| INC-B15574 | 869929 | Corrected overlapping columns in Export to PDF | The column that contains the currency property was overlapping with the column to the right of it when exporting a report as a PDF. This has been corrected by updating the pyReport_ExportToPdfStyles.css file. | User Experience |
| INC-B16001 | 875111 | Supported locales list available | The documentation regarding internationalization and localization has been updated with a list of the valid Locales with appropriate formats | User Experience |
| INC-B16320 | 870817 | Corrected tooltip overriding control label | JAWS was no longer reading the label of a control after an inline tooltip was added. This was due to the control label being overridden, and as has been resolved by providing an ID for the helper text div and giving it to aria-described-by instead of aria-label. | User Experience |
| INC-B16345 | 866726 | Clear filter focus outline appears for non-optimized table | An update has been made to correct a missing focus outline on Clear Filter by adding a selector specifically for a non-optimized table filter. | User Experience |
| INC-B16594 | 870958 | Corrected label default for afternoon period of current date and time | An error in the date/time widget for the current date and time default was evaluating the period between 12:00:00 PM (12 noon) and 12:59:59 PM as AM instead of PM. This has been corrected. | User Experience |
| INC-B16914 | 869818 | Added condition to prevent Mozilla Firefox navigation collapse | During runtime in the user portal it was not possible to select any of the AccessGroups using a mouse and the Mozilla Firefox browser. After Opening the dropdown and hovering over the area with the possible options, the whole section collapsed and jumped back to the initial PortalNavigation section. Investigation showed there was a "mouseleave" event called when the mouse is over "select" control options list, which is a behavior specific to the Firefox browser. This has been resolved by adding a condition to not collapse left navigation in this scenario. | User Experience |
| INC-B17170 | 871953 | Corrected visibility condition incorrectly evaluating to false | If a view contained views/fields with a visibility condition on them, they were not shown even if the visibility condition was satisfied. The views/fields only displayed if the parent view contained at least one field set as always visible. This was traced to the visibility conditions for the fields inside the conditionally rendered EmbeddedData views all evaluating to false when checked by the getComputedVisibility method in corejs. Because a field with no visibility condition was not incorrectly evaluated as false, the view was determined to have at least 1 visible child. This has been resolved. | User Experience |
| INC-B17397 | 871481 | Removed hard-coded aria-label interfering with localization | When adding a date time control to a section or applying a date time column to a non-optimized or optimized table, the date time calendar icon picker had an aria-label of "Date Picker" which was not translated. This was caused by the aria-label being hard-coded for this field; as the aria-label is not required here, it has been removed to resolve this issue. | User Experience |
| INC-B17863 | 878484 | Error messages are correctly updated for conditionally visible fields | When a view contained conditionally visible and mandatory fields, the error message triggered when a mandatory field was skipped was not cleared after the answer was updated and submitted. This led to error messages which were previously displayed being shown again with the latest one appended. This was a missed use case, and has been resolved with an update to ensure the error messages are cleared before validating the form while finishing the assignment. | User Experience |
| INC-B18193 | 868152 | Calendar date picker contrast improved | The background color of the date picker has been updated from #0089ec to #076bc9 for improved accessibility. | User Experience |
| INC-B18562 | 874037 | Updated Authoring regex for custom true/false condition | A custom condition did not accept 'true' and 'false' strings. This has been resolved by updating the method for the regex matcher in expression.js in Authoring to check for ".FirstName == true" vs ".FirstName == 'true'" so true will be treated as boolean while 'true' will be treated as text. | User Experience |
| INC-B18735 | 873737 | Home+end works with hidden columns | Attempting to use the shortcut command 'home'+'end' to navigate to the end of the current row of the table was not working when a column was hidden by default within app authoring. This has been resolved with an update to calculate the last cell even when columns are hidden in an optimized grid, and focus correctly. | User Experience |
| INC-B19809 | 874041 | Localized the fields width and height in the binary field | The fields (height , width ) were not localized when delegating binary rules in an Arabic locale. This has been resolved by updating the pzbinaryImage control. | User Experience |
| INC-B19813 | 871396 | Support added for manual localization rule creation | Attempting to manually create a localization rule via the class explorer did not generate the rule correctly. Investigation showed the localization rule instance was created with an empty JSON object if pxLocaleJson was not present. To resolve this, a pydefault datatransform has been added to handle a localization rule which doesn't has pxLocaleJson defined. | User Experience |
| INC-B20427 | 871996 | Scroll bar works for disabled text area | Scroll bar was not working for a text area when it was set to Disable the Text Area Always. This has been resolved by updating the disabling CSS to specifically ignore the text area. | User Experience |
| INC-B20656 | 870259 | Corrected display of readonly hyphen | After update, the "--" for readonly with no value was misaligned for Inline labels in dynamic layouts. This has been corrected by updating the width to 2px for no-value-span. | User Experience |
| INC-B20809 | 872123 | Stakeholder widget visible in Constellation | A stakeholder widget with an added visibility condition for embedded section was not displaying as expected in Constellation. This has been corrected. | User Experience |
| INC-B21180 | 871598 | Corrected activity registration for FieldHistoryCustomAction | Attempting to download the Field History from a case was generating a SECU0019 alert. This was traced to pyExportFieldHistory not being correctly registered when using BAC, and has been resolved by updating the registered activity for the download button in the pyFieldHistoryCustomAction section. | User Experience |
| INC-B21364 | 876030 | Corrected Print Screen overflow handling | After adding a section containing a read-only text field with a property to a harness with a modal popup, pressing Ctrl+P in the popup generated a Print Screen where blank values were populated as \"No Value\". This was traced to the overflow property being overridden, and has been resolved by updating the CSS to add "overflow: hidden !important;" to class no-value-span in the userworkform. | User Experience |
| INC-B21747 | 874055 | Validation errors displayed on all embedded records | When validating embedded data, errors did not show up under the fields after the 9th record. No red outline or message was seen even though the error count at the top of the page included the non-highlighted fields and all error messages were listed. This was has been resolved by modifying the regular expression handling to support an unlimited number of rows. | User Experience |
| INC-B22567 | 875179 | Updated refresh call handling for rapid selection | After opening a case, choosing multiselect options quickly caused the Check Refresh call to fail and already checked items were getting unchecked and then checked again after a successful refresh call. This has been corrected. | User Experience |
| INC-B22612 INC-B23379 |
874563 876501 |
Corrected DirtyCheckConfirm context | If an activity was performed which caused the dirty dialog popup to appear when working within a report with filters, clicking OK to discard the changes resulted in the Home page being loaded instead of any other landing page that was originally selected. Investigation showed the "pyDirtyCheckConfirm" was being called from the @base class section instead of the work-section, and this has been corrected. | User Experience |
| INC-B22665 | 877644 | Updated container handling for overflow report titles | The full Report Title was cut off when the length of the title was more than the container height. This has been resolved with the addition of a helper class "text-ellipses-2lines" to limit title lines to 2 and ellipse overflow. | User Experience |
| INC-B22699 | 876359 | Corrected time conversion error in Taiwanese calendar | When using the zh_TW (Taiwan) locale, entering a time between 11:30am-11:59am was converted to PM when saved. This was an error in the date/time conversion, and has been corrected. | User Experience |
| INC-B22745 | 877865 | Corrected Anypicker scrolling | Anypicker results were scrolling with the parent webpage scroll. This has been corrected by setting height 0 px when the height has been calculated as a negative value. | User Experience |
| INC-B22996 | 876290 | Text area character count correctly decrements when using voice recognition | The character count on a text area did not decrement as words were added to a text box using Voice Access or other speech recognition software in Microsoft Windows. This has been resolved by adding the necessary code to support this use case. | User Experience |
| INC-B23036 | 873701 | Corrected uneven row height in grid | After update, the row height of the grid table layouts were not consistent across different portals in the application. This has been resolved by adding "display: none" to the extra span added for for an empty data cell. | User Experience |
| INC-B23163 | 877307 | Masked values made read-only | After configuring an access control policy to mask certain property values, the masking was performed as expected, but when the properties were included on an editable view they were displayed as editable. When the values were submitted without change, the literal masked value was passed rather than the actual value of the field and validation failed. This has been corrected with an update to ensure masked values are maintained as read-only. | User Experience |
| INC-B23201 | 874089 | Added handling for localization syncing issue | When using an application ruleset stack with multiple rulesets which each can contain localization records, issues were seen when generating the localization pack due to the pzFetchRecords and pzFetchRecordsForSync reports having conflicting filter definitions about which files to pick and in what order. This has been resolved with an update which will set a filter for the base locale. | User Experience |
| INC-B23529 | 878555 | Updated XML error handling for Mozilla Firefox | After upgrade, submitting the pop-up screen in the Mozilla Firefox browser caused it to freeze. This was due to a difference in the XML error handling for CalculatedValueTargets which was related to a change in the underlying Java version. To address this, an update has been made to CalculatedValueTargets to use StringUtils.isNotBlank to check if tools.getPrimaryPage().getMessagesAll() is not empty. | User Experience |
| INC-B23548 | 873756 | Corrected handling for Japanese double-byte values | After entering a number value like [１] using Japanese IME double-byte characters, moving focus out from the input field cleared the value. This has been corrected. | User Experience |
| INC-B23770 | 877552 | Filtering supported for pxCreateOperator | Previously, the property pxCreateOperator fetched a list of all operators available in the system and could not be customized. An update has been added to support the option of having a custom datasource for filtering the results list with a "UserReference" type to be sourced only with unique table values. | User Experience |
| INC-B24642 | 877603 | LocationComponent preserves location value for "Use as it is" | When using using the Address component in Constellation with an address not present in Google, the value was not preserved when selecting the "Use as it is" from the address dropdown and the field was reset to empty after the blur event. This was traced to the value not being set in OnSelectHandler in location component in this scenario, and has been corrected. | User Experience |
| INC-B24720 | 876297 | Corrected error message color | After update, the error message test background color was gray instead of the expected red banner. This was traced to the layout-noheader-errors class not being present, and has been resolved by adding the needed class pageErrorList layout-noheader-errors and role alert. | User Experience |
| INC-B24915 | 876428 | Corrected duplicate copy/paste for Rich Text Editor | After update, copying content from "Reflection Workspace Mainframe" by OpenText and pasting into the Rich Text Editor duplicated the value. This was traced to CKEditor treating the pasted input as an image in base64 format, and has been resolved by updating the handling. | User Experience |
| INC-B24929 | 877971 | Corrected style of stage buttons on chevron | When simple style for buttons was used in workflow chevrons, setting background color in the skin caused poor contrast and resolution. This has been addressed by adding a background color style in the CSS. | User Experience |
| INC-B24966 | 875882 | Updated autocomplete dropdown accessibility | JAWS was not reading the first value of a dropdown list in autocomplete. This has been resolved by ensuring the live region div is updated when autocomplete results are rendered as a grid. | User Experience |
| INC-B25264 INC-B18163 |
876735 872693 |
Corrected error messages being duplicated | Duplicate error messages were being appended during validation instead of replacing the existing error message for each refresh call when using Constellation. This has been resolved with a check for duplicate error messages before populating. | User Experience |
| INC-B25266 | 876126 | Empty cells correctly display double hyphens | After update, double hyphens were no longer appearing inside the tables. This has been resolved by updating the CSS to show double hyphens when there is no data in grid cells. | User Experience |
| INC-B25382 | 878688 | Corrected cleared date field value being repopulated | In a DateOnly field control set to required always, a value which was set through a data transform in a pre-flow action reappeared after having been manually cleared. This was caused by the value being undefined on clear, and has been resolved with an update to set the date value to empty string when clearing it. | User Experience |
| INC-B25437 | 876557 | Updated modal flowaction for "Close the Work Object" | When using the "Close the Work object" configuration on the last flow action in a case flow under the actions tab, completing the case flow generated a blank space in the portal rather than the worklist as expected. This happened when a work object was opened in review mode and the assignment was opened in the primary Ajax container, and has been resolved with the new function closeWorkObject in the utils file to handle the close of the work object. | User Experience |
| INC-B26158 | 876338 | Added handling for aborted localization process | The Constellation localization wizard was getting stuck if a localization had previously been canceled / aborted by closing the modal dialog after the Excel/JSON package had been generated. When generating the package the second time, the error "Create new record failed: this instance already exists" was shown. This has been resolved with an update which will delete the old file. | User Experience |
| INC-B26566 | 878366 | Corrected validation error incorrectly persisting | If a validation error message was triggered on a particular screen by clicking the "next" button, the same message was shown when the "back" button was clicked on the same screen. This has been resolved with the addition of an explicit step to clear context messages from the active work area during navigation. | User Experience |
| INC-B3711 | 858658 | 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. | User Experience |
| INC-B3966 | 854297 | File upload alert and busy indicator display in correct position | Uploading a file that exceeded the max upload size resulted in the the file loader alert / busy indicator not being properly centered on the screen. This was traced to multiple modal dialogs and overlays causing incorrect calculations for pega_ui_busyIndicator.js, and has been resolved by setting the active modal as the root element when calling the busy indicator. | User Experience |
| INC-B4451 | 852936 | Updated handling for Date Picker date out of bounds error | When using Constellation, selecting a date late in a month and then adjusting to a month with fewer than that number of days from the dropdown caused the picker to skip the short target month and display the next one containing 31 days. While there was a workaround of selecting any date from 1-28 from the current month and then selecting the desired month, this has been corrected by improving the handling when switching months of different lengths. | User Experience |
| INC-B4761 | 859246 | Corrected section grid alignment for To Do | After performing the case action "Save to my worklist" and assigning the case to a logged-in user, the To Do section grid alignment was not correct. This was traced to the showHideAssignmentGadgets function which was attempting to show/hide the hierarchical table sections on some actions. As the hierarchical table section was marked as display: none, the height was not correctly calculated while refreshing the section. This has been resolved with an update to the widget row heights on show of the pxAssignmentView section when the assignment block is visible. | User Experience |
| INC-B4844 | 857427 | Overflow correctly applied to optimized grid in popup | When there were more than 15 columns in a optimized table displayed in the overlay, scrolling the page up and down caused the column names to come out of the overlay and become disorganized. This issue Issue only occurred when the pop-over was displayed above the grid and contained enough columns to trigger a scroll bar, and was caused by the overlay container with id ="po0" on the first load not having the overflow CSS applied. This has been corrected. | User Experience |
| INC-B5095 | 858438 | Cancel button corrected for temporary mode | The Cancel button was not functioning on the case worker area when the case was opened in temporary mode. This has been corrected with an update to pycaseactionareabuttons. | User Experience |
| INC-B5434 | 855747 | ARIA-Expanded set correctly for Accordion Layout Group | When using a custom accordion layout group with "Collapse all panes on load", the screen reader was announcing the state of the button as expanded even though it was collapsed. This has been corrected. | User Experience |
| INC-B5484 | 864617 | Views dereferenced correctly | When getting the case view data, dereferencing the view with pConnect generated an error and returned null. This was traced to OpenCase returning empty values for pyName, and has been resolved by adding a safe check while resolving the view name. | User Experience |
| INC-B6140 | 867335 | Filter date selection correctly triggers filter | When making a selection from the promoted filter date icker, the filter was not immediately triggered based on the entered date range and instead required clicking in and out of the field in order to trigger the filter. This has been corrected to the expected behavior of the filter being applied immediately after closing the date picker pop over. | User Experience |
| INC-B6531 | 871462 | Corrected unexpected scrolling in control timeline details | Clicking on an icon in the control timeline opens the details overlay, but clicking anywhere else to close the overlay caused the screen to move down to the expand icon in the table. This was traced to work done on pega_ui_modaldialog in the performFlowACallback API to check for multiple overlays before focusing into the grid row, and has been resolved with an update which will focus on the table when the overlay launching element is part of an active grid. | User Experience |
| INC-B6613 | 859056 | Function onGridFilterClose added to improve performance | In an optimized table, enabling a filter for columns having unique data caused the filter overlay itself to contain thousands of records. Once the filter overlay was opened, subsequent interactions took significantly more time than required. This was traced to the filter body not being removed and the results having an extremely large markup which stayed in the DOM, and this has been addressed with a new onGridFilterClose function. | User Experience |
| INC-B7407 | 871131 | Corrected reference for child cases in collapseModal function | Creating a child case in a modal window and then deleting or minimizing it before finalizing it caused an incorrect reference to be used for other actions, leading to other child case confirmations being displayed with an unexpected size and placement. To resolve this, an update has been made to set a value for the variable _openCaseOnCreate in collapseModal function. | User Experience |
| INC-B7782 | 858201 | Save button in pyApproval flow action made available | By default, the save button is hidden in the pyApproval flow action for automation steps. In order to support local use for cases such as completing a lengthy form (HierarchicalForm) in Constellation, an update has been made which will display the 'Save for later' button on an approval step based on the SaveLater visibility checkbox in the pyApproval flow action. | User Experience |
| INC-B7857 | 860317 | 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 | 862195 | Added accessible name for iframe | Aria label has been added for the live composer iframe name in App Studio for improved accessibility. | User Experience |
| INC-B9218 | 867659 | Clarification for keyboard shortcuts instruction | The Text Editor keyboard shortcuts instruction in Knowledge Management article creation has been updated to clarify that "use keyboard shortcuts Alt+F10" applies only when inside the Rich Text Editor body. | User Experience |
| INC-B9573 | 861473 | Updated handling for autocomplete using datapage query | Autocomplete was not presenting a complete list if the search characters were changed while the data was being loaded. This occurred when the autocomplete was sourced with a datapage and dataapiobj was querable in an embedded data as a fieldgroup, and was caused by the load-more call back setting duplicate items while concatenating the previousItems and searched Items. This was a missed use case and has been resolved with an update to avoid rendering AutoComplete menu items with duplicate keys. | User Experience |
| INC-B9833 | 867544 | Corrected handling for changing the Display As for an embedded property | After creating a case type in Constellation of an abstract class with properties, followed by adding a page of the abstract class to the case, adding a view to the case type, and adding a property of the abstract class to the view which was then configured, there was no option to change the Display As property. This was due to a missed use case, and has been resolved with an update to get the needed field property for embedded field to display the required configuration. | User Experience |