Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
Low-code Application Development
Case Management
24.1 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-229623 | 829820 | App Studio case type creation chooses correct ruleset | When the application ruleset had versions such as 01-01-01 and 01-99-01 and 01-99-01 was unlocked, during the case type creation App Studio was always selecting the 01-99-01 version to create the rules even though the application rule had restricted the version to 01-01. Analysis showed the activity PZCREATECASETYPEWRAPPER step 8 was using the GetRuleSetVersion function to get the ruleset version to save all the rules and was always returning the highest unlocked ruleset present for a ruleset. This has been resolved. | Case Management |
| INC-267671 | 830168 | Show results in new window working in Case Worker portal | After update, searching for a work object in the Case Worker portal and clicking "Show results in new window" incorrectly displayed 1000+ records. Investigation showed the pySearchString was incorrectly passed to D_pyWorkSearch as pyDisplayHarness.pySearchText instead of pyPortalHarness.pySearchText, and this has been resolved by updating the parameter configuration in the section pyShowResultsInWindowWrapper to send SearchString param as D_pyWorkSearchPreferences.pySearchString. | Case Management |
| INC-270434 | 821788 | Duplicate attachment check updated for iOS | In work done previously, a change was made to append a UUID to the attachname when the device = mobile and browser = Apple Safari. This was done to prevent photos captured through the camera app from being treated as duplicates when being attached to a case and was in response to the iOS default of naming all of the camera uploads as "image". As a side effect of this, UUID was also added to the images/photos uploaded through the gallery/library of an iOS device with the result that uploading a previously taken photo called 'image_205589' became a unique filename with the UUID added which was able to bypass a check for duplicate uploads. To address this, an update has been made to only add the unique ID when the filename is exactly equal to "image" and the upload is from an iOS device. | Case Management |
| INC-270806 | 803763 | GetNextWork conditional assign actions loaded correctly | When GetNextWork is used to pull a case from work queue, the assign actions are determined before the case is moved to the user worklist. However, a few assign actions contained 'access when' conditions based on worklist or workbasket and assigned user or work queue, and these assign actions were not loaded correctly. Investigation showed this was caused by local actions not being repopulated when there was a context change, and this has been resolved by setting the RepopulateActions parameter as true so the MoveToWorklist activity will populate the actions correctly when GetNextWork is performed. | Case Management |
| INC-270931 | 816423 | Virus check available for Survey | A call virus check activity has been made available for uploading files through Pega Survey. | Case Management |
| INC-A10602 | 823168 | Corrected security error on HTML sections | Flows that call the activity ShowNewFlow with HTML stream 'NewFlow' were generating a 403 Forbidden error. This was a missed use case for BAC implementation, and was caused by the ShowNewFlowHtml and StartNewFlow activity missing the necessary encryption in the NewFlow HTML rule. This has been corrected. | Case Management |
| INC-A14336 | 827366 | Updated radio button control used in TransferCaseOwnership | After update, radio buttons disappeared on click in a section using pyTransferCaseOwnership. This was due to an incomplete cleanup for a deprecated radio button control used in the section rule and has been resolved by removing the deprecated control and adding the current pxRadiobuttons control to replace it. | Case Management |
| INC-A14973 | 827353 | FindWorkGadget control deprecated | After upgrade from Pega Platform version 7.2 to Pega Platform version 8.7, searching for a case using FindWorkGadget generated the message "Error 403: SRVE0295E: Error reported: 403". The FindWorkGadget control contains the list view control to view the data, which is a deprecated control. This was a missed use case, and has been resolved by deprecating the FindWorkGadget control. Alternate widgets present in the dashboard such as work list, work queue, and the search gadget may be used to find work in its place. | Case Management |
| INC-A15636 | 828131 | Survey questions validated when questions are hidden | After update, Survey Question Page validation was not triggering for Q-1 if the visibility condition for the last question on the page, Q-3, evaluated as false. If the visibility condition for Q-3 was true, validation for Q-1 was triggered. This was traced to the 'when' rule configuration in pzSurveyProcessing which skipped the validation on the question page if the visibility condition was hidden for the last question on question page, and has been corrected. | Case Management |
| INC-A15741 | 833064 | Resolved case date/time shown correctly after actions menu | After returning to a resolved case, clicking on Actions for the available case showed the case update date/time as "A minute ago" even though no action was taken. Opening the case again restored the correct value. This has been resolved by updating the handling for the "pxUpdateDataTime" property in the pzPrepareInternalAssigmentForResolvedCase activity. | Case Management |
| INC-A15836 | 832093 | ShowAllOperators and WorkBasketGadget controls deprecated | The ShowAllOperators and WorkBasketGadget controls were calling the showView activity, which called the deprecated ListView rules and triggered a BAC registration error. As these controls are no longer used directly in the portals and have been replaced with alternatives, the ShowAllOperators and WorkBasketGadget controls have now been deprecated. | Case Management |
| INC-A1709 | 810936 | Added handling for Section Presentation read-only | A 'when' rule to make a property read-only in the presentation tab was not working. Because this is an optimized table, row level expression is not supported. To resolve this, an embedded section will be used for pyCategory instead of a property to satisfy the read-only conditions. | Case Management |
| INC-A18362 | 839585 | Select File(s) button accessible using Nuance Dragon | Nuance Dragon was unable to open a file selection dialog when given the command "Select File(s)". In addition, when using the "Click button" command for buttons which were assigned numbers, the "Choose two" command for the Select File(s) did not open the dialog. This was due to the select file button having been created as a overlay button which did not have any action on it, and has been resolved with an update to the pzMultiFilePath control to add role="button" and aria-label="<%=buttonName%>" to the input element to improve accessibility. | Case Management |
| INC-A20546 | 834823 | Corrected post-cancel Create focus | After navigating to create a case using the Create Menu, selecting Cancel and Delete on the confirmation modal dialog did not return the focus to the Create menu as expected. This has been corrected. | Case Management |
| INC-A22781 INC-B2703 |
840711 852718 |
FlowDependency page handling updated | In Activity pxCheckFlowDependencies step 16.5, a call to System-Queue-FlowDependency.pzSpawnQueueItemForFlowDependency is used to create and then remove a page named pyQueuePage of context System-Queue-FlowDependency. However, since the name of the primary page during the QP Execution is also pyQueuePage, the Page-remove step does not remove the page because it has the same name as the primary page. This has been resolved by replacing all the references to pyQueuePage with pyFlowDepQueuePage in the pzSpawnQueueItemForFlowDependency activity so the FlowDependency page will be created and removed as expected. | Case Management |
| INC-A23928 | 839043 | Improved security for PDF generation | Cross-site scripting protections have been updated for dynamically generated PDFs. | Case Management |
| INC-A26232 | 840734 | Added missing property for case opened by inbound email | A runtime error was seen on the dispute transaction page of a case created via inbound email indicating an undefined property, pyWorkPage.pyRelatedWorkList(1).pyRelatedWorkClass. This has been resolved by adding the property pyRelatedWorkClass for the Java step of GetRelatedWork. | Case Management |
| INC-A4335 | 822965 | Handling updated for security alert on case submission | A section included on a data page which was flushed and recreated on click of a button reloaded correctly in the UI, but the PDC registered a SECU0001 alert. This has been resolved by modifying the newAssignPage.pyCurrentActionLabel property from hidden control to Text input to mitigate these alerts. | Case Management |
| INC-A4692 | 813316 | Custom guardrail warnings made available for Rule-PegaQ-Question and Rule-PegaQ-QuestionCollection | Support has been added for customizing the CheckForCustomWarnings activity in Rule-PegaQ-Question and Rule-PegaQ-QuestionCollection classes by making the activity available. | Case Management |
| INC-A8610 | 834033 | Added missing property for Access control policy | Adding Access control policy on Assig-WorkBasket class caused an issue with visibility of flow actions and the "GO" button was hidden. Investigation showed the AssignPage, which is passed as the argument to the have haveAccess method, did not have the needed pxApplication property which is used in Access control policy condition. This has been resolved by adding the pxApplication property to assignPage in the pxCreateAssignmentFromFlowPage function along with updating the pyPopulateAssignmentContents and pyPopulateCaseContentsWrapper activities to add the pxApplication property onto the D_CaseAssignments page. | Case Management |
| INC-A9499 | 826846 | Corrected CoveredHeaderForReview error | A 403 error was generated after approving a campaign and clicking the case name. This was caused by a missed use case in making activities compatible with BAC, and has been resolved by updating the encryption. | Case Management |
| INC-A9603 | 827567 | Performance improvements for bulk processing | Performance issues were seen when using additional filters during bulk processing. This was traced to non-optimized properties for the LookUpList activity in the pzGetPropertiesToUpdateInBP activity, and has been resolved. | Case Management |
| INC-A9617 | 822061 | Handling added for double quotes in survey questions | When a page with a question that contained a double quote ( " ") was displayed, the message "Exception occurred in Rule-HTML-Section for Question" appeared and the question was not rendered correctly in the Rich Text Editor. This has been resolved by adding logic to escape double quotes in survey questions. | Case Management |
| INC-A9870 | 822962 | Switch application gadget reloads correctly after UI refresh | After a refresh occurred on the main user portal thread, the Switch App Launcher only loaded the search bar and required a page refresh in order to get the gadget to function correctly. This was a missed use case and has been resolved by moving the style bundle outside the onlyonce tag to load the CSS for switching the application gadget. | Case Management |
Cloud Services
24.1 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A15258 | 833031 | Logging added to assist in diagnosing import issues | Additional diagnostic logging has been added to assist with tracing issues related to serialization during the import of RAP or third party jar using a client-specific application other than the PegaRULES application. | Cloud Services |
| INC-A16382 | 831071 | Added handling for non-fatal rollback errors | After initiating a rollback, trying to use getStatus for the rollback failed with an error. Reviewing the logs showed that there were issues with the rollback itself, and investigation traced this to the operator who was doing the rollback also being part of the rollback. This has been resolved with an update which will clear the processing status when a non-fatal error occurs opening the instance. | Cloud Services |
| INC-A18016 | 836391 | Instance picker updated to better handle missing columns | The instance picker for RAP form used for individual instances to include encountered issues with some data instances if the Rule-Admin-Product.pzQueryClassInstances activity contained an obj-browse step that included pyRuleSet, pyRuleSetVersion and pyLabel. These are only reliably present for Data-instances. To address this, an update has been made to enable the instance picker to work with missing columns. | Cloud Services |
| INC-A18235 | 830173 | Default classpath mode updated to avoid class conflict on import | Import using prpcUtils in hybrid mode was failing in one environment with a class conflict issue between versions of classes on the file system and in the database. This has been resolved by updating the default classpath mode to database for prpcUtils and static assembler. | Cloud Services |
| INC-A20851 | 835420 | Code loader updated to avoid Windows password issue | Running the command line upgrade process with WebSphere/DB2 was failing if the password contained the special characters ‘^’ and ‘#’ . This was an edge case related to Windows CLI handling and specific to the install/upgrade script and the code loader task. To resolve this, an update has been made to invoke the code-loader with a java task instead of on Windows to avoid issues with special characters. | Cloud Services |
| INC-A21157 | 838677 | Updated authorization handling for reindexing requestors | The execution of a column population job was stuck and not progressing. Investigation showed the required authentication for the reindexing requestors was missing for the use case of an imported archive containing a class that contained an externally mapped property that was the target of a declarative expression whose value was retrieved from a Data Page load activity. This has been corrected. | Cloud Services |
| INC-A29698 | 848381 | Handling improvements for column population during heavy use | Several updates have been added to mitigate issues with column population jobs that have exceptionally high counts of classes: The calculations in the IntegerRoll class have been modified to mitigate the risk of overflow of the the java int capacity (up to Integer.MAX_VALUE). During schema import, the systems will fall back on the list of classes in the archive if building the class list for internal tables fails. If this occurs, a warning will now be logged indicating the failure happened and that not all necessary column population jobs may have been generated. The total instance count query has been optimized so that it will try to utilize columns in a single index. For internal tables, it will try to use a pxobjclass index if one exists, otherwise, it will filter using pzinskey. Column population jobs will be saved even the system fails to calculate the total instance count. If this happens, the instance count will be written as "-1" and the agent will attempt to recalculate it when the job is picked up for processing. If this second attempt also fails, the column population job will be treated as failed. |
Cloud Services |
| INC-A4383 | 811137 | Update to Oracle datetime handling | When trying to import a schema jar, the error "pzCurrentComponent: The following SQL statement contains a change to column type. Type changes are not allowed." was generated. This was traced to the Oracle driver reporting DATE columns as JDBC type TIMESTAMP during the import, and has been resolved with an update to treat all datetime types on Oracle as TIMESTAMP for better portability to other platforms. | Cloud Services |
| INC-A4542 | 816774 | Corrected Rulebase Compare logic | Using the Rulebase Compare tool to compare rulesets from two different environments was not working as expected, with results being returned from non-specified rulesets. This has been resolved by updating the logic used to compare the rules. | Cloud Services |
| INC-A7463 | 814197 | Warning added for restricted index not added to export | When exporting work history tables, one particular index was not being added to the RAP and no warning was seen. The root cause for the index not being added was that the index was restricted by a block list, and an update has been made to log a warning message when this occurs. | Cloud Services |
Conversational Channels
24.1 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-270877 | 823578 | GetAvailableEmailAccounts and GetAllEmailAccounts use current application stack | When using two implementation applications, the pzGetAvailableEmailAccounts activity was fetching all the instances of the Data-EmailAccount objclass irrespective of the application. However, for some of the email accounts the incorrect ruleset was picked, causing errors in the logs. To resolve this, the GetAvailableEmailAccounts and GetAllEmailAccounts activities have been updated to pick only email accounts which belong to the current application stack. | Conversational Channels |
| INC-A10994 | 842380 | Email manager supports rich text | Rich text support has been added for the email manager. | Conversational Channels |
| INC-A1210 INC-A28404 |
825709 851540 |
Updated handling for missing file type extension on email processing | A java.lang.IllegalArgumentException error was logged with the message "FileExtension may not be null or blank for filename ../datacontent/Image/social/pulse_123456-0". Investigation showed the pyGetHtmlMessage activity was iterating through the email attachments/inline images during the processing of an email triage case and then creating the Data-Content-Image entry for it as part of the pySaveFileToImageContent activity. Because the file did not have any extension, pyAttachMimeType and file extension were null for the attachment /inline image. To resolve this, an update has been made to the pzAttachUploadedFile, pzCreateInteractionReply, and pzCreateExternalPostFromMail activities which will extract the mime-type information in the attachment encoding property and save it with an attachment file. If that also fails, the system will proceed and save the attachment as is. | Conversational Channels |
| INC-A15747 | 831713 | Support added for special characters in email address | An email address was detected as invalid if it included special characters in it such as "+" or "-". This has been resolved by modifying the Reply / Reply All logic to allow special characters in a customer email address. | Conversational Channels |
| INC-A21364 | 834219 | Mandarin added for messaging widget | The Digital Messaging widget now supports replies in Mandarin. | Conversational Channels |
| INC-A21693 | 841153 | Inbound email handling updated for disabled NLP | An OutOfBound Exception was being thrown during the InboundEmail interaction case creation. This was traced to a customization of CPMSetDataEntities which removed the reference to the data transform SendFeedbackToNLP used to execute the activity CSSendFeedbackToNLP. Because natural language processing analysis was skipped, TASummaryID was not present and the history record fetch failed. This was due to the system assuming NLP is always enabled, which is not a valid assumption. To resolve this, an update has been made to check for pyMode (Inbound/Outbound) instead of of pyTASummaryID to determine inbound emails. | Conversational Channels |
| INC-A25002 | 845063 | Corrected attachment visibility property handling for deferred load | The email interaction flow was going into an error state when wrapping up an Interaction case. This was traced to the pyPostEmailContent for attachments visibility using an auto-populated property value instead of the correct data page value when pyDeferLoadEmails was true. This has been resolved by changing the visibility condition to 'always' for the attachments dynamic layout in pyPostEmailContent and pyPostEmailContentV2. | Conversational Channels |
| INC-A25392 | 842466 | ElasticSearch initialization made more robust | During ElasticSearch initialization, the error "Initialization of full text search is either in progress or has failed on this node. Please check the logs if search initialization is complete." was generated, and some emails were missing from the search. This was traced to Elasticsearch failing to initialize correctly on background processing nodes, causing pzUpdateTriageWork to not find the referenced case ID present in an archive index. To resolve this, error handling has been updated and page-clear and activity-clear messages have been added to clear error messages in the archival activity called from pzupdateTriageWork. | Conversational Channels |
| INC-A2589 | 808610 | Empty and not empty validation added to pyValidate | After update, cases were not getting created for some case types when using the ServiceHub email channel. This was traced to a configuration issue. The configuration could not be changed because channel save was failing with the error ".pzRouting.pyRouteTo(2).pyConditions(1).pyCompareTo:Invalid topic", which was occurring because routing condition "Topic -- Is empty" was selected, which is not supported. To resolve this, empty and not empty validation has been added for Topics in the pyValidate rule. | Conversational Channels |
| INC-A4292 | 819619 | Corrected highlight markup for entity | The entity word was not highlighted when it was the last word of the subject and the first word of the body. This was an issue is with MarkJS and has been resolved by adding a space between <br> tags. | Conversational Channels |
| INC-A8248 | 819615 | Corrected HTML tags shown in email | After update, incoming correspondence showed the full HTML code instead of a readable text without the HTML tags. This has been resolved by updating the pyTreatIncomingText activity to force creating an email html attachment regardless of the "As Html attachment" setting on the listener, and by adding a new rule pyCheckAndCreateEmailContent to create email-content file in cases where the body has <html>. | Conversational Channels |
Data Integration
24.1 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-214354 | 722344 | MethodStatus made available in Rule-Declare-Expression | After update, attempting to select the Declare Expression Record type in Dev Studio failed to list any records. This was traced to the "filter by application context" using UDFs which attempted to consider pyMethodStatus when the applies-to class was Rule-Declare-Expressions, and has been resolved with a schema change to expose pyMethodStatus in the rules.pr4_rule_declare_expression table. | Data Integration |
| INC-230002 | 820149 | Updated handling for incorrect chat agent availability | An intermittent issue was seen where an agent was not getting chats even when active and marked as Available in the queues. The chat routing engine makes a decision on the correct agent based on their presence status. Under some conditions such as a network interruption this status could be set incorrectly and no more chats would be delivered even when the network connection resumed until the agent logged off and on again. To resolve this, an update has been made to modify the push-notification message system by sending back a client acknowledgment which confirms that the message has reached to the subscriber. Success and failure handler activities have been added which will be invoked based on whether message has reached subscriber or not. For this function, the DSS "prconfig/server-push/message/clientacknowledgementenable/default " must be set to true. The flag "Enable acknowledgements for Notifications" has been added on the channel rule form and needs to be enabled for the channel which needs client acknowledgement messages in order for the message to be published on the channel. Please note that different channels having same Applies To class should either enable or disable this flag. This flag needs to be the same on those type of channels. | Data Integration |
| INC-237044 | 744186 | Documentation updated for manually generating and applying the DDL | The Deployment documentation has been updated to clarify steps for generating and applying DDL for an upgrade if you do not want the upgrade to automatically apply the changes. | Data Integration |
| INC-243875 | 767991 | Added handling for special characters exception | An exception was generated when special characters were entered in the root cause description or solution description of a case resolution. This has been resolved by adding exception handling to the pxContainsViaRegex function. | Data Integration |
| INC-258450 | 794919 | Corrected intermittent compilation error | An intermittent component compilation error was generated if a specific When condition was called. This has been resolved by adding a missing import statement in When rule compilation unit builder. | Data Integration |
| INC-261780 | 815390 | NodeID max length increased | After update, attempting to sort the list of nodes resulted in the error ".pxResults(4).pySysNodeID: "pega-selektionen-background-pu-app-0" is too long, maximum length allowed is 32". This has been resolved by updating the System-Status-Nodes property pySysNodeId size to 64 to handle node names that exceeded the 32 character length. | Data Integration |
| INC-262203 INC-A16665 |
804497 831598 |
Corrected SQL generation for purge/archive | When the PegaArchival job scheduler was run, the error "Type pegarules. pub. PRRuntimeException" was generated. This was traced to incorrect SQL being generated due to the same type of child case being present at leaf node and elsewhere in the hierarchy, and has been resolved. | Data Integration |
| INC-262866 | 807688 | Connect-REST wizard data page handling updated | When using the Connect-REST wizard and choosing the data page label and data page ID, setting the data page ID at the final step was ignored and instead the connector ID name was used for the data page ID. This has been resolved with an update to properly consider the editable data page name and to use the data source name as fallback if the configured data page name is not proper. | Data Integration |
| INC-263633 | 811321 | Sensitive data filtering added for JSON logging | In order to ensure potentially sensitive data is not included in the log file as JSON output, an inclusion list has been added to determine which fields should be present. | Data Integration |
| INC-264088 | 818248 | Support added for PEC-signed emails | When a certified email using PEC (posta elettronica certificata) was received, the original message of the email was not displayed. In order to support this use, the class "JavaMessageParser.java", which handles content extraction when using IMAP, has been updated to handle email of content type "application/pkcs7-mime". | Data Integration |
| INC-264237 INC-A5045 INC-A15993 INC-A26087 |
830754 833814 832065 840127 |
Calendar Object found after recycle | The Calendar entry was not getting picked properly in production environment after JVM recycle. This has been corrected. | Data Integration |
| INC-265376 | 821731 | Corrected duplicate emails being forwarded upon error | Emails were randomly getting struck in the inbox and the same message was being repeatedly processed until manually removed from the inbox. This caused the system to send multiple emails to the forwarded email ID. This initial issue was traced to a third-party JSoup parser library which was throwing an exception on an unexpected empty value, and handling has been added for that exception. In order to prevent sending multiple copies of a failed email, a check for an existing DuplicateKeyException has been added so only one email will be forwarded per failure. | Data Integration |
| INC-267735 | 830291 | Resolved PageCannotBeSerializedForPassivationException error | Non-serializable java object values were being left behind on the thread parameter page as a result of parsing the SOAP response XML. This caused a PageCannotBeSerializedForPassivationException when the requestor attempted to serialize the parameter page. To correct this, code has been added to the Rule-Connect-SOAP Invoke and InvokeAxis2 activities and the ParseRuleUtils java module to clean up the parameter page after executing the connector or parse rule. | Data Integration |
| INC-269067 | 824702 | Updated file closure for static content server | The static content server was holding files open, eventually leading to the error "Log4j2-AsyncAppenderEventDispatcher-1-ALERT-ASYNCAES ERROR Cause: java.net.SocketException: Too many open files". This has been resolved with an update to close the InputStream properly to avoid leakages. | Data Integration |
| INC-269469 | 818596 | Added handling for WrongModeException | When a case was passivated and reactivated, the case/portal was hanging and the error "pegarules.pub.clipboard.WrongModeException" was logged. This occurred when the case referred to a page property in a report definition which was sourced by a data page, and has been resolved by adding handling for a WrongModeException when a page is being activated. | Data Integration |
| INC-270119 | 817203 | API added to clear archival CSV files from tmp directory | High disk utilization on utility nodes caused them to frequently recycle. This was traced to extremely large archival CSV files taking up most of the disk space in the tmp directory, pulled in by a job that opens hundreds of service cases at a rate which exceeded the capacity of the normal purge process. To resolve this, a new API has been added, removeArchivedTempFile(String aInstanceHandle). This can be used in a java step such as pega.removeArchivedTempFile(pzInsKey) and will remove the temporary archival CSV file for a given handle [pzInsKey]. It returns true if the file has been found & removed; otherwise it will return false. | Data Integration |
| INC-271722 | 805708 | Updated JSON logic for embedded arrays of same name | An incorrect JSON string was created when an embedded Pagelist Clipboard Page was serialized. This was traced to a nested array structure with the same attribute name in child and parent which caused pre-popping of the JSON Element from mapping context.This has been resolved by updating the logic to not pop until execution is completed. | Data Integration |
| INC-272293 | 833699 | populateActivity method updated for PATCH | After setting up Service SLA with fallback activity in REST service, the response body did not appear at all for PATCH method. This has been resolved by updating the populateActivity method to populate for PATCH method as well. | Data Integration |
| INC-273213 | 820381 | Corrected nested data transform execution | After update, calling a data transform inside another data transform was not working as expected. This has been resolved with an update to enable declare processing when needed for DataTransform execution. | Data Integration |
| INC-A10091 | 830306 | Updated pxConvertPageToString for converting JSON | Discrepancies were seen in the output of pxConvertPageToString depending on whether the CasePage was JSON or XML when there were “Ref” properties that referenced data pages. Investigation showed there was an issue the prevented page properties that used "refer to data page" from showing in JSON. This has been resolved with the addition of a new pxConvertPageToString function to accept the parameter if reference properties should also be expanded to support JSON references to datapage. | Data Integration |
| INC-A1049 | 815399 | Additional stack trace logging added to ConvertPageToString | A function used in multiple places to convert clipboard page to JSON format was generating an exception due to invalid inputs while performing ConvertPageToString, but logging was not able to help identify where the problem was originating. To resolve this, a new exception has been added to the ConvertPageToString function which will print the stack trace to help identify the source of the null Clipboard page. | Data Integration |
| INC-A11245 | 822832 | Added database type check for VacuumFreeze | After upgrade, the the job scheduler "pyPegaArchivalVacuumFreeze" was failing with the error "There was a problem getting a list: DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-00900: invalid SQL statement". This was caused by the PostgreSQL command VacuumFreeze encountering an Oracle database, and has been resolved by adding conditional handling on execution of connect-SQL to run the command for PostgresSQL databases while skipping other database types. | Data Integration |
| INC-A11557 INC-A28696 INC-A24588 |
828719 844494 847168 |
Updated data transform to use correct context for embedded properties | When using a JSON data transform to output an object with a property Page List, the properties were not being correctly mapped after encountering embedded pages. This has been resolved by popping the clipboard context after Append and Map to action. | Data Integration |
| INC-A12214 | 826255 | Resolved timeout errors when using MSGraph | Sites which upgraded to MSGraph and blocked the default SMTP host smtp.office365.com were experiencing extraneous connection timeout notices related to the SendEmailNotification and SemSImpleEmailMessage activities due to an unused legacy connection call made by the JavaEmailClient constructor during the process of converting MSGraph messages to MimeMessages. To resolve this, the variable JavaEmailProfile::skipConnect has been introduced to skip the call in the JavaEmailClient constructor for sites configured to use MSGraph. | Data Integration |
| INC-A12865 | 826009 | Currency input format corrected for en_ZA | After update, the currency input data format for the en_ZA locale generated the error "Not a Valid Decimal value". This was an inadvertent side effect of previous work to ensure the thousand separator and decimal separator are displayed as space and comma respectively, and has been resolved by updating the grouping separator from the literal " " to the space unicode " ". | Data Integration |
| INC-A13061 INC-A26573 |
828671 846529 |
Check added for custom associations history class | After adding associations for the standard classes Link-Tags, Link-Association-Follow, and Link-Association-WorkBookMark, the casetype archival fails. This was due to the custom associations missing properties, and has been resolved by adding a validation condition to check whether the history class for a given class is present, and if not it will not be added to Data-Archival-Batch (DAB). | Data Integration |
| INC-A14416 | 828038 | Updated handling for email meta tags | The email listener was not processing some specific set of emails and throwing an exception. This was traced to the messages containing a meta tag charset with a varying number of attributes and different meta tag combinations and has been resolved with updated handling. | Data Integration |
| INC-A16919 INC-A15380 |
839468 839970 |
Documentation updated for REST API date format conversion | Effective with Pega version 8.8, DX APIs started emitting date/time in ISO format and the Clipboard started supporting ISO date/time formats. Information about this behavior change has been added to the ISO date/datetime API documentation for the Clipboard behavior. | Data Integration |
| INC-A17736 | 830587 | Security updated for debug logging | Potentially sensitive information could be logged when Debug was enabled for the RestConnector class. This has been addressed with an update which will mask the information. | Data Integration |
| INC-A17907 | 831933 | Null check added to temp file deletion | A null pointer exception was generated from the MultipartRequest.deleteFilesFromTempDirectory call after submitting a page with uploaded files. This has been resolved by adding a null check condition. | Data Integration |
| INC-A18106 INC-A25696 INC-A1570 |
839070 844706 832944 |
Archived pegasocial-document display as expected | Attachments were not displaying for pegasocial-document archived cases. This has been corrected. | Data Integration |
| INC-A19576 | 835369 | References to pzGetLocaleListSeperator updated to pyGetLocaleListSeparator | After update, extracting data for 3rd party stopped working. This was traced to the comma having been replaced with a semicolon in the locale list separator, and has been resolved by changing the outdated references to pzGetLocaleListSeperator to the new pyGetLocaleListSeparator. In order to preserve backwards compatibility, pzGetLocalSeperator will be utilized as a wrapper that calls the new pyGetLocaleSeparator. | Data Integration |
| INC-A20809 | 837408 | Corrected Date Range control change event timing | When a Date Range control was configured with a refresh section or post action on change, three separate network requests were sent to the server. If there was an attempted interaction with the Date range control while waiting for a response from the server, the date range control stoped functioning. On clicking the date input, the calendar opened and closed right away. This has been resolved with an update which will fire the change event on the start and end dates only when the value changes, and the extra change event on StartInput which is causing the third network call has been removed. | Data Integration |
| INC-A20996 | 840039 | REST connector supports lax redirects | Support has been added to allow enabling lax redirecting for the REST connector by adding handling for a blank or null host for lax redirects and corresponding tests. | Data Integration |
| INC-A22454 | 843850 | Corrected en_NL localization issues | After update, the DateTime field with calendar and decimal field were not working in the case manager portal when using the "en_NL" locale. This was traced to a change in the underlying JDK version used, where discrepancies in data returned are seen with JDK 8 and JDK 11. To resolve this, a locale XML file has been added, en_NL.xml, which returns the needed data irrespective of the underlying JDK version. | Data Integration |
| INC-A24163 | 838213 | Case Archival documentation updated | Documentation has been updated to specify that Case archiving is available for on-premises and Cloud Choice clients for only the following databases: PostgreSQL, Oracle, and MS SQL. | Data Integration |
| INC-A24646 | 843339 | Corrected check in error for Connect-JMS | After checking out the Connect-JMS rule, checking it in generated the error "CheckIn was unsuccessful. Original Instance does not contain Lock Information. Original Instance Handle : RULE-CONNECT-JMS @BASECLASS". This has been resolved by modifying the when rule pzSaveRefresh of @baseclass to be set to true for private edit so the latest rule set is picked up and the check in will be allowed. | Data Integration |
| INC-A24930 | 843345 | Corrected attachment delete after switch to new repository | View/Download actions were working after switching to a new repository, but deleting attachments failed. Investigation showed pzDeleteFromRepository was using application settings instead of fetching the repository information from the work/link attach tables, and this has been resolved. | Data Integration |
| INC-A25464 | 846990 | Expunger updated for use with CloudK environments | Archived cases were not deleted from secondary database as expected, and the error "Skipping expunge, environment is not running in the Pega Cloud." was generated. This was caused by Expunger using a validation logic which was only valid for Cuttyhunk-based environments. This has been resolved by updating Expunger validation for use in CloudK environments. | Data Integration |
| INC-A25973 INC-A14410 |
846837 836508 |
URLs in archived cases can be opened | A URL attached to a case could not be clicked to open after the case was archived. Investigation showed the Link-Attachment instance of Note and URL were archived so attachments were visible, but the Data-WorkAttach-Note and Data-WorkAttach-URL instances were not moved to file storage so the attachments of those types could not be opened. This has been corrected with an update to support archival attachments of type Data-WorkAttach-Note & Data-WorkAttach-URL. | Data Integration |
| INC-A26768 | 843357 | Improved Client for Windows sync performance | The delta sync in Pega Client for Windows was very slow when posting multiple cases to the server. Investigation showed there was an SQL query being called twice in each delta sync, and this has been corrected to improve performance. | Data Integration |
| INC-A26836 | 846727 | Additional time zones supported for GMT conversion in en_US localization | Support has been added for converting the Singapore, Auckland, and Sydney time zones to GMT through the FormatDateTime(strDateTime, strPattern, strTimeZone, strLocale) function when using the en_US locale file. | Data Integration |
| INC-A27233 | 849753 | Added failsafe to Redux ClipboardPage for missing reference | A context switch generated the exception "Caused by: external.clipboard.StacklessUnsupportedOperationException: Because lightweight clipboard mode is enabled, execution has failed. Message : Property is a reference or autopopulate property and is currently not supported by redux. on property reference". This has been resolved by adding support to Redux ClipboardPage so it sets a value for the reference property when one is not present. | Data Integration |
| INC-A27482 | 842099 | AddContainerItem handling updated | The Constellation UI was not loading. Investigation showed the deferload tab was considering the resourceType as 'CASE' when the correct value should be 'PAGE'. To address this, an update has been made to set resourceType as 'PAGE' when calling addContainerItem from loadPortalView. | Data Integration |
| INC-A28342 | 850917 | View renders when embedded property is empty | When a table view on Work-A was sourced from DataPage (sourced from Report) defined on Work-B and Work-B had an embedded SinglePage property on Data-X, the view failed when property Data-X.Prop1 was empty. When the property had value, the view displayed correctly. This has been resolved by updating the handling in the PagePropertyRenderer component which registered the child components of Scalar list values as form fields. Note that only optimized properties will be supported for being added as columns. | Data Integration |
| INC-A28382 | 851460 | Pega-Social attachment retrieval updated | An update has been made to recover Pega-Social documents which were not archived properly by using a hybrid approach to fetch the Rich Text attachment from the primary database if it is not present in secondary storage. | Data Integration |
| INC-A28710 | 844459 | Updated child thread cleanup | After upgrade from Pega version 7.1 to Pega version 8.7, information from one case was carried over to the next and the error "Existing entry overwritten for WORK-OBJECT-PAY xx-xxxx" was logged, where the object identified was from the original case. This was traced to thread destruction not occurring correctly, and has been resolved by updating the API so that if any children are detected while cleaning up the parent thread, those children will also be cleaned up. The use of parameterized data pages is also recommended in order to ensure the page being used is related to the case at hand. | Data Integration |
| INC-A3080 INC-A7375 INC-A13372 INC-A13926 |
826982 829120 829704 836860 |
Updated handling for throttled websocket connections | After idling, issues were seen with refreshes happening when no action was performed, the portal notification count badge had an incorrect count, or the error "Unable to find presence agent with Application" intermittently appeared when a call was coming in. This was traced to some browsers throttling connections when idle, causing websocket timeouts. To resolve this, updates have been made to the PresenceSessionStateTrackerDaemon to handle websocket throttling. | Data Integration |
| INC-A3880 | 812959 | Date field usage clarified | To avoid input issues, the usage details of the pxDateTimeisPastOrFuture function have been updated to explicitly state that 0000 is not a valid year for the input. | Data Integration |
| INC-A4594 | 822068 | Support added for custom S3 endpoint | In order to support the use of a custom S3 endpoint, updates have been made to enable a Path style request based on DSS, enable endpoint configuration based on the Service Endpoint URL, and honor the custom service endpoint URL from the DSS to create a system repository. | Data Integration |
| INC-A5354 | 828985 | Email format retained for auto generated request | After updating Microsoft Office 365, the previous structured format for auto-generated email requests was changed to plain text email. This was traced to HTML handling relating to MS Graph: HTML new line characters and spaces are expected to use < >, but for the auto generated emails \n was present instead, and part of the processing was to remove the new line characters (\n). This has been resolved with an update to address the email message HTML formatting issues by retaining the original data. | Data Integration |
| INC-A5522 | 817417 | Corrected localized RuleSet List Name and LocalePattern name | After updating from Pega Platform version 8.5 to Pega Platform version 8.8, attempting to import a RAP file failed with the error message "Found exception running import: com.pega.pegarules.priv.deploy.DeploymentException: PegaArchiveException RuleArchiveLoader.importContents(PegaArchive) Unable to import file: rules.jar because a problem occurred during import: java.lang.StringIndexOutOfBoundsException". This was traced to the localized RuleSet List Name and LocalePattern name starting with "de", and has been resolved by adding an underscore (_) as a prefix to the localePattern variable name. | Data Integration |
| INC-A7067 | 822143 | ABAThinDebugLogger made available | The present ABA loggers generate an excessive number of messages, rendering it challenging to keep them enabled for extended periods to determine the root of the issue. To assist in debugging issues such as an incorrect rule from a different class being rendered during runtime, a new ABA logger "ABAThinDebugLogger" has been introduced which is very thin and can be turned on for longer period on production environments. | Data Integration |
| INC-A7133 INC-A13072 |
817431 823833 |
Corrected en_SG locale datetime | After update, the datetime calculations in the SGT locale were incorrectly displaying as GMT + 8. This has been resolved with the correct format for the en_SG locale. | Data Integration |
| INC-A7781 | 819136 | Error message security udpated | In order to prevent potential security issues, an update has been made to limit the amount of information publicly disclosed in detailed error messages related to available libraries. | Data Integration |
| INC-A7878 | 818314 | Data page creation documentation updated for endpoint URLs | Documentation for the endpoint URL configuration in a Data Page has been updated to clarify that only string literals are accepted and parameterized Data Page references are not supported. | Data Integration |
| INC-A9085 | 820212 | Corrected PDC illegal argument exception | An Illegal Argument Exception in was seen in the PDC when starting the Listener in the Staging environment. This was traced to a missed use case and has been resolved. | Data Integration |
| INC-A9470 | 840511 | Updated time zone handling for pyGetStartOrEndDate | The pyGetStartOrEndDate function gave an incorrect result when triggered at 11:00 AM. This was identified as an issue with the date formatting function formatInternalDate in the function pyGetStartOrEndDate which considers the GMT timezone for formatting the date. The output was correct for @DateTimeUtils.pyGetStartOrEndDate("currentmonth",false,true), but @DateTimeUtils.pyGetStartOrEndDate("currentmonth",true,true) returned the last day of the previous month instead of the 1st of the current month if the expression was tested before 11AM AEST. This has been corrected. | Data Integration |
| INC-A9934 | 828444 | Extension of Pulse classes archived correctly | On enabling the Archival strategy, classes created under PegaSocial-Post were not indexed and purged as expected. This has been resolved with an update to archive Pulse messages which are descendants instances of PegaSocial-Post. | Data Integration |
| INC-A9983 | 822275 | Connect MQ charset handling updated | When processing response messages, the character set specified by the MQ header in the message (UTF-8) appeared to be decoded incorrectly. Characters within the ASCII range were unaffected. UTF-8 is a variable-length encoding, where characters can be represented by one to four bytes depending on the character code point. Characters like "Å" (a Welsh character) in UTF-8 can be represented by two bytes, but reading them one byte at a time might lead to the "Å" character being split into two separate characters and lead to an incorrect interpretation. This has been resolved by adding support for the MQ connector to read response messages using charset along with byte length. | Data Integration |
| INC-B2674 | 850229 | Support added for retrieving archived Data-Corr-PhoneText attachments | After archiving a case, attempting to open attachments of type "Phone text" generated an error. This has been resolved by modifying the activity pzDownloadArchivedFile to show Data-Corr-PhoneText attachments. | Data Integration |
Decision Management
24.1 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-A4585 |
820337 | Updated label handling in proposition filter | If the value for any condition in the proposition filter was same as the criteria label, compilation failed for the proposition filter rule. This has been resolved with an addition which will wrap all labels with ## to ensure the system is not substituting a value with a label. | Decision Management |
| INC-249372 | 830157 | Corrected file extension for compressed JSON export | When exporting interaction and decision results with compression enabled, the dataset named "InteractionFiles" had the extension ".json" instead of the expected ".json.gz". This has been resolved. | Decision Management |
| INC-253217 | 798092 | Corrected batch compilation error for globally optimized strategy | A decision table with a @GetContextPage expression that was used in a substrategy with a Switch Driver generated an exception when compiled. This has been resolved by correcting the compilation. | Decision Management |
| INC-259934 | 800678 | Improved query performance | A performance issue was seen with database queries. Investigation showed a slowdown related to binding the recipient IDs and notifications IDs caused by the system making database query calls for each bound value, and this has been resolved by replacing the connect SQL call with Native SQL which creates prepared statements so one SQL call is sufficient. | Decision Management |
| INC-270817 INC-A27147 |
823213 841073 |
Updated aggregation partition handling | Real Time Data Grid (RTDG) nodes were continuously restarting. Investigation showed that when handling very big simulation data, the partition of records being inserted became older than current partition, i.e. after an hour the system was still inserting records from the previous hour, causing the aggregation to fail while the collection buffer continued to build up. When the buffer hit the limits related with arrays (due either to current JVM settings or JVM limit) then the JVM crashed and the restart occurred. To resolve this, an update has been made to use a proper limit for the array size and modify the aggregation to aggregate all partitions and not just the current one. | Decision Management |
| INC-273071 | 803235 | Check added to ensure artifacts are checked in before job deletion | When the IngestionDataFlow was checked out while the import data job was deleted, the data job was removed but the checked out IngestionDataFlow could not be opened or checked out to be removed. This has been resolved with an update to check whether all artifacts are checked in before job deletion, and the deletion will fail if any artifact is checked out. | Decision Management |
| INC-A10575 | 827414 | Corrected Visual Business Director time group logic for aggregates | Visual Business Director aggregates by month were incorrect. Investigation showed that when a query groups by time (monthly, quarterly, etc), the records for the last minute of the last month/quarter were missing. A similar query with the 'group by' removed, did include records from the last minute. This was traced to logic which rounded the end timestamp for the bucket to 11:59:00 instead of using 11:59:59, and has been resolved by updating the time binning to use inclusive logic to correctly calculate the end timestamp for the last bucket as passed in the API. | Decision Management |
| INC-A11680 | 839842 | Updated handling for empty PropositionCache | No offers were delivered to customers as Strategy was not importing any offers. Investigation showed the Proposition cache was being refreshed from two different classes which resulted in an empty cache. This has been resolved by checking if cache data is empty or not, and if so, the cache will be refreshed with the correct application context. | Decision Management |
| INC-A11748 | 822083 | Updated handling for duplicate predictions | Multiple versions of each prediction were shown on the Prediction landing page in Prediction studio. Investigation showed these were created in two different classes due to application context, and this has been resolved with an update to ensure if there are two predictions with the same name in different classes then selection will be based on rule resolution. | Decision Management |
| INC-A12371 | 824273 | Handling added for node stuck in queue processor initialization | The real-time data flow was getting stuck in the initialization state. This was due to it waiting for an in-progress partition to finalize, but before it was allowed to fail the data flow was run and it was skipped in the new partition assignment because it was shutting down and was never detected as an unhealthy partition. To resolve this, an update has been made to reset a dead partition when a run is in pending pick up state and has fail intent. | Decision Management |
| INC-A12433 | 826435 | ADM node threads set to max 10 | Previously, the number of ADM node threads was auto-populated based on the calculation "CPU count * 2 - 1". However, in some environments this allowed as many as 200 threads. While the higher number of threads can help ADM in reducing the archiving job processing time, there were scenarios where memory issues were seen. To address this, the calculation now has an added ceiling of 10 threads set in the availableProcessors variable in AdmServiceConfiguration. This value may be configured locally. | Decision Management |
| INC-A12661 | 823393 | BigInt values handled by File Data sets | When using Data flows and File Data sets where one of the fields (AccountID) was configured as bigInt in the source system, the created JSON did not have quotes around it and executing the data flow generated a "Completed with Error" status. To resolve this, support has been added for bigInt values in the parsing logic. | Decision Management |
| INC-A12911 INC-B3007 INC-B899 |
829351 854255 852880 |
ADM model queuing criteria updated | Model Factories were being updated continuously without any changes to the ADM model or when there were no model responses to update. Due to the continuous update, table space was filling and performance issues were seen. This was traced to the Factory table not showing data for the model keys but there were records in the scoring table on Cassandra side, causing unwanted queries to be issued for these 'phantom' models. To resolve this, an update has been made so models are only queued for update by the ADM service when both the time interval is met and new training data is found. | Decision Management |
| INC-A13515 | 824177 | Resolved ADM Node rebooting due to Invalid Factory keys check | An ADM Node was rebooting continuously. At ADM service startup, a database check is run for any factories whose keys have become invalid because they do not contain all of the Context Keys that have been configured on the model rule (e.g. when Context Keys have been added to the rule while there are already existing models which do not have this key). The service will be in a Pending-Joining state until this process finishes. In this scenario, the node was being restarted before the startup had finished, leading to a loop. To resolve this, the invalid factory key check no longer generates empty factories. The ADM node will start immediately even when there are invalid factory keys, and the invalid or empty value keys will be logged. | Decision Management |
| INC-A14125 | 826047 | Corrected Decision Strategy Manager (DSM) API delegation | Obj-sort in activity and Sort in Datatransform were failing with the error "java.lang.UnsupportedOperationException at decision.dsm.strategy. clipboard.DSMClipboardPageAbstract" Investigation showed that when using a batch data flow with a data transform which called another data transform performing the sort action, a new method introduced to execute data transforms for optimized pages in Decision Strategy Manager (DSM) did not delegate to the correct API. This has been corrected. | Decision Management |
| INC-A1479 | 833874 | Ignore case option enabled for Pulse operator search | Operator search in Pulse was not working for SRS elastic search but worked as expected with an embedded elastic search configuration. This was caused by the SRS elastic search system using a case-sensitive query. There is a workaround of extending the rule 'pySearchContextPosts' RD from 'PegaSocial-Message' class, and in filter condition, selecting the 'ignore case' check box for 'pyActor', but this has been resolved by enabling the ignore case option from the setting in report filter for pysearchcontextposts report of PegaSocial-Message. | Decision Management |
| INC-A15306 | 828196 | Removed javascript files for deprecated Visual Business Director (VBD) planner | A cleanup has been performed for legacy Visual Business Director (VBD) planner files which are not in use, including outdated versions of moment.js. | Decision Management |
| INC-A15641 | 827124 | Updated handling for multiple real-time dataflow runs | When using a set of queue processors given very similar names such as CreateCases, CreateCases1, CreateCases2, CreateCases3, CreateCases4, etc, which all used the same queue processor activity CreateCases, stopping the queue processor CreateCases in production stopped all of the other queue processors of the set which then reinitialized, and when any one of the queue processors was started, all of the queue processors were started. This behavior was only seen when the set of queue processors CreateCases{1 .. N} were created by "Save As" of the original rule queue processor without the suffix. Investigation showed that whenever a real-time data flow went to an end state (stopped or failed), wrong assignments were invalidated in a few cases. This was happening because of a deletion query removing a few too many entries due to an incorrectly configured 'like' query, and has been resolved with an update that will only delete accepted assignments for the data flow that is stopping so the other queue processors will be unaffected. | Decision Management |
| INC-A17541 | 832763 | Corrected clipboard handling for Interaction History summary cache | After populating the “pxPegaSummaries” list in the activity and invoking the single case data flow using the pxSingleCaseDDF API by passing the “useOptimized = false”, the execution failed and started throwing the exception "Expected DSM clipboard pages but got com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl". The same configuration worked as expected if “useOptimized=true” was used. This was traced to the Interaction History summary cache returning the wrong type of Clipboard page in some environments, and has been resolved by converting the page to the type defined by the tools before returning it from the Interaction History summary cache. | Decision Management |
| INC-A17949 | 831646 | DSS added to allow Backfill to skip errors | The error "Positions out of order" appeared in the Backfill (BF_Interaction History) dataflow, and the Aggregate dataflow became stuck with failures. This was traced to duplicate Interaction History records in the S3 location. Backfill is configured to fail if there is an error on a record, as errors in records most commonly reflect errors in configuration (e.g. two separate environments pointing at the same S3 repository), but two new DSS setting have been introduced for ruleset Pega-DecisionEngine to allow configuring Backfill to skip errors if desired. - cep/aggregation_service/error_on_backfill_duplicate Values: True/False (default: True). When running Backfill by default the dataflow will register errors if records are out of order/duplicates. Changing this value to false will disable this behavior and ignore these duplicate records. - cep/aggregation_service/max_backfill_errors Values: 0-MAX_INT (default: 0). By default the Backfill run will fail on the first error. This is currently done out of concern for storage errors (e.g. Cassandra read/write problems). This DSS allows this configuration to be changed, for example to handle a small number of invalid records in S3. |
Decision Management |
| INC-A18248 | 842175 | DSS added for expressionCompatibilityMode | After upgrade, expression conditions which checked for blank values were failing. This was due to a change in behavior in the more recent Pega releases where blank and 0 are evaluated as different values for properties such as TrueFalse, Decimal and Integer. In order to improve backwards compatibility, the DSS "decision/strategy/expressionCompatibilityMode" has been added. When set to "true" expressions are handled by SSA programs so that they work similarly to the previous behavior of evaluating blank as equal to 0. When set to "false" or unset, the expression evaluation will use the current behavior. | Decision Management |
| INC-A18449 | 842359 | Case statuse reflected accurately on data migration pipeline | The data migration pipeline showed import case creation failed despite it being created successfully in the candidate environment. This was traced to the service to create the import case returning a time-out error, which was caused by the work object not being committed until it encounters an assignment or a wait shape in the final stage. To resolve this, a wait shape has been added at the beginning in the first flow of the data import case so that the work object is committed as soon as it is created and the service signals the successful creation of the case back to the caller. | Decision Management |
| INC-A19109 | 831792 | Conflicting validation dependencies in ADM resolved | After update, the d-node could not be started. This was due to conflicting validation dependencies in the Adaptive Learning core library and the WebLogic internal module, and has been resolved by updating the version of the Adaptive Learning core library. | Decision Management |
| INC-A20145 | 837293 | Correct null pointer error for nested decision strategies | Decision Funnel simulation was failing in the Strategy execution when the source was a data flow that included another decision strategy as part of its logic. This was traced to a null pointer error when building decision strategy parameter page, and has been resolved. | Decision Management |
| INC-A20805 | 839852 | Tumbling Time Window made more resilient | Some of the Actions and/or treatments were not showing up in the Action Aggregate report, but were showing up in the Interaction History. Investigation showed the events for certain offers remained in the tumbling window for an excessive amount of time when the distribution of records was based on an aggregate partition key and partitions contained varying amounts of records from a few million to a billion. This was traced to some scenarios where the tumbling time window's timestore data could be lost, for example when expanding the Cassandra cluster, and has been resolved with an update to emit records stuck in the window on the very next incoming event. | Decision Management |
| INC-A21199 INC-B1892 |
846500 852565 |
Check added for CDH instance | A PEGA0161 Adaptive Models alert was generated when there was no CDH instance involved. Investigation showed this was related to checking whether the pxHandleResponses dataflow was up because the javascript was placed into the Pega-DecisionScience ruleset. To resolve this, a check has been added to determine whether a DDS node is available for decisioning along with validating if the system has at least one prediction. | Decision Management |
| INC-A21243 INC-A25868 INC-A27923 |
835119 839311 844360 |
Handling updated for DDS service shutdown | If a node scale down happened while a resumable batch dataflow run was in progress, the DDS save operation failed with the error "dsm.dnode.api.ExceptionWithInputRecord: java.util.concurrent.ExecutionException: DdsPrpcConversionException: java.lang.IllegalStateException: Shutdown in progress". This was traced to an explicit check for shutdown in progress in the DDS save operation, and has been corrected. In addition, Cassandra sessions will also be cleaned up during DDS service shutdown when the dataflow service is already stopped. | Decision Management |
| INC-A21605 | 833183 | Updated handling for node partitions check | When performing a batch run, records could be processed multiple times if a scaledown happened during the process. In a batch run, the system will periodically go through all partitions assigned to a node and verify if they are still alive. Partitions assigned to dead nodes are unassigned so that another node can pick them up. However, if a node is STOPPING or LEAVING, it was be considered dead even though it might still be processing, and might therefore be considered unassigned. If another node picked up this partition before the first node finished, duplicate processing could occur. To address this, an update has been made to properly consider all node states that can still be doing the processing as alive, i.e. consider LEAVING and STOPPING states as alive. | Decision Management |
| INC-A22208 | 839233 | Optimized proposition filter saving process | On a site with a very large number of proposition filters, check in was taking an excessive amount of time after each rule change. To improve performance, the process of validating a proposition filter has been optimized and the cache will only be refreshed once instead of for every action to avoid rebuilding the proposition cache unnecessarily. | Decision Management |
| INC-A22506 | 836045 | Updated SanitizedLogicString hash for InstancesCount | Given two actions where each had a specific criteria using a HasInPageListWhen function but with different comparison operator (> 0 vs = 0), only one function was generated in the internal method cache. This produced incorrect results for legacy execution / explain mode and decision funnel due to the result being the same for both actions, and has been resolved by updating the pzSanitizedLogicString hash by including pyInstancesCountValue. | Decision Management |
| INC-A22995 INC-B8955 |
838395 860971 |
Performance improvements for compiling globally optimized strategies | Compiling changes to the GOS_NBA_TOPLEVEL optimized strategies was taking an excessive amount of time. This has been addressed by implementing ForEach SSA compile time optimization. | Decision Management |
| INC-A23959 | 837847 | Corrected StringLength return type | An error in libraries/ssa/ssa-core/src/main/java/com/pega/decision/compute/ssa/function/functions/StringLength.java caused the return value to be _string_ instead of the expected _int_ . This generated the runtime exception "class java.lang.Integer cannot be cast to class java.lang.String". The function StringLength return type has been corrected to resolve this issue. | Decision Management |
| INC-A24131 | 839587 | Top-up can be turned off for browse operation | The browse operation for the Interaction History data set did not work when the Top-up DSS was enabled. When using the interaction history database as a source, the Summary dataset browse operation will get the list of IDs from either the _ih_customer_v2 table or by executing distinct(pysubjectid) on the fact table and then iterating over each key. This implementation was designed to support Top-up, but even when Top-up was turned off the behavior was the same. This is incorrect behavior: when Top-up is turned off it should just browse the summary dataset storage. This has been corrected. | Decision Management |
| INC-A24246 | 838171 | Decision session count shows correct value | There was a mismatch in session counts when capturing decisions and sessions. Investigation showed the Channel Group was not pushing to the PDC due to a property name mismatch, and this has been resolved. | Decision Management |
| INC-A25200 | 843993 | Overhead of DSMClipboardPage size and keySet methods reduced | The DSMClipboardPage implementation was using the keySet method which utilized a ConcurrentHashMap iterator each time to walk through all the key properties defined in the class, regardless of whether they were actually assigned or not, in order to figure out how many of them were actually present in the actual page. To improve performance, an update has been made so that keySet walks only assigned properties and avoids creating an extra iterator. | Decision Management |
| INC-A2548 | 817813 | Able to set pyOutputClassName on simulation reports | After previously creating a database output destination, it could not be selected because it was not visible in the add Existing output screen. This was due to pzGetDataSets being designed to get all data sets in the system without a good filter condition. To support this use, the report definition pzGetDataSets has been updated to only return results for data sets with applies to class starting with "Data-". | Decision Management |
| INC-A25668 | 840995 | Corrected decision data reference validation | Strategy Validation was missing for the decision data reference on strategy save. This has been corrected. | Decision Management |
| INC-A26904 | 846309 | Updated access check for Private Post attachments | Attachments were not visible or available for download when using the “Private Post” option. Investigation showed the GetAttachmentReference activity was failing when calling pzIsPrivatePostAccessCheck, and this has been resolved by changing the parameter handling for the access check. | Decision Management |
| INC-A27229 | 849878 | Updated Prediction Studio email digest generation | After configuring Prediction Studio to send an email digest, notifications appeared but the email was not sent. An AccessDeniedException error was generated. Investigation traced this to insufficient permissions to create a file in the environment, which was due to the system attempting to create a CSV file as part of the email generation process. To resolve this, the activity has been updated to use only stream to generate the notification and not create the file. | Decision Management |
| INC-A27774 | 844425 | Updated error handling for record parsing | If an invalid record was found and then a connection error was encountered during file browsing, the file data set failed during parsing of the records during retry. This was traced to an error in the file dataset implementation where the dataset retried the previous failed record instead of skipping it, and has been corrected. | Decision Management |
| INC-A29495 | 846298 | Sharable link security updated | Cross-site scripting protections have been updated for sharable links. | Decision Management |
| INC-A29641 | 852709 | Added conditional rule handling and exception catch for Globally Optimized Strategies | While saving the GOS strategy, the exception "StrategyParserRuntimeException: Optimization failed to parse "XXXX" using IL parser because The type ILListType<ILPageRecordType[pageClass=XX-Data-Customer, typeRoot=BASECLASS]> is not supported in this context" was generated. This has been resolved with an update which will ignore unresolvable descendants rules when parsing an external-sub-strategy component. If the SSAUnsupportedExprException error is encountered, the system will catch it and fall back to legacy execution. | Decision Management |
| INC-A29685 INC-B7366 |
849543 859033 |
Corrected PropositionFilter simulation/explain calculation | After update, proposition filter conditions that referenced a property on a page in a page list and which were referenced directly in a comparison caused an error in decision funnel execution. This was traced to an error in the PropositionFilter simulation/explain mode which was not retrieving the actual value, and has been corrected. Note: re-save / re-validate the PropositionFilter rules after updating to this version to ensure they are incorporating the corrected function. | Decision Management |
| INC-A29702 | 847177 | Supported functions updated for GOS serialization | An intermittent issue was seen where strategy changes or action and treatment changes were not reflected in external testing and sessions took an excessive amount of time to run. This was traced to a serialization issue when using BAC which prevented some globally optimized strategies from saving into the database, resulting in every node being required to compile the GOS instead of reading it from the database. To resolve this, an update has been made to ensure all standard functions are listed in SupportedFunctions. | Decision Management |
| INC-A3322 | 812065 | Corrected document inline view handling | When using the pyAttachmentFeedDescription control to display attached documents with just minimum details such as type (PDF) and file name but not upload date, operator, etc, the 'when' condition in pxHaveAttachmentInlineViewAccess that evaluates if the document can be previewed was not checking the correct file which was clicked. Investigation showed this function was taking the Inskey of the work object and trying to pull all the attachments linked to the case, then retrieving the attachment(1) from the results that were sorted by pzInsKey. For example, given 10 attachments uploaded into 10 different file categories, trying to open/display the document caused the system to get all documents and take the oldest document (based on pzinskey sorting order) for checking the category access. This has been resolved with an added check in the DisplayAttachFile activity to use the correct page value to check if inlinepreview is allowed for the attachment. The activity will exit if not allowed. | Decision Management |
| INC-A3416 | 824958 | Handling updated for proposition cache refresh | After update, TopLevelNBO was not providing results. Results were given on individual nodes only after running application validation or accessing proposition hierarchy landing page. This was traced to the proposition cache being refreshed from the PegaRules application context. The RAP import which has Actions, Prop filters and other rule types triggered the system pulse which queued the activity pyReloadPropositionCache activity. This queue item was picked up in PegaRules application context when the master agent woke up to process the pending queue items, and the execution caused the system to replace the proposition cache with empty results as there were no issue/groups defined in the PegaRules application context. To resolve this, a 'when' condition has been added which will exit the activity when invoked in the PegaRules application context. | Decision Management |
| INC-A3886 | 809224 | ALT attribute information updated for attached file icons | When a document was attached, the default alt text was "Document type icon" regardless of the type of extension on the file. This has been updated for better accessibility with added field values and a decision table for alt text for attachments. | Decision Management |
| INC-A4475 | 824777 | Corrected condition check for Pulse messages | After update, attempting to post Pulse messages from assignment tasks generated the message "Error in commit:BadTableMappingException: Database-BadTableMapping-TooManyProperties PegaSocial-Message pegadata.pc_work_social PegaDATA". This was traced to the PropertyHasValue method adding a property to the page instead of returning the boolean value, and has been resolved by revising the condition for checking the .pyReference value. | Decision Management |
| INC-A5643 | 826766 | Migrated ADM Rule saves correct ruleset details after edit | After update, privately editing an ADM rule or checking it out and checking it in again resulted in incorrect ruleset details. Investigation showed the migrated adaptive model had different predictors and the adaptive models adjusted the predictors as per the old configuration. To handle this missed use case, an update has been made to sync model configuration to the back-end using rule resolution in all editing scenarios. If needed, the activity Rule-Decision-AdaptiveModel.pySyncModelConfigurations has been made available to manually trigger a complete sync-up using rule resolution. Additionally, a banner has been added to the Adaptive Model rule form to inform that private checkout changes are not synced to the back-end service. | Decision Management |
| INC-A5718 | 815043 | JAWS correctly announces New Task error message | When using Microsoft Edge and JAWS 2022, JAWS did not announce the error message when any field was missing a value on the create task screen on the Home tab. This has been resolved by updating the accessibility of the section to 'component/widget'. | Decision Management |
| INC-A5936 | 819059 | Visual Business Director security update | HTML injection protections have been updated for Visual Business Director. | Decision Management |
| INC-A7802 | 823007 | All relevant records appear on the landing page | If more than 50 strategies were marked as relevant, the Relevant record landing page only showed the first 50 strategies. This was traced to the 'pxLoadRelevantRecords' of class Rule-Decision-Strategy having the checkbox 'Enable Paging' checked, and has been resolved by removing pagination from Rule-Decision-Strategy pxLoadRelevantRecords. | Decision Management |
| INC-A8654 | 816240 | Support added for NBA Explainability and Eligibility Extract | An update has been made to support extracting a customer's list of eligible actions for all interactions in production with details that would explain why an action would not be prioritized against other actions. This is handled by adding a section to the property panel of the Strategy shape in a data flow which allows persisting only a subset of the strategy results to pxDecisionResults for Delayed Learning by choosing a result component in the strategy rule. | Decision Management |
| INC-A8663 | 818622 | Null check added to Interaction History initialization | During initialization of the Interaction History cache, a list of both empty and populated subject IDs was included. This led to the Interaction History failing to load when it tried to process a record with a empty ID for the subject, which then created an issue with the data flow run. To resolve this, a null check has been added to the initialization so Interactions with empty subject IDs will not be included. | Decision Management |
| INC-B11000 | 860415 | Performance improvements for Customer Decision Hub metrics | The activity "PegaAESRemote-Interface-CDHMetricsInfo.PopulateOtherMetricsWrapper" used to publish Customer Decision Hub usage metrics to the Pega Diagnostic Center each hour was causing performance issues. This was traced to the D_pxListFiles API not having pagination, which meant everything was loaded at once. This has been resolved by updating the API so pagination is available. | Decision Management |
| INC-B232 INC-A22043 INC-B702 |
846598 836166 847706 |
Conditional DSS added to skip S3 metrics | The D_pxListFiles utility can cause high memory consumption and lead to an out of memory condition when PegaAESRemote-Interface-CDHMetricsInfo is enumerating files on cloud storage. To resolve this, the DSS SKIPS3STORAGEMETRICSCOLLECTION has been added to allow configuration of this behavior. | Decision Management |
| INC-B2833 | 850409 | Updates to improve performance for tumbling windows | Event Strategies with tumbling window, on a pulse method, were loading all expired groups from Cassandra and loading all aggregates and windows for these keys into memory. This was all done at once without a chunking mechanism, leading to a performance issue that could make nodes appear unhealthy and a process for expiring old windows which required it be repeated from the beginning if a failure was encountered. To improve this, updates have been made to immediately address performance by implementing quota handling for Tumbling Asynchronous windows (both optimized and not optimized). The amount of timeout entries (time -> list of group keys) read from the time store is not currently limited, but there is a limit on the amount of timeouts that will be processed, which limits the number of groups that will be read from the Cassandra. Additional refinements and improvements will be made available in a future release. | Decision Management |
| INC-B4799 | 853560 | Condition label supports hyphen | Support has been added for non-standard labels such as "E-1" or "C-23" attached to condition rows in proposition filters. | Decision Management |
| INC-B4904 | 854713 | Corrected context for nested data transform | After update, data ingestion failures failed for a dataflow with a data transform shape which internally called data transforms based on embedded properties. Investigation showed that the context was not getting set correctly for the embedded data transform dataflow when it referenced a nested data transform, which was traced to the platform clipboard taking the class of the step page by default and only falling back to the class name from the argument when it's not available. This was a missed use case for resolving a data transform in DSM clipboard, and has been resolved. | Decision Management |
| INC-B5742 | 856016 | Updated handling of authenticated anonymous user in FUA | A globally optimized strategy compilation for Customer Decision Hub was failing on first use assembly (FUA) due to an authentication error when using OAuth 2.0. The errors "operator does not exist" and "UnauthenticatedThreadException: Could not authenticate thread with access group" were generated. To resolve this, an update has been made so than an anonymous user session (e.g. request from a REST call) which is already authenticated will skip the step to also verify the user ID in the database. | Decision Management |
| 832206 | Updated stack handling for strategy execution engine | During execution of a strategy the exception "pegarules.pub.context.PRStackFrameNotTopException: Specified stack frame 'null' does not match top of stack: 'doActivity Rule-Decision-Strategy' at pegarules.session.internal.mgmt.Executable.popStackFrame" was generated. The exception did not occur when the strategy execution engine (SSAVM) was turned off. This was traced to the stack size per thread being bigger when when using SSAVM. To resolve this, an update has been made to ensure the stack is updated even if there is a problem in evaluate method. | Decision Management |
Low-Code Application Development
24.1 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-227637 | 737458 | Updated handling to avoid null parameter in Service REST | Attempting to create or save the Service REST rule generated an error. Investigation showed there was a blank parameter being passed which resulted in a null value exception. This was a corner case which involved quotes around the parameter value, and has been resolved. | Low-Code App Development |
| INC-241832 | 764043 | Security improved for exporting CSV | The Export to Excel function has been updated to improve security when handling CSV files. | Low-Code App Development |
| INC-245124 | 759230 | Updated Operators search text limit | The search text field on the Organization and Security > Organization > Operators landing page has been updated to remove the limit that only returned a maximum of 10,000 operators. | Low-Code App Development |
| INC-250699 | 787439 | Test case skips unneeded validation | Refreshing a test case rule generated the error 'Rule no longer exists'. This has been resolved by skipping unnecessary validation for a scenario test case. | Low-Code App Development |
| INC-267156 | 834478 | Improved security for signatureData parameter | Handling for the signatureData parameter has been updated for improved security. | Low-Code App Development |
| INC-A14890 | 830445 | Resolved DX API v1 security check issue | The DX API v1 security check for first use assembly (FUA) was not working when checking "create stage" (New) harness. This was traced to a missing "creation_page", and has been resolved by adding a wrapper creation_page to the pzSecurityCheck call. | Low-Code App Development |
| INC-A16711 | 829760 | Enabled Constellation back button for Alternate stages | The checkbox provided for allowing users to go back to the previous step in Constellation was not working in Alternate stages. This has been corrected. | Low-Code App Development |
| INC-A17989 | 832060 | Corrected logic for conditional validations | A When rule should be used in a Validate rule that requires a combination of conditions such as "A AND B OR C". The When rule will also allow you to choose how the condition should be evaluated - "(A AND B) OR C" or "A AND (B OR C)". When multiple conditions are added directly in the Validate rule, they should use all ANDs or all ORs. In some scenarios the validate rule form allowed a combination of AND/OR conditions to be configured even though it is not a supported configuration, creating unexpected results. To address this, an update has been made so the validate rule can only be created with all ANDs or all ORs, and not a combination. When modifying one condition then all conditions will be updated. | Low-Code App Development |
| INC-A19242 INC-B3572 |
835341 852227 |
Added check for pyInterestPageClass during validation | Given subflows executed on an embedded page of a different class which had some assignments displayed through the front end using DXAPI, a PEGA_API_001 / HTTP 400 error was generated on submit of the screen. A trace showed that the page data was being validated against pyWorkPage, which was a different class to where the embedded subflow/assignments was defined. This has been resolved by adding logic to check for the pyInterestPageClass and consider it while opening the flow action. | Low-Code App Development |
| INC-A23480 | 849330 | Rule actions updated for Siteminder compatibility |
Attempting to discard private edits on a rule generated a "403 Forbidden" error. This was caused by an interaction with Siteminder, and has been resolved by updating a number of actions including checkout rule, discard rule, expression builder and open rule within rule so as to not trigger Siteminder. | Low-Code App Development |
| INC-A25287 | 848379 | Updated service export directory access for download | After update, the Usage Validation Utility (UVU) reports were generated but could not be downloaded. A 404 error was generated. This has been resolved by updating the access to the service export directory. | Low-Code App Development |
| INC-A25488 | 841100 | Logic updated to find unique rules for summary | When a branch had two rules of different types with the same name and same class, the API returned the wrong number of rules without unit tests. This was due to pxInsName being considered while finding out the number of rules that have Pega units. Since there can be multiple rules in a branch with same pxInsName but different type(pxObjClass), the logic has been enhanced to consider type along with pxInsName to identify a rule uniquely. | Low-Code App Development |
| INC-A26750 | 845998 | DSS expanded to allow missing properties for @when rules | Beginning with Pega version 8, the way properties are read off of legacy clipboard pages in the context of declaratives was changed. The current behavior is that an empty property is defined as missing and will throw the MissingPropertyException. This was a change in behavior from Pega version 7, where MissingPropertyExceptions were only generated when the property was not present on the page. In order to better support backwards compatibility for upgrades, the DSS "DecisionTable/ObtainValue/AllowMissingProperties" has been added. When this is set to true, decision tree processing will continue even if a referenced property is not present on the clipboard. To expand the use of this DSS, the ObtainValue function has been updated to allow missing properties for decision table @when rules based on the DSS value. | Low-Code App Development |
| INC-A30094 | 847621 | Increased record count returned by ConfigurationsForSet | The maximum number of records retrieved by the ConfigurationsForSet report used to fetch the list of configuration settings has been increased from 500 to 9999 to ensure all settings are listed. | Low-Code App Development |
| INC-A3161 | 812311 | Data modeling and survey respect property optimization DSS and privilege | After update, leveraging the Questionnaire creation to non-developers failed as they lacked access to Column creation in the database. This was due to a change in the handling for questionnaire creation: in Pega Platform version 8.3, questionnaire answers are mapped to a field and data stored in Blob. In Pega Platform version 8.7 and higher, the property is exposed by default and thus the creation failed due to permissions. To resolve this, a check has been added to evaluate if pxIsPropertyOptimizationAllowed is true in places from data model so the Data modeling and survey will respect property optimization DSS and privilege settings. | Low-Code App Development |
| INC-A7376 | 816517 | Corrected workPage for pzApplyPageInstructions | The pzUpdateCaseWithRequestBody activity for the pzApplyPageInstructions activity work page parameter was not passing during the PUT/Refresh DX API call. This caused the pxObjClass (ex: Data-Party-Ind) of the pyWorkParty(Customer) to override with the class defined in the pyWorkParty page group property, which resulted in the DX API returning a validation error. This has been resolved by setting the Param.workPage parameter, which is used in calculating class for content, while calling the pzApplyPageInstructions activity from the pzUpdateCaseWithRequestBody activity. | Low-Code App Development |
| INC-A7629 | 816785 | Branch Quality limited to test cases for Rules in branch | Branch Quality was showing test cases for Rules not in the branch. Investigation showed it was pulling the test cases based on the rule name only and ignoring the type of rule. This was due to the activity rule that populates the pyBranchAUTs property list for the Unit Test Cases under the Branch quality dashboard referencing the Data page and passing a null parameter. This has been corrected. | Low-Code App Development |
| INC-A7987 | 815361 | Decision Table column layout correctly honors edit option | It was possible to add columns in a Decision Table even if column layout edit option was disabled in configuration. This has been resolved by updating the logic in pzRuleDeclareDecisionTableStandard to ensure the canChangeColumns flag is checked before other actions occur. | Low-Code App Development |
| INC-A8032 INC-A23804 |
818945 844378 |
Post-upgrade decision table correctly shows horizontal scrollbar | After upgrading from Pega Platform Version 7 to Pega Platform version 8, the horizontal scrollbar was not visible for a decision table with a large number of columns and rows unless the page was scrolled all the way to the bottom. This has been corrected by adding grid CSS to the pZDecisionTable section. | Low-Code App Development |
| INC-A8821 | 822388 | Corrected guardrail warning for for Onchange Activity | Calling the Onchange Activity type from the onchange rule caused the activity to throw a severe guardrails warning. This has been resolved by updating Rule-Obj-Activity!checkForWarnings to distinguish between trigger and onchange type activities so it will only show the guardrail message when appropriate. | Low-Code App Development |
| INC-B4251 INC-B6712 |
854402 856893 |
Modified case usage data agent | The execution of PushDailyCaseData was returning more than 3 million rows which were then attempted to be added to clipboard in a report. This caused memory to get full and cause node instability which resulted in cases being carried over to the next day. This has been resolved by updating the group-by clause for a report definition to improve the handling. | Low-Code App Development |
Mobile
24.1 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A13899 | 829881 | Sync error message properly displayed on mobile | An empty message was shown on mobile if there was a sync error. Investigation showed this happened when the work object was being processed in the browser at the same time as on the mobile device, and was caused by the ErrorSync record being assigned an empty value. This has been resolved by updating the handling to preserve the error and display it. | Mobile |
| INC-A14019 INC-A11637 |
829533 830300 |
Mobile splash screen background reflects custom branding | The splash screen background color was not reflecting the branding asset in the custom.properties file and instead defaulted to the Pega background color. This was traced to pySplashUploadType being set to "Upload" if it was empty during mobile channel open, but when custom branding assets are uploaded it should be empty. This has been resolved by adding a condition to not set the pySplashUploadType when pyLabel is "Custom". | Mobile |
| INC-A26432 | 844847 | Corrected signature capture for offline mobile app | After update, the signature capture in the Pega Infinity Mobile Client (PIMC) worked on the first offline use, but subsequent uses were not capturing the signature correctly. Investigation showed the drag gestures were not received by the control but rather passed to the outer UI controls after the first use, and this has been corrected. | Mobile |
Project Delivery
24.1 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-A24094 | 841765 | DX API documentation updated for preserving special characters | Documentation for the DX API has been updated to clarify that when using special characters like '%3D' (which are not be escaped) in query parameters, encodeURIComponent must be used in order to prevent escaping the characters when building a request. | Project Delivery |
| INC-A25486 | 842096 | Virtual Report documentation updated | The documentation for using virtual reports in Activities has been updated to specify that non-autogenerated controls must be used for virtual report definitions. For Rich Text Editor, use the pxRichTextEditor control. | Project Delivery |
| INC-A26631 | 843038 | Documentation clarified for MS Graph configuration | The documentation for configuring OAuth 2.0 authentication for sending and receiving emails by using Microsoft Graph has been updated to clarify that the permission type must be Application. | Project Delivery |
| INC-A644 | 813129 | Parent/Child case interaction documentation added | Documentation has been added explaining the expected behaviors when parent and child cases are worked in multiple tabs in the same user session. Please refer to "Best practices for managing interactions between parent and child cases". | Project Delivery |
Reporting
24.1 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-180408 | 660619 | Handling improved for BIX 'Use last updated time as start' filter | A runtime error was seen when processing BIX extract rules if the BIX filter "Use last updated time as start" was selected. Investigation showed that this was caused by a socket timeout error related to the filter's use of pxCommitDateTime causing a full scan of the interaction table which contained more than 10 million records. This has been resolved by updating the extraction rule to use pxSaveDateTime instead of pxCommitDateTime for the incremental extraction. | Reporting |
| INC-232228 | 739167 | Focus correctly set for keyboard navigation with filters | Clicking on edit filters in the reports and using the keyboard to navigate was not correctly setting focus. This has been resolved by adding the necessary CSS in pyReportEditorStyling. | Reporting |
| INC-247942 | 764093 | Performance improvements for class reindexing | Utility nodes were unstable and giving a PEGA0039 alert for blob read time exceeding the limit when reindexing a class. This has been resolved with updated handling that includes implementing partitioning to distribute the preparation work. | Reporting |
| INC-250429 | 769341 | Report editor pagination link made accessible | JAWS was not correctly reading the report editor pagination link. This has been resolved by updating the page link to include aria-label with "Page #" and the href to enable tabbing through page numbers. | Reporting |
| INC-251114 | 780107 | Corrected DateTime report filtering | The DateTime filter was not working for a report on the user portal. Investigation showed there was a case mismatch which caused the datatype to not satisfy the filter conditions for pzpopulateselectedvalues. This has been resolved by setting the filter value to Range. | Reporting |
| INC-263976 | 807241 | Corrected unneeded decimal localization for Dutch locale | When using the Dutch locale (nl_NL), the progress chart in a section showed 100% complete as "1,0". Investigation showed the chart control center label "percentage" setting was localized too early during the pxFormatValue -> pxFormatNumber call. This transformed "1.0" to "1,0" which then failed to be converted to a percent. This has been resolved by updating the appendFormattedString in AbstractJsonDataGenerator to avoid localizing for this specific situation as the final percentage value will be localized afterward. | Reporting |
| INC-A12390 | 830697 | Report definition modified for deleted LowerCase function | After update, the actions list in the schema tool did not populate for a table in the pzDBDetailsInner section rule sourced from the report definition pzFetchDBTableHistoryLog. Investigation traced this to the @@pxLowerCase function being referenced in the pzFetchDBTableHistoryLog report definition even though that function was removed during previous refinements to the code. This has been resolved by adding a column without the function alias in the pzFetchDBTableHistoryLog report definition so it will work in alignment with sections. | Reporting |
| INC-A13181 | 825331 | Custom header/footer DSS added for Export to Excel | Support has been added for custom Header/Footer text in Excel files using the ExportToExcelStaticText DSS. The Static Text appears on the top and bottom of each exported page if the DSS Setting is not empty. | Reporting |
| INC-A14123 | 826103 | Select values time period modal made accessible | The <select> element within a report used to display the Time periods tab was missing an accessible name. This has been resolved by adding an aria-label to the select tag for the two custom controls used in the Report browser. | Reporting |
| INC-A14124 | 826096 | Added accessibility to My Reports data tables | Data tables within My Reports were missing an accessible name. This has been corrected. | Reporting |
| INC-A1480 | 815344 | Updated PDF cross-site scripting protections | Cross-site scripting protections have been updated for PDF generation. | Reporting |
| INC-A20600 | 837573 | SRS indexing handling updated for pattern inheritance turned off | After update, SRS indexing failed with the error "Unknown property: MemberID" when pattern inheritance was turned off. This has been resolved by updating the inheritance algorithm name in the indexing request from patternAndDirect into flatParentHierarchyList which was previously calculated by the indexer and contains the correct inheritance order. | Reporting |
| INC-A20951 | 853544 | Updated pyCompactStylesforPDF to ensure expected font handling | Adding font families for Chinese characters in PDFs was not generating the expected results. This was traced to pyCompactStylesforPDF not picking up the correct font family due to PD4ML ignoring the first CSS from the file, and has been resolved by adding "#{}" in the beginning of this file to get the styles/fonts picked in the generated PDF. | Reporting |
| INC-A22978 INC-A25991 INC-A28364 |
838636 839625 843504 |
BIX exports updated for CloudK | An update has been made which will allow BIX exports to be able to switch to Cloud mode for CloudK by reacting to the pegacloudrepository repository existence. | Reporting |
| INC-A23823 | 842758 | Permissions updated for Landing Page | The Show Data option was generating a "403 Forbidden" error after performing a refresh in the Chart Actions drop down of the Landing Page. This has been resolved by adding the needed registration code in the pzBACActivityRegistration section. | Reporting |
| INC-A24184 INC-B1888 |
852583 859918 |
DSS added to support indexing data page retrieved automatically | After migration to Cloud services, a nested custom data page was not being indexed. Investigation showed the data was stored in the ClipboardPage but SRS was not trying to check it. To resolve this, a DSS has been added to enable/disable indexing data retrieved automatically from a data page. This setting is available during serialization to JSON in the MetadataCollectorSettings field 'indexDataRetrievedAutomatically', and the default value is 'false' to disable this feature. | Reporting |
| INC-A24242 INC-A3434 |
839461 812576 |
Option to enable/disable elastic search Cluster Service logging | After update, system slowness was seen during startup. This was traced to the the behavior of logger "org.elasticsearch.cluster.service.ClusterService" being changed to log all entries. Disabling it or resetting it to "Error" still resulted in DEBUG and TRACE entries in the log. To resolve this, the logging has been made configurable with the setting "disableOverrideElasticsearchClusterServiceLogger". The default value is false. | Reporting |
| INC-A24283 | 838832 | Updated date range picker filters in Insights | After configuring an Insight with Date or DateTime as a filter, using the Date Range picker type to narrow down the results retrieved with the preselected date values was not working. This has been resolved by updating the DateRange picker condition to use the BTW function to calculate the dates. | Reporting |
| INC-A27657 INC-A25829 INC-A26791 INC-A25829 INC-A22348 |
842822 842755 843249 842738 836524 |
Report display corrected | Display issues were seen after update when viewing reports, including the "Review Report" table not being properly placed in the white box. This has been resolved by modifying the format of the container to noHeader in the DisplayReport harness. | Reporting |
| INC-A28875 | 847770 | Corrected SRS serialization error | During the serialization process for external search and reporting, the stack trace error "java.lang.IllegalArgumentException: [Indexer][Data model] Cannot find data model for entity" was generated. This has been resolved by removing an unnecessary conditional check | Reporting |
| INC-A29777 | 845196 | SASIncrementalIndexer alert default raised to 250,000 items | The pySASIncrementalIndexer queue processor was configured to generate a PEGA0134 error at 100,000 items in its queue. As there are large sites which may encounter circumstances where there will be more than 100,000 items awaiting index update, the default value has now been increased to 250,000 items for triggering an alert. This setting is customizable if a different value is desired. | Reporting |
| INC-A6794 | 819277 | Accessibility improved for My Reports - Select values | On the Select Value modal, the search text field, search button, and checkboxes were missing an accessible name. This has been corrected. | Reporting |
| INC-A6961 | 832580 | Updated BIX creation in branch | When BIX was created in a branch with filters added, merging the same rule to the base application and trying to Check out and save generated the error "Filter Name—This is not a valid property, or this is a property that cannot be used here.". This was traced to an issue with ruleset context. Internally, BIX makes use of a report definition. When the BIX rule is created in a branch, then the ruleset is a branch ruleset for the report definition as well. Merging a BIX rule to the base application moved the BIX ruleset but not the hidden report definition ruleset. To resolve this, the ruleset of the report definition will be updated in alignment with BIX to ensure the proper context. | Reporting |
| INC-A7495 INC-A4889 |
825565 828716 |
Improved query time for reindexing internal class | A socket and statement timeout occurred while reindexing a dedicated internal index class. This has been resolve dby updating the query to remove the sorting condition while indexing internal classes to avoid timeouts. | Reporting |
| INC-A9602 INC-A11469 INC-A12028 INC-A12194 INC-A12029 INC-A12976 INC-A11974 INC-A14590 INC-A14590 INC-A14590 INC-A14590 INC-A14590 |
820966 822229 822159 822932 822163 823265 824918 826597 828306 826599 825733 825686 |
Support added for Postgres MATERIALIZED/NOT MATERIALIZED | Performance impacts were seen after upgrading Postgres. Beginning with Postgres 12 there has been a change in query plan allowing common table expressions (CTEs) to be inlined into the outer query. CTEs were not inlined in Postgres 11 and were always evaluated before the rest of the query. With Postgres 12 and higher, they are automatically inlined if they have no side-effects, are not recursive, and are referenced only once in the query. Inlining can be prevented by specifying MATERIALIZED, or force multiply-referenced CTEs by specifying NOT MATERIALIZED. In order to improve performance, this update adds support for the materialized keyword to improve the performance of the descendant classes native SQL query for Postgres 12 and above. | Reporting |
| INC-B1903 INC-A24595 INC-A27741 INC-B5459 |
850286 838037 848061 857457 |
PD4ML updated | PD4ML has been updated to the most recent version to correct layout issues and improve security. | Reporting |
| INC-B2629 | 850884 | Corrected custom report display for "right to left" locales | When using an Arabic locale, the columns section did not appear for custom reports and the UI was not displaying correctly. Investigation showed the application styling was not correctly considering the "Right to Left" settings, and this has been corrected by updating the pyReportEditorStyling CSS. | Reporting |
| INC-B3466 | 851645 | Report Editor security updated | Cross-site scripting protections have been updated for the Report Editor. | Reporting |
| INC-B5953 | 854703 | Insights updated to use operator time zone | Insights was showing EST when the case data had the correct GMT Value for the UK locale. This has been resolved by updating Insights to consider the operator time zone. | Reporting |
| INC-B972 | 850882 | Corrected Report Editor properties display | Stylings in the pyReportEditorStyling CSS have been updated to correct an issue with property values overlapping in the Report Editor edit filter dropdown. | Reporting |
Security
24.1 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-268552 | 822238 | Corrected authentication handling for Proof Key of Code Exchange (PKCE) | When using SSO for Google Angular via OAuth2.0 (PKCE) and SAML (for IDP), the Angular dashboard had intermittent loading issues after successful authentication from IDP. Investigation showed this was caused by a token request failure due to the matching pair of code verifier / code challenge not being correctly validated, and this has been resolved. | Security |
| INC-A13971 | 829424 | Improved customization for “discoverable results” message | It is possible to customize the displayed message generated by the pxDiscoverableItemsCount section rule by overriding the pydiscoverableItems and pydiscoverableItemsnocount field value rules, which are marked ‘Available’, but it was not possible to remove the hyperlink (which displays a secondary list view with the case IDs of any suppressed items) because the pxDiscoverableItemsCount section was marked as ‘Final’. This has been resolved with an update to make discoverable messages within the report customizable. | Security |
| INC-A19094 | 831656 | Handling updated for keytool instances history values | Keytool instances contained incorrect information in the history tab. This was traced to missing pxCreate* and pxUpdate* property values for each instance and instead showed these instances as being created by the person who opened the rule, and was related to using IDP certificate keystore instances. This has been resolved by updating the logic to persist the Create Date time and Operator details while creating the keystore via authservice. | Security |
| INC-A19870 INC-A30017 |
832238 847030 |
Signature algorithm made case-insensitive | The error "Signature algorithm is null" was seen in the engine class . This was traced to the signature algorithm being identified as 'SHA256WITHRSA,' while in the signature map, the key is maintained as 'SHA256withRSA.' Due to this case mismatch, the signature algorithm was recognized as NULL, resulting in a failure of the SAML login. This has been resolved by modifying the map to accept case-insensitive keys. | Security |
System Administration
24.1 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-261841 | 788099 | Performance improvements for heavy AuthService use | Cascading node failures were seen, correlating with extremely high requestor counts. This was traced to the blob read for every enabled AuthService being put into the D_pzGetAuthServices.pxResults(x) page, resulting in extremely large datapages that were not being cleared from memory after the authentication. This has been addressed by changing the D_pzGetAuthServices list from a requestor level page to a node level page, along with returning just the data that is needed for displaying pyDisplayAuthScreenSelector screen and any service calls to oauth2.v1.webwb Rest Service for static content lookups. The option to clear the data page after use has also been enabled in the settings under load management. | System Administration |
| INC-239397 INC-B4713 |
814344 853177 |
Corrected property handling in Rule Assembly | A large number of Rule Assembly alerts were being generated which were affecting performance. This was traced to the assembly not being correctly saved to the database due to the value of the ExplictMetadataIsReliable property being set as false for one DependentRuleInfo. This value handling has been corrected. | System Administration |
| INC-271349 | 818389 | Corrected queue processor delay factor increasing when localized to Italian | When the locale was set to English, the "delay factor" parameter of the queue processor remained constant. If the locale was set to Italian, the delay factor increased by a magnitude of 10 each time the queue processor settings were saved and the page refreshed. If the value increased and the locale was set back to English, it did not continue to increase. This has been resolved by enabling the displayUsingReadOnlyFormatting checkbox in the final section pzDefinition in Rule-Async-QueueProcessor for the delayFactor field which will format and show the correct values in the decimal field. | System Administration |
| INC-272335 | 806060 | Run in background lockconfig made available | The pyLockTimeout field, which specifies how long queue processor activity should attempt to lock, was not available from the SendBackground shape despite having fields listed. An update has been made to include Timeout to acquire lock in RunInBackground shape. | System Administration |
| INC-A12381 INC-B914 |
825998 852235 |
Improved job scheduler rescheduling | A job scheduler configured to run every day except Sunday at 19:00 hours displayed unexpected behaviors such as not scheduling a job for a specific Saturday, or missing a run which then had to be manually triggered. Investigation showed the job scheduler which was run on all associated nodes (no locking) multiple times a day had an activity which was processed really quickly (e.g. empty activity). This caused other jobs to start running a couple of milliseconds before schedule. After the mechanism detected that the job scheduler execution was triggered too early (ex 18:59:59,994) it decided to recalculate the execution launch time again and reschedule. Usually it gets rescheduled to couple of milliseconds later, but in this case rescheduling took place at 19:00:00,005, which generated next runtime for the next day. This has been resolved by adding verification before job execution. | System Administration |
| INC-A14326 | 827098 | Stale queue processor partitions cleaned during initialization | After scaling down the queue processor partition count from 6 to 3 using the pxAlterStreamPartitions activity, scaling the partition count up later resulted in the queue processor only processing records from a few partitions and an error was generated regarding partition IDs. Investigation showed that the records for a specific queue processor were not deleted from the pr_data_qp_run_partition table while scaling down, resulting in a mismatch in offset when the partition count was scaled up later. To resolve this, after changing the number of partitions, the queue processor partition will be cleaned during data flow reinitialization. The cleanup is based on data flow partitions: all queue processor partitions which are not available in the data flow partition table or are in "Marked for deletion" state will be removed. | System Administration |
| INC-A18414 | 842447 | JobSchedulerLifecycle logging warnForced | The warning message "Detected duplicate job scheduler execution. Skipping execution." was being generated unnecessarily for sites running job schedulers on multiple nodes. To address this, the warnForced log line in PersistentJobExecutionFactory has been updated to a debug message. | System Administration |
| INC-A23287 | 838601 | MonitoredShutDown thread close added | Shutdown tasks are sometimes unable to shutdown the executorServices (which hold executing threads for Agents, Job Schedulers and Async Services Executor) within the 5 minute time limit, causing system hang. To address this, an executor pull shutdown has been added to mitigate hanging threads after shutdown is completed and a thread dump will be generated. | System Administration |
| INC-A5765 | 811824 | Added handling for default value in job scheduler date calculation | The configuration to pass certain parameters to be used in the Date calculation in Job Scheduler activity was not working as expected, leading to incorrect calculations. This was traced to an issue with using a Default value in the activity and expecting the background job to pick it up as a parameter, and has been corrected by explicitly setting a parameter on the javascript ruleform activity parameter section. | System Administration |
User Experience
24.1 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-243030 | 757694 | Focus Indicator shows for Expand/Collapse Headers on skin | Changes to the onFocus of Expand/Collapse Headers on the skin rule were not reflected on the Case Manager portal. This has been resolved with a modification which will change the tab index for the main div instead of the inside div. | User Experience |
| INC-244187 | 756163 | Image annotation registered with BAC | Annotation of an image not working in the user portal, but did work when the user had access to Developer Studio. This has been resolved by registering the activity in the pyAnnotateArea section for BAC. | User Experience |
| INC-258073 | 781567 | Group popover accessibility improvements | When using JAWS and activating “Group” from a repeating grid, a pop-up appears and “Add a field to group” receives visible focus. Selecting enter brings up a combobox to make a selection while focus remains on the “Add a field to group” link to allow users to add up to three combobox variations. However, when the focus remained on the link there was no accessible announcement that the combobox had appeared. Once the user has selected three comboboxes, the announcement from JAWS simply said “My Work”. This has been resolved with several accessibility improvements, including announcements that the combobox has been added. | User Experience |
| INC-258134 | 823118 | 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-263486 | 823558 | Updated handling for saving embedded data on refresh | Field data populated in the UI using a pyRefreshData data transform was not getting saved with the case. This occurred when using a Repeating Page list (pyWorkPage.Directors(1), pyWorkPage.Directors(2)) etc. Investigation showed the response of the refresh-api call was not generating any page instruction so the value coming from the server was not captured. This usecase has been handled by registering a call on serverChanges so the callback will contain context and the property reference and its value for use on submit. | User Experience |
| INC-263891 | 807701 | Corrected focus going to negative positioned elements | When selecting the values from a multiselect, the scroll bar was not auto-adjusting properly and focus was moving to the top. This was traced to the text area in multiselect being hidden using negative positioning, and has been resolved with an update which will not focus Negative positioned elements. | User Experience |
| INC-264149 | 789284 | Delete Row works in Field Group | When using Constellation, the Delete icon in the Field group template was keeping the row and just deleting the data from the list instead of deleting the entire row. If the view was expanded before Delete then the entire row was deleted as expected. This has been corrected. | User Experience |
| INC-264720 | 807806 | Added support for PD4ML document view parameter | After upgrading from Pega Platform version 7 to Pega Platform version 8, a generated PDF did not have Fit to Width scrolling as expected. This was due to an issue with PD4ML, and has been resolved by updating to the latest version and adding support for the parameter pd4ml.document.view.mode. This parameter defines the default view mode for generated document, with the accepted values being "SinglePage", "OneColumn", "TwoColumnLeft", "TwoColumnRight", "TwoPageLeft", and "TwoPageRight". | User Experience |
| INC-266527 | 810799 | Offline mobile app error message localized | Localization has been added for the error message "Please correct the errors indicated and try again" in the offline-enabled mobile app. | User Experience |
| INC-266708 INC-A28777 |
797606 847336 |
Corrected aria attributes for MultiSelect Lists | The aria attributes for MultiSelect lists have been updated so JAWS will announce "combobox" instead of "listbox". The "listbox" role is appropriate for the drop-down list container (e.g., <ul>), and the options (e.g., <li>) within the list with role of "listbox" container have the role = "option". | User Experience |
| INC-268234 | 797485 | Corrected Navigation Tree node name handling | After creating a Navigation Tree in UI Gallery and selecting the Width Component as Pixels(fit) in the presentation tab of the element, double-clicking on the node and then single/double clicking on any other node showed a duplicate node name and replaced the other node name. Investigation showed the node element was being replaced in the table whereas the description field still held on to the original element name, and this has been resolved. | User Experience |
| INC-268876 | 829836 | Corrected lock release for child case | When completing a child case, the system returned to the parent case but then threw the error "You have lost the ability to make this change". This was traced to DoClose causing the lock to be released, which was an inadvertent side effect of previous work done on the context for the doClose activity. This has been resolved by adding a condition to check if a parent/child relationship is there between the cases, and if so skip the code that adds pzPrimaryPageName to safeURL so the lock will not be released. | User Experience |
| INC-269073 | 815987 | Parameter added to handle Base64 encoding | While generating a PDF with image from a case, the image was not visible if it was sourced from Base64 encoding. The same encoding worked as expected in browser and in the standalone PDF generation utility. Investigation showed the image's base64 content was causing an exception when decoded via MimeUtility from Java Mail. To resolve this, a new parameter "pyUseBase64Decode" has been added to support the use of base64 encoding. By default it will be set to false. | User Experience |
| INC-269105 | 816064 | Corrected dynamic UI date conversion | A date chosen based on timezones was being converted to the operator time zone on submit of the flow when using dynamic UI fields. This has been corrected. | User Experience |
| INC-269951 | 818738 | Null check added for datarepeater layout | Multiple Dynatrace errors indicated an issue with pzpega_ui_datarepeateractions js where layoutInfo was undefined. This has been resolved with the addition of a null check which will return from the method if the layout information is null or not defined. | User Experience |
| INC-270615 | 816150 | Corrected missing GroupByOrder registration value | Intermittent 403 BAC errors were seen when an authorized user attempted to move a report from one category to another category. This issue was due to the parameter "GroupByOrder" which requires the default value of "asc" for the pzGetDropdownOptions activity, but which was being set as empty or no value by the generated java of the section pzMoveShortcut7. To resolve this, an update has been made to set GroupByOrder parameter to "asc" when the value is empty or null. | User Experience |
| INC-270887 | 827911 | Text contrast updated for placeholders and controls | Updates have been made to placeholder color values and link disabled styles to meet the IT Accessibility Standards of a color contrast ratio of 4.5:1. | User Experience |
| INC-271915 | 807785 | Updated handling for text area resize | After choosing size to content for textarea and adding more rows than the specified minimum row height, the text area expanded as expected, but the last few rows were not visible when coming back to the screen in the screen flow until the down arrow was pressed. In addition, when the end user screen resolution was around 1344 * 840 or less, the text area was not resized when minimizing or maximizing. This has been resolved by adding a resize observer for textarea. | User Experience |
| INC-272052 | 822562 | Corrected filter application after report column sort | After referring a embedded section in a column and adding a reference property in filtering, sorting and then filtering the column showed an empty result. Filtering without sorting first worked as expected. This has been resolved by updating pzpega_ui_templatizedgridcomponent_js. | User Experience |
| INC-273017 | 807603 | Corrected HTML for readonly with helpertext | The layout was distorted when displaying text input fields when DynamicLayout's Skin: Label settings were set to Label Position: Left and the Helper text was present (specified as "Help icon with overlay on focus"). Investigation showed this was caused by one closed span tag not getting generated as part of the HTML if the field was readonly and helpertext on focus was configured. This has been corrected. | User Experience |
| INC-A10334 INC-A21119 |
830262 833925 |
Display harness updated for Advanced attachment view | A 403 error was generated when accessing the Advanced attachment view if the case was launched by clicking on a link from an email. The error did not occur when logging in, navigating to the case, and then clicking on the Advanced attachment link. This was caused by a security authorization event, and has been resolved by adding the portal name to the display harness action with target as popup. | User Experience |
| INC-A10466 | 831292 | JAWS correctly announces OperatorImage icon | When the work object was assigned to a work basket / work queue and not a specific operator, JAWS did not narrate the operator icon correctly. This has been corrected by updating the tags. | User Experience |
| INC-A10776 | 825277 | Dirty popup triggered for date control | When a date control was used with the configuration of "allow text entry" set to no, dirty popup was not getting triggered when a value was entered by choosing a date from the control. Picking the Yes option for "allow text entry" triggered the popup as expected when a value was entered. This was a missed use case for isContainerDirty in pzpega_ui_doc_dirtyhandling and has been added. | User Experience |
| INC-A10839 | 823618 | Navigation menu focus reset | Navigation menu focus was not getting reset to the current active navigation. This was traced to an issue with the styling and has been corrected so the blue styling is set on current menu item on the left navigation focusout. | User Experience |
| INC-A10982 | 826494 | Resolved custom portal menu focus | When a custom portal menu was focused and there was a click on the next menu, both menus remained focused instead of just the current menu. Investigation showed there were many Items taking focus in the backend, and this has been resolved with a modification to remove the active class from the navigation parent menu item of the case if there is a click outside of it. | User Experience |
| INC-A10991 | 823282 | Text area honors max characters for pasted contents | When using a data transform or activity to copy contents from one text area with no max character limit to another text area which had a max number of characters, the character-limited field accepted more characters than the limit and showed the remaining character count as a negative number. This has been resolved. | User Experience |
| INC-A11040 | 823899 | Corrected Helper and tooltip text | Dropdowns using both Helper text and per-item tooltips were broken. Investigation showed the value in the template file for this helper text was set to the property reference instead of the static helper text kept at design time. This was caused by referencing the property in the incorrect path if there were any tooltips associated with the options, and has been resolved. |
User Experience |
| INC-A11944 | 828488 | Added 'when' rule to handle text as datetime | After upgrading from Pega Platform version 7.4 to Pega Platform version 8.8, dates entered were off by a day when saved. For example, selecting the date August 10th, 2023, was saved as August 9th, 2023. This was traced to the data type of the property being Text instead of DateTime, which caused it to use the local timezone. In order to facilitate using the large number of Text type properties already present in the applications, the 'when' rule pyConvertTextAsDate has been added. Setting this to true will convert the date value in the text property to GMT and not the user timezone. | User Experience |
| INC-A1195 | 814288 | Corrected mobile sort and filter for embedded section | When pyIsMobile || IsMobileResponsive is added as a visibility condition for layout, it is not possible to sort or filter the columns. This was traced to the property name starting with '.' when the embedded section gives the section name without '.' . This was a missed use case for sort and filter of an embedded section in mobile, and which has been resolved. | User Experience |
| INC-A12035 | 822992 | Regex filtering updated for autocomplete | Autocomplete was throwing a console error for the '+' character when "Results display" was list in the Presentation Tab and the "Highlight match" checkbox was selected in the General Tab. This has been resolved by updating the regex filtering. | User Experience |
| INC-A12509 INC-B4304 |
824629 853850 |
Script HTML tags blocked from personalization view name | When using a table or grid in the UI with Optimize code and Personalize table checked, filtering on a column and trying to save that view using PersonalizationName caused the system to freeze. This was traced to an issue in the parsing logic of parseAndGetMetaDataTree when the value of pyPersonalizationName had script tags, and has been resolved by blocking the invalid strings (<script>, </script>, <SCRIPT>, </SCRIPT>, ....) in the personalization view name of template grid. | User Experience |
| INC-A13736 | 826756 | Handling added for plus sign in currency property | A currency text type property with a value that included a plus sign (+) generated an invalid argument error and the section would not load on the UI. This has been resolved by adding a check for a plus sign while formatting the number. | User Experience |
| INC-A13846 | 827803 | JAWS correctly announces null read-only fields | When using arrow keys to navigate read-only fields with JAWS 2022, JAWS was reading "ndash ndash" for read-only fields which had null values. This has been resolved by adding accessibility support for no value so JAWS will announce the field is blank. | User Experience |
| INC-A13962 | 827489 | Text input security updated | Security protections around sanitizing input text have been updated. | User Experience |
| INC-A14040 | 827636 | Improved accessibility for opening dynamic grid work items | My Reports table rows are interactive and when clicked with a mouse open a new tab, but the rows were not keyboard accessible. This has been corrected by adding a VirtualRD attribute with added role="link" and tabIndex=0 on first cell. | User Experience |
| INC-A14075 | 827047 | Configuring an Autocomplete control documentation updated | The documentation for configuring an autocomplete control has been updated to clarify that "Property for value" and "Property for display text" configured on the property definition will not work for Autocomplete. | User Experience |
| INC-A14082 | 826098 | Accessibility improvements for My Reports table menu options | My Reports table menu options, Summarize and Appearance, displayed modal dialogs which contained controls which did not have accessible names. This has been resolved with an update to use dynamic layout and correctly set the labelFor. Grouping has also been added for some of the checkboxes. | User Experience |
| INC-A14098 | 831402 | Corrected accessible labels on controls when using autocomplete | Using an autocomplete with "additional field set" configuration was preventing other controls such as text input or dropdowns from getting accessibility names. This was caused by hidden fields that were generated from the autocomplete control based on the "additional field" configuration. Since ID generation is based on the property name, these hidden fields had the same ID as the manually-added other control for the same property and resulted in an empty accessible name. This has been resolved by removing the ID for hidden fields. | User Experience |
| INC-A14274 | 829239 | View Less button translation corrected | Localization has been added for the View Less button translation in repeating dynamic layouts. | User Experience |
| INC-A14339 | 827404 | Corrected layout for sort and table filter icons | The table filter and sort icons were overlapping when used together. This has been corrected. | User Experience |
| INC-A14548 INC-A24703 |
831346 843640 |
Corrected section assembly error | Loading sections was generating the message buildWhitelist_1();pzSectionBody_1() on UI. This was traced to pzAssemblepreprocessor becoming corrupted, causing an issue with stream assembly. This has been resolved by adding a check to the section generation and log a warning while also correcting the generation code to run down the auto-generated path. | User Experience |
| INC-A14647 | 831448 | UI accessibility improvements | To improve accessibility, the “Preview” button in the Notifications panel has been enhanced with a soft light border to make it more visible on a dark background. Universal focus styling which works well with both light and dark backgrounds has been added to Theme Cosmos to improve contrast in the left navigation panel. Additional tuning was done on the focused bookmark icon button color and the “Preview” button opacity in Notifications when the link is focused. | User Experience |
| INC-A14978 | 832783 | Focus moves to alert message as expected when tabbing | An alert message that obscured a portion of the screen unexpectedly required tabbing multiple times to be able to access the close button. This has been resolved by updating the pxhamessage-script-wrapper function to bring focus on close button. | User Experience |
| INC-A15107 | 829697 | Corrected handling for custom application switching | After update, users with multiple Access Groups were not able to switch between applications by choosing from the dropdown. This was traced to custom transition styles that triggered a call to a method created as a part of left navigation accessibility enhancement, and has been resolved with an update that will ensure focusing on the back button will be fired only for a "transitionend" event called for slide in panel and not when "transitionend" comes from other controls (for example dropdown). | User Experience |
| INC-A15171 INC-A27720 |
828150 842346 |
Corrected accessibility for Create Menu focus | When using keyboard or JAWS, the initial focus was not on the intended element when creating a case using the Create Menu. This was traced to the busy indicator stealing focus, and has been resolved. | User Experience |
| INC-A15224 | 845732 | Google Map reuse flow updated | After update, the Marker Info section map control was not loading. This was traced to a local configuration which was reusing the Google Map object, and has been resolved by updating the pypega_map_googlegis and pzpega_ui_addressmap files to better support the Google Map reuse flow. | User Experience |
| INC-A15272 | 830864 | Defer load inside Dynamic layout group updated | After upgrade from Pega Platform version 7 to Pega Platform version 8, defer load inside a dynamic layout group was not working, and the contents were loaded at the time loading the screen itself. This has been corrected by updating the logic for isDeferloadDLG from DynamicLayoutTemplateCell.java. | User Experience |
| INC-A15284 | 831586 | Support added for Checkbox control for property with declare expression | The checkbox control was not displaying the true/false text configured for the control in section when using a property with declare expression. This has been resolved by adding the logic necessary for this use case. | User Experience |
| INC-A15513 | 832401 | Added handling for empty caseNavigation menu | The Summary Panel was not expanding after being collapsed on the Case View when the caseNavigation menu item was empty. This was traced to a customization for CaseNavigation which selected "Separator" as the type. In this scenario, when toggleSummaryPanel executed on click of the icon to toggle the summary panel, an undefined error was generated due to navList resolving to an empty array. As using CaseNavigation without a navigation item is not supported, an update has been made to handle this configuration by overriding the template and removing the existing menu. | User Experience |
| INC-A15996 | 829780 | Display details read only made consistent | The integer control was not removing dot(.) immediately on entering when "Display details read only" was unchecked for integer control. Investigation showed there was a difference between text and integer handling in the pega.c.ITextInput.prototype.keyup method: it removed the dot character immediately for type=text but for type=number control it removed the dot after one more character was entered. This has been resolved by adding code to restrict the entry of dot for integer control with integer property if the input type is number so the behavior is consistent between text and integer. | User Experience |
| INC-A16652 | 829401 | Run time content reflected in Rich Text Editor | As part of a local action which sends email from a case, an email template is selected from a dropdown list. The view uses a property "Body" of type Text (Paragraph) with RichTextEditor as "Display As" option, then the data is dynamically populated using a pyRefreshData data transform. The Body property was properly set with the email source stream on the Content Page, but while all simple properties were displayed, the template was not. This has been resolved with an update which automates Rich Text Editor content assertion on assignment refresh. | User Experience |
| INC-A16713 INC-249538 |
838130 774524 |
Corrected duplicate header announcement | The accessibility popup dialog was announcing the heading twice. This has been corrected by changing aria-labelledby to aria-describedby in the modal wrapper Dialog_Title. | User Experience |
| INC-A16740 | 834702 | AJAX tab names display special characters correctly | Tab names containing special characters were not displayed as expected when using an AJAX container. This has been resolved. | User Experience |
| INC-A16885 | 829205 | Document library generation library updated | Running the wizard through the localization landing page was failing. This has been resolved by updating the document library generation version. | User Experience |
| INC-A16975 | 837512 | Handling added for data pages with parameters containing ampersand | A 400 HTTP error was generated when using the getPageDataAsync PCore API to retrieve a page type data page by passing a data page parameter value containing an ampersand (&). A 500 HTTP error was generated when using the getPageDataAsync PCore API for retrieving a page type data page by passing a data page parameter value containing ampersand URL encoded. This has been resolved by updating the handling for decoding the input/parameter value to avoid error codes 400 & 500 when the URI contains encoded values. | User Experience |
| INC-A17145 | 832669 | Modified check-in for Helper Text configuration in Sections | Checking out any section which has Helper Text Configuration as 'Help icon with overlay on focus' and then checking it in without making any changes to the Helper Text configuration caused the Helper Text configuration to change to 'Tooltip (not recommended)'. This was traced to pyModes() being in an unexpected state which caused the pzUpgradeOnOpenHelperText activity to reset the pyHelperTextType property incorrectly. This issue was limited to Pega Platform patch version 8.8.3, and has been resolved. To ensure the issue does not occur on higher release versions, the pzUpgradeOnOpenHelperText activity has been modified to prevent this issue. | User Experience |
| INC-A17186 | 830265 | Corrected modal dialog focus order | After adding the pxAttachContent control to a section, opening the modal dialog and tabbing through to the action buttons caused the focus to go to the button on the right before the button on the left. This was an issue with pzModalTemplate and has been resolved. | User Experience |
| INC-A17190 | 833508 | Corrected table focus issue for primary column | When tabbing into a table with select all checkboxes, the focus was not on the intended checkbox element and the table was able to be navigated via the tab key. If a column was marked as primary and one of the cells contained an item that could receive focus, it was possible to tab to that as an element. This has been resolved by correcting the focus issue when a column is marked as primary. | User Experience |
| INC-A17474 INC-A5981 |
831672 844589 |
Home screen correctly loads when skipDocsRecreation is true | When pega.u.d.skipDocsRecreation was set to true, the harness only displayed a white screen. This has been resolved by adding code to load the home screen when skipDocsRecreation is true. | User Experience |
| INC-A17530 | 839806 | Cancel on form from Workarea gives warning message | After opening a form and editing some details, hitting cancel on the assignment caused all changes to be lost without warning. If there was a click away instead of a cancel, the dirty popup was shown as expected. This has been resolved by adding a dirty popup for the workarea cancel button and modifying the save and close action. | User Experience |
| INC-A17551 | 829873 | Toggle added for resize Rich Text area button availability | The option has been added to toggle the availability of the resize button on a Rich Text Editor area using the enableResize setting. The default for this is =true to make the resize available. | User Experience |
| INC-A17922 | 836585 | Handling updated for case in review mode | When moving a case from one stage into another where the target stage contained a process which was not executed by the operator, the local actions at stage level could not be selected anymore and the message "Uncaught TypeError: m.caseInfo.assignments[0].actions is undefined" appeared. Investigation showed that in the failing case, the actions were not present in the openLocalAction API with the result that the local action modal did not appear on the screen. To resolve this, a condition has been added to the openLocalAction API so that if a case is in review mode, the step to save the assignment will not be executed. | User Experience |
| INC-A17974 | 833239 | Mobile check added for autopopulate control | After update, a screen using an autopopulate dropdown control worked on the desktop application but did not work on mobile. This has been resolved by adding a check for !isMobile before calling the setXY function. | User Experience |
| INC-A18376 | 834740 | Corrected preview panel close button focus | When Preview Panel was launched from the Notifications list on the left-navigation bar, focus did not stay in the preview panel after it loaded. This has been resolved by removing an unintentional focus action. | User Experience |
| INC-A18916 | 832540 | Added Iframe registration to support upgrade | After upgrading from Pega Platform version 7 to Pega Platform version 8, the flow action was submitting instead of only saving when using a save button or control in the flow action. Investigation showed that when trying to click on Save in the perform harness, the case is moving to the review harness and the background Finish assignment was getting triggered from Work- .ActionHTML of Pega-EndUserUI. This occurred due to the use of the deprecated Iframe-based action area, and has been resolved by registering the activity. Note Iframes is a deprecated functionality, and it is recommended to update to use pyActionArea. | User Experience |
| INC-A19025 | 833309 | Logo appears in Constellation | After uploading the logo from the channels, the logo was not visible in the staging and production environment. This has been corrected. | User Experience |
| INC-A19409 | 831466 | Added handling for locales with multiple underscores in the name | Singapore-based users were unable to use Google Chrome to access an EMEA-hosted Pega Cloud Constellation application when the locale in the profile was left blank so the locale was taken from the browser. Investigation showed that when Google Chrome is set to "English (United Kingdom, Oxford English Dictionary spelling)", the locale code sent from server is "en_GB_oxendict". In environment-info > setLocale function, only the first underscore (_) was replaced with dash (-) so the locale value became "en-GB_oxendict", which is invalid. There is a workaround of setting the locale, for example "en_SG", or changing the Chrome browser language to English (United Kingdom), but this has been resolved by adding handling for a locale which contains multiple underscores. | User Experience |
| INC-A1964 | 814769 | Updated helper text for date property | Helper texts added to text properties were working as expected, but a helper text created for date property was not reflecting the correct values. This was due to the 'when' condition for the date/time control helper text not bringing up the proper control name in the pyName attribute, returning the value as "pxVisible" instead of the expected "pxDateTime". This has been resolved with an update which will take pyName from the nested "node.pyTemplates[0].pyTemplates[0].pyName" instead of the top level if the visibility is based on a 'when' condition. | User Experience |
| INC-A19688 | 834230 | CaseID correctly displayed as Tab title when case is opened in new Tab | When case was opened in a new tab, the case ID was not displayed in the Tab title. Instead, the portal name "User portal" was displayed. When case was opened in the same tab, the case ID was correctly displayed as Tab title. This was a missed use case in actionrouter.js for the portalCategory when a case was opened in a new tab, and has been resolved by updating the condition to check for formFactorIframe. | User Experience |
| INC-A19993 | 834325 | Conditional check added for validation | Client-side validation failed to trigger for an autocomplete field after selecting from the list. This occurred when the autocomplete option was selected using keyboard, and was due to calling the "gridmousedownhandler" two times (onkeydown, onKeyup). This caused the second time to add tempvalidation as "null", leading to validationtype being null. This has been resolved by adding a conditional check for validation. | User Experience |
| INC-A20585 | 834409 | DevStudio Resources help query updated | The file rule pxJsAPI, used for opening the help document "Javascript API" from DevStudio Resources menu, has been updated to use pzpega_jquery_latest. | User Experience |
| INC-A21269 | 833272 | Corrected validation message display in two column layout | The validation message generated from the date control was overlapping the other controls the Theme Cosmos when the date control was embedded in a dynamic layout designed as two columns or 2 columns layout. This has been resolved by adding a separate "white-space" styling to the error div so it can wrap as expected. | User Experience |
| INC-A21302 | 837798 | Added apostrophe handling in locale strings | Creating a home field property that contained ' (apostrophe) resulted in a blank screen when converted to the French locale. This has been resolved by sanitizing variables that are used for string values in the file. | User Experience |
| INC-A21970 | 839357 | Corrected manually entered date handling for ko_KR | Manually entering a calendar date in the "ko_KR" locale generated an error indicating it was not a valid date value. Selecting a date from the calendar picker worked as expected. This was caused by the handling for the separator and has been resolved. | User Experience |
| INC-A22244 | 838154 | Validation skipped when using "save for later" | Validation rules assigned to flow actions on the validation tab were being triggered when clicking the "Save for later" button in the case form, preventing saving partially completed forms. To resolve this, an update has been made to skip validation on fields when performing a "Save for later" action. | User Experience |
| INC-A22304 | 844746 | Added check for Mashup field values | After upgrade, gadget file contents were executed during Mashup but nothing happened after that call. This has been resolved by adding an undefined check for field values list. | User Experience |
| INC-A22337 | 835527 | Corrected focus issue when link control is present in table | When an optimized table contained a link element, hovering over the link changed the tab-index to 0 which incorrectly allowed the link to be focusable by tab. When a link was not present, the cells were correctly only able to be navigated to via the arrow keys.This has been corrected by adding a condition to prevent changes of tab-index inside the table. | User Experience |
| INC-A22549 | 836032 | Updated handling for temporary page used by Notifications | The Notification preference settings page from the Notifications bell icon was not loading and the error "There has been an issue; please consult your system administrator" was generated. Investigation traced this to an improper Page-remove in pzGenerateMessageSubscription, and this has been resolved by renaming the temporary page name to TempNotificationChannelPage in the pzGetChannelByName activity. | User Experience |
| INC-A22668 | 836768 | Corrected Stakeholder field display issues | After adding additional properties to the pyPartyDetails view, editing the Stakeholder widget caused the fields to be distorted on the UI, but decreasing the zoom level adjusted the fields. This has been resolved by adding a scroll to the area. After clicking the “View All” link in the stakeholder widget to edit a stakeholder action, the Stakeholders popup window was displayed behind the View All window, making the Stakeholders popup window uneditable. This has been resolved. | User Experience |
| INC-A22746 | 817674 | Corrected duplicate field labels | After update, duplicate field labels were showing up for embedded data pagelists. This has been resolved. | User Experience |
| INC-A22887 INC-A28410 |
837059 845759 |
Modal heading coding corrected | Visual headings in modal dialogs were coded as 'span' instead of the HTML heading. This has been corrected by changing span to the h2 tag for modal heading in pzmodalheader, and modifying aria-labelledby to aria-describedby in the template form for improved accessibility. | User Experience |
| INC-A22948 | 838971 | Localization corrected for pyStatus work value with special characters | The pyCaption value for an optimized grid was not being localized when the pyStatuswork value contained parentheses. This was due to special characters in table cell values being encoded using the crossScriptingFilter stringUtils API, and has been resolved by using restoreFilteredString to restore the encoded characters and use the result to get the localized string. | User Experience |
| INC-A23582 | 841079 | Optimized grid filter works when sorting disabled | After update, attempting to perform filtering of the columns across all tables of an optimized grid with the 'enable sort' option in the column disabled was unexpectedly showing the funnel icon instead of setting icon (3 dots). This was due to design changes in table filters and sort, and has been resolved with an update to pzpega_ui_template_grid_helpers which will show the filter icon in the menu item for an optimized grid. | User Experience |
| INC-A23674 | 840619 | Improved accessibility for expanded/collapsed My Worklist | In order for the pyWorkItemOwnerDropDown section to function like a menu and allow JAWS to read the expand/collapse state of the "menu", myWorkListWidgetExpandCollapse has been added to the section to handle the aria-expanded attribute on the My Worklist widget header. | User Experience |
| INC-A23976 INC-A29658 INC-A27981 |
843310 846644 851949 |
Rich Text Editor security updated | Cross-site scripting protections have been updated for the Rich Text Editor control. | User Experience |
| INC-A24244 | 841165 | "Today" flag in DateTime picker set to local time zone | The default date in the DateTime picker was displayed based on the timezone configured in the operator profile, but the flag and Today option was showing based on GMT. This has been corrected with an update to show the triangle on Today's date based on the user selected time zone. | User Experience |
| INC-A24410 INC-A25518 |
839449 841324 |
Corrected container handling for open-Assignment | After opening an assignment, performing an optional action involving a PDF smart shape, and then closing the assignment, the assignment could not be opened again even by clicking on 'GO'. Investigation showed that due to the previous container holding old values, the open-Assignment Action was activating the container instead of having a DX API call. This has been resolved with an added action to remove the previous container when a case is in review mode after launching the optional process action. | User Experience |
| INC-A24454 | 842619 | Arabic text displayed correctly in Insights | Arabic text set in one Insight dashboard was being displayed as encoded characters when the Insight was viewed in other dashboards.This has been resolved by updating the encoding mechanism in the pzLaunchView control to handle non-ASCII characters. | User Experience |
| INC-A24769 | 844810 | Email and phone length validation updated for Constellation | Max length validation has been added for the Constellation email and phone number fields. | User Experience |
| INC-A24973 | 845796 | Handling added for default attachments category | When the default FILE category for attachments was deleted and custom attachment categories were present, no default category was selected even if there was only one category. To resolve this, an update has been made to set the default category to be the first category in the categories call response if the 'File' category is not present in the response. | User Experience |
| INC-A25293 | 841838 | Resolved MashUp URL issue | Cross-site scripting filters have been updated to add validation for context URL when using MashUp. | User Experience |
| INC-A25324 | 854650 | JAWS reads property label along with help button | In order to improve accessibility, a field label value has been added inside the aria-label to support adding helper text to the "Help icon with overlay on focus" option. | User Experience |
| INC-A25458 | 844989 | Localization corrections and Update Wizard enhancements | Missing localizations were causing HTTP 400 network errors. In versions of Pega prior to this release, the Upgrade Wizard created the localization rule for associated properties and the JSON was user-generated. With this update, the Upgrade Wizard has been improved to make sure the associated properties (i.e. local list) will have their localization rule created with JSON containing its values and this JSON will be generated by wizard itself. In addition, the "Quick links" and "My Tasks" labels were not localized in the self-service portal. This was due to an error in the locale reference for pyHome1 in pxDependencies, and has been resolved. | User Experience |
| INC-A25954 | 849140 | Corrected Constellation localization for zh_CN | When using the Simplified Chinese locale (zh_CN) in Constellation, the ruleset was localized but the system was still displaying in English. This was traced to an issue where the userLocale and baseLocale evaluated as the same due to a condition failure, and has been corrected. | User Experience |
| INC-A26261 | 846446 | Corrected window focus when using escape key | Focus was lost on any control when the escape key was pressed. This was caused by an error in the handling of keyboard accessibility for the left navigation panel, and has been resolved by updating the listener for the "Esc" key so it is only implemented on the sidebar and not on the entire window. | User Experience |
| INC-A27891 | 844346 | Updated missed use case for dirty check pop-up | A dirty check pop-up window was shown on the screen even if no changes had been made when there was a date control set with display mode as dropdown list. This was an inadvertent side effect of previous work on the dirty popup, and the missed use case of the dropdown date input has now been added to resolve this issue. | User Experience |
| INC-A28301 | 845238 | Updated handling for Worklist to Worklist transfer assignment | After transferring an assignment from the worklist to a workqueue or from a workqueue to a worklist, the user is taken back to the Review mode in Constellation. When transferring an assignment from a worklist to another worklist while in Perform mode, the assignment was transferred but the user was not taken back to the Review section as expected. Investigation showed the Go button and assignment staying in Perform mode is dependent on canPerform flag coming from DXAPI team, and in this use case where the user had access to both work queues, the canPerform flag was being set as 'true'. To make the behavior consistent, the assignment will be moved to Review mode for all scenarios. | User Experience |
| INC-A28455 INC-B1980 |
846236 852503 |
Corrected ConfigManager text wrap | After update, table headers were wrapping when the filter icon was visible on the optimized table column header in the ConfigManager even when there was empty space available for the text. This has been resolved by removing the width :100% from pzColumnFilterIcon div. | User Experience |
| INC-A28881 | 844537 | Updated context handling for drag and drop in repeating dynamic layout | After update, adding a new list Item in a repeating dynamic layout and reordering it with drag and drop only reflected the changes after save. This has ben resolved with an update to ensure the proper harness context on drag in the webwb_pzpega_ui_rubaxa_sortable js file. |
User Experience |
| INC-A28907 | 845804 | Removed row level actions caching | After enabling row level actions for the list of cases which were the case level local actions for the case type, performing the first action refreshed the UI and the status changed on the display but the actions were not being updated and the older actions were still displayed until the Cancel and Go buttons were clicked. This was caused by a delay due to the row level caching not refreshing the updated local action list, and has been resolved with an update that removes caching of row actions to support expressions and when rule configuration on row actions. To avoid confusion, the UI will show the loader until the row actions update is fetched. | User Experience |
| INC-A28933 | 846177 | Focus corrected for Assignment title | After update, when an assignment launched the focus briefly went to the Assignment Title and then immediately moved to the top of the DOM instead of remaining on the title even though pySetFocusOnAssignmentTitle was set to 'true'. This was a missed use case in previous work done to set focus on the header text when harnesses are launched which allowed the focus on the assignment title to be overridden, and has been resolved. | User Experience |
| INC-A29933 | 847346 | Max length validation corrected | Search field maximum length validation was not working after clearing the fields. Investigation showed clearTransientData was removing the classID from redux store so it was not available in the transient container context, and this has been resolved by avoiding the clearing of classID field even in nested pages. | User Experience |
| INC-A30043 INC-B1528 |
846380 849163 |
Corrected handling for visibility expression | A client-side visible expression was not working as expected if a when condition or custom condition with multiple fields was used. This was traced to an issue with the isReadable check from the IS_NULL/IS_NOT_NULL condition in getExpressionText function, and has been corrected by updating the expression logic used for comparisons to an empty string. | User Experience |
| INC-A3539 | 823989 | Corrected post-resize context handling for navigation arrows | After lowering the resolution for a tab layout, the arrows used to toggle between the tabs were not visible until there was a click on a different tab. This was traced to a context issue caused by the global resizeaction removing the resizeCall of setimeout, and has been resolved. | User Experience |
| INC-A3599 | 820461 | Corrected portal focus issue | Focus was getting lost from the portal text boxes and autocomplete dropdowns and preventing data entry. This has been corrected. |
User Experience |
| INC-A3999 | 831138 | Defer load logic updated for continuation of queue | The add criteria button was not bringing up autocomplete when configuring the engagement policy. This was traced to having multiple defer loads set for a section, and was caused by navigating to the home page before all of the deferred sections were loaded. The deferload queue is locked first, and when the defer-loaded section/layout is loaded, the queue is unlocked and proceeds to process the next item in the queue. In this case, one of the deferload-section network calls returned an error response on switching to the Home tab, and the queue did not unlock. To resolve this, an update has been made to unlock the defer load queue if the DOM is stale due to thread/context. | User Experience |
| INC-A4113 | 811960 | View focus moves to top of new view | On a view where a user was required to scroll down to view all the relevant information and then click continue, clicking continue loaded the next step but the focus on the screen remained at the bottom of the next view and not at the top as expected. This has been resolved with an update which focuses on the first focusable element in the assignment region upon render. | User Experience |
| INC-A4239 | 814023 | Updated parameter registration for Flow in Modal Dialog | A SECU0019 error indicating "Unauthorized request detected : Unregistered request encountered" was generated when using 'Flow in Modal Dialog'. Investigation showed this was caused by the modalflowParams string being generated differently during registration and in the AJAX request payload due to the randomized order of parameters being returned while iterating over the clipboard. As the individual parameters and values are already registered, the registration of modalFlowParams is unnecessary and has been removed. |
User Experience |
| INC-A426 | 812900 | Required field error message persists on UI | When a text input field was set with a required condition with Number as the presentation option and the property was configured as decimal, after entering a value and tabbing out and then going back to clear the field the error message flickered and was not persisting. This has been resolved by adding an empty condition check for DecimalPrecision. | User Experience |
| INC-A4741 | 825158 | Added handling for Spellcheck exception in Rich Text Editor UI | Using the spellcheck in the Rich Text Editor UI component was causing the browser to hang after pressing the spellchecker button. Investigation showed this was caused by a call to the activity SuspectWords_V2 from pzspellchecker_v2.js which returned HTML to the JSON parsing and crashed the spellchecker. This has been resolved by adding a check for spellChecker returning HTML and exception handling will generate a warning. | User Experience |
| INC-A4746 | 811788 | Corrected accessibility focus on dynamic layout expand/collapse | When using JAWS2022 it was possible to get focus on the expand/collapse icon on dynamic layouts while navigating a section with the virtual cursor (arrow keys). This expand/collapse icon should not be present in the Accessibility focus order as the expand/collapse functionality is triggered from header, and this has been resolved by making aria-hidden="true" for the <i class="icon icon-openClose" />. | User Experience |
| INC-A4890 | 820204 | Restored previous confirmation dialog for case reopening | In previous versions, the text on the confirmation dialogue for opening a case was "Case_Name (Case_Id) is already open." After update, this was changed to "Case_Id (Case_Id) is already open." To address this, the label condition has been updated in the showConflictDialog function of dynamiccontainer.js for the Confirmation dialog shown in the browser alert box for reopening a case. | User Experience |
| INC-A4955 | 814067 | Corrected autofocus on Text Area on validation error | Auto focus was not working on a text area after a validation error. This has been resolved by updating focus for the textArea element in focusFirstElement() in pzpega_ui_doc_focus.js file. | User Experience |
| INC-A5074 | 829283 | Updated parameter handling for dashboard filtering | Clicking on the filter option in one section of the Pega dashboard generated the error "There has been an issue, please consult your system administrator." This was traced to an invalid parameter exception related to nested tables where a section ID was used as the grid metadata page with the combination of grid source. To resolve this, the section pxreportwidgetgridandchartsection has been updated to use the custom result page pyResultReference. The grid activity has also been updated to use the primary page while fetching the unique record and use the pxreportwidgetsetreference activity to populate the unique results page. | User Experience |
| INC-A5235 | 818030 | Step name localized | Localization was not working for the step name which comes as a header in the task when using the Constellation interface. This has been resolved. | User Experience |
| INC-A5528 | 818686 | Updated row selection implementation for optimized tables | Enabling checkboxes within an optimized table with select all functionality did not persist to all pages within the table. This has been resolved, and support has also been added for being able to check a row checkbox and enable the row header checkbox. | User Experience |
| INC-A5924 | 821456 | Corrected Unicode characters present in radio button aria label | Some radio button labels were being read to JAWS users with Unicode characters not decoded. This has been resolved by adding decodeCrossScriptingFilter. | User Experience |
| INC-A6248 | 820114 | Removed duplicate guardrail warnings | The section rule pzAssemblePreProcess logic was adding duplicate guardrail warnings. This has been corrected. | User Experience |
| INC-A6303 | 819497 | Corrected AM/PM localization issue | The Native Calendar control was not populating P.M. time (12-23 hours) correctly in offline mobile when localized to Chinese locales zh_tw and zh_cn or Arabic locales starting with ar_ This has been corrected. | User Experience |
| INC-A6414 | 815791 | Go button on To-Do screen made unique for accessibility | When using Microsoft Edge and JAWS 2022, opening an existing case showed the to-do list with case assignments, but if there were multiple case assignments of the same type/flow action, the GO button titles/tooltips were not unique and JAWS/AT users were not able to differentiate between the different GO buttons. This has been resolved by changing the Accessibility label for GO buttons to use fieldValues to describe the button's aria-label. | User Experience |
| INC-A6420 | 814679 | Helper text displayed when property visibility conditional | If a property was visible based on a "when" condition, the "?" icon for the property was visible but the helper text was not displayed. If the the visibility condition of the property was changed to "always", the helper text became visible. When the "Visible When" condition is configured on Property Level, the tooltip value is sourced from a different nested level and the DLCellTemplate file was trying to get the value from an unexpected place. This has been resolved by adding handling to get the value from the correct nested position. | User Experience |
| INC-A6631 | 814886 | Dropdown with Local Value list correctly translated | After update, the localization of a dropdown with local list stopped working. This has been corrected by setting the correct localePath for the RadioButton and Dropdown components when the source is picklist or a datapage. | User Experience |
| INC-A6637 | 817650 | Rich Text Editor toobar accessibility improved | In order to improve accessibility, tooltips have been included for the Rich Text Editor keyboard shortcut tool bar. | User Experience |
| INC-A6641 | 820906 | Accessibility improvements for report table menu controls | The menu labels and controls for the dynamic grid header of Report Viewer have been updated to improve accessibility. | User Experience |
| INC-A6787 | 827063 | Improved uploaded file display for mobile | On a small mobile device there was no space for the file details once uploaded, and only a few letters were displayed. This has been resolved by removing a redundant container reference. | User Experience |
| INC-A6792 | 817901 | Calculation Builder accessibility improvements | The links to return to a previous calculation in the Calculation builder modal were not keyboard accessible. This was due to the links being coded in <span> tags instead of HTML link or role link, and has been resolved by adding the necessary aria-label to non-auto Autocomplete and Text controls. The fields on the modal were missing an accessible name. This has been addressed with the new pyPinModalHeader HTML fragment which uses the h2 tag for modal header inside it. Error handling for the calculation builder modal has also been updated. | User Experience |
| INC-A6846 | 823334 | Focus moves to intended element from Notifications Tab | After navigating to the Notifications tab and tabbing to one of the notifications, clicking "Enter" to open it did not correctly move the focus to the notification harness that was launched. This has been corrected. | User Experience |
| INC-A7014 | 813880 | Updated handling for Mashup with iFrames | After upgrade, Mashup code was not working for multiple app names in Pega version 8.8. This was traced was a missed edge use case caused by the window.parent function returning null when iFrames are used, and has been resolved with an update to use the getDesktopWindow api instead of accessing window.parent directly in webwb_pxcasemgrheader_js file. | User Experience |
| INC-A7018 | 816427 | DSS added for Rich Text Editor SVG | The DSS setting ENABLESVGFORRTE has been introduced to enable/disable SVG tags while submitting the content from the Rich Text Editor. The default setting for this is false, which will disable SVG tags. | User Experience |
| INC-A7038 | 817770 | Locking error correctly appears for child case launched from local action | When parent and child cases were configured with default locking, a second user trying to add a child case from the Actions menu did not see any error or lock message and instead an empty popup appeared briefly and then closed. This has been resolved with the addition of a script to prevent the closing of local action modal when a work object has a lock. | User Experience |
| INC-A7141 | 825152 | Corrected case id display in header | After update, creating a new case from the first case did not update the summary panel with the correct case details. This was traced to an incorrect case context when a tertiary container is not used to create the case, and has been resolved by fixing the empty handle error issue. | User Experience |
| INC-A7610 | 816248 | Corrected Rich Text Editor screen jump on enter | When using Constellation, entering large amounts of text inside a Rich Text component which spanned outside the visible areas and then adding text in the middle and hitting the enter key caused the screen to scroll to the bottom of the page. This has been resolved with an update which prevents the editor from scrolling when the enter key is pressed. | User Experience |
| INC-A7718 | 823176 | Handling added for plus character in search term | When using anypicker and searching a local data source for a country code which starts with a "+" such as +966, it was not showing results. Searching with 966 did produce results. This has been resolved with an update to handle the "+" character in the search term. | User Experience |
| INC-A7748 INC-A21764 |
816388 834408 |
Focus set correctly for datetime control cursor | After update, the focus was not being set correctly after a single digit month value was given in the datetime field. This has been resolved. | User Experience |
| INC-A7863 | 817083 | Corrected filter handling when searchText is integer | After defining two columns of picklist type in a table view, selecting "Dropdown" as the Display mode for the columns caused the values to appear properly with sorting, but the values appeared without sorting when "Search box (Default)" was selected as the Display mode for the columns. In addition, the values selected in the picklist disappeared when switching between screens in the screenflow using the Previous and Next buttons. Investigation showed that an ignoreCase filter option for integer type of key was added when calling buildFilters in data-view, but it was not supported for integer. To resolve this, a conditional statement has been added to skip the ignoreCase filter when searchText is integer. | User Experience |
| INC-A7877 | 821735 | Corrected date resetting on refresh | After generating the reports, clicking on refresh from the actions menu was resetting the date if the report was configured with column format. This has been resolved by adding pyFormatType before calling pxFormatDateTime. | User Experience |
| INC-A8340 | 818663 | Modal dialog flow releases hidden button space | After using 'Hide Default Button' in a flow action, the buttons were hidden but the space was still taken. This has been resolved by adding the condition .pyShowFAButtons != true for pyModalFlowTemplate and pzModalFlowTemplate | User Experience |
| INC-A8639 | 823621 | Added handling for empty activity name on landing page | After creating a landing page and adding it to the application as the first page, logging in generated the error "java.lang.IllegalArgumentException". This was traced to actionPage.getPageValue().getString("pyActivity") being empty, and has been resolved with an update which will not execute the activity if the name is null or blank. | User Experience |
| INC-A8942 | 819978 | Support added to disable drag and drop in optimized tables | Drag to reorder is not available to keyboard users for optimized tables. You may ensure that your application does not include operations that users cannot perform by keyboard by turning off the ability to reshuffle columns for tables that you use in the group by overlay. In this way, you provide equal access to your applications to users with all levels of ability and reduce user frustration from not being able to fully navigate your product. To support this, the pyDragDropCategorizeColumns 'when' rule has been added. This will return true by default to enable mouse-based drag and drop for reordering columns, and setting it false will disable the rule. Disabling this rule must be combined with unchecking "Enable drag to reorder items" (in the operation tab of the repeating dynamic layouts property panel) in pyGridCategorization to fully disable drag/drop. For more information refer to Pega documentation under the subject "Disabling drag and drop in optimized tables". | User Experience |
| INC-A9145 | 818585 | Accessibility added for report table sort | The sort controls in the report tables have been made accessible with a visible focus ring for table header's filter, sort and table pagination and report viewer (summary report) cells. | User Experience |
| INC-A9184 | 828330 | Updated signature event handling on mobile | After a signature was made on mobile, any movement gesture was captured on the mobile screen and the signature was not recognized. This has been resolved by stopping the event propagation during the process. | User Experience |
| INC-A9213 | 822820 | Pega Call widget labels updated for modal template | The Buttons on the Pega Call widget were not labelled correctly when using a modal template. This has been resolved by adding the aria-label in pzModalClose control (non-auto). | User Experience |
| INC-A9867 | 829035 | Screen reader accesses Create button expand/collapse | When a screen reader placed focus on the Create menu navigation element on the left navigation element, there was no announcement to suggest the menu was expanded or collapsed or that it was possible to activate this. This has been resolved by adding the aria-expanded attribute for the Create menu. | User Experience |
| INC-B1415 | 849382 | Corrected index update on table row deletion | When a table row was deleted in Constellation, the data in the rows below the deleted row was cleared and replaced with default values. This was traced to the ref index of the row being incorrectly updated, and has been corrected. | User Experience |
| INC-B2984 | 851895 | Corrected labels in stage chevrons not showing ellipsis | An issue with the default case stage chevron not displaying an ellipsis when the window size was adjusted to a point where the label outgrows the size of the chevron has been resolved by updating the CSS. | User Experience |
| INC-B3991 | 851410 | Corrected secondary button styling | After update, the secondary button was set to use a dark background which making it difficult to distinguish it from the primary button. This was an unintended side effect of work done to address another issue and has been resolved by updating the CSS for the secondary button. | User Experience |