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
Special Notes
| Ticket # | Issue # | Title | Description | |
|---|---|---|---|---|
| Special Note | E-98302 | "No actions" counts included for Decisioning | An update has been made to more accurately measure Session counts and Decision counts when the decision results in no action. As a result, an increase in metrics may be seen as Session and Decision count totals will now include these "no action" counts. | |
| Special Note | 891720 | PEGA00167 alert added to identify UDF activity | Relying on Java UDFs to extract one or more BLOB columns to be used for reports or application queries can negatively affect application performance, especially with large database tables or multiple, simultaneous BLOB column extractions which can occur on large, complex applications. Issues such as database out-of-memory errors or queue processors failing to process records may be seen and affect all nodes in cluster, impairing recovery. Beginning in Pega Platform version 8.6, Pega deprecated usage of the Java user-defined functions (UDFs) due to their severe performance impact. In a future release of Pega Platform, Pega will no longer support Java UDFs for on-premises deployments. Pega Platform deployments do not require Java UDFs and in most cases, Pega does NOT recommend the installation of Java UDFs. In order to assist with this transition, the PEGA00167 alert has been added to notify if any report or any use case is using UDF. |
Case Management
24.1.2 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B17952 | 869511 | 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-B18764 INC-261181 |
875349 810260 |
Designer Studio portal launch speed improved | Launching a portal from Designer Studio was very slow. This was caused by using a rule resolved report definition which was trying to get all application logos using pzLoadApplicationLogo activity, and has been addressed with an update which will switch the application context and open the binary file record, then switch to the correct application context and use efficient data page handling to fetch the application logo details. | Case Management |
| INC-B1967 | 855589 | 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 | 873683 | 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-B20251 | 871556 | Case data object security updated | Cross-site scripting protections have been added to the case data object creation activity. | Case Management |
| INC-B20254 | 871561 | Alternative Stage Name security enhanced | Security has been updated for Alternative Stage Name. | Case Management |
| INC-B21012 | 874364 | 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 | 874373 | "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 | 873978 | 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-B23963 | 875854 | Added file upload handling for user with quote mark in name | When a user with a single quote in their name (eg Joe O'Sullivan) attached files to a case, those files were not able to be previewed or opened. This has been resolved with an update to the pyAttachmentFeedDescription and pyWorkAttachmentIcon controls which will modify the UploadedBy value to replace the single quote. | Case Management |
| INC-B24617 | 880582 | Corrected handling for auto-processed SLA queue item | When the DSS UseSLAQueueProcessor was set to true, an assignment configured with "Allow auto Process" and SLA defined was moved to the broken queue instead of being removed when the assignment was auto-processed. This has been resolved by updating the logic in the flowfua_task_assignment function. | Case Management |
| INC-B26685 | 878467 | 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-B28855 | 885745 | Document Viewer updated for more than 50 attachments | When attempting to view a case attachment containing more than 50 documents, the 51st attachment and beyond were blank and the error "The attachment is not available" was generated. This was due to the DEFAULT_FETCH_SIZE = 50 value being hard coded, and has been resolved with the addition of the DSS "maxRecordsToPreviewAttachments" to expand the number of attachments fetched for viewing. This has been added to the Pega-EndUserUI ruleset, and has a default of 100. | Case Management |
| INC-B29165 | 880857 | Improved accessibility for "Where am I" icon | The "Where am I" icon has been updated with a title attribute for accessibility by creating a field value for pyCaption which is mapped to the title in pyAssignmentsLabel for "Display Flow Location". | Case Management |
| INC-B29572 | 881419 | Case status flag updated with alt text | To improve accessibility, alternative text has been added to the case status flag. | Case Management |
| INC-B31136 | 882359 | Improved stage progress color contrast for accessibility | To improve accessibility, the green used to indicate the active state of the stage progress section in pyDisplayStages has been modified from # 179595 to # 127F7F to meet color contrast ratio standards. | Case Management |
| INC-B31250 | 886818 | Added handling for annotating subflow | When attempting to add an annotation in a sub-flow in App Studio or Dev Studio, the error "Server response error, no update data returned." was shown in a popup. This has been resolved by adding the pyShapeType "Data-MO-Annotation-Comment" field value in the Pega-ProcessArchitect rule set to avoid the error. | Case Management |
| INC-B33358 | 889928 | Updated handling for wait configuration | The Assignment page was not correctly set after reaching a wait configuration with a dependency. This has been resolved by updating the function in the pyContinueAfterWaitPre data transform to PageExistsWithClass and ensuring the necessary parameters are passed. | Case Management |
| INC-B3548 | 858166 | Corrected hint text for case lock | When using a parent and child cases structure in Constellation, if a case was locked (user 1 started an assignment in one of child case) and a second user attempted to start an assignment in another child case that belongs to same parent case but which was not opened by user 1, the error "Flow_CoverLockFail THK-XXXX [user name]" was displayed instead of the expected lock error message. This has been corrected by updating workUnlock to show the message as expected. | Case Management |
| INC-B36450 | 888666 | Updated accessibility for BulkActionsWrapper | In sections pzBulkAdd, pzBulkUpdate and pyBulkProcessingSearch, the headers were being added as a standalone label instead of being adding as a header on a wrapper layout. This has been resolved by adding the header title value to the sections to improve the accessibility. | Case Management |
| INC-B37071 | 893569 | Added support for Pulse notes archived to secondary storage | When long text was submitted to a Pulse message, the full message was not visible on the archived case. This was traced to the Data-WorkAttach-Note record not getting saved into secondary storage, and has been resolved by adding logic to copy the Data-Attach-Note instance of a case. | Case Management |
| INC-B40273 | 893596 | SendEmail security updated | Cross-site scripting filters have been added to the SendEmail control. | Case Management |
| INC-B40285 | 893917 | Mandatory validations correctly enforced for launch screen | In Theme-Cosmos applications, it was possible to continue from the screenflow Create screen without completing mandatory fields if "Allow Errors" was checked. After launching new case the second time, no mandatory field errors were displayed when clicking on the create button. This has been corrected by updating the isDeferError and customClientErrorHandler functions in the Navigation rule to ensure the "Allow Errors" checkbox is handled correctly. | Case Management |
| INC-B40474 | 893084 | Corrected pxProcesses page handling for change stage automation | When a change stage was used in the flow process as a shape, the action was not marking the task/assignment as done. Using change stage from the Action button as a case-wide action worked as expected. Investigation showed that while performing the change stage with a "Change to a specific stage" automation step, the pxProcesses page used by the pxStageHistory page was being removed from the pyWorkPage for that stage. This has been corrected. | Case Management |
| INC-B43205 | 893394 | Check added to ParseMentionedItem to limit search | Long email threads that include email domains containing hyphens (ie coca-cola.com) were causing performance impact. This was due to the system is pulling all references to the hyphenated text in the activity pzSaveMentionedUsers and then iterating through the entire list of mentions to determine if they are users, cases, etc. This was a missed use case, and has been resolved by adding a 'when' condition to check for "." in the string passed to Pega-Ext-Mentions-Cases.pyParseMentionedItem to limit the search. | Case Management |
Cloud Services
24.1.2 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B12861 | 877517 | Corrected values for PEGA0117 alerts | PEGA0117 alerts were showing incorrect values, causing alerts to be triggered with a time well above the threshold that did not match the total time. This was traced to the calculateMetrics method in QPExecutionContext.java, and has been resolved by setting the total request time to the current duration instead of the cumulative value of the total request time. | Cloud Services |
| INC-B25421 | 876779 | Product rule loads data instance key | The data instance key was not loading in the Product rule. This was an unintended side effect of work done to enable the instance picker to work with missing columns, and has been resolved with an update to ensure the pzInsKey is populated by the query as part of the individual instances to include section. | Cloud Services |
| INC-B26562 | 883278 | Support added for double-quoting Postgres GRANTs with special characters | Errors were seen when importing a new table on a system with a base and admin user configuration where the base user name required quoting to handle special characters. This has been resolved by adding support for quoting the user identifier when generating GRANTs with Postgres. | Cloud Services |
| INC-B33933 | 885037 | prpcUtils updated to use explicit schema properties | The error 'Could not fetch code set versions from database' was generated while running the prpcUtils. This has been resolved by using explicit schema properties in generated prbootstrap.properties instead of schema-qualifying the table name property. | Cloud Services |
Conversational Channels
24.1.2 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| BUG-822783 | 895346 | Handling added for extra characters in inline email attachments | On some occasions, inbound email replies sent from Microsoft Outlook web clients were not correctly being attached to an existing case, and the runtime error "PRRuntimeException Paths may not navigate out of the scope of their definition" was logged. This was traced to extraneous characters included in file paths for inline attachments such as logos in email signatures where the filepath started with ../ (two dots instead of one). This has been resolved by updating the pyPreProcessTriageWork activity to remove unnecessary characters from attachment names and replace special characters with '_' for the inline attachments of inbound emails. | Conversational Channels |
| INC-A28855 | 874605 | 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. | Conversational Channels |
| INC-B14761 | 884222 | Updated CaseMappingActions handling of hidden content | When using a local action to call pzCreateLinkedCase, the case was created but a blank overlay was seen that persisted until there was a click outside of the section. This has been resolved with by updating the pzCaseMappingActions section hidden content with none function. | Conversational Channels |
| INC-B18492 | 871373 | Time to live attribute added for Pega Digital Messaging Token | The expiry attribute was missing in the digital messaging token generated in for outbound APIs. This has been resolved by adding a time to live token for the JWT authentication method. | Conversational Channels |
| INC-B21921 INC-B30324 |
872014 881069 |
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. | Conversational Channels |
| INC-B22367 | 878552 | Timestamp correctly localized on email conversations | The timezone configured in the operator localization section was not being honored in the email manager Constellation portal and was being rendered in GMT. This has been corrected by updating pxLoadEmailThreads to ensure the timestamps are localized on the server side. | Conversational Channels |
| INC-B23417 | 873693 | Agent name correctly populated in reply | The Agent name was not populating in a reply. This was caused by the logic assuming the use of Asyncemailprocessing, causing the UserName to not be set when it was not used. This has been resolved by updating the activity with the proper sequence of logic and jump statements. | Conversational Channels |
| INC-B26569 | 880141 | Resolved Email Triage cases show correct SLA details | After the email triage cases were resolved in Constellation, the SLA details showed dummy values. This was caused by the resolved case having both Goal and Deadline values as null in D_pxTriageCaseMetadata, so the CaseSummary widget displayed the date difference computed from 1970. This was a missed use case for resolved cases that has now been addressed. | Conversational Channels |
| INC-B27145 | 879728 | Training recording from email made consistent | The training data was not recorded as expected if a CSR responded to an email by using the reply button instead of the suggested replies. This was due to a difference in handling: the pyReplyTemplateID was set on pyWorkPage if the template button was clicked, but selecting a template in composer used a different rule which did not set the template ID value on pyWorkPage so it was not present on the primary page. In both cases, the template value result is subsequently set on the ReplyMetadata page in pypopulateReplyMetadata, and this issue has been resolved with an update to use the this page in the 'when' rule in step 2 to submit the feedback on reply. | Conversational Channels |
| INC-B28596 | 879934 | 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 |
| INC-B30137 | 883735 | Manager key handling updated | The Manager key in Digital Messaging security and Private Key are now obfuscated. | Conversational Channels |
| INC-B31710 | 886248 | Corrected br tag replacement handling | In some instances when br tags were removed (pxExtractLatestReplyFromBase64), the plain text was presented without spaces between the words. This has been corrected with an update across elements in pzTextToPropertyMapping and pyParseReplyMail to replace br tags with new line when text with br tags is sent for NLP analysis. | Conversational Channels |
| INC-B32934 | 883090 | Corrected subject repeating in email thread history | When an email was forwarded to a third party, the message subject was repeating in the email body in the email thread history. This has been corrected with an update to prevent unnecessarily adding the subject to the forwarded body. | Conversational Channels |
| INC-B33097 | 889375 | "Run visibility condition on client" unchecked for PostEmailContentV2 | The UI and icons of an email triage pane changed automatically if the case was left open. This was caused by an auto-refresh of section by the SystemHealthIndicator evaluating all of the visibility conditions present in the current AJAX container (IFrame). During that validation by the change tracker, the conditions were returning false and affecting the icons and their visibility. This has been resolved by unchecking the "Run visibility condition on client" in the section pyPostEmailContentV2, which is part of the work being done to remove client-side visibility conditions and switch to server side checks. | Conversational Channels |
| INC-B33098 | 883558 | Updated handling for recipient view in email compose window | While performing "Reply All" on an inbound email which contained more than 15 To/CC recipients, some of the recipient email IDs were truncated when viewing the list. This has been corrected by retrieving the full recipient list on "View All" by loading the pyHistory record from the database. | Conversational Channels |
| INC-B34829 | 889052 | Base 64 inline image handling updated | Illegal characters were detected during the sending of auto-acknowledgment emails, causing an exception. Investigation showed this was caused by the recent change in the pxReply activity which replaced pxPostMessage with pzUploadRTEImageFromBase64Url to handle base 64 inline images, and has been resolved by using "Image+<datetime>" instead of the alt attribute for the filename. | Conversational Channels |
| INC-B35358 | 889837 | Updated harness types for IsHarnessTypePerform 'when' rule | After reopening a Service Case containing an email thread and moving the case to Resolved-Completed status, the Reply button option was visible in the Confirm Harness screen even though it had a 'when' condition to display only in the Perform harness. This has been resolved by adding PerformFrames to the custom list of harness type parameters in the pyIsHarnessTypePerform 'when' rule of both Work-Channel-Triage-Email and PegaSocial-Message classes. | Conversational Channels |
| INC-B35986 | 889069 | Corrected table headers in email thread | Table headers were not displayed in the email thread on a case when defer load email was set to true. This has been resolved by removing new lines from the generated email content when using the correspondence template. | Conversational Channels |
| INC-B37192 | 888183 | Added handling for History Index race condition | Incorrect To/CC recipients were populated on the reply window. This was traced to a race condition related to the History Indexes, and has been resolved with an update to set the correct history index in this situation so emails are properly threaded and recipient details are shown accurately. | Conversational Channels |
| INC-B39766 | 891034 | Handling added for history item errors | Runtime exceptions from the natural language processing (NLP) analysis resulted in pyHistory being created with incomplete data. To resolve this, Rule changes have been added to ensure pyHistory record creation when an error occurs in NLP, along with added logging and an extension point. | Conversational Channels |
| INC-B40433 | 892498 | Added check to exclude drafts when forwarding email | When an email draft was saved, the draft was included on the thread accordion of the original email when forwarded. This has been corrected by updating pyUpdateConversationAsSaved to check for pzInsKey when looking for drafts. | Conversational Channels |
| INC-B40592 | 894268 | Added extension point for custom access group used for Data-Channel-BotAgent-Integrations | The error message "You are not authorized to save instance DATA-CHANNEL-BOTAGENT-INTEGRATIONS of class Data-Channel-BotAgent-Integrations" was being logged. This was traced to the background processing being run with the default access group of the operator who triggered the pzRefreshIntegrations activity and not the access group used when queueing the background processing. This was an implementation issue which did not account for site-specific variations in the permissions for the default access group of an operator, and has been resolved by adding an extension point for a custom access group with the needed permissions for the background processing activity. The Extension point pySetCustomAccessGroup will be used when the flag pzUseCurrentAccessGroupForChild is set to true and will be added during queueBatchActivity processing in the pzRefreshIntegrations activity. | Conversational Channels |
Data Integration
24.1.2 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B16627 |
882736 | 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-A18369 INC-B18082 |
870411 872106 |
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-A26543 | 873462 | 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-B10053 | 894544 | Corrected ruleInsKey parameter handling for Admin studio | The rule cache API was not working when invoked from Admin studio. This was traced to the parameter value of ruleInsKey not being populated, and has been resolved by updating the rule ins key variable to camel case. | Data Integration |
| INC-B10224 INC-B27412 INC-B31085 INC-B23839 INC-B25678 INC-B30445 |
880807 | Dev Studio search updated for SRS | In order to facilitate the changeover from embedded ElasticSearch to SRS, a new set of search capabilities has been introduced: ENGINE_WORK_ID_SEARCH_GADGET - allows for workid search in Dev Studio's search gadget ENGINE_RULE_SEARCH_GADGET - allows for rule search in Dev Studio's search gadget ENGINE_DATA_SEARCH_GADGET - allows for data search in Dev Studio's search gadget In case of archival indexing, the getIndexName method for the PegaIndexManager API has been updated to allow the SearchHelper class to handle both SRS and embedded Elasticsearch. |
Data Integration |
| INC-B10336 | 877133 | 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-B12600 | 865197 | 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-B12718 | 880599 | PerformReindexing accepts parameters to limit scope | In order to facilitate reindexing on sites with a large amount of archived data, pzPerformReindexing has been updated to accept the parameters archivedZipFilePath, startResolvedDate, and endResolvedDate to constrain the targeted archived data to be reindexed. | Data Integration |
| INC-B13020 | 894218 | Updated retry handling for file listener | After enabling Ignore Duplicate Files and Attempt Recovery for the file listener, the file listener was not correctly retrying up to the maximum number of attempts set. Investigation showed the first failure resulted in the .err file being created which was then queued for retry. However, in the second retry the file listener skipped processing the file and renamed it as a .dup file, which then caused the system to consider it a duplicate file and stop the retries. This has been resolved with an update with additional checks to reprocess unprocessed files instead of marking them as duplicate. | Data Integration |
| INC-B13031 | 877821 | Updated check for readonly data page | After creating an optimized table with row reordering where the data page was queryable, an extra data page call was triggered without an implicit parameter. The second call did not happen if "allow row reordering" was not checked. The extra call was traced to the data page being loaded to check if that's readonly or not for the purpose of the row reordering, and this has been resolved with an update which will load the data page to determine readonly status if the grid is not queryable. | Data Integration |
| INC-B15649 | 879222 | Handling added for mapping duplicate objects | When a JSON data transform was defined with 5 levels of embedded JSON attribute structure while not changing the clipboard context, nothing was mapped after the second page-pagelist in the JSON even though 2 or more sibling pages-pagelist were defined. This was a missed use case, and has been resolved by updating the mapping method to not use the property name as a key for mappings and instead use uniqueMappingID for duplicate properties. | Data Integration |
| INC-B16148 | 867349 | 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 | 885359 | Added re-read to correct retry failing due to clipboard corruption | After encountering a "Connection Reset" error that was interrupting the file read, the retry configured on the File listener was also failing consistently with the error "Failed with MapToParseException, Reason: reference must contain property name". This was traced to a clipboard corruption, and has been resolved with an update which will read the CSV headers again in case of error handling and recovery. | Data Integration |
| INC-B17344 | 875398 | 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-B17414 | 875700 | Security updated for responses | Cross-site scripting (XSS) security has been updated for service request responses. | Data Integration |
| INC-B18059 INC-B31660 |
884099 884114 |
Corrected MapInput API exception | After update, the mapInputJSON() API was generating an IndexOutOfBound exception while mapping the list data. Analysis showed the API worked if there were no new page lists in the request payload, and the issue was traced to previous work done in the PZAPPLYDATAFORPERFORMACTION activity. This has been corrected in Constellation with the use of a content section that uses embedded page list properties with declaratives. | Data Integration |
| INC-B19006 INC-B18991 |
884154 888034 |
BLOB reindex added to clear lingering orphan data | Issues were seen with unexpectedly large database consumption, including sporadic runtime exceptions related to StorageStreamCommonImpl. Investigation showed a large segment of the database was occupied by a work table associated with pzPVStream and DirectStreamEncoder, and that space was not being released even when the objects were removed and a resave was performed. To address this, an update has been added which will forcefully reindex the BLOB during encoding to ensure the orphan data is correctly cleared. | Data Integration |
| INC-B19025 INC-B36801 |
880564 888870 |
Handling updated for TemplateInputBox property creation | After upgrade, attempting to save an instance into an existing external table(no BLOB) generated the error message "Cannot save instance of class XXXXX-Data-Address; it belongs to fully exposed table PEGADATA.YYY_ADDRESS in database PegaDATA, but the instance has properties which do not correspond to columns: pyTemplateInputBox". This was traced to the presence of a button in the section. Buttons generally add code to get the clipboard reference of getProperty for pyTemplateInputBox, and would create the property if it was not found. To ensure this property is not created for button / image / link actionable controls where there is no need of any editable properties, the handling for pyTemplateInputBox property creation has been updated. | Data Integration |
| INC-B20255 | 873105 | Null ruleset handling added for Dev Studio tracer | Running the SOAP service from Dev Studio with tracer indicated a failure response when the "SOAP messages" and "Services" options in the settings were enabled. The failure was not seen when these options were disabled. Investigation traced this to the rulesets being shown as null due to the ServiceRequest not being initialized, and this has been resolved by adding handling for this scenario which will skip the event and the event will not appear on tracer. | Data Integration |
| INC-B22062 | 876711 | Corrected null pointer error during NBA run | A null pointer error was reported during a Next Best Action (NBA) run. This was traced to the evaluation of a when rule which caused a class-level dependency property to be read multiple times, and has been resolved with a refactoring to address this. | Data Integration |
| INC-B22806 | 877843 | Improved database table connection testing security | Cross-site scripting protections have been updated related to testing the connection to a database table. | Data Integration |
| INC-B22959 | 887467 | Added handling for \"-\" in decimal field | If a number control with decimal property had a validation in the flow action, running the case and inserting a "-"(minus) symbol in the field generated an error on submit. This has been resolved by adding handling in pega_validators.js with logic/expression in the function "numeric_isDecimal()" for the scenario where only "-"(minus) is given as input for a number control. | Data Integration |
| INC-B23270 | 886293 | Support added for abstract property generation | When using the connector and metadata wizard to generate classes properties and parseXML rules for use in a large new XSD with abstract properties, properties were not getting generated from the XSD when abstract=true. This has been resolved by adding support for generating the properties with abstract. | Data Integration |
| INC-B23600 | 876801 | 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-B23640 | 877786 | Filter for queryable data page uses correct context | After creating a queryable data page and allowing filtering on any column and then creating a field value for that column data in baseclass and the datapage's class, the localized value was picked from baseclass. If the datapage was made non-queryable, the localized value was picked from the correct context. This has been corrected with an update to use the proper class instead of Embed-FilterColumnValues for resolving the field value. | Data Integration |
| INC-B24110 | 880347 | Query Runner Excel export updated | After running Query Runner with successful results and clicking Export to Excel, the generated download file was not able to be opened due to site policies which do not support the Microsoft Excel 97-2003 Worksheet (*.xls) format. To resolve this, the activity pzexportexcel in Query Runner has been updated to use the updated Excel format of .xlsx for export. | Data Integration |
| INC-B26326 | 880428 | Date handling updated for en_HK locale with Java 11 | After upgrading to Oracle Java 11, an exception in date format was seen on start up. This has been resolved by adding the en_HK.xml file to support the en_HK locale. | Data Integration |
| INC-B28487 | 881449 | Corrected client-side validation performed on hidden fields | Client-side validation was firing on elements that were not visible in the Constellation UI or which were configured as not required, generating the error "Correct all fields containing errors" and a browser alert "Please correct all flagged fields before submitting the form!". This has been corrected with an update to not consider client side validations for hidden fields. | Data Integration |
| INC-B28508 | 879322 | Updated OpenAPI Export parameters for Service-REST | The generated OpenAPI specification for a Service-REST rule was incorrectly generating the field allowEmptyValue for all parameter types. This has been resolved with an update to restrict allowEmptyValue to true only for query parameters and not for path/header parameters. | Data Integration |
| INC-B29513 | 893166 | Performance improvement for data_views | When using the v2 data_view/{data_view} API, the request was sent with Includetotalcount:true and Returntotalresultcount:true, causing it to fetch all of the data instead of fetching data based on the pagination. This has been corrected to improve performance. | Data Integration |
| INC-B31997 | 887732 | OpenArchivedWorkObject updated to enable opening archived parent of current case | In the Pega Smart Dispute framework, the case overview section of a dispute case refers the data from pyWorkCover (claim case). When the child case was archived and and the archived case was opened, the pyWorkCover was not populated and some fields were blank. In order to address this, a place holder activity has been added to the activity pzOpenArchivedWorkObject to open the parent case of the current case. | Data Integration |
| INC-B32312 | 885797 | Accessibility improved for pyMapFieldsInner | Helper text has been added to all default fields the MapFieldsInner section for improved accessibility. | Data Integration |
| INC-B32313 | 885759 | Removed unnecessary checkmark on MapFieldsLegend | The image being used to display the checkmark in MapFieldsLegend near the CSV import line did not contain alternate text and was causing issues on automated scans and screen readers. This image has been removed as it is not necessary and was impeding accessibility. | Data Integration |
| INC-B32717 | 886206 | Archival pacing available to reduce database impact | In some system configurations, the InMemory Pipeline mode of case archival may exceed the available input/output (I/O) operations per second, resulting in socket timeouts during column population jobs. To address this, a sleepduration parameter has been added to pyPegaArchivalUsingPipeline. The SleepDuration parameter is configured in milliseconds, and applies a delay between each cycle of archival process. One cycle of archival is considered as archiving limitperpolicy DSS(default value : 1000) cases per case type which are configured for archival in the case type setting screen. | Data Integration |
| INC-B32764 | 889901 | Connect-FTP handling added for multibyte code filename | An update has been made to support transferring files with names that include multibyte code such as Japanese characters on an IIS FTPS server using Connect-FTP. These changes are dependent upon the DSS "ftp/enableUTF8Encoding" which must be set to true for this use. | Data Integration |
| INC-B35352 INC-B36106 INC-B42455 INC-B43016 |
887070 890582 893760 893891 |
DSS added to control "SkipHitNotFound" issue | The Next Best Action (NBA) outbound run failed with the error "IllegalArgumentException: DataFlow page has errors over overwrites applied: .pyModelProcess.pyShapes(Destination).pyRuleName: BatchOutPR4004 does not exist or is not a valid entry for this ruleset and its prerequisites". Investigation traced this to a race condition: the instance cache is dependent on the system pulse for invalidation, and if any rule is created after the instance cache initialization and the system pulse is missed or the rule is created before the system pulse module is loaded, then the event cache is not updated and there is a "hitnotfound" error for the rule. To resolve this, a DSS has been added to control the behavior when this error is encountered. Setting CACHE_RULE_INSTANCE_SKIPHITNOTFOUND_ENABLE to true will result in the change that if rule is not present in the instance cache, the system will search the database and add the entry into the alias cache and instance cache. | Data Integration |
| INC-B35491 | 887789 | Email Listener updated for MSGraph subfolders | Email listener was not working for multi-level subfolders such as Inbox/Sub-Folder1/Sub-Folder2 when using MSGraph, and decrypted mail content wasn't visible in the work-channel object. Support for these has now been added. | Data Integration |
| INC-B35624 | 887623 | Webservices libraries updated | The webservices-rt and webservices-api libraries have been updated to the most recent versions. | Data Integration |
| INC-B37040 | 892040 | Corrected decryption of embedded properties | After update, case search was failing with the error "An internal error occurred while fetching the results using data view. Please contact administrator." Investigation showed when there was a combination of pagelist and a property with the syntax ".AddressList().City", the decryption of the mixed use case syntax was not handled from data page API end. This has been corrected by updating the decryption of the embedded page and pagelists for lookup and list endpoints. | Data Integration |
| INC-B4258 | 862215 | 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-B42844 INC-B11228 |
895123 871067 |
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-B7171 | 873676 | User ID handling updated for CaseOperator | The CaseOperator widget for Constellation has been updated to properly handle and persist referencedUsers lists to ensure IDs are correctly reflected for updates. | Data Integration |
| INC-B730 | 862466 | 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 | 849390 | 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-B8774 | 894215 | Corrected mapping initialization for nested JSON | After update, a JSON data transform used to map a pagelist property to JSON objects was not working if it called another JSON data transform to do some of the mappings. This was caused by the rules engine looking for the data transform in the Primary Class rather than the applies-to class of the pagelist property, and has been resolved by correcting the initialization to fetch from the mapping model instead of the step page. | Data Integration |
Decision Management
24.1.2 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-B24750 |
875846 | 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-B13172 | 864952 | Added Dev Studio check for Model landing page before loading strategy rules | While implementing post upgrade steps after moving from Pega 8.5 to Pega Infinity 24.1, error messages about strategy related components appeared, indicating "Error in Obj-Open database.BadClassDefinitionException: Attempting to access a rule with a bad defined-on class: Trying to open rule "SMS" of class "Rule-Decision-Strategy", but no defined-on class (pyClassName) was specified." This has been resolved by adding a check for the Model landing page activity before loading when opening from Dev Studio. | Decision Management |
| INC-B16167 | 882252 | External stream delivery and request timeouts made configurable | External stream delivery and request timeouts made configurable In order to assist with analyzing Kafka timeouts, the stream delivery timeout and request timeout have been made configurable values to support a "fast fail" mechanism. The delivery timeout default is 2 minutes, and the request timeout default is 30 seconds. Delivery Timeout: services/stream/producer/delivery/timeout Request Timeout: services/stream/request/timeout Conditions: Delivery Timeout Value Range (in ms) = 5000 to 120000; Request Timeout Value Range (in ms) = 1000 to 30000; At least One Try Possible = Delivery Timeout > Request Timeout |
Decision Management |
| INC-B17549 | 875819 | 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-B18411 | 875083 | 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-B19169 | 878947 | PreviousComponent property handling updated for Strategy | After customizing the strategy for an interaction using a setProperty with pyPreviousComponent in the strategy to get the name of the model, the pre-previousComponent name(filter name) was unexpectedly returned as the output if an API call was made through the NBA container. This was traced to property optimization occurring at different times for different processes, and has been resolved by updating the logic handling for the default property notification propagation according to which component should expose default properties when they are used in the logic of a given component. | Decision Management |
| INC-B20725 INC-B18063 |
873916 869237 |
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-B20765 INC-B36418 |
871843 889689 |
Legacy strategy execution profile updated | The legacy Pega strategy execution profile feature was not working as expected after update. This has been resolved by updating the parameter handling so the report correctly includes total strategy execution time and a strategy/component breakdown. In addition, an update has been made to improve visibility by adding parents for strategies up to two levels and number of calls for all components and strategies. "Strategy Parent” and “Number of Calls” will also be included in the report available for download after running the non-GOS strategy. | Decision Management |
| INC-B21535 | 877738 | DSS added to allow using multiple Cassandra data centers for balancing | Adding more than one data center to the database instance for use as the Cassandra cluster "local data center" generated an exception error and the connection did not work. When Cassandra is configured with a local data center, the balancing policy is based on the assumption that being local means it's the fastest. Other data centers were used only if the designated local one failed. To support this use case of spreading the balancing between all data centers, the DSS "loadBalancingPolicy" has been added to configure the balancing policy for the Cassandra database data set. Note that using remote data centers or multiple data centers will make request handling slower than only relying on the local one. | Decision Management |
| INC-B22142 | 878572 | Removed reference to deprecated WhenTabListener | Opening/saving a "when" rule in Revision Management generated the error "DebugInfoForRuleNotFound". Investigation showed this was due to RevisionRuleFormLayout and pyRMRuleFormLayoutDE referencing the the deprecated and removed section pzWhenTabListener in the RuleFormLayout. This issue has been resolved by removing the stale references. | Decision Management |
| INC-B22734 | 881671 | New version of a case will be detected on the dataflow canvas | After setting a dataflow to Output data to a specific case type and locking the ruleset, creating a new open one and then modifying the selected case and saving it resulted in the selected case type being removed from dropdown in the UI. This was caused by the dataflow shape holding the handle of the flow rule. Locking a ruleset and then editing the case in the Case Wizard created a new version of the flow rule in the higher ruleset version which the system perceived as a different rule instance with a different handle. The dropdown in UI is populated with only the latest version of each case, so the property was set to a value that was not available on the dropdown because the handle of the old rule instance was selected and the dropdown only contained the handle of the newer version. This resulted in it showing as empty in the UI. To correct this, a preloading activity has been added to the shape configuration section which will detect if a new version of the case has been created and update the handle if necessary. | Decision Management |
| INC-B23097 INC-B40284 |
881568 892523 |
Improvements in TakeExecMonSnapshot execution | The dataflow pzTakeExecMonSnapshot was causing node termination during the snapshot process of symbolic predictors in environments with 130k+ unique symbols. To resolve this, the distribution table will store the top 200 symbols for each symbolic predictor, and count any symbols beyond 200 as 'others'. The efficiency if the merge process has also been optimized by updating the handling of symbolic predictor aggregation. | Decision Management |
| INC-B23275 | 886175 | Logging added for diagnosing operator "unable to authenticate" error | Diagnostic logging has been added to capture data flow run ID to aid in diagnosing issues where a data flow run reports that an operator is incompatible while it executes the DetectPartitionChange data flow pulse task consistently. | Decision Management |
| INC-B24605 INC-B30274 |
876277 883115 |
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-B25391 | 876570 | 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-B26125 | 885263 | Updated chat intent model handling for missing language | During a live chat, sending an emoji from the CSR to the user resulted in a null pointer exception being printed in the logs and an alert triggered in the PDC. The issue occurred when intent model was selected in text analyzer, and was caused by the intent cache loader returning a non-null object with model bytes as null due to not being able to parse the language. This has been resolved by modifying the intent cache loader to return null when language is not present. | Decision Management |
| INC-B26433 INC-B36418 |
877085 889391 |
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-B27294 | 881284 | Extra logging added for VBDDataPartitionLoadTask | To assist with debugging, the logging for VBDDataPartitionLoadTask failures has been expanded to include the block ID of the problematic block along with all of the block summaries that are available. | Decision Management |
| INC-B27326 | 878684 | 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-B29173 | 882509 | Corrected custom date-time format handling for Pulse CreateDatetime | The pxCreateDatetime in the Pulse feed was displaying the month value in place of the minute value. This was traced to the pxCreateDateTime in pyFeedSubtitle having "custom date-time format" set to 'MMM dd, yyyy h:MM a'. As the minute place has the format in upper case "MM", this caused it to use the month value. To correct this, the "custom date-time format" has been updated to 'MMM dd, yyyy h:mm a' to display minutes correctly. | Decision Management |
| INC-B29637 INC-B29154 INC-B29045 |
880660 881775 881779 |
Improvements to Kafka Producer Metrics on Cloud | Kafka producer metrics have been improved, producer latency metrics have been introduced, and the Kafka client version for KAAS clusters has been updated. | Decision Management |
| INC-B30540 | 885733 | Questionnaire views correctly handled by localization wizard | When using a questionnaire case-type with one question page and one question with rules saved in the ruleset version included in the FomsSales application, the Excel sheet produced by the Localization wizard did not contain any field keys related to those question pages and question rules. This has been resolved by modifying the getQuestionnaireMetaData parameters for view meta-data generation and adding steps to publish localization for the question page views. | Decision Management |
| INC-B30596 | 882886 | Corrected memory issue with Summary Browse operation | After update, opening the Interaction History summaries in the Customer Decision Hub caused an out of memory error. This was traced to the implementation of persistence layers for the summary dataset which resulted in the browse operation loading all records into memory at once, and has been corrected. | Decision Management |
| INC-B31624 INC-B31930 |
881540 887822 |
AssignPartitionsTask refactored to improve rebalancing | Large environments with 100+ real-time runs were taking an excessive amount of time to reassign partitions when scaling up or executing other topology changes. To improve performance, the save task has been refactored to batch value handling in the key value store to improve performance for the AssignsPartitionsTask activity, use batch inserts for assignment acceptance, and batch-read and execute streamable assignments and tasks. | Decision Management |
| INC-B31735 | 882989 | DSS added to toggle Interaction History backfill | The DSS "cep/aggregation_service/backfill_enabled" has been introduced to control enabling or disabling the backfill run. By default the backfill processing is enabled. | Decision Management |
| INC-B31818 | 889379 | Addressed ArrayIndexOutOfBoundsException for API mapped to GOS | Invoking an API which was mapped to a globally optimized strategy (GOS) resulted in an ArrayIndexOutOfBoundsException error. Triggering the GetDecision API which is mapped to Trigger NBA strategy worked as expected. To address this, the DecisionTable serialization process has been modified in the GOS mode and more detailed log messages will be provided in case a similar issue occurs. | Decision Management |
| INC-B33286 INC-B36057 INC-B42760 |
886059 891466 894397 |
Updated GOS database handling for Postgres and Oracle | The error "java.lang.IllegalArgumentException: A null or empty handle has been specified in the database 'open by handle' method" was generated when flushing the aggregated strategy execution profiles to the database. This has been resolved by replacing the hardcoded pzinskey column property name with the property name variable so it is consistent regardless of database type, and an alias has been added for the selected column so that the case of the key and returned column name match. | Decision Management |
| INC-B33517 INC-B35763 |
885498 885861 |
User ID and updated message added to queue processor diagnostics | A queue processor and its associated dataflow were stopping unexpectedly with the error "context.PRQueueException: Enqueue to queue processor Process_SPLC failed : Unable to find the queue processor instance in memory". It is normally difficult to determine the origin of the stop runs task; with this update, user ID information will be added to stop/start/restart/update/reprocess run task life cycle events and it will be possible to log trace the stacktrace. The message generated will also be differentiated when the stop action is performed by the data flow run config updater. | Decision Management |
| INC-B33634 | 885343 | Check added for AI decision connector in CaseType wizard | After enabling the "Create data model using spreadsheet" option and uploading an Excel sheet with properties to be created, the wizard parsed the data and displayed it on the Wizard UI correctly, but clicking "Create" only created the CaseType along with AI suggested fields and the uploaded fields from Excel were not created. This was traced to the preconditions of the D_pzNewCaseTypeDetails.pyCaseFlow=="AI" function of the pzCreateDataModel activity being always evaluated as true, causing the activity execution to jump ahead. To resolve this, a check has been added for the AI decision "True" connector. | Decision Management |
| INC-B34133 INC-B28701 INC-B38911 INC-B43969 |
886030 879966 889416 894282 |
Resolved DDS dataflow deadlock | A dataflow deadlock was seen when shutting down DDS. Issues were also seen where one pod was not running the Decision Funnel Simulation dataflow as expected. This was traced to the ‘DSM init service: DDS.Default’ thread holding the lock, preventing the DDSClient class initialization from completing. This has been resolved by preventing the DDS service from initializing during the DDS Client classes initialization. | Decision Management |
| INC-B34199 | 885072 | Updated load handling for data partitions | Attempting to browse / query / clear Visual Business Director (VBD) data sets after loading a partition without data blocks was failing with the error "IllegalStateException:Failed to load data for partition". Further access attempts failed as the partition was regarded as being still loading. This has been resolved with an update which will ensure partition task completion on load, and a partition with no data will also be removed from the Collection Container's partitions map. | Decision Management |
| INC-B34437 | 893189 | DSS added to control conversion of empty values during handling | After update, an empty value that was created in the clipboard page if an empty value existed in the provided CSV file was instead being converted to 0 rather than remaining as empty. This was traced to the JSON serialization which can write empty values as empty string by default. To control this behavior, the DSS dsm/serialization/disableConvertingEmptyValuesToDefaults has been added with owner ruleset Pega-DecisionEngine. The default value is set to true | Decision Management |
| INC-B34437 | 886171 | File data set now distinguishes between empty values and values not present in files | When importing data to a customer table where each import partially updated the customer record, attempting to update and remove a value by setting it to null was not working as expected. In this scenario, the update being imported contained an empty value for that column. However, the file data set did not distinguish between empty values and values not present in files, leading to the value not being correctly updated to remove the information already stored. To resolve this, the file data set will now set an empty value in the clipboard page if an empty value exists in the provided CSV file. If there is no column mapped to a property, that property value will still not be set. | Decision Management |
| INC-B36076 INC-B41044 |
889421 891854 |
Check added to purgedecisondata to skip unrelated files in the repository | Many clipboard.InvalidValueException error messages were being generated indicating "T GMT is not a valid date/time value". The reported error is originated from pzpurgedecisondata activity, and was traced to a file titled as ".directory" in the Customer Decision Hub (CDH) repository which could not be parsed. This has been resolved by adding a 'when' condition to the date check which will skip metadata and folders starting with ".". | Decision Management |
| INC-B37106 | 889986 | Removed 10k records limit in GetListOfValidOperators and GetQuestionList | The Operators and Questions list was not displaying if there were more than 10k records. This has been resolved by updating the GetListOfValidOperators and GetQuestionList report definitions to change the value of the maximum number of rows to retrieve field to 0 in the Data Access tab. | Decision Management |
| INC-B37892 | 889467 | Tokenizing handling added for entities with quote marks | Text Analyzer was not returning the expected results for keyword based entity after update. This was traced to entities not being detected due to a tokenization issue if the string had quotation marks. This has been corrected by cleaning up the text before passing it to the tokenzier. | Decision Management |
| INC-B38375 | 889853 | GetNextWork-related activities for Revision Management moved from Work- class to RevisionManagement-Work class | Intermittent issues with opening and populating items using "Get Next Work" were seen when using the Client Lifecycle Management (CLM) application. This was traced to locally added access Rulesets causing the GetNextWork activity to be overridden in the Work- class of the Pega-DecisionManager Ruleset when Revision Management was not being used. To resolve this, these GetNextWork-related activities have been moved from the Work- class to the RevisionManagement-Work class as this activity in Pega-DecisionManager ruleset is only needed for Revision Management-specific scenario. The Work Pool of Revision Management access groups has been updated to RevisionManagement-Work so the GetNextWork functionality works as before for Revision Management users. When not using Revision Management, the GetNextWork activity will be picked up from the Pega-ProcessEngine Ruleset. | Decision Management |
| INC-B39314 INC-B42281 |
894768 896038 |
Avro null logging level decreased | Publishing a message to a topic was generating a large number of alerts in the tracer, all reading "AvroSerdeException: Unsupported data type! NULL". The message was successfully posted despite the error. This exception is only thrown when property with a value is used with an optional field defined with "null", which may occur when those properties aren't used during serialization in other schema. As this excessive WARN logging could cause the disk to fill up and impact the system, the logging level of the messages has been lowered to DEBUG. | Decision Management |
| INC-B39672 | 893373 | Corrected event store error in campaign run | After upgrade, running a campaign was generating the error "EventStoreException: Exception in writing event store record". This has been resolved by updating the event store keyspace handling. | Decision Management |
| INC-B40283 | 890315 | Corrected comparator used in CPD validation | During the platform profile validation for Customer Profile Designer (CPD), the associated data sorted failed with the error "java.lang.IllegalArgumentException: Comparison method violates its general contract!", which then caused the whole profile validation to fail. This has been resolved by correcting the comparator used in the platform profile validation. | Decision Management |
| INC-B40512 | 892367 | Improved multithreading synchronization for database tables | When trying to read more than 25K records from a table with BLOB content, the dataset was reading duplicate records and causing the data flow to process more records than present in source table. This occurred when the destination component was an activity in the data flow and took more than one second per item to process the record and which was combined with many small database partitions which caused multiple threads to be created. To avoid reading duplicate records, an update has been made to database multithreading synchronization. | Decision Management |
| INC-B41055 | 894894 | SSAFactory preconditions updated | Following work to make the DecisionTable more consistent, additional updates have been made to enhance the information in the SSAFactory preconditions. | Decision Management |
| INC-B41277 | 894444 | Meta files correctly created during hive migration | After migration to hive structure (using Embed-DataSet-File-Repository-Replay.pyRunMigrationToHiveStructure), folders did not contain the expected .directory/, .last-date, and .last-key files, and additional last-date-[number of partition] files were seen. This has been resolved. | Decision Management |
| INC-B42406 | 893551 | Improved performance for strategy execution | Strategy execution during inbound container calls was taking more time due to higher CPU utilization during ADM model execution. Investigation showed this was related to the number of properties on the Customer Page where Adaptive Models were executed, and was caused by the snapshot process for the predictor data using the hash of that page. This has been resolved by removing StaticPredictorDataHolder use of IdentityHashMap on source pages. | Decision Management |
Low-Code Application Development
24.1.2 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A27961 | 848508 | StageHistory updated when stage is restarted | After implementing an email listener which consumes a rejection response and processes it to resume flow action on a case, attempting to restart the stage with a local action caused a new pxStageHistory entry to be added instead of updating the existing entry. This was a missed use case, and has been resolved with a modification that will update the stage history record instead of creating a new stage history record when the same stage is restarted. | Low-Code App Development |
| INC-B10692 | 893501 | UIKit version updated in Usage Validation Utility (UVU) | Applications built on CustomerService 8 in Pega Infinity '23 or '24 were generating guardrail errors. This was caused by a difference in the UIKit versions: the Usage Validation Utility (UVU) component used in Pega Platform was built on UIKit 13.01 whereas PegaCRMBase 8 is built on UIKit 15.01. This has been resolved by upgrading the UIKit for PegaUVU to 15.01, and the pyInstanceList has been modified to add more columns. | Low-Code App Development |
| INC-B16799 | 877466 | 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-B19196 | 880162 | Blank value handling updated for export to Excel | Generating an Excel file using pxGenerateExcelFile activity where one column needs to be set blank led to random static values being added in the generated Excel file. This has been resolved by updating the GenerateExcel file to handle empty properties or properties with blank values. | Low-Code App Development |
| INC-B22726 | 880055 | Cache-Control updated | A cache-control: no-store response header for "application/json" has been added for Constellation DX API endpoints. | Low-Code App Development |
| INC-B23721 | 878560 | 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-B24335 | 881708 | Case ID not shown in Recent section when case is not created | When case creation was restricted by flow privileges, a non-privileged user attempting to create a case received the error "Unable to authorize flow execution RULE-OBJ-FLOW XXORG-DOC-WORK CREATEFORM_DEFAULT" on the screen, but the case ID was shown in the Recents section. Clicking on that case ID resulted in the error "Empty Work Item Handle". This has been corrected so that in this scenario the case is not shown in Recents. | Low-Code App Development |
| INC-B25455 | 875212 | 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-B26277 | 877124 | Generated rule assembly will be discarded if exception encountered | If the connection was lost to an external database during rules assembly, the cache would become corrupted. After the connection was reestablished, the database cache updated properly but the node memory cache retained the corrupted class. This has been resolved with an update which will discard the generated assembly completely if a database exception is generated during assembly, and the exception will be logged. | Low-Code App Development |
| INC-B27754 | 885931 | Warning message added for changing type of property from Casetype | When changing the property type in Data model tab, all of the instances associated with the class are deleted. A warning message for this has been added with the text "The class {3} ({4}) and/or its descendant classes have existing instances that would be impacted by changing the type of the field {1} ({2}). These instances will be deleted on submit if the type is changed." | Low-Code App Development |
| INC-B29056 | 884719 | Screenflow name handling updated for multiflow navigation | When using a flow with multiple screenflows, clicking on the back button in the case screen to go back to previous screens in another screenflow caused the screenflow name to disappear. This has been resolved by updating the flow name with the subflow name when navigating back to the subflow from the main flow. | Low-Code App Development |
| INC-B30719 | 894436 | URI updated for Dev Studio system information page | A blank popup was displayed when attempting to access the system information page in Dev Studio. This occurred on a multi-node system with a load balancer with no direction connection allowed to the nodes, and was caused by the XSL file URL using pxReqHomeURI for the node instead of a relative URL. This has been resolved by updating the home URI to use .pxReqURI. | Low-Code App Development |
| INC-B31358 | 885721 | Job scheduler automation added for Usage Insights reports | The Usage Insight job scheduler has been added to the Usage Validation Utility (UVU) to automate running regularly scheduled reports using the System Runtime Context. For more information, see the documentation for Usage Insights. | Low-Code App Development |
| INC-B340 | 849396 | 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-B36301 | 894490 | Resolved Case Usage agent disabled | The Push Resolved Case Usage Data AES Remote agent (agent activity - PushCaseEventDetails) was throwing numerous exceptions and alerts in the logs due to connection timeouts. This is a resource intensive query which slowed down other SQL executions and was recommended to be deprecated due to performance impact. With this update, Resolved Case Usage agent has been disabled in PegaAESRemote. | Low-Code App Development |
| INC-B43438 | 895592 | Improved server response security | Security has been updated for the response from the server when an update is made to a user object. | Low-Code App Development |
Mobile
24.1.2 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A23427 | 849456 | 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. | Mobile |
| INC-B11890 | 869987 | 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-B12602 | 879246 | 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-B18304 | 875935 | Modified dirty state handling for Datetime UI control drop-down list | When a datetime control in display mode was used on mobile device, navigating to a drop down and then navigating away without making any changes resulted in a dirty state popup. The issue was visible only in the Mobile web browser in the Mobile application and only for the Mobile native control property of type TimeOfDay; using the Pega control for TimeOfDay did not display this behavior. To address this, an update has been made to only add the data-initialValue attribute when type is "hidden". | Mobile |
| INC-B20796 | 879405 | Dropdowns corrected for Android tablet in Desktop view | Dropdown rendered correctly on mobile and on a tablet browser, but did not display the correct results on an Android tablet using Desktop view.This has been resolved by adjusting the event loop to better handle the execution necessary. | Mobile |
| INC-B23982 | 884740 | Corrected AM localization for Taiwan | In the offline mobile app used on Taiwanese language devices, inputting AM 4:40 displayed as 凌晨 04:30 until save, when it was correctly displayed as 上午 04:30. This has been corrected by updating pzpega_ui_formatDateTime to add a specific condition for the locale "zh_TW". | Mobile |
| INC-B24829 | 885258 | Added handling for iOS autocomplete called from local action | When using an iOS device, an autocomplete control triggered within a local action froze when sourced with a data page (structure: list) which was itself sourced with a data transform which called another data page that sourced itself with a REST connector. This has been resolved with a check for a delay in opening the result popup container. | Mobile |
| INC-B33256 | 890378 | Setfocus updated for iOS | Setfocus to target property was not setting the focus correctly on text input fields for iOS. This was traced to iOS devices not supporting setTimeout, and has been resolved by adding the condition to explicitly execute for iOS. | Mobile |
| INC-B38030 | 889446 | Phone control supports dirty form handling | The dirty check handler has been added for the Phone control. | Mobile |
Project Delivery
24.1.2 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B17244 | 867179 | Documentation updated for updating an expired identity provider certificate | The documentation for updating an expired identity provider certificate in a SAML Authentication Service has been updated to clarify that if the XML contains both old and new certificates, it may be necessary to manually select the correct certificate from the Certificate Alias dropdown. | Project Delivery |
| INC-B17331 INC-B15644 INC-B15439 INC-B14808 INC-B14305 INC-B13369 |
868734 | Documentation Improvements for BIX Extract Design | The documentation for dividing Business Intelligence Extract (BIX) operations into smaller parts to speed up the extraction process has been updated to clarify the process and necessary steps. | Project Delivery |
| INC-B19849 | 877361 | 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-B20179 | 884025 | Offline mobile app documentation updated for offline mode | The documentation for local actions offline mode has been updated to remove references to hiding the default buttons of a flow action. This is not a supported configuration for the offline mobile app. | Project Delivery |
| INC-B25813 | 881785 | Custom cipher creation documentation updated | The documentation for creating a custom cipher has been updated to clarify that compiling the Java will require the prprivate-exec.jar, prpublic.jar, and prenginext.jar files. |
Project Delivery |
| INC-B28578 | 892268 | Application URL alias documentation updated | The documentation for adding an application URL alias ha been updated to highlight that when an application is first created, the application URL alias defaults to the name of the application. After the URL alias is changed, it is still possible to log in to an application using the default app alias that contains the application name. | Project Delivery |
| INC-B29347 | 884366 | Documentation updated for customization of mobile login | The documentation for configuring the browser requestor has been updated to note that customizing mobile login screens requires updating the OAuth 2.0 service package to use the unauthenticated Access Group. | Project Delivery |
| INC-B32153 | 889230 | Circumstanced rule skimming documentation updated | The documentation for creating a rule specialized by circumstance and for rule skimming for higher ruleset versions has been updated to clarify that the existing "Base Rule" check box status is ignored when skimming and the rules are moved from lower to higher ruleset versions regardless of the "Base Rule" setting and circumstancing. When skimming circumstanced rules, the "Base Rule" check box in the rule availability dialog box must be explicitly selected for a newly skimmed rule to be recognized as a base rule during rule resolution. | Project Delivery |
| INC-B32984 | 882660 | Documentation updated for indexing class data | The "Indexing class data" documentation has been updated to clarify that a manual re-index of the search indexes should be performed from the Search landing page after a database restoration. | Project Delivery |
Reporting
24.1.2 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B1263 | 851261 | Corrected IAM authentication handling for Amazon OpenSearch connection | When running the helm chart to deploy the Search and Reporting Service (SRS) by connecting to Amazon OpenSearch (running ES 7.10) with awsIAM configured as the authentication method, the SRS pod failed to start and generated the error "RuntimeException: Unable to load credentials from any of the providers in the chain." This was an issue with the provided helm charts, and has been resolved with the release of search-n-reporting-service-aws:1.32.2 . | Reporting |
| INC-B1412 | 851155 | Row focus maintained on close of report | Opening the last report from a list in an optimized table and then closing the report caused focus to shift to the first row of the list. This has been resolved by adding set focus in the pzRBShortcutsGrid7 and pyRecentReportsWidgetRow sections. | Reporting |
| INC-B16714 | 875592 | 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-B1827 | 886314 | Added null property handling for AccessPolicyCondition | After update and migrating to the SRS service, case search was not working for the end user portal. Investigation showed that if the embedded properties in the AccessPolicyCondition were verified for IS_Null condition, a java.lang.IndexOutOfBoundsException error was generated. Handling has been added for this scenario. | Reporting |
| INC-B19661 | 875694 | Updated date handling for Export to Excel | Export to Excel was using the value 1/1/1970 even when a value was present and displayed correctly in the UI. Investigation showed the property was being set via a declare expression which was taking the value from pxCreateDateTime. To resolve this, declare expression has been turned off in pzDataExplorerExportToExcel. | Reporting |
| INC-B20878 INC-B7434 |
883093 885954 |
Updated SASIncrementalIndexer management | After enabling the Search and Reporting Service on Pega Cloud, an intermittent InvalidParameterException was generated during batch case creation using a background job scheduler process, some RuleNotFoundExceptions were generated during case processing with ResumeFlow by queue processor, and attempting to map data to the .ResponsePage property would occasionally result in an "unsupported mode: Unknown" error when performing a REST call to another application. This has been resolved with the addition of Thread Modification Helpers to manage incremental flow efficiently for the thread APIs. | Reporting |
| INC-B22862 | 874549 | 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-B22966 | 887330 | Added Chart control handling for empty parameter | When an empty parameter was used in a Chart, the property name was displayed instead of a null value. This has been resolved by updating the conditions for passing the report parameters in the Chart controls. | Reporting |
| INC-B23827 INC-B28446 |
877817 878838 |
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-B23876 | 880899 | Corrected missing privilege for scheduled reports | After upgrade, a scheduled report failed with the error "InsufficientPrivileges:RuleExecutionDenied RULE-OBJ-ACTIVITY SYSTEM-QUEUE-SCHEDULEDTASK PZSCHEDULEDTASKPROCESSOR". This was due to a missing privilege name and has been resolved. | Reporting |
| INC-B25029 | 880060 | Corrected DisplayReport filter alignment | After configuring a header at the top of the portal in Theme-Cosmos, accessing any report using the DisplayReport harness and clicking on the Filter icon resulted in a spacing issue where the height of the header was being added to the top attribute. This has been resolved by updating the CSS in pyReportEditorStyling. | Reporting |
| INC-B26442 | 884864 | Documentation updated for BIX Get All Properties option | The documentation for enabling the BIX ruleset has been updated to clarify expected results related to using the BIX "Get All Properties" checkbox. When using this option with an extraction rule defined on a class that contains a blob, an extraction rule defined on a class with XML output type BIX will extract all the properties that are present in the specified class's pzpvstream. However, if the extraction rule is defined on a blobless class, BIX will only add the key columns and exposed columns like committedDatetime and pxObjClass. | Reporting |
| INC-B31102 INC-B40044 |
884745 892733 |
Corrected duplicated extract folder structure | After update, the folder structure of BIX extracts was modified and the folder with the extract was moved inside another folder. This was an unintended side effect of the change to an alternative third party encryption library, and has been resolved with an update to remove the duplicated folder structure during the zip file extraction. | Reporting |
| INC-B31654 | 882453 | Copy Report handling updated | After update, attempting to copy reports to a new or existing category was not working. Copying to the same category is not supported, and an error message indicating "Report already exists in category" has been added to reflect the limitation. Copying to a different category has been corrected by updating pzcopyshortcutpostactivity7. | Reporting |
| INC-B32603 | 885184 | Corrected report grid column header alignment | The report grid column header was not correctly aligned with the top. This has been resolved by updating the CSS in the pyReportEditorStyling file. | Reporting |
| INC-B34693 | 887738 | Scheduled insight export to Excel matches manual insight export | When an insight was scheduled, the generated Excel was limited to 5000 rows. If the insight was run manually and exported to Excel, all rows were exported. This has been resolved by updating the 'when' rule from using pyServiceActivity=="pzDataExplorerExport to instead use Param.UseRuntimeDefinition=="true". | Reporting |
| INC-B35340 | 888912 | Report Filtering working for drag/drop column reordering | Report filtering was not working as expected in the Dashboard if a column from the table was dragged and dropped. This has been resolved by unchecking the "Allow invocation from browser" checkbox in the pzDropNewFilterFromColumn activity. | Reporting |
| INC-B36538 | 887752 | Accessibility improved for viewing filtered reports | When viewing filtered reports, keyboard users were not able to focus on the filtered labels, and the CSS for focus on the Select button was not correct. This has been resolved by updating the styles to get the correct focus effects when traversing through tabs. | Reporting |
| INC-B36941 | 890292 | Cloud3 documentation updated for usage of a Customer SFTP/Custom path | The documentation for BIX extractions has been updated to clarify the use of SFTP-based methods to obtain extract files in Pega Cloud. This comprehensive information is available in the documentation "Overview of BIX extractions in Pega Cloud environments". | Reporting |
| INC-B38322 | 894038 | Scheduled report field values correctly translated in the UI Validation | When working in the case manager portal, scheduling a report and entering an old date or old time for the task scheduling produced an error message consisting of the field value name instead of displaying the value. Investigation showed the field value pzEnterAValueBeyondTheCurrentDateAndTime was created in the class Pega-ScheduledTask instead of the expected Embed-ScheduledTask-Scheduling. This has been corrected. | Reporting |
| INC-B38690 | 892127 | Added category report sorting for CMReportBrowser7 | The sorting of reports and of categories AtoZ or ZtoA worked as expected when using the default browser pyReportBrowser, but sorting was not working when using a harness with pyCMReportBrowser7. This has been corrected by adding a condition in the pzReportListSort which sets the legacyRB value as true for the pyCMReportBrowser7 harness. | Reporting |
| INC-B39471 | 889707 | Report editor sort highlighting corrected | When using a menu item that called a report definition rule attempting to sort on the column resulted in the highlighting being displayed as two separate boxes instead of one. This was due to newly introduced styling in the report viewer, and has been resolved by correcting the pyreporteditorstyling CSS file. | Reporting |
| INC-B39700 | 890298 | Report unsubscribe UI handling updated | After a report was scheduled, clicking on 'unsubscribe' caused checkboxes to lose labels and the radio button at the bottom was not visible. This was caused by previous work to update the controls, which resulted in small discrepancy in the UI display. This has been corrected with updates to pytaskoutputprocessing. | Reporting |
| INC-B40231 | 891837 | Report viewer opens in new tab using UIKit | The new Navigation rule pyRBItemActionsUI has been created in the UIKit to support the function pega.desktop.infinity.openReportInNewTab . | Reporting |
| INC-B40272 | 892410 | Corrected heading display in Report Editor | The header pop up was appearing as distorted in the Report Editor screen. This has been corrected with additional stylings in pyReportEditorStyling.css . | Reporting |
| INC-B41112 | 892903 | Corrected focus issue on Category type | When using the dropdown within the "Create new Category" modal, focus shifted unexpectedly to previous field after selecting an option from the Category type drop-down list. This has been resolved by updating pznewcategory7 so that when an option is selected from the Category type drop-down list, focus remains on the combo box until Tab is used. | Reporting |
| INC-B6183 | 856595 | 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 |
Security
24.1.2 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A28575 | 873763 | 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-A29650 | 848169 | Pega MFA Screen session expiry redirect updated | At session expiry, the Pega multi-factor authentication screen redirected to a screen showing all authentication services instead of the default authentication service. This involved an uncommon scenario where multi-factor authentication (MFA) was enabled and the default authentication service was mapped to the app, and has been resolved by redirecting to the default authentication service associated with the application during a node crash scenario or when the application has Interactive login configuration selected. | Security |
| INC-B20617 | 876579 | 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-B20727 | 872670 | Check added for incorrectly formed CORS endpoints | After constructing a new REST API and adding an endpoint to a cross-origin resource sharing (CORS) policy to restrict access for the endpoint to certain domains, the restriction was not working as expected and allowed all domains. Investigation showed the endpoint as supplied in the CORS policy dropdown was incorrect: the endpoint should begin with "api" but did not. This has been resolved by modifying the logic to append /api for REST APIs with a service version. | Security |
| INC-B20904 | 872587 | 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-B21044 | 884161 | Additional logging added for security issues | To aid in diagnosing SEC0017 errors, additional logging has been added identify the underlying activities or streams. | Security |
| INC-B23015 | 874338 | Updated OperatorID security | Security has been updated for the OperatorID clipboard page. | Security |
| INC-B23163 | 877305 | 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. | Security |
| INC-B23403 | 875642 | Sanitizing filters added for query parameters | Cross site scripting filters have been added to the URL query parameter input. | Security |
| INC-B27152 INC-B19337 INC-B34964 |
878836 877615 887453 |
Field values security updated | Cross site scripting filters have been added on Field Value strings. | Security |
| INC-B2902 | 863209 | Websocket connection handling updated | Security handling has been updated for websocket connections. | Security |
| INC-B29444 | 887693 | Updated redirect for post access-group timeout | Using SSO OIDC for access group timeouts was working for some groups, but for others the portal was intermittently freezing after timeout. To address this, the false flag has been updated to aTimedOut so there will be a redirect back to the logoff screen once the user clicks on the screen post access-group timeout. | Security |
| INC-B31047 | 883916 | Updated Constellation certificate | The PegaAATTS keystore for Constellation has been updated with a new certificate in advance of expiration. | Security |
| INC-B32829 | 887215 | Additional handling for custom browser CSP | Additional work has been done on the handling for Content Security Policy headers to ensure only one CSP header is present at any given time in both traditional and Constellation portals. | Security |
| INC-B33773 | 885333 | PRConfig available for Java check | A PRConfig with setting security/blockJavaInjection has been made available. If present, this configuration will be honored over the existing DASS security/enableJavaInjectionMitigation. Additional logic has also been added to trigger a security alert when the checkForJavaCodeInjection method is called and Java Injection is allowed in the system. | Security |
| INC-B33917 | 883935 | DSS added to refresh the access token | Some downstream calls were failing with a "Token expired" error during PING token validation. To resolve this, the DSS "security/token/refreshEarlyBefore" has been added. This is used to refresh the access token early to avoid expiry by the time it reaches the server, and can be set to add 0-60 seconds. | Security |
| INC-B35024 | 885802 | OAuth2DataProviderImpl logging added | Additional logging has been added in OAuth2DataProviderImpl to assist with diagnosing login issues. | Security |
| INC-B35148 | 894512 | Server path not disclosed in upload error message | The error message in the UI generated by an exception during file upload will not include the server path. | Security |
| INC-B36579 | 894549 | Updated search panel security | Cross-site scripting protections have been added to the search panel. | Security |
| INC-B38494 | 895511 | AddCalendar updated with DSS to use operator timezone | By default, the date/time calculations of the addCalendar function are dependent on the server timezone. This may cause validations to fail across different implementation applications if the Cloud server is in a different timezone than the operator. To resolve this, a DSS is available to set the function to calculate date/time based on the operator timezone. Owning Ruleset: Pega-Engine Setting: datetime/addcalendar/version Value: 2 |
Security |
| INC-B39506 | 891410 | Switch application popup correctly closed | After creating two different authentication services for two applications using SSO, logging into one and clicking on the second application from the switch application option launched the second application in a new tab but the popup to login remained active in the first window. This has been resolved by adding an event close in the pzSwitchAppDispayLoginScreen section. | Security |
| INC-B40295 | 894419 | Cache-control sent in mobile app response headers | The pzGetUserinfo activity has been modified to send the "Cache-Control" header as a response for the oauthclients/v1/userinfo/json REST call. | Security |
| INC-B43931 | 895185 | Mobility header supports disabled caching | An update has been made to disable caching in headers for pzGetMobileLogsConfiguration. | Security |
| INC-B7191 | 859926 | 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-B9267 | 874630 | 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 |
| INC-B948 | 881836 | Value List supported for headers in token profile | When using a JWT profile as authentication schema within Authentication Profile, running the REST connector with authentication profile generated the error "Access token endpoint invocation failed". To address this, support has been added for a Value List for headers in token profile. | Security |
System Administration
24.1.2 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-B12369 | 867638 | Corrected localization formatting issue | After unpacking and translating and then importing the JSON package for localization processing, it was observed that some areas did not take effect. This has been resolved by updating the document-generation-lib version to correct JSON formatting issues. | System Administration |
| INC-B13493 | 868011 | 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-B17485 | 871617 | 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-B24085 | 880241 | Performance improvement for BuiltOnAppRoutesReportDefinition | In order to improve the performance of database responses for pzBuiltOnAppRoutesReportDefinition, the d_pzbuiltonapproutingtable scope has been modified to "node" to avoid the multiple report definition executions which internally make heavy database query calls. | System Administration |
| INC-B26274 | 879842 | Hazelcast updated | Hazelcast has been updated to version 5.4.1. | System Administration |
| INC-B28033 INC-B33340 |
884467 889204 |
QueueProcessor log category visible in Admin Studio | The BatchIndexProcessor queue processor was failing with an error while trying to calculate lag, and the log category was not visible in Admin Studio. This was traced to the log category not having the correct ID, and has been resolved. | System Administration |
| INC-B28716 | 894660 | Added logging for chat queue diagnostics | Extra diagnostic loggers have been added for subscribe and unsubscribe call to assist with diagnosing issues where the the global and queue-specific max number of conversations for chat operators is intermittently not being honored. | System Administration |
| INC-B30013 | 883932 | Handling updated for MessageContent exception logging | In order to ensure pzMessageContent does not include potentially sensitive information when a queue processor queue throws an exception, an update has been made to sanitize the XML and JSON before sending to the log. | System Administration |
| INC-B32037 INC-B36052 |
886186 887714 |
Corrected property handling in Rule Assembly | A large number of Rule Assembly alerts were being generated which were affecting performance and stability. Investigation showed the assembly was slow for stream rules on the first access to pods after startup, and this has been addressed by adding pzAssemblePreProcess to trigger section reassembly. | System Administration |
| INC-B33533 | 884546 | Settings added to assist in controlling Kafka writes and retries | Node unavailability during Kafka's log roll over process caused threads trying to write to Kafka to eventually pile up, impacting response times for API calls. In order to better handle Kafka writes and retries, two additional DSS settings have been added to function in a circuit breaker pattern. If the system is not able push the 100 consecutive messages to Kafka, then there will be a 5 second pause, and these values are configurable. SettingPurpose: queueprocessor/dataset/circuitBreaker/threshold/timeoutSecond default value: 5 (seconds) SettingPurpose: queueprocessor/dataset/circuitBreaker/threshold/failedMessages default value : 100 OwningRuleset: Pega-Engine |
System Administration |
| INC-B39157 | 891908 | Improved performance for semantic tab layout | Performance issues were seen when enabling semantic tab layout. This has been resolved by adding a safe check for pageName. | System Administration |
| INC-B41124 | 891450 | Diagnostic logging added for OpenMobileChannel | Additional logging has been made available for database exceptions at openMobileChannel in order to facilitate diagnosing intermittent issues with connecting to the synchronization service when processing an offline case or when attempting to log in. | System Administration |
| INC-B41777 | 893292 | FieldValue conclusion logging added | Diagnostic loggers have been added to assist with diagnosing issues related to loading FieldValue conclusions. | System Administration |
User Experience
24.1.2 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-226187 | 729456 | Corrected display row numbers in table layout | When the width of content was changed to Pixels(Fixed) from Fill(100%) in the table layout, the row numbers displayed by checking "Display row numbers" were not properly displayed. This has been resolved by correcting the padding for grid when using a fixed width in pixels. | User Experience |
| INC-A24088 | 843700 | Layout group menu icon visible after relocation | After changing the layout group menu icon position from right(default) to left, the menu icon was not shown on the section in Theme-Cosmos. This has been resolved by adding padding-left to the CSS so the icon has some room to be visible. | User Experience |
| INC-A27587 | 846349 | Updated harness focus for drag and drop in repeating dynamic layout | Work done to ensure the proper harness context when using drag and drop in a repeating dynamic layout has been updated to ensure the harness focus is set correctly. | User Experience |
| INC-A29934 | 855719 | Inline image documentation updated for external applications | The documentation for configuring a Rich Text Editor control has been updated to specify that using Base64 encoding is necessary when interacting with external applications to display the images inline to the text. For internal use, the image uploader remains the preferred option because of security and data storage capabilities. | User Experience |
| INC-B10108 INC-B28149 |
880167 893592 |
Updated parent thread handling for refresh | After creating an activity inside an appointment, attempting to open the activity after refresh generated an intermittent “A processing error has occurred” or "Failed to load harness" error. This was traced to the inclusion of the "Refresh Current Harness" action on tabs, which created a new state without passing the parent thread and clearing the previous state. It is unexpected for the previous state to be retained, and this has been resolved with an update to ensure the parent thread is passed correctly for clearing the state. | User Experience |
| INC-B10225 | 873839 | 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-B10511 | 894217 | Accessibility improved for table filter selection | When using a screen reader and NonVisual Desktop Access (NVDA), the checkbox and label were read separately upon selection of a table filter. This was traced to the table filter checkbox not being associated with the label, and has been corrected. | User Experience |
| INC-B11674 | 878304 | 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-B12432 | 868840 | 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-B12766 | 864596 | 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-B13177 | 877793 | Corrected locking for confirm harness | After submitting an assignment and routing the next assignment to Workbasket, refreshing the browser from the review screen caused a lock to unexpectedly be re-acquired on the work object. This was traced to the aceprimary_0 empty DOM not being removed in the confirm harness, and has been resolved with an update which will exclude acquiring a lock when it is a confirm harness. | User Experience |
| INC-B13558 | 867670 | 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-B13609 | 882591 | 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 structure from screen layout to "container - No header". | User Experience |
| INC-B13743 | 868371 | 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-B14528 | 875619 | 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 | 866544 | 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-B14600 | 874758 | 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. | User Experience |
| INC-B14617 | 866211 | 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 | 882412 | 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-B15294 INC-B10447 |
879809 866845 |
Corrected and improved accessibility for My Worklist | The following layout and accessibility issues have been corrected for My Worklist: In the user portal, the dashboard Menu option is included in the worklist when navigating from the default view to user defined views. The tab order header button to expand the list of options has been reordered to match the visual options and receive focus before the table toolbar buttons. The overlay has been given an explicit level 2 visible heading. | User Experience |
| INC-B16001 | 875109 | 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-B17863 INC-B27509 |
878485 877697 |
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-B18562 | 874035 | 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 | 873735 | 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-B18778 | 868929 | Localization updated to remove "[]" in email subject string | The newer Pega-Social field value pyAddUserMentionedPostEmailSubject has 2 parameters, which did not match the number of parameters in the Japanese Language pack field value(3 parameters). As a result, "[]" was unexpectedly shown in the mail subject. This has been corrected by setting the additional field value pyAddUserMentionedPostEmailSubject to 2 parameters as the localized field value. | User Experience |
| INC-B19809 | 874039 | 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 | 871394 | 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 | 871994 | 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-B21364 | 876028 | 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 | 874060 | 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-B22163 | 874830 | Local action dropdown updates on cancel assignment | In some scenarios, the visibility "when" condition configured for a local action or local optional process on a case did not update until the case was refreshed. This was traced to the available processes in the local action dropdown not being updated on cancel assignment, and has been resolved by adding an update to consider this response for updating data. | User Experience |
| INC-B22612 INC-B23379 |
874564 876499 |
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-B22618 INC-B24417 |
887543 880202 |
Chart Control Actions menu handling updated | After update, opening subsequent charts on a dashboard with multiple chart controls did not dismiss previously opened menus for other charts. This was traced to a blank referral attribute in the linking page window object related to the deprecated Adobe Flash player, and all references to this in the chart-related files have been removed. To resolve the related menu issue, the handling of the showReportRCMenu function in pzPega_chart_actionmenu has been updated to ensure the open menu is closed as expected when the next menu is selected. | User Experience |
| INC-B22665 | 877642 | 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 | 878193 | 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-B22714 | 877714 | Corrected AM/PM handling for localized values | When using the Taiwanese locale (zh_TW), the calendar was showing times as AM(上午) when it should have shown PM(下午). Investigation showed the toDate() function in the moment.js library was unable to identify the AM/PM with localized text and converted the hours into 12 hour format, such as a date time value of '2024/7/1 下午4:15:22' returned as "Mon Jul 01 2024 04:15:00" where the hour was calculated as "4" instead of "16". This has been corrected. | User Experience |
| INC-B22745 | 877863 | 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-B23294 | 881699 | Markup allowed for dynamic layout title field | Support has been added for markup language in the field value of a dynamic layout title. | User Experience |
| INC-B23529 INC-B27865 |
878556 883060 |
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 INC-B6922 |
873754 861345 |
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 | 877550 | 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-B23804 | 882062 | Corrected lost focus for submission button | Focus on the button was lost after submitting the modal dialog when using the Apple Safari or Mozilla Firefox browsers. The focus was not lost when using Google Chrome or Microsoft Edge. This was traced to a check in the pega_ui_modaldialog js file for function _processActionModalOnlineHandler which used an "if" condition for the reload which was applied only for Google Chrome. This check has been removed, as the button needs to be set as reload element for all of the browsers to bring the focus back after closing the modal. | User Experience |
| INC-B23853 | 882293 | Case notification close updated to handle both AJAX and non-AJAX containers | When using the Theme-Cosmos application, the pyCaseMainPageNotification section was not closing when clicking on the 'X' icon. The GO button needed to be clicked from the worklist in order to continue to complete the stages. This has been resolved by updating the action from refresh section to openworkbyhandle to support both AJAX container and non-AJAX container behavior. | User Experience |
| INC-B24013 | 877147 | CSS corrected for Case Information display | Grid column headers and data were distorted. This was traced to a word-break in the caseInformation section of the 'Case Information UI template', and has been resolved by updating the CSS. | User Experience |
| INC-B24327 | 880639 | Corrected repeating dynamic layout title appearing on buttons | When using a repeating dynamic layout with inner sections, the title of the repeating layout or containing dynamic layout was being added to the cancel and submit buttons. This was traced to the fieldset being used within the application, and has been resolved by adding role='presentation' in the fieldset tag of the webwb_pzpega_ui_template_form file. | User Experience |
| INC-B24571 | 876759 | Updated text accessibility in case utilities pane | The text below the task / attachment pyAttachmentFeedDescription section in the case utility panel was being skipped and not being read out by the screen reader. This was due to the role="tab" automatically switching NVDA from "browse mode" (where keyboard events are sent to NVDA) to "forms mode" (where keyboard events are sent to the application). This has been corrected so the text will be read. | User Experience |
| INC-B24642 | 877601 | 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 | 876295 | 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 INC-B9167 |
876426 865151 |
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 | 877969 | 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 | 875880 | 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-B25266 | 876124 | 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-B25268 | 884954 | Additional Text tab correctly displays localized custom data pages | Localized custom data pages and their properties were not appearing in the Additional Text tab when using Constellation. This was traced to the localization handling for the D_pyAvailableCaseStages activity, and has been corrected. | User Experience |
| INC-B25382 | 878689 | 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 | 876555 | 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-B25508 | 879562 | Focus in Rich Text Editor persists after refresh | After setting up a modal dialog containing both a textarea and a Rich Text Editor where the text area had an onChange event to trigger a section refresh, inputting text and clicking on the Rich Text Area triggered the refresh but the cursor shifted back to the textarea. This was caused by a loss of focus due to the Rich Text Editor click event not being captured like other controls, and has been resolved by ensuring that if the onchange event is triggered by clicking on the RichText Area, the focus will correctly go to the Rich Text Area. | User Experience |
| INC-B26158 | 876336 | 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-B26334 | 884148 | Updated handling for datetime dirty check | When datetime controls were used in a dropdown contained in an editable table, the dirty check popup appeared even when no changes were made. This has been resolved by updating the dirty validation check handling on the initial load. | User Experience |
| INC-B26646 | 881870 | Search filters cleared properly | In a multi-step form, if a record was selected and viewed and "Next" was clicked, using "Previous" to go back to the search screen for a new search resulted in the existing filters not being visible on the UI but those filters were applied to the new search. This was an issue with the stale values being stored, and has been resolved with an update to clear the messages from redux in the context passed in the payload as well as clearing the error messages for the workarea context. | User Experience |
| INC-B27071 | 881496 | Corrected filter popover context handling | When using Theme-Cosmos with a non-optimized grid, a console error was generated by clicking to open a filter popover and then clicking on the dashboard from the left navigation bar without closing the filter. Clicking on the filter icon again caused the loading icon to appear and the page became unresponsive. This has been resolved by setting the correct context while closing the filter popover. | User Experience |
| INC-B27090 | 881078 | Clear messages API context expanded | When the redux action "CLEAR_MESSAGES" was triggered with the context as "app/primary_1/workarea_1" from PCore.getMessageManager.clearMessages(), the error messages were cleared in the parent context "app/primary_1" but not "app/primary_1/workarea_1". This has been updated to clear the messages from workarea context as well. | User Experience |
| INC-B28040 | 884641 | Focus shifts to required control in non-optimized table | When a control was placed inside a non-optimized table column and set to required, focus did not go to the control that required a value when the form is submitted, but instead stayed on the submit button. This has been corrected. | User Experience |
| INC-B28123 | 879816 | Recent Work control updated for accessibility | To improve accessibility, the pyRecentWorkContent section has been updated with role type "Link". |
User Experience |
| INC-B28537 | 880231 | Submit handler updated for multistep form | Searching for a product in a dropdown and using the Enter button to submit the choice was causing the browser to refresh unexpectedly. This browser refresh behavior was also seen when creating a case and pressing the Enter key for the create modal. Investigation showed that the issue occurred when only one datareference dropdown was present, and was not seen when multiple controls were present in the view. To resolve this, a submit handler has been added for a multistep form containing only one datareference. | User Experience |
| INC-B28733 | 886970 | Corrected accessibility for calendar close button X icon | The NVDA screen reader was announcing the "X" special character as "times" in the calendar pop-up close window. This was caused by a missing title attribute for the close icon, and the CSS has been updated to correct this. | User Experience |
| INC-B29053 | 881176 | Fullname populated correctly for Constellation stakeholder | When using the Edit and Delete options for the Stakeholder widget in Constellation, the pyFullName property was not fully populated unless PyEmail was also included in the payload even if pyFirstname and pyLastName contained values. This has been resolved by updating the logic. | User Experience |
| INC-B29164 | 880314 | Corrected accessibility for tablist menu | When using a repeating dynamic layout, the left and right arrow appear as well as an expand icon to list all of the tabs if there are more tabs than screen space available. This used a anchor tag contained in a div with the correct attributes, however the anchor tag itself was missing attributes and had a tabIndex = -1 so it did not receive focus. This has been corrected by removing the anchor tag and replacing it with a span with aria-hidden so screen readers and scanners can correctly access the area. | User Experience |
| INC-B29708 | 884428 | Specific Date Range filter corrected for optimized table | After selecting the "A specific Date range" option in the popup filter dropdown for a date column in an optimized grid, the filter became blank once a date was selected from the calendar popup. This was an unintended side effect of work done to improve performance for filtering, and has been resolved by correcting the trigger of the onGridFilterClose function in the pzPega_ui_templatizedgrid js. | User Experience |
| INC-B29709 INC-B30961 INC-B29378 |
890269 886129 880217 |
Multi-select correctly displays all options in mobile view | Clicking the down arrow in the multi-select control did not display all of the results as expected when using an iPhone. This was an unintended side effect of work done to improve accessibility, and has been resolved by modifying the focus method and post-event actions. | User Experience |
| INC-B30098 | 891266 | WebEmbed first load improvement | The first load of the WebEmbed Channel was taking an excessive amount of time. This has been resolved by modifying the scope of the data page d_pzbuiltonapproutingtable from requestor to node level in order to improve performance. | User Experience |
| INC-B30156 | 894320 | Restored error message for attempting to preview restricted case | After update, the preview of an unauthorized case was not showing any message or preview panel and did not display an error. This was a missed use case for the blended co-existence UI, and has been resolved so the Restriction window opens with the expected message. | User Experience |
| INC-B30368 | 881847 | Updated date field control for Search and Select | Date field value handling has been updated to correctly clear the values from Search and Select when "Clear" is clicked, and to preserve other portions of the value when correcting mm or dd. | User Experience |
| INC-B30533 | 884363 | Corrected blank tooltip for channel header | When the Channel Header was selected as the channel name in Constellation, hovering over the application logo showed a blank tooltip. This has been corrected. | User Experience |
| INC-B30586 | 884343 | Updated save button with case-wide action condition | Flow actions with transient data that is not saved anywhere contained a save button when appearing in the action area for functions such as transfer assignment and change stage. In some cases clicking the save button caused the data to be lost. This was traced to the harness handling, and has been resolved by adding the !pzisCasewideaction condition to the save button so the button will not be available for case-wide actions such as edit details, change stage, etc. | User Experience |
| INC-B31175 | 886372 | Updated accessibility visibility handling for autocomplete carrot dropdown | After creating an Autocomplete and checking the "Display as combo box (field and button)" in presentation, the focus moved to the caret icon which did not contain any accessible text. To improve the accessible experience, pzpega_ui_template_autocomplete.js" has been updated to implement the aria-hidden="true" attribute for this icon. | User Experience |
| INC-B31288 | 882355 | Corrected extra white space in read-only controls | When using the standard read-only controls, additional whitespace was seen due to display:inherit CSS. The no-value span has been changed to display block to correct this. | User Experience |
| INC-B32127 | 884590 | Busy indicator displays during modal submit | After update, the busy indicator was not being displayed during the modal submit even if the interaction was waiting at the server side for too long. This has been corrected. | User Experience |
| INC-B32315 | 884174 | Improved accessibility for progress indicator | An aria-label has been added to the progress indicator control to describe what the purpose of the element is. | User Experience |
| INC-B32418 | 892243 | Updated SessionTimer X button click behavior | When the popup box was counting down the seconds remaining, clicking on the cross button to close the popup rather than clicking on the OK button caused the entire session to be terminated immediately instead of the expected behavior of the cross button behaving the same as the OK button. The pxSessionTimer function has been updated to resolve this. | User Experience |
| INC-B33012 | 887641 | Corrected error when changing App Studio theme color | After update, attempting to change the theme color in App Studio was failing with the error "pega.openUrlInModal.showModalDialog - error when calling callbackfunction: 'dataCtlJSON is not defined". This was an unintended side effect of work done related to showing a validation message on the UI, and has been resolved by adding a safe check for the data-ctl attribute. | User Experience |
| INC-B33065 | 890117 | Navigation Menu announced parent child expand/collapse | To improve accessibility, the necessary aria-label attributes have been added in the slideToNextLevel function in pzpega_control_menu to announce parent child expand/collapse in the navigation menu. | User Experience |
| INC-B33209 | 885843 | Corrected null event in 'group by' for optimized grid | After update, applying a multiple 'group by' on an optimized grid and then re-ordering the 'group by' columns caused the grid to stop responding. Investigation showed this was due to the event being passed as null after the reorder, and has been resolved by adding an event safe checker in the pzPega_ui_templatizedgrid js file. | User Experience |
| INC-B33742 | 886980 | Updated accessibility for non-optimized pagination | To improve accessibility, an aria-label has been added to pzGridActivePage for pagination 1-Y in a non-optimized table. | User Experience |
| INC-B33916 | 887603 | Corrected local action discard error | Cancelling a local action configured on a case was generating a data view error in Constellation. This has been resolved by adding a safe check for dataInContext in getResultsFromDataPage. | User Experience |
| INC-B34026 | 886876 | Corrected displayFieldNameInValidationMsg error text | When any field with required property was added to a dynamic layout and the DSS displayFieldNameInValidationMsg was set to true, the required field name was appended without a space in the error message below the field. This has been corrected. | User Experience |
| INC-B34297 | 885303 | Corrected customer search and results table sort | After launching a customer search using Constellation, the search screen was failing when "search by phone number" was used repetitively. The error "DOMException: Failed to execute 'querySelector' on 'Element'" was generated. This was caused by the multi-select view not refreshing correctly to call D_GetPropertiesForInquiry, and has been resolved. In addition, clicking on the column header to sort the results was breaking the table. This was traced to a condition where the self referencing property(composite key) had a JSON string, which was not a valid CSS query value and could not be handled by the the animation involved. This has been resolved with an update to convert the value to be valid for a CSS query. | User Experience |
| INC-B34981 | 885192 | Added alt attribute to Chart control image tags | The alt attribute has been added for img tags in the Chart and pzRRChartDiv rules to improve accessibility. | User Experience |
| INC-B35455 | 889000 | Corrected aria-label for setTodayCell | The pzpega_ui_calendar.js file has been updated to correct a typo in the aria-label for the "setTodayCell" function which interfered with accessibility. | User Experience |
| INC-B35504 | 888530 | Filters cleared after Theme-Cosmos search | After opening the Theme-Cosmos portal and performing a search which opened a new tab, changing the filters and closing the tab carried the filter revisions to the next search from the portal. This has been corrected. | User Experience |
| INC-B35736 | 886821 | Corrected Constellation AM/PM handling for en_HK locale | When using en_HK locale in the operator context with Constellation, the AM/PM drop down did not work, the control only captured time in PM, and the date time value submitted was 12 hours behind the actual time. This has been corrected. | User Experience |
| INC-B35776 | 888181 | Server-side validation error specifies field | The Constellation error banner for server-side validations has been updated to display the name of the required field needing attention. | User Experience |
| INC-B35788 | 886626 | Additional Info displayed correctly | When no text was configured for the additional info of the "pyNote" property, the UI was inconsistent displaying the information symbol beside the property. This was traced to the paragraph-handler.ts is not resolving the values in the instructions text correctly, and has been resolved. | User Experience |
| INC-B35895 | 885641 | Data reference field selection correctly persisted for embedded data | When using a table with a modal edit option that utilized a search and select design pattern, the add function worked as expected, but the search field and associated properties that were filled in from the selection were not retained and caused an update to function as an add instead. Investigation showed the system was not appending the needed dataRelationShip Context to the path to store the value, and this has been resolved with an update to ensure propName is passing the correct value for updateFieldValue in listActions. | User Experience |
| INC-B35984 | 892092 | Corrected Smart Tip handling for empty content of an optimized table | After configuring the Smart Tip for optimized grid columns, hovering over a blank column displayed a blank Smart Tip if the "Short", "Medium" or "Tall" Table densities were set. No Smart Tip was shown when hovering over a blank cell if "Full Content" Table density was used. This has been corrected so no Smart Tip will be shown for an empty cell regardless of table density. | User Experience |
| INC-B36334 | 890400 | Corrected drag/drop issue in repeating list | After adding an embedded data table with several columns to a repeating list in Constellation, performing a row drag/drop operation on any of the rows caused the row to get stuck if it was dropped outside of the table. This has been corrected. | User Experience |
| INC-B36431 | 887263 | Corrected blank value handling in PDF | When a section contained a read-only control with a blank value, the generated PDF showed the blank value as "no value" when UseCompactStylesforPDF was set as TRUE. This has been resolved by updating the CSS. | User Experience |
| INC-B36484 | 892964 | Column sort functionality removed for "Refer to Data Page" | The sort icon was visible on a report table even though sorting was not available when using a pagelist specified in the source of the repeating grid with a configuration of "Refer to Data Page". This has been resolved by updating pyReportBrowserAllReports to uncheck the checkbox "Allow column sorting". To sort data on the clipboard and reflect it on the UI, use "Copy to data page" as the data access for the pagelist property that serves as the source for the repeating grid. | User Experience |
| INC-B36536 | 889166 | Corrected accessibility for report case ID links | The case ID column links of a report were not accessible via keyboard in the pxReportWidgetGridAndChartSection section. This has been corrected by adding the enter key action on the table configuration level to work with accessibility tab keys. | User Experience |
| INC-B37456 | 893959 | Updated handling to persist response for reuse | On property change, the refresh action was being triggered to fire a data transform and calculate a value. A custom component button then saved the form data using save assignment and launched another local action. Attempting to access the calculated data from the earlier step did not work as the save was made in a different thread. This has been resolved by updating the handling so the data is available. | User Experience |
| INC-B37492 | Mandatory validation control returns to Rich Text Editor | The mandatory validation control was not directing back to the Rich Text Editor (RTE) fields as expected when using a form containing both Text Input and Rich Text Editor fields. Both types were required for submission, however if the Text Input was filled in but the Rich Text Editor field was blank, clicking submit caused the validation to incorrectly focus on the Text Input field instead of returning to the Rich Text Editor field. This has been corrected. | User Experience | |
| INC-B37800 | 893663 | Explicit on-change added for textinput control on Apple Safari | Values with a separator were not updating on refresh when using the Apple Safari browser. This has been addressed with a new flag which can be used to fire an explicit changehandler. Set pega.ui.setExplicitOnChange to true for the specific browser as per requirement. | User Experience |
| INC-B37817 | 891860 | Attachment correctly deleted from modal | After adding any attachment and minimizing the modal in Constellation, the attachment could not be deleted after opening the modal again. This was an issue with the deleteModal method of the modal component losing its reference after being minimized, and has been resolved by reassigning the deleteFile method when the component is remounted. | User Experience |
| INC-B37919 | 892607 | New controls provided in pyActionAreaParams | Due to the pyActionAreaParams section having deprecated controls and layouts, the required parameter actionSection was not set properly when including the pyCaseActionArea and resulted in a different path in the doSave API. This has been resolved by updating the layout to a dynamic layout and modifying the UI rule pyActionAreaParams to provide new controls in the section. | User Experience |
| INC-B39185 | 890690 | Attachment error correctly cleared | If a 'when' condition in the attachment widget was used to prevent a file attachment of a specific category, the error message was shown and the upload of the document stopped but clearing the document did not clear the error message with it. This has been corrected with an update to ensure the http error messages are cleared on file upload cancel. | User Experience |
| INC-B3966 | 854296 | 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-B39897 | 892595 | Color contrast increased for recents | The color contrast when the display window is contracted has been improved for greater accessibility for the RecordID in the pyRecentWorkContent section. | User Experience |
| INC-B40151 | 891842 | Check added for blank name in file attachment |
It was possible to attach a filename and edit its name to be only spaces and the extension type when using Constellation. This has been resolved with a validation check which will trim an edited fileName to remove the extra spaces in the string and check if the string is empty or not in updateFileDetails function. | User Experience |
| INC-B40253 | 890715 | Stakeholder names prevented from exceeding container bounds | In the "Stakeholder" section of the UI, the names of stakeholders were extending beyond the boundaries of the container instead of getting wrapped and interfering with the layout. This has been corrected. | User Experience |
| INC-B40374 INC-B37302 |
891042 889108 |
Corrected currency symbol alignment | The "$" character was distorted and not aligned properly if there was a validation error in the Currency control. As a workaround the "Reserve space for label" checkbox under the presentation tab of the property panel could be checked to avoid this. To resolve this, a wrapper span has been added for the currency symbol. | User Experience |
| INC-B41176 | 894252 | Checkboxes rendered correctly when 'Group By' preselected | When using list view on a table in Constellation with bulk action and 'group by' preselected, checkboxes were cut and the bulk checkbox was not visible at all. This has been corrected with an update to the row select column auto size calculations. | User Experience |
| INC-B41300 | 892918 | File size check added for edited file name in upload | If a file was uploaded that exceeded the size limit set in pyMaxDragDropAttachSizeMB, changing the name of the file on the Constellation upload component enabled the "Attach Files" button and allowed the upload, which then failed due to the size. This has been resolved by adding a max size check to the edit file component to validate the size before allowing the process to continue. | User Experience |
| INC-B41401 | 895147 | Updated handling for View deletion | After making some changes to a View in an open Ruleset, using the trash can icon to delete a data reference field from the Summary / Highlighted regions also withdrew the view previously present in a Ruleset which was closed/locked. Attempting to restore the view generated the error that it was not possible because it was a closed Ruleset. This has been resolved with an update to prevent rules being deleted for a reference field, as well adding handling to ensure unique viewnames for newly added reference fields. | User Experience |
| INC-B41667 | 891831 | Sorting corrected for TimeofDay property type | Sorting of the "TimeOfDay" property column in a Constellation table view was not working as expected. This has been resolved by adding type-specific sorting for time fields. | User Experience |
| INC-B42324 | 893868 | Corrected image distortion in Rich Text Editor upload | When an image is uploaded in the Rich Text Editor (RTE), it is resized to fit within the editor. However, the resizing was inconsistent the first time and required opening the image properties and clicking 'OK' to display it correctly. This has been resolved by adding a function to set the height and width values for dropped/pasted images to be populated in the image dialog. | User Experience |
| INC-B42453 | 895606 | Updated grid handling for modal launched from case wide action | After update, clicking on an item from the Actions menu, making selections, and clicking submit caused the modal window to freeze and required a browser refresh to clear. This was traced to an issue with the grid row height handling in the Change Stage activity, and has been resolved with additional checks for the dom grid value and by refactoring the "readjustGrids" to take parameters. | User Experience |
| INC-B439 | 849515 | Updated handling for focus styling | Clicking on the recent tag and then clicking on the left menu bar resulted in both displaying the blue styling indicating focus. This was caused by similar styling for the focused and current menu item: the fixed navigation menu item was set blue because it is focused, while the main navigation item was blue because it was marked as the current/selected one. This has been resolved with an update for current item styling when a fixed navigation item has focus selected so only one menu item will have blue styling applied. | User Experience |
| INC-B4451 | 862754 | 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-B5390 | 857133 | Corrected timezone "today" handling | The default current / today's date was set to an incorrect day on any date picker icon. This was traced to "today" being picked based on UTC time, and has been resolved by updating the timezone handling. | User Experience |
| INC-B6140 | 869893 | 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 | 871460 | 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-B6783 | 859363 | Improved accessibility for login error message | JAWS was not reading the error message if incorrect credentials were entered on the login page. This has been resolved by adding the alert role and aria live attributes to the error div. | User Experience |
| INC-B8247 | 860728 | Updated spellchecker to limit area | When using a Rich Text Editor with a property also used in the autocomplete set value in the general tab, clicking on spell check after entering some content resulted in an error in the console loader. This was a missed use case and has been resolved with an update to select only the Rich Text Area for spellcheck. | User Experience |
| INC-B9435 | 881799 | 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. | User Experience |
| INC-B9573 | 861475 | 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 |