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.)
For information on downloading this patch, see Pega Patch Release for 8.8.3.
Low-code Application Development
Case Management
8.8.3 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-253078 | 776820 | Added harness type for custom temporary case | After creating a custom implementation which created a work object in a new tab, the form content was not showing when the browser refreshed. This was traced to a missing harness type when refreshing a temporary case created in a dynamic container, and has been resolved by adding a pyCreate value for the harness purpose in the pyIsHarnessTypePerform when rule. | Case Management |
| INC-254403 | 783664 | Updated handling for unauthorized case access | After upgrade, an incorrect error message was seen for unauthorized access to a case. In Pega 7.4 the message was "The work object XXX could not be locked: You are not authorized to create, modify, or lock instance XXX". After upgrade to 8.7, the error "There has been an issue; please consult your system administrator" appeared when executing the same scenario. Investigation showed this only happened when the user did not have a standard skin rule in their application stack, and the issue has been resolved with an update to call the Open assignment function instead of the ProcessAssignment activity, as ProcessAssignment doesn't have error handling configured. | Case Management |
| INC-257406 | 780805 | Step added to stop busy indicator for zero length file upload error | If a 0KB file was attached using the pzMultiFilePath control, clicking on "Okay" on the pop-up warning message did not dismiss the busy indicator. This was traced to a missing step for this scenario which would stop the busy indicator for an incomplete file upload, and this has now been added. | Case Management |
| INC-260916 | 785684 | Bulk activities updated to consider context | Bulk Transfer was not working after customizing the "pyTransferAndAdjustSLA" section rule (in Work- class) to be in the implementation layer. This was traced to the system picking the section rule from 'Work-' class and not from the implementation layer, and has been resolved by modifying the pzPreBulkProcessModal activity to consider the context. | Case Management |
| INC-263726 | 796691 | CheckFlowDependencies updated for StepPage context | When there were multiple parent and child case dependencies where the parent case waited for the child case to reach a certain status before further propagating the case information from child to parent, the child to parent propagation was not working. This was traced to an incorrect StepPage context at run time due to previous work done in CheckFlowDependencies involving the handling of the pyTopCaseWork page. To resolve this, pyTopCaseWork will be removed in pzUpdate before performing findpagebyhandle in step 5. | Case Management |
| INC-264225 | 797414 | Bulk action withdraw works for embedded page assignment | When using a process flow with split-for-each on an embedded page, if the case had one embedded page and created one assignment with interest page as that embedded page, bulk action withdraw failed. Investigation showed the tracer was its taking the interest page as primary page and trying to open the case with that page key, which failed. To resolve this, the step page name(WorkObjectName) has been added for all the steps in pyInvokeForceWithdraw activity so WorkObjectName will have the correct context in all the scenarios. | Case Management |
| INC-264941 | 792162 | Updated validation for Change Stage parameters | In Pega 8.1 the shape 'Change Stage' uses stage IDs like 'PRIM1', 'PRIM2', 'PRIM3', 'PRIM4' etc instead of the actual stage name. Beginning with Pega 8.2, a flowaction called "pzChangeToSpecifiedStage" uses a validation rule which only accepts stagename as a ChangeToStage parameter. This caused validation issues after update and resulted in the error "Go to Stage— Please select a valid stage" in case type rules and in flow rules with this configuration. This was a missed use case and has been resolved by adding the needed additional logic to validate StageID if is a valid one in the pzChangeToSpecifiedStage validate rule. | Case Management |
| INC-264955 | 791880 | Approval task naming changed | An issue was seen with the handling of the parameter used for the localized "Please approve or reject this" label, causing it to not be correctly passed. This has been resolved by creating an extension data transform pyInstructionsForApproval to change the instructions message in the approval/reject smart shape. | Case Management |
| INC-266208 | 794355 | Handling updated for HasChildWithDependencies | An issue was seen where disabling the automatic instantiation of child cases did not reset the flag HasChildWithDependencies to false. This has been resolved by updating the condition to set the flag when automatic instantiation of child cases is checked and dependency fulfillment is selected. | Case Management |
Cloud Services
8.8.3 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-251646 | 779762 | Null DateTime check added for column population job after import | When importing a RAP file, the StatementYear column was created and the column population job was scheduled and started, but the job was only running for a portion of the table. Running 'optimize for reporting' on the same property later caused the time column population job to complete for the entire table. This could be seen the landing page first showing 18% complete but no errors for the first job, then the optimized job showed 100% completed. This has been resolved by modifying MaxCommitDateTimeFilter to consider pxCommitDateTime is NULL as well in order to include rows without a timestamp. | Cloud Services |
| INC-265030 | 791080 | Corrected race condition for column population | Duplicate column population jobs were seen. This was traced to a race condition in the query, and has been resolved. | Cloud Services |
Conversational Channels
8.8.3 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-263298 |
788039 | Chatbot AnalyzeInput updated for multiple topics | During a chat, the "multiple matches" system responses were sporadically displayed in the conversation if more than one topic was included, such as "Chatbot: Can you clarify what you mean? * Chatbot: Call us * Chatbot: Menu * Chatbot: This conversation has been ended due to Customer inactivity". This has been resolved with the addition of a check for escalation mode in the pyAnalyzeInput and pyOutputAdapter activities: if the chat is in escalation mode and NLP detects multiple topics, the system will not show multiple matches. | Conversational Channels |
| INC-249647 | 775270 | Text analyzer identifies buzzword in subject line when email is blank | Text analyzer was not identifying a confirmation buzzword, causing an incorrect case type to be created. This occurred when a system-generated email had a blank body and no HTML content, and was traced to entity detection not running on the subject line. To resolve this, the pyTreatIncomingText activity has been updated to handle this usecase. | Conversational Channels |
| INC-256756 | 786279 | Corrected case ID increment incorrectly extracted from email subject | An email with a subject that contained several capital letters + "-" + several numbers (ex : HEQUET-399014365) created the case ET-399014365 with no information inside except a label for the case equal to the subject of the email. This was traced to the increment of the Work-Channel-Triage-Email object being incorrectly extracted from email subjects: ET- or M- with an ID specified in a subject line is valid only when surrounded by space or brackets like (,[<{. This has been resolved by updating the regex in pzGetIncomingMailContext. | Conversational Channels |
| INC-259069 | 787972 | Parameters passed correctly to interaction data page | After update, log warnings indicated there was a missing parameter during use of D_pxUserFromChannel in step 6 of pzCreateInteractionReply. This was traced to the parameters not being passed correctly, and has been resolved. | Conversational Channels |
| INC-261573 | 786625 | Checks added to resolve "Index out of range" for incoming DSN email | An "Index out of range" issue was seen when a DSN email was processed for deployment notifications. This was caused by pzGetIncomingMailContext assuming that pyInReplyTo is always present and has a value that contains "@" when the DSN email ReplyTo is blank. This has been resolved by adding a null check to the ReplyTo check on the InboundEmail page and checking for "@" in messageid. | Conversational Channels |
| INC-262516 INC-262629 |
787535 793002 |
Chat message handling updated | Chat was getting disconnected when the customer or agent reply included any keyword present in the channel text analysis. This has been resolved with an update which will ensure the command is not detected in escalation mode, and which will uniquely identify messages using message_id and timestamp fields returned in both the regular message exchange as well as in the history API. | Conversational Channels |
Data Integration
8.8.3 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-229957 INC-230002 |
794590 782686 |
Additional logging added for push notification chats | Additional logging has been added to assist with diagnosing an issue where chat messages may not be correctly handed to an agent when using the push notification framework. If the browser receives notifyOperator advice, the messaging manager will be triggered to run the PYDEBUGACTIVITYFORPUBSUB activity from the client side. | Data Integration |
| INC-235155 | 786056 | Declare trigger correctly triggered by Deployment Manager | After configuring a declare trigger to run on a committed save of a rule, the declare trigger was not activated as expected when the rule was deployed to higher environments through Deployment Manager. The trigger worked as expected when the rule was manually imported through Configure > Application > Distribution > Import. Investigation showed that when the data transform was saved, the declarative trigger was called but was not able to find the activity due to this use case running the declare trigger activity as "In Background On Copy". This created a child requestor to trigger the activity in the default access group instead of the application context. To resolve this, an update has been made which will execute the declare trigger activity in the current user context when the activity is configured as "In Background on Copy" and the "pzUseCurrentAccessGroupForChild" property is true in the parameter page. | Data Integration |
| INC-243067 | 764730 | Message IDs correctly appended when using MSGraph | After switching to MSGraph, the Message-IDs were not appended to the References header for reply, reply all, and forward, causing an issue when identifying whether a work object already associated with the existing thread was in the system. This was traced to a difference in message ID formats between MSGraph and IMAP, and has been resolved by overriding the updateMessageID() method of MimeMessage class. | Data Integration |
| INC-246705 | 768588 | Support added for custom CORS endpoints | The URLs of custom REST services were not showing when setting the endpoint for CORS policy mapping. This has been resolved by adding the necessary property set to the pzGetAllRestServices Activity. | Data Integration |
| INC-249024 | 796236 | Added handling for passivated modal dialog flow | After passivating a modal dialog flow launched from the user portal context, launching the flow again encountered a security exception error. This was caused by the modal dialog flow thread being lost during passivation, and has been resolved. | Data Integration |
| INC-250997 | 792859 | Archived data for email triage and pegasocial-message class fetched with all attachments | Some Pulse messages were missing when attempting to retrieve archived data for email triage cases. To resolve this, support has been added for data work attach notes, handling for the pyObject in pulse message and translation logic has been updated, and the pxGetCompleteMessage activity has been updated to check secondary storage for social messages and notes. | Data Integration |
| INC-251713 INC-255730 |
783053 786044 |
Debug logging added for page open | In order to better diagnose an issue with a 'when' condition configured in the Access role being called on an unnamed page rather than the pyworkpage after update, additional logging has been added. | Data Integration |
| INC-252499 | 786718 | Updated error handling for CommitWithErrorHandling | The exception "Error during Encode" was generated when running the activity CommitWithErrorHandling. This has been resolved with an update to fix the IndexOutOfBound exception during BLOB encode. | Data Integration |
| INC-253409 | 793612 | Updated handling for null requestor returned to ManagementDaemon | Previous work done to add handling for an InvalidParameterException in cases where the requestor is deleted before the job is executed on it has been updated to include the use case where the case requestor is "batch". | Data Integration |
| INC-256360 | 781538 | Services PAL properly displayed | Despite configuring the settings for Services PAL, the Services PAL log was not populating any data when navigating to the log file. This issue was traced to the logic in StatisticsLogHelper and has been resolved by extracting the logic into helper functions and adding an explicit check for PALType Average. | Data Integration |
| INC-257385 | 796787 | Email listener updates for logs and send-as | Unneeded warning logs were printed for the email listener. This was an unintended side effect of previous work to check for empty SendAs in MSGraph, and has been resolved by moving the unnecessary log into a catch block.In addition, using Global Resource Settings (GRS) for send-as in the email listener rule form was not working. This was a missed use case and has been corrected. | Data Integration |
| INC-257386 | 787152 | Added Calendar Type check for .ics attachments | Whenever a message with an .ics file attachment was sent to the email listener, the filename was automatically changed to noname_1.ics in the portal. This has been resolved with the addition of a check to evaluate whether MimePart has a file name for Calendar Type. | Data Integration |
| INC-257869 | 783424 | French locale uses semicolon delimiter for CSV export | An exported CSV file was unexpectedly opening as comma-separated data for French users. This was an unintended side effect of work done to add the language code "fr" to the Decision Table pzGetLocaleListSeparator, as the French locale uses "," as a decimal separator. With this update, the previous behavior of CSV exports using a semicolon instead of a comma as the delimiter when the operator default_locale set to "fr_FR" has been restored. | Data Integration |
| INC-258105 INC-268493 |
794765 797048 |
PushDailyCaseData query optimized | Case data was missing in PDC Telemetry due to the PEGAAESRemote agent report pushdailycasedata timing out. To resolve this, the GetInstancesOfCaseType report definition and the FetchDailyCreatedCaseInstanceData activity have been optimized by removing the date function in filters. | Data Integration |
| INC-258416 | 793407 | Corrected File Listener trace | After update, the File Listener trace from Admin Studio was running but the events were not captured in the trace. This was an unintended side effect of previous work done around OAuth2.0 threads, and has been resolved. | Data Integration |
| INC-258764 | 783751 | REST connector Authentication redirection updated | An authentication REST connector which redirects to another URL was not working. This has been resolved with an update to AllowListLaxRedirectStrategy which checks for the Name in addition to the Value of the header. | Data Integration |
| INC-258871 | 797181 | Updated WebUser requestor timeout to resolve intermittent spike | An intermittent user/requestor spike was seen in WebUser nodes, requiring a node restart to recover. Investigation showed that whenever a requestor was terminated through Admin Studio, two "NONE" requestors were being created through Web-Login and pzunKnownSessionAlert HTML: Web-Login's "NONE" requestor was treated as a shortlived requestor and removed from Admin Studio after reaching the configured shortlived timeout value, but the pzunknownsessionalert "NONE" requestor was considered a normal browser requestor and deleted based normal browser timeout value. This has been resolved with an update to correctly set pzunKnownSessionAlert's requestor as "shortlived". | Data Integration |
| INC-259204 | 795289 | Added handling for space in folder name for MSGraph-based listener | When the MSGraph folder name contained spaces (for example "toms inbox"), the email listener was not able to read the messages. The error "Caused by: java.lang.RuntimeException: java.net.URISyntaxException: Illegal character in query" was generated. This has been resolved by using URLEncode with folderName in MSGraphEMailClient.getMailFolders to properly encode the entire folder name value. | Data Integration |
| INC-259525 INC-256888 INC-258256 |
790654 788811 789418 |
S3 repository credential handling updated | Uploading or downloading documents from an S3 repository was not working, and the error "Repository pegacloudfilestorage not authenticated. Directory does not exist." was logged. This was traced to an expired token, and has been resolved by setting the repository default credentials to be InstanceProfileCredentialsProvider. | Data Integration |
| INC-261011 | 784482 | Additional logging for Parse XML | More detailed logging has been added to the Parse XML feature to help diagnose an issue where SOAP Service response XML Phrasing was not working after update. | Data Integration |
| INC-262213 INC-268772 |
789184 796599 |
Connect-SOAP Guardrail warning updated for File Listener | When an endpoint URL in a Connect-SOAP rule was configured to use a data page, a Severe guardrail warning appeared on the rule. This has been resolved by updating the pxAddWarningsForGRSField Activity to add a condition to check for the File Listener class. With this change, Severe guardrail warnings appear only for File Listeners instead of all Integration rules. | Data Integration |
| INC-262348 | 795979 | File upload error message made less verbose | Overly verbose error messages may contain information that is not inherently sensitive but could potentially be used to exploit a vulnerability. To resolve this, error message that is generated when uploading files with extensions that are not allowed in the application will only use the last portion of the message from the exception to create a FileNotFoundException. | Data Integration |
| INC-262467 INC-261811 INC-262800 INC-265501 |
785546 785022 786068 789984 |
Retry logic added for MSGraph | Microsoft Graph was intermittently having issues with the email listener. From the Inbox, the email was read, processed and the case was created, but the email was not getting deleted from the Inbox. On some occasions, the email was read but the case was not created, or when two or more emails came in to the listener at the same time, the email listener was unable to process the emails. The error "com.pega.platform.integrationcore.client.email.EmailClientException: Error during http request" intermittently appeared. To resolve this, logic has been added for a retry mechanism using maxRetries and retryCounter. | Data Integration |
| INC-262797 | 795691 | Corrected decimal separators for en_ZA locale | While entering financials the amount gets multiplied with 100 automatically in the en_ZA (South Africa) locale. This has been resolved by updating the thousand separator and decimal separator as space and comma respectively for the en_ZA locale. | Data Integration |
| INC-263576 | 787460 | Case archival made more resilient | In order to improve the performance and increase resiliency of the archival process, an update has been made to case archival to run the job using pipeline mode. | Data Integration |
| INC-264237 | 797171 | Thread safety added to checkCalendarCache function | When three jobs were scheduled to start at the same time, two of them experienced the same event and only one of them executed successfully. All subsequent jobs completed normally. This was traced to the the business calendar object not being found due to the business calendar reading the cache when the cache was not ready, and has been resolved by adding a synchronized block in the checkCalendarCache function for thread safety. | Data Integration |
| INC-264515 | 793240 | Corrected date formatting issues for en_SG locale | After update, date formatting was incorrect for the en_SG (Singapore) locale. This has been corrected. | Data Integration |
| INC-264617 | 791973 | Added MessageID for MSGraph email listener | After update, email listeners stopped processing emails and the error "javax.mail.IllegalWriteException ( POP3 messages are read-only )" was generated when reading email from the mailbox. To resolve this, an update has been made to set the MessageId if MSGraph is being used while setting up Email account. | Data Integration |
| INC-264711 | 792100 | Archived case email attachments open as expected | Attempting to open an archived case email attachment resulted in an error from pzDownloadArchivedFile activity step 4. This was traced to a recent logic update, and has been resolved by adding a 'when' condition that will skip the unneeded step for email attachments. | Data Integration |
| INC-265138 | 796185 | Data-Retention-Policy rule reflects Associated classes added from Archival screen | After adding and saving "archival associated classes" and "Search using embedded page-list properties" from the Case Types -> Settings -> Archival screen, these added changes were not reflected in the archival case type instance when opened from Data-Retention-Policy. Support has now been added for Data-Retention-Policy archival case type instances. Note that Pega does not support or recommend any archival-related change from the Data-Retention-Policy instance, and associated classes and embedded page-list properties changes will not be saved if added from the Data-Retention-Policy screen. Changes should be done from the Case Types -> Settings -> Archival screen only. | Data Integration |
| INC-265462 INC-266830 |
791259 793143 |
Interaction History Summary replay updated for large repositories | The Interaction History Summary replay from the File Repository was not working if there were more than 1000 entries in a folder. This was due to a limitation of the RepositoryAPI, and has been resolved by replacing the ListNextBatchOfObjects API with ListObjects. | Data Integration |
| INC-266964 INC-265224 |
792832 794259 |
Null check added to resolve multipart service error | After update, calling an endpoint of a REST service which returns a multipart format response to obtain the content of a file resulted in the error "Caught throwable while accessing message body: null". This has been resolved by adding null check for the disposition. | Data Integration |
| INC-268994 | 798631 | Added null check for SFTP location | After successfully uploading files in the SFTP location, listeners attempting to process the files encountered an exception indicating "Premature end of file". This has been resolved with a check for a null location. | Data Integration |
| INC-271212 | 84246 | Kafka data migration process made more resilient | Updates have been made to the migration process in order to to maintain data integrity and prevent downtime when externalizing Kafka services. | Data Integration |
Decision Management
8.8.3 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-245472 | 764510 | Bkp decision data correctly removed before revision deployment | While completing/packaging a revision, some of the decision data backup rules were merged into the locked overlay ruleset instead of being deleted from the branch ruleset. This has been resolved by updating the activity to be case insensitive to handle both "bkp" and "Bkp" naming in the the cleanup. | Decision Management |
| INC-247223 INC-264205 |
782720 795345 |
Handling added for Pega Calendar time zone consideration | When appointments and tasks were set for after 5pm in Pega Calendar, the appointment was displayed on the calendar for the next day and notifications followed this schedule even though the correct date was displayed in the table. This was traced to the event highlight for goal and deadline not considering the requestor timezone, and has been resolved with the addition of the pyShouldDisplayEvent when rule called from pzShouldDisplayEvent which will properly handle the goal and deadline highlight in the calender gadget. | Decision Management |
| INC-247310 | 781810 | Handling updated for resuming HandleResponses data flow | After an accidental restart of the pxHandleResponses data flow, the events already waiting in the window were held waiting for the complete duration configured in the response timeout. To help in processing the future conversion responses faster, pxHandleResponses has been updated to calculate the delta time between decision time and response waiting time and subtract the response wait time to create the queue. | Decision Management |
| INC-252392 | 791437 | DDR count updated correctly after record deletion | The count on DDR was not updated appropriately after a record was deleted from it. Investigation showed the step for updating the count for DDR was missing in activity pzModifyDDRule, and this has been resolved. | Decision Management |
| INC-253125 | 785133 | #resolvedissues note: Empty value handling added to bias report |
The default reports "Bias report" and "Detailed Bias report" were not showing any records. This has been resolved with an update to handle empty numeric values. | Decision Management |
| INC-253154 | 789625 | Time to live works for embedded pages in Cassandra | When the Time To Live (TTL) value was applied via a property instead of being hardcoded, the embedded pages were not deleted after the TTL expired. This has been resolved by updating the decision data set save operation to allow accessing parent page properties in order to read the TTL value. | Decision Management |
| INC-254267 | 778505 | Updated failure handling for CallVirusCheck | A case was not able to proceed after enabling call virus check for attachments. Investigation showed that after getting the error message from the attachment gadget, the failure operation was performing a deferred save and throwing an error. This was a missed use case, and has been resolved by adding a rollback step when the pzmanagecontentpostprocessing activity fails. | Decision Management |
| INC-255453 | 789192 | Max character limit made configurable for language detection | On sending email to the listener in a single language the acknowledgment mail was correctly generated in the respective language, but if any keyword in the mail body or subject header was in different language than the rest of the email received by the listener, the language used for the acknowledgment mail was in an unexpected language even if English was set as a fallback language. This led scenarios such as a customer who sent mail in German where the email subject contained a single English word receiving back an acknowledgement in Dutch. To resolve this, the Prediction Studio settings have been updated with a configurable limit for language detection which allows for more characters to improve the performance of language detection. The default for LANGUAGE_DETECTION_MAX_CHAR_LIMIT is 200 characters, which was the previously hardcoded limit. | Decision Management |
| INC-255532 | 787540 | Resolved exceptions from ExecuteHandleResponseDataFlow check | The ExecuteHandleResponseDataFlow activity was continuously throwing IndeterminateConditionalException errors due to a condition calling HasFunctionalNodes to check for available realtime nodes before starting the data flow run. All the nodes were in the cluster but the function call failed, causing the alerts. This has been resolved with an update which removes the condition in ExecuteHandleResponseDataFlow which was calling HasFunctionalNodes to check for realtime nodes, and adding a refresh of the last known snapshot when the topology never has been refreshed or has been marked as stale. | Decision Management |
| INC-257347 | 790935 | Corrected rule checkin error in ValidateRuleData | Submitting a change request generated the error "You are not the owner of this checked out rule". This was traced to a missing "when" condition for the step where the rule is checked in the pyRMValidateRuleData activity, and has been corrected. | Decision Management |
| INC-258442 | 788528 | Create Pin control updated | The control for the Create Pin description has been updated from label to text to resolve an issue with displaying in read-only mode. | Decision Management |
| INC-259667 | 796504 | Corrected feedback training data edit issue | Attempting to edit training data for unreviewed feedback in the training data tab was not working when the feedback was added using the pxCaptureTAFeedback API. This has been corrected. | Decision Management |
| INC-260119 | 785002 | CDH metrics available for partitioned and ordinary ih_fact tables | The SQL query for CDH usage metrics has been updated to work with both partitioned and ordinary ih_fact tables. | Decision Management |
| INC-260253 | 787372 | Sibling rules button visible | The button for the sibling rules was missing after update. This has been resolved by updating the cross-site scripting filters to better handle rules without an applies-to class. | Decision Management |
| INC-260618 | 786775 | Handling added to clean up test cases with exceptions | When a test case generated an exception, the pass/fail status was not being returned and the test case was not cleaned up. This has been resolved by adding handling for the exception so that clean up block gets executed and an error report is generated for the test case failure. | Decision Management |
| INC-261207 | 788509 | When rules applied in Treatment Eligibility behave consistently | The proposition filter was not producing the expected results when there was more than one "when" condition given. Investigation showed the treatment filters were only evaluating the first criteria and not all criteria even if "AND" was used for grouping. This has been corrected. | Decision Management |
| INC-261912 | 790816 | Change to Event Strategies detected by the digest validator | After update, the pxhandle response dataflow was failing. The issue was caused by changes in pxQueueResponses dataflow between Pega 8.5 and Pega 8.7: the number of output properties changed for the Event Strategy, causing a mismatch between the state storage and the event strategy/dataflow definition. With this update, when any change is made to Event Strategy rule or Event Strategy shape in DataFlow then it should be detected by DataFlow and internal state of Event Strategy should be truncated. | Decision Management |
| INC-263219 | 795257 | PropositionFilter able to set nestedLevels in condition builder | After upgrading from Pega 7.3 to Pega 8.7, the node crashed when trying to add a new "when" condition in a proposition filter. Condition builder contains the pySetWhenGadgetContext extension data transform needed to override pyNestedLevels, however in this use case pySetWhenGadgetContext was not getting called when the PropositionFilter condition builder was loaded. This has been resolved. | Decision Management |
| INC-264935 | 794225 | Corrected Pulse "show tags" parameter casing | After setting the D_pzRenderFeedContext parameter of "show tags" to false, Pulse was still displaying tags. Investigation showed the activity PegaGadget-Pulse-Feed.pySetPulseContext had the parameter in camel case format like 'showTags' where the datapage declares the parameter in pascal case format like 'ShowTags'. This has been resolved by updating the activity PegaGadget-Pulse-Feed.pySetPulseContext's parameter from "showTags" to "ShowTags" so the parameters match. | Decision Management |
| INC-265011 | 792765 | Resolved metrics deserialization error | After upgrading from Pega 7.3 to Pega 8.7, the PegaRULES log file began to fill up with error messages related to metrics. This was caused by the current data flow metrics not being compatible with the 7.3 version of the metrics, resulting in serialization errors. This has been resolved. | Decision Management |
| INC-265549 | 791232 | Corrected weekly / monthly snapshot for Execution monitoring | No weekly or monthly snapshots were being generated for Execution monitoring. This was traced to an error in passing the snapshottime parameter and has been resolved. | Decision Management |
| INC-266507 | 791950 | DASS added to control initial state of ServiceAPI Circuit Breaker | When an initial request triggers the Global Optimization strategy compilation, all other requests are blocked while the strategy is compiled. Once the compilation is eventually done, all waiting threads start to execute the cold strategy. This high concurrency plus hotspot compilation and cache priming may cause high latencies for 30 seconds or so. To address this, an update has been made which will allow the Circuit Breaker in the Service-REST rule to start in open mode during node recycle while the Globally Optimized strategy is being compiled for the first time. This Circuit Breaker open mode allows default offers or responses to be sent to the end user during this delay window instead of impacting the performance for the inbound calls. 'Start in open mode' should only be enabled on Decision Hub nodes. | Decision Management |
| INC-267142 | 797983 | Addressed memory leak related to secondary branch strategy shape | A memory leak was occurring in the batch and realtime dataflow execution when using a strategy shape in a secondary branch, such as a dataflow source in compose and merge configurations with a strategy shape. Investigation traced this to the flush listeners which hold references to all the dataflow stages executed in the secondary path and which can build up over time if many stages are executed. To resolve this, an update has been made to call onPulse and onFlush at least once after secondary source has produced all its output. | Decision Management |
| INC-267360 | 797029 | snakeyaml updated | The snakeyaml library has been updated. | Decision Management |
| INC-268426 | 795316 | Analyzer edit access corrected for staging | Attempting to edit text analyzers in the staging environment was not working. This has been resolved. | Decision Management |
| INC-270318 | 798854 | When condition added for delete ruleset on update overlay | When the overlay instance from Data-Decision-RevisionRecords became corrupted and did not have the ruleset and version information, the underlying rules were getting deleted when the revert logic was executed and the overlay was updated. To resolve this, a "when" condition has been added to check for empty ruleset and version and delete only if it is not empty. | Decision Management |
Low-Code Application Development
8.8.3 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-247170 | 767804 | Removing an operator from a team correctly updates default | If a current operator was assigned to multiple teams (team 1 and team 2) with team 1 as the default, removing themselves from team 1 correctly changed their default to team 2, but if they were removed by a manager the system did not automatically pick up the new default. This has been resolved by updating the logic in .pyWorkGroupList(local.nextDefaultTeamIndex).pyRadioButtonAG. | Low-code App Development |
| INC-263623 | 788022 | pyWorkCover handling updated for DX API | While invoking DX API from the front end in a clone environment, pyWorkCover page was not present in the clipboard. Because the when rule used to determine visible condition checks properties on pyWorkPage and pyWorkCover, the when rule returned false and the dynamic layout was not visible. To resolve this, an update has been made which will read pyWorkCover for the skipWorkLock scenario in acquireworkobject. | Low-code App Development |
Mobile
8.8.3 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-221348 | 748098 | Addressed iOS mobile app memory leak | The mobile app displayed a white screen after a period of using it on iOS devices. This was traced to a memory leak related to javascript objects created in a child webview and then stored in a shared (hidden) webview which were not properly cleaned up after use. To resolve this, ClientCache has been refactored. | Mobile |
| INC-255461 | 793047 | Check added to handle integer with comma on mobile | After entering an integer value on mobile which was presented as a comma-separated value, the case was submitted but the particular integer field was highlighted in red. Subsequently attempting to reopen the work object on desktop generated the error that the particular integer was not a valid integer. This was traced to the value being saved as a comma value on the backend but the desktop only saving the number without the comma. To resolve this, a check has been added in getFormJSON in the ui_property.js file. | Mobile |
| INC-255687 INC-267512 |
778666 793890 |
Push notifications supported on iOS with proxies | The mobile app was not receiving push notification on iOS devices if proxies were used. This has been resolved by adding proxy configuration support to Pushy APNS. | Mobile |
| INC-258229 | 789043 | Dirty flag pop-up closes as expected on Client for Windows | It was not possible to close the 'Unsaved changes' dirty flag dialog with the "ok" button when using Client for Windows. This was an unintended side effect of work done for pyclosecase on mobile, and has been resolved by modifying the implementation for Client for Windows. | Mobile |
| INC-266494 | 796645 | Focus handling updated for pre-filled date field | After update, changes were not retained when attempting to modify a pre-filled date value. This has been resolved by updating the focus handling on the text input for date time. | Mobile |
Project Delivery
8.8.3 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-197795 | 702810 | Autocomplete control documentation update | The documentation for configuring an Autocomplete control has been updated to clarify that parametrized data pages and large data pages are not supported in data transforms when they are used in offline-enabled case types. | Project Delivery |
| INC-216681 | 718978 | Pega deployment tiers documentation update | The documentation on github for Tiers of a Pega deployment has been updated. "Pega supports deployments using a multi-tier architecture model that separates application processing from k8s functions. Isolating processing in its own tier supports unique deployment configurations, including the Pega application prconfig, resource allocations, and scaling characteristics. To avoid misconfiguration, use a single helm chart to deploy all your tiers simultaneously. Pega does not support using separate charts for different tiers in a single deployment. Use the tier section in the helm chart to complete your tier deployment with appropriate nodes dedicated to the logical tasks of the tier." | Project Delivery |
| INC-243156 | 761951 | Browser support documentation updated | The documentation for browser support has been updated to clarify that because Pega Platform version 8.5.6 introduced changes incompatible with Internet Explorer 11 and Edge Chromium in “IE mode”, version 8.5.6 is not supported on those browsers. Versions 8.5.1 to 8.5.5 continue to be supported. | Project Delivery |
Reporting
8.8.3 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-235968 | 744323 | Documentation updated for includeEmbeddedPropertiesInCSP DSS | The documentation for enabling the indexing of embedded properties has been updated to include details for configuring the DSS "indexer/srs/includeEmbeddedPropertiesInCSP". This is used to ensure all embedded properties from CSP are analyzed so there is no need to create a separate CSP instance for any of them. |
Reporting |
| INC-248354 | 792068 | Custom search works for embedded properties | Embedded page properties were not being included in a custom search even after adding the properties in the pySearch instance and indexing the data and work classes. This has been resolved by adding a check to detect an embedded property by evaluating whether there is a dot in a property name, and if the property is embedded it is moved to the properties array. | Reporting |
| INC-249740 | 768701 | Excel export issues corrected | Updates have been made to resolve the following issues when exporting to Excel: non-hidden fields are correctly exported in the same order as they appear in an Insight; field names are accurately exported to match the column names in the Insight; the User Reference field column header has the necessary label for correct export; changes made to column names by using customize column on the column header 3 dots action menu are correctly reflected in the export; and sorted columns are correctly aligned with their labels when exported. | Reporting |
| INC-255371 | 780828 | Updated search handling when ForSpecifiedProperties is used | When using global search, selecting "All content" instead of "Name" caused almost all searches to return 0 results. This occurred when the "For specified properties" option was checked and dedicated data instances were used, and has been resolved with an update which will always append to the content for rule reindexing even if ForSpecifiedProperties is selected. | Reporting |
| INC-256165 | 791540 | Correct error shown for insufficient privilege | After adding privilege to some report definitions accessed through the report browser, one user who without the privilege received the proper "insufficient privilege" error message while another user was shown an error screen. Investigation showed the original error was being overridden. This has been resolved by cacheing the exception so that original one will be displayed as expected. | Reporting |
| INC-256992 | 784873 | Added style tag to force custom radio button appearance | Selecting the "Embed link to output in notification" radio button in report scheduling caused the radio button to disappear. This was traced to the custom control "RadioButtonsForSchedule" used to create this radio button. This is different than platform provided radio button which has the css(appearance: none) to make default appearance to off and create appearance as per the Pega standard/design/skin by applying a different CSS class. The custom control applied the same css(appearance: none) to make it hidden, but there was no other CSS used to make it display. To resolve this, style tag "appearance: radio;" has added to force the appearance style in the RadioButtonsForSchedule control so that it does not collide with default radio skin styling. | Reporting |
| INC-257867 | 781663 | Added accessibility for grid/list toggle | The grid/list toggle on the Cosmos reports browser was missing a label for the currently selected toggle and an accessible cue as to the current state (which option is selected). This has been added. | Reporting |
| INC-259565 INC-260991 INC-265187 |
793301 794360 797710 |
FTP listener updated to support BIX data extracts in Pega Cloud |
BIX zip files generated in the Cloud environment were not able to be transferred to an SFTP location when the shared path was configured as PegaCloudRepository URI. This has been resolved by updating pzFTPService to handle BIX file transfers | Reporting |
| INC-262378 | 788202 | Added handling for magnifying glass when using BAC | The magnifying glass next to "Format values" was not functional and a security error was generated when attempting to create or edit a report in the report browser and edit a column of that report. This has been resolved. | Reporting |
| INC-262855 | 788575 | Corrected sorting on report list on Reports Landing Page | After launching the portal, clicking on Reports, and then "show as list", clicking on the column headers to sort them did not work. This was due to the page list source being referred to a data page directly. Instead, the "Copy data from a data page" option on the page list property needs to be used, and an update has been made to pzRBAllReports property to resolve this. | Reporting |
| INC-264087 | 798404 | Exception handling added for BIX extraction path errors | When running a BIX extract from the command line using the activity java step ((com.pega.pegarules.priv.PegaAPI)tools) .executeCommandLineExtract(args, tools.getThread()); , the above java step exited abruptly and was not handled by the jump StepStatusFail or Exception condition if the 'path' value of the arguments was incorrect (such as the specified folder did not exist). To resolve this, an update has been made to ensure all the steps in the "pxExtractDataWithArgs" activity are executed, and handle the exception properly if the extraction path does not find and update the actual status in the extraction history. | Reporting |
| INC-265336 | 794713 | GetPropsForTreeGrid registered with BAC | A 403 error was generated when trying to modify a report, and an error indicated there was an unregistered request. Investigation showed pzGetPropsForTreeGrid was not registered properly in pzBACActivityRegistration, and this has been corrected. | Reporting |
| INC-265362 | 792099 | Performance improvement for global Consult case search | Searching for Consult cases was intermittently not working when there were many millions of records. Investigation showed that if the index on pzInsKey was too large the database could decide to not use it and to sort the data on the disk. This led to resource consumption with long wait times and key generation failed. To resolve this, an update has been made so that rather than fetching all properties for external tables, only keys will be fetched. | Reporting |
Security
8.8.3 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-231380 | 787803 | Corrected application switch authentication issue | When attempting to switch applications, a popup window appeared with the message "Switch application with different authentication service". This issue was due to an error in the debug logger "com.pega.pegarules.session.internal.mgmt.authentication.Authentication" created in Log Category. While there is a workaround of deleting the debug logger and restarting the node, this has been corrected. | Security |
| INC-240511 | 82711 | PRPCServiceUtils used for pre/post upgrade actions | An update has been made to use prpcserviceutils in place of JMX to run pre/post upgrade actions. | Security |
| INC-254671 | 777543 | Corrected handling for asynchronous REST calls with Oauth | An OAuth-protected asynchronous REST service was not processing the data as expected. This was an unintended side effect of work done for application switching to set a custom AuthServiceName instead of "mAuthServiceName" being blank: as custom authentication service doesn't have operator provisioning, this use case failed. This has been resolved by correcting the asynchronous call handling for custom authentication with access group context. | Security |
| INC-256267 INC-265290 |
786332 798585 |
Performance improvement for rule assembly | After update, the assembly time increased significantly for Correspondence rules with embedded pictures. This was traced to the new vulnerability scanner mechanism taking considerable time to parse through all the text in the rule, and has been resolved by optimizing the code. | Security |
| INC-257111 | 777841 | getXML method removed from debug logger | When attempting to work on cases, the error message "you are not authorized to open instance" repeatedly appeared. The issue was caused by AccessEvaluator logger, which when set to DEBUG retrieves all of the properties using autopopulate in order to print the log message. Autopopulate was disabled by default for obj-open and page-copy, getMessage, etc, but this was triggered unexpectedly with getXML when the logger was enabled for debugging purposes. To resolve this, the getXML method has been removed from the debug logger statement. | Security |
| INC-257638 | 782288 | Token endpoint failure security alert added | A new alert SECU0022 has been added for OAuth2 token endpoint failure. | Security |
| INC-261689 | 785518 | JWT token processing updated for clone environment | Validation of the token by pxProcessJWT was failing in the clone environment with the exception "JSON web token is rejected during signature verification due to bad signature : Signed JWT rejected: Another algorithm expected, or no matching key(s) found". To resolve this, code changes have been made for local JWT configuration to consider x5t/kid. | Security |
System Administration
8.8.3 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-243905 INC-253093 INC-243905 |
775918 782801 773234 |
Corrected job scheduler running unexpectedly | A job scheduler that was expected to run at the same time every day (8:15pm) was triggering twice a day and started even before the scheduled time i.e., 8:14:58PM. This has been resolved with an update that will verify if the current runtime is in the past for non-periodic job schedulers before execution. | System Administration |
| INC-265987 | 793510 | Additional thread dump support added for failed node health check | If queue processor slowness and stale threads caused utility nodes to terminate after health check failures, the shutdown task was sometimes unable to shut down the executorServices (which hold executing threads for Agents, Job Schedulers and Async Services Executor) within the 5 minute time limit. In order to assist with this, an update has been made to add a thread dump after the dataflow health check fails the very first time, and to introduce monitoring which will generate thread dumps if the shutDown Engine task takes too long. | System Administration |
User Experience
8.8.3 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-231365 | 748004 | Multiple error messages for a property displayed correctly | If a property had more than one validation error message, field values were not displaying the actual full verbiage. This was traced to the newline character handling in the getMessagesMap() API, and has been resolved. | User Experience |
| INC-239930 | 748452 | Refresh loads portal menu correctly | Browser refresh was not loading the Menu as expected on the Portal. This has been resolved by adding a lookup to the active menu item before the browser refresh so the system sets the active menu accordingly post refresh. | User Experience |
| INC-239979 | 800937 | Currency code works in embeded data list | The currency code was not displayed correctly when the property value was in an embedded data list. This was traced to the context metadata not being generated for all properties referenced in the configuration object of the children in a multi-record case, and has been resolved with an update that ensures the context metadata is generated accordingly when a condition exists for a field. | User Experience |
| INC-240651 | 756150 | Bullet numbering corrected for paragraph rule in optimized table | A paragraph was not showing bullet/numbering points in an optimized table. This has been resolved by adding the necessary CSS. | User Experience |
| INC-240654 | 785797 | Added handling for harness open error | After update, attempting to open assignments resulted in an error indicating "The flow this assignment corresponds to is no longer at this task." This was caused by a failed openWorkByHandle call. To resolve this, a check has been added to handle the NoID harness error in pz-cosmos-ui-portal .js file. | User Experience |
| INC-241738 | 779647 | Corrected memory leak for offline mobile app using maps | Attempting to navigate to a worklist and open a case on an offline mobile app displayed a white screen after application refresh. This has been resolved by addressing memory leaks related to the canvas element created for map and signature controls by removing references and by removing unneeded listeners. Because map object creation can consume extra memory, support has been added to reuse the map object in the refreshsection case. To reuse the map object in the refereshsection case, configure the data-test-id. | User Experience |
| INC-242439 | 778585 | Screen display correct after iPad orientation change | When switched from landscape to portrait, the screen in the iPad mobile app only used half of the display space. This was traced to the modal resize logic not updating correctly, and has been resolved by executing the resize logic after the orientation change event. | User Experience |
| INC-244936 | 788020 | Removed case sensitivity for parser check | The javascript check for JsoupParserUtility has been made case-insensitive. | User Experience |
| INC-246072 | 771094 | Corrected notification count placement on access group change | After adding a flow action which allows changing the default access group, the notification gadget's count number (red circle) was displayed over the operator's image. Resetting it required refreshing the entire browser tab. Investigation showed that because the notification counter position was set with positionNotificationCounter method, the position was lost during the navigation section refresh and the method was not called to set it again. To resolve this, an update has been made to call positionNotificationCounter on the notification gadget section render. | User Experience |
| INC-246814 | 766263 | JAWS correctly reads case preview inputs | When opening the case preview panel and navigating Details with JAWS, some of the information was presented audibly in blocks of data and not as the equivalent of the visual presentation. This was traced to multiple text inputs being grouped together into one focus when tabbing into the case preview, and has been corrected by adding the necessary label descriptors. | User Experience |
| INC-250184 | 793402 | Modal close button correctly announced by screen reader | The modal close button was not being announced correctly with the screen reader, announcing the button as "button" instead of "close". This has been resolved by updating the aria-label attribute. | User Experience |
| INC-250392 | 792650 | Identity type column filters work for mobile view | Filters for the identity type column were not working in mobile view for an optimized table. This has been corrected. | User Experience |
| INC-251305 | 769042 | Focus preserved on initial load | When a work object was opened via Open Assignment, the focus moved right to the top of the Layout Group If any control within these sections had a OnChange->Refresh this Section configured. This was due to the total work area being covered via Perform harness instead of a Review harness, and has been resolved with an update which will prevent focus being stolen on the initial load. | User Experience |
| INC-251538 | 786913 | More informative error message shown on report definition timeout | An "Insufficient privilege" error message was intermittently displayed after opening a datatype, passivating it, and then opening the same datatype again. This error message was hard-coded in the "UIActionFailHeader" section, and updates have been made to the pxOpenLandingPage and UIActionFailHeader to show the error message that is coming from the report definition instead of showing the insufficient privilege error message. | User Experience |
| INC-253871 | 798126 | Updated mobile browser mashup cookie handling | Every time a mashup website was opened from mobile browser a request to enable cookies was shown. Giving permission for cookie consent resulted in asking the user to refresh to load the mashup. This issue was due to incorrect URL filtering which resulted in an encrypted URL, and has been resolved. | User Experience |
| INC-254270 | 784895 | Autocomplete correctly captured in scenario testing | Given a screen where values for some fields were set based on the selection of an autocomplete, recording it using scenario testing kit version 1.6 captured the auto-complete value, but the other fields based on auto-complete selections were not being captured. Investigation showed there was a timeout related to an internal on-change event occurring on an autocomplete element which has now been resolved. | User Experience |
| INC-254768 | 780718 | Corrected class search that caused RuleNotFoundException for teams | Clicking on the teams menu item on the user portal home screen resulted in a blank screen. The error "RuleNotFoundException:Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PZINITIALIZETEAMDASHBOARD' that applies to 'Data-Admin-WorkGroup' " was logged. Investigation showed this was caused by the PZINITIALIZETEAMDASHBOARD activity being searched for in the wrong class, and this has been resolved. | User Experience |
| INC-254875 | 781048 | Smoothed resize on change of assignment view | When a new assignment was opened, the assignment frame resized and jumped before displaying the expected content. This has been resolved by enforcing the min-height of the editor during the initial render cycle so that TinyMCE does not override it with a larger value, thus preventing the jumping of content. | User Experience |
| INC-255063 | 783576 | Tabbing out of multiselect correctly closes the item | When using the keyboard to navigate to a drop down pill box and select an item, tabbing out of the field caused an additional item to be selected. Investigation showed that on tab the system was incorrectly calling the createCapsule method for selecting an item instead of closing the multiselect popup, and this has been resolved. | User Experience |
| INC-255734 | 791919 | Security improved for desktop actions | Cross-site scripting protections have been improved by wrapping desktop actions using the crossScriptingFilter function. | User Experience |
| INC-256041 | 791805 | Session timer corrected to ensure complete countdown | Work done on the pop-up timer to trigger close() when the timer reaches 0s has been further updated to remove an additional extra space on the pop up and ensure the timer is accurate for the closure. | User Experience |
| INC-256362 INC-244695 |
784007 783062 |
PD4ML updated | PD4ML has been updated to v.4.0.13fx7 to resolve an issue with the HTMLtoPDF activity is taking 15 minutes to generate a PDF file from a section. | User Experience |
| INC-256426 | 793021 | Corrected "Unregistered request" errors | After a security update, repeated errors regarding "Unregistered request encountered with params pyActivity" were seen. This was traced to the PreDataTransform parameter which was added for ReloadHarness when the pre-activity is SaveAndContinue, but which was missed during the cleanup of the DoSave map. This has been corrected. | User Experience |
| INC-256835 | 779128 | Check added for dynamic pre-activity parameters in dropdown | After configuring a drop down with options loaded on hover sourced by a clipboard page using a pre-activity accepting parameters, an "Invalid clipboard stream detected in module (unspecified)" error was generated by pzGetDropdownOptions indicating invalid JSON. Thereafter the pre-activity was called without any parameters, static or dynamic. This was happened only when static parameters were passed in the pre-activity for loading dropdown options, and has been resolved by adding a check for dynamic parameters in the pre-activity. | User Experience |
| INC-257485 | 788942 | JAWS reads Inline errors on multi-select controls | JAWS was not announcing an inline error displayed under the control when the user tabbed away from a multi-select control marked as required. This has been resolved by setting aria described for the error div. | User Experience |
| INC-257940 | 782697 | Filter pop-up anchored correctly during horizontal scroll | When applying filters in the last few columns of a delegated table, the pop-up was not sticking to its respective column but instead scrolling horizontally with the screen. The pop-up location worked as expected for a non-delegated table. This was traced to an eventListener not firing as expected in harnessMainRegion for scroll event, and has been resolved. | User Experience |
| INC-258008 | 780662 | JAWS reads radio control client side errors consistently | Radio controls marked as required were triggering client side validation messages, but JAWS was not reading these messages consistently. This has been resolved by adding the needed roles alert to read out an error message when focus is changed using the tab key. | User Experience |
| INC-258097 | 784080 | Theme Cosmos event type check updated | An error seen when the Theme Cosmos harness refreshes and the case screen becomes unresponsive or some sections do not fully render was traced to the event type being unknown. This has been resolved by modifying the event type check condition from unknown to undefined if strreloadtype case is a section in the reload function. | User Experience |
| INC-258134 | 785961 | Keyboard access added for portal tab close icon | An issue with the tab close icon in the portal not being accessible by keyboard navigation has been resolved with the addition of the necessary CSS styling. | User Experience |
| INC-258271 | 781011 | Improved reports browser table accessible navigation | When accessing the report browser in list mode, the accessible navigation was not always applied to the grid, resulting in inconsistent keyboard navigation which required a browser refresh. This has been resolved by adding a check for the grid element in the DOM. | User Experience |
| INC-258272 | 781642 | Improved accessibility for multiselect in reports navigation | In the All Reports section of Reports navigation, JAWS announced the incorrect role “tab” when navigating to the “search by..” text box and “Category” combo box. This was caused by the role application being added to the body during multiselect focus, and has been resolved by removing the setting of the role application for the body in the multiselect updateMSLiveRegion API. | User Experience |
| INC-258314 | 786610 | Custom date format correctly applied to Mail template | After creating a custom date time control with DateTime format set to custom, the format was not applied when a property with this custom control as the format was embedded in a correspondence rule. If the same control was used in a section, the format was displayed correctly. This has been corrected. | User Experience |
| INC-258845 | 794846 | Mashup correctly shows landing page when using authentication | After implementing a Token Credentials authentication service to handle authentication and authorization of the user for a mashup implementation, the login screen was shown instead of the mashup landing page. Investigation showed this was caused by the authentication headers not being sent, and this has been resolved by adding additional logic for a null check to PegaCompositeGadgetMgr.js. | User Experience |
| INC-259790 | 783259 | Check added to set time zone for Calendar Picker | Calendar Picker was taking System time zone by default regardless of Operator time zone. Investigation showed that when the timeOfDay property type was used to represent a time-only property, the flag "hasDays" was false and the computation of a time string and a date string from input date string was not being done and the input date string was itself treated as time string. This has been resolved by adding a check which will compute the time string from the input date if hasDays is false. | User Experience |
| INC-260140 | 794364 | Null check added for instantiating tab | Refresh of the interaction portal was causing an instantiation error for the thread index:2 in the log. A null check has been added to resolve this issue. | User Experience |
| INC-260644 | 788437 | Updated handling for configuring embedded view in data class | The error "TypeError: Cannot read properties of undefined (reading 'split')" appeared when attempting to open the embedded view configurations and set the visibility condition. Custom forms created in Data Object authoring have viewType set as "embeddeddata" to determine if a regular view reference property panel or embeddeddata property panel is shown. When these custom forms were included in other forms of the Data Object without context, the system generated an error or opened the wrong property panel. To resolve this, the code in useConfigureDialog has been updated to only open the Embedded data property panel for complex fields. | User Experience |
| INC-260796 | 790717 | Subcase assignments correctly refreshed/removed | Assignments from the sub-cases remained visible on the UI after sub-cases were closed. This was caused by the add_container_item holding the old data, and has been resolved by calling Delete_Case_summary to delete childcases from app/primary_1. | User Experience |
| INC-260892 | 788660 | Improved accessibility for categorized tables | Using the tab key to move focus from the "refresh" button did not go to the first column of the grid as expected, instead moving to the second column, "ID". When navigating with the arrow key the toggle button was read as "column header", and arrow buttons did not give the expanded/collapsed state to JAWS. These issues have been resolved. | User Experience |
| INC-260942 | 785842 | Function values from report definitions work for multiselect controls | When using a multiselect control field with a report definition that included a function to concatenate firstname and lastname, the system failed to retrieve the value for multiselect. The function was retrieved as expected if dropdown was used. This was a missed use case, and support has been added for handling function values from a report definition optionName in multiselect results. | User Experience |
| INC-261255 | 785811 | Added role for JAWS to read client side validation messages | Radio controls marked as required triggered client side validation messages, but JAWS was not reading these messages consistently. This has been resolved with an added role for radio button tab support. | User Experience |
| INC-261275 | 787907 | Grid search works with boolean property | Attempting to search in the grid generated an error if there was any column present in the grid with boolean entries. This has been resolved by adding a check for boolean without displayAs in the DefaultViewMeta.js. | User Experience |
| INC-261897 | 788819 | Calendar correctly sets "Today" | Selecting "Today" on the calendar showed yesterday's date. This was caused by the date property not considering the operator's time zone for the date, and has been resolved by modifying the code for setToday in the ui_calendar function for DateTime Control with date property. | User Experience |
| INC-261950 | 790941 | Updated focus so JAWS doesn't read out DOM | When an edit modal was launched from within a grid / table context, JAWS was reading a lot of unnecessary context information before reading the contents of the modal. When the modal is launched, the original button that the menu was introduced from receives momentary focus prior to the popup appearing. When a slow network is introduced into this scenario, it had the result of JAWS reading the entire DOM into the table because the menu populated from the button is appended to the end of the DOM. When focus returned to the button element, JAWS was positioned to think that it has gone from the end of the HTML tree into multiple layers to the table so it read everything to get to the table, then read the modal that appeared. To resolve this, an update has been made such that if the menu item target parent is from template grid and if its opening a modal, don't focus on the showMenuTarget. | User Experience |
| INC-262011 | 797909 | Tab key works as expected in Repeating Dynamic Layouts | After opening a case type that has repeating sections, attempting to tab through the fields in the section resulted in the focus moving out of the section and to the adjacent section heading instead of to the next field. This has been corrected. | User Experience |
| INC-262094 | 791630 | Time zone will be assigned by serverTimeZone if TimeZone is not available | Two different timezone formats were displayed in two places of the application: Operator Timezone was set as America/Los_Angeles so the date time control displayed the operator time zone as PST, but for pxTimeCreated it was showing as UTC. This occurred when the pxTimeCreated property used in the case history table was configured to display format as Operator Time Zone, and was caused by the pega.u.d.serverTimezone not being considered while converting from PST to moment-supported timezones in the ui_formatDateTime text rule. To resolve this, code has been added to assign the timezone if pega.u.d.TimeZone is not available and pega.u.d.serverTimeZone is available. | User Experience |
| INC-262337 | 789175 | Required field and help test designations both appear | The required field asterisk and the help text question mark were not showing at the same time. This has been resolved with a CSS update. | User Experience |
| INC-262506 | 788604 | Corrected autofocus for non-mobile devices | Focus was not retained in the address field, instead jumping to another icon on top of the screen. This was traced to the setFocusToInput function in the pzpega_control_autocompleteag.js file checking for a touchable device. If it is touchable, the condition will not execute and focus will not be removed, but this condition leads to failure in touchscreen laptops/devices. The condition has been modified with a check for mobile to resolve this issue. | User Experience |
| INC-262558 INC-258050 INC-266067 |
788705 794756 795100 |
List control correctly populates values in Mashup | After update, multi-select list functionality was not populating the values when using Mashup. This was traced to the parent.document in the popover file causing a cross-origin issue when used in Mashup, and has been resolved. | User Experience |
| INC-262564 | 789078 | Corrected Pega Call widget labels | The Buttons on the Pega Call widget were not labelled correctly. This has been resolved by adding the aria-hidden="true" attribute on the icon/image markup inside the Button/Link. | User Experience |
| INC-262864 | 788276 | SessionTimer modal header correctly set | The title of the standard modal dialog (launched from script using "showModalDialog") was not referencing the title from an embedded HTML rule. This was caused by the function "pzDisplayModalDialogLoaderOnLoad" passing _isOverlay as a string instead of boolean, and this has been resolved. | User Experience |
| INC-262877 | 788212 | Corrected empty space in mashup after deleting table rows | Empty space was visible on the screen after the grid rows were added and deleted from a mashup. This was due to the mashup iframe height not being resized correctly after removing elements, and has been resolved. | User Experience |
| INC-263025 | 790429 | Case Preview button highlighted when focused with keyboard | The Case Preview button did not change color when it received focus while navigating a grid via keyboard. This has been corrected. | User Experience |
| INC-263037 | 794214 | Improved accessibility for repeating dynamic layouts | A number of accessibility challenges were seen when using keyboard navigation for repeating dynamic layouts. In order to improve accessible navigation, the new DSS property "pyRDLNAVIGATIONTYPE" has been added in the repeating dynamic layout configuration to allow specifying whether the tab key or arrow keys should be used by default for the system. If the DSS is not set or is undefined, the individual repeating dynamic layout configuration is honored. | User Experience |
| INC-263322 | 791054 | Default value displayed in mobile responsive dynamic layout dropdown | In mobile responsive view the dynamic layout group was displayed as a dropdown list but the default selected value was not displayed. This has been corrected. | User Experience |
| INC-263833 | 788694 | Updated parameter handling to avoid special character issue | After update, attempting to launch a new window failed when a property contained a special character (') on a page. This was traced to the harness action configured to open in a pop-up window having a data transform whose parameter value contained a single quote character “'” in it, causing a javascript error ‘Uncaught SyntaxError: missing ) after argument list’. To resolve this, an update has been made which will use paremKey instead of parmValue while checking the identifiers. | User Experience |
| INC-263870 | 790289 | Corrected handling for numbers added to formatted number field | After creating a number field (Decimal/Currency) with auto-format enabled, typing in a value and clicking outside the field formatted the value as expected, but then clicking inside the field to add values at the start of the existing formatted number resulted in the newly typed numbers not being placed at the correct positions. For example, typing in 34 and then having it formatted, then adding 12 before the 34 resulted in 1324 instead of the expected 1234. This has been corrected. | User Experience |
| INC-263931 | 793778 | Able to embed sections with tables/repeating dynamic layouts in Templatized sections | A section from Sales Automation for Financial Services could not be saved into the section ContactPrimaryDetails that was in the implementation class of Contact. This scenario called rules that exist in two different rulesets that embed a same section, so as a result during the view generation process there was issue where the process was trying to loop infinitely to call the same section rule, causing it to throw a Stackoverflow exception. This was a missed use case for repeating dynamic layouts with an embedded section from a different target class, and has been resolved using the embedded section's class and not the parent class while creating the views for section. | User Experience |
| INC-264014 | 798283 | Browser refresh from local action opens correct target | When a local action performed a browser refresh, pending task opened instead even if the task was not assigned to the current user. This was traced to the local action target being an ACPrimary (AJAX container) call instead of popup, and has been resolved by adding the NewTaskStatus and TaskIndex parameters to the payload for the ACPrimary call to ensure the local action is opened as expected. | User Experience |
| INC-264131 | 789592 | Datepicker correctly updates values in mobile view | When accessing a Constellation application from a mobile device, selecting a new date value and submitting while the focus was on the value did not change the original value. If the data field was de-focused before submitting the screen, the new value was accepted. This was traced to the blur event from Date and the click event from button not firing one after another as expected, and has been resolved. | User Experience |
| INC-264150 | 796467 | Corrected Row 1 being added automatically for field group | When a page list was configured as field group, Row 1 was being added automatically without the user clicking on 'add'. Investigation showed the field group was adding an extra empty INSERT instruction from the server while inserting records due to the FieldGroupTemplate being rendered twice for referenceList.length == 0 . This has been resolved. | User Experience |
| INC-264529 INC-266114 |
793159 794905 |
Optimized table has correct row values | An optimized table was showing showing Pega property names as row values after update. This was traced to an issue with resolving the parentPage if the pageList was referenced as a property, and has been resolved. | User Experience |
| INC-264642 | 789638 | DX attributes and symbols converted correctly in JSON | When invoking the DX API for dropdown and tooltip, the JSON was not parsed due to incorrect formatting. This has been resolved. | User Experience |
| INC-264872 | 796212 | Handling updated for switching portals | After update, switching to an interaction portal from a primary portal resulted in a distorted portal which did not hold the right UI. Investigation showed the threads were not being properly cleared when the switch happened, and this has been resolved by adding a new parameter for the switchPortal use case where the pyPortal page has to be updated. | User Experience |
| INC-264901 | 791680 | Updated validation for sourced report definition with class join | Values were not fetched as expected when using a report definition sourced in a section as a table with class join conditions. This was a missed use case and the needed logic has been added for the java step performing the validation. | User Experience |
| INC-265481 | 795958 | Date picker error messages picked up by translation wizard | The date picker error messages "incorrect Date" and "incomplete Date" did not appear in the translation Excel. (Retranslate all layers selected). Manually adding the values in the Excel worked and after upload the values are translated, but the additions were missing when the translation file was downloaded again. This has been resolved by adding the keys for Incomplete Datetime and Incorrect Datetime in pyGenericFields. | User Experience |
| INC-265775 | 792086 | Display value using read-only formatting resets datepickervalue | When the checkbox "Display value using read-only formatting" was selected on the presentation tab of a date time control, the date was reset upon switching the page. Investigation showed that if there was a default value provided to date time property with "Display value using read-only formatting" checked, the data-value was already added onto the DOM with default. As the user selected the date from the date picker, the data-value was not updated to the latest selected value (update only happens on blur), causing the submit infrastructure to pick the old data-value and reset the date. This has been resolved by updating the handling for the data-value when it is non-empty. | User Experience |
| INC-266401 | 795263 | Corrected focus issue when using hide column | Selecting "Hide field" from the ‘Open Menu’ for any column of an optimized table in a section in a case caused focus to shift to the browser top left. This has been corrected. | User Experience |
| INC-266973 | 795306 | Multi-line warnings correctly localized | Single validation warning messages were correctly localized, but multiple warnings appeared in English only. This has been resolved by updating the code to handle localizing multiple errors associated with same field. | User Experience |
| INC-267032 | 795662 | Focus will skip calendar icon if Datepicker is disabled | When Datepicker was disabled, the calendar icon had tab index as 0 and screen readers were reading the calendar icon on the tabs instead of skipping it. This has been resolved with an update which will avoid focusing on the calendar icon when the date field is disabled. | User Experience |
| INC-268507 | 798299 | Left Navigation panel focus moved to back button for sub-menus | When opening the "My applications/notifications/recents" panel via keyboard, focus landed on the hidden search edit field on the “My Applications” panel instead of the Back button on the "My applications" panel as expected. In order to have the focus align with the implementations of the other buttons within the sidebar, focus will be brought to the back button when going into the sub-menus rather than the header. | User Experience |
| INC-268688 | 796844 | Moment library updated | An issue with date/time not updating to reflect Mexico's DST changes has been resolved by updating moment.js to version 0.5.43. | User Experience |
| INC-269304 INC-269163 |
798080 798373 |
Browser 400 error handling updated to resolve intermittent loading issue | Custom components were intermittently not loading correctly. A status 400 event was recorded in the network trace, referencing the disk cache. The issue did not occur when using Google Chrome incognito mode. This has been resolved with an update which will add 'cache-control: no-store' on HTTP 400 response. | User Experience |
| INC-269342 | 796736 | Dirty check warning added for Rich Text Editor textArea | The cancel button was not providing a dirty flag warning as expected, causing automation scripts to fail due to the different behaviors of the cancel button on different UIs. Investigation showed the Rich Text Editor control textArea was not being considered for the dirty check while performing the cancel action, and this has now been added. | User Experience |
| INC-269535 | 799981 | Nested data pages supported for non-localized sections | When sending correspondence for review, the "Transfer To" drop down was empty and no operator names were listed. Investigation showed the dropdown display value was coming from a different class which was nested, but when localize check is not added in a section, the non-localized value is not extracted due to the property value being nested. This has been resolved with an update supporting the nested data page option for a non-localized section. | User Experience |
| INC-269662 | 800222 | Query from parameterized data page correctly refreshed | Data was not being refreshed as expected for a table sourced from a query property which in turn was sourced from a parameterized data page where parameter value was set based on a property in the case. Changing the value of the property triggered a refresh but the values shown in the table were not updated. The PConnect is expected to be a single object across re-renders, not to be created on every re-render. To resolve this issue, the createPConnect logic has been moved to a useRef to hold the singular instance of it, and the raw parameters will be passed while creating PConnect for list view. | User Experience |
| INC-269887 | 797771 | My Applications "Back" button focus updated | When selecting the back arrow from “My Applications” navigation item from the left hand navigation, the focus was set back up to the top level page of the screen rather than returning to the navigation button that launched the “My Applications” Section. This has been corrected. | User Experience |