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
8.3.5 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-133615 | 581399 | Rendering corrected for contextual prompt in Case Type | In Case Type with multiple stages, clicking to add step->More at the last stage caused the More menu to be distorted and not usable. Investigation showed that whenever the contextual prompt was opened in this way and the layout had no space on the right side, it shifted left and moved beyond the visible layout. This was traced to the two column layout in pxContextualPromptWithPreview having display styling set to block, and has been resolved by updating this setting to display as table. | Case Management |
| INC-134113 | 591543 | Child case locking error message has correct parameter | A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value. | Case Management |
| INC-135335 | 588512 | Parent flow next step will take precedence over sub-process | A Breadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation. | Case Management |
| INC-135751 | 587289 | Null check added for embedded section pyInclude tag | When attempting to implement a call to the Pega API casetypes endpoint, the end point /casetypes/{id} returned data for only some of the casetype IDs. For others there was no content in the response and in the logs the error "null at com.pegarules.generated.pzAPICreateJsonForGroup" was seen. This was traced to the use of an old section which did not generate the embedded section pyInclude tag. When the API was called on the same section, it tried to perform an equality check on the variable which gets the pyInclude value, and the null value caused the Null pointer exception. This has been resolved by adding a null check to cover pyInclude in an embedded section. | Case Management |
| INC-136208 | 585228 | Case history filter added for manual instantiation of Child Case | After upgrade from v7.4 to v8.3, creating any child case from a parent case unexpectedly added the audit history "Child case xxxxx has been manually instantiated" to the parent case. In order to make this customizable, an "isHistoryAvailable" function has been added in the 'when' condition of "AddCoveredWork" Activity's "History-Add" Step. This will use the FilterHistory decision tree, which now has a setting for "ChildCaseInsAudit" to control whether or not the manual Instantiation of a Child Case will appear in the case history. The default is "true"; setting it to "false" will suppress the message. | Case Management |
| INC-136327 | 591468 | Stage keeps proper order placement on restart | When a user restarted a stage, the stage moved to the end of the list of stages and stayed there even when completed. Investigation showed that when pxRestartStage was configured as a post-processing activity for a flow action, pxStageHistory was updated with a new list item which considered pxCameFrom and pxStageId as the same. Due to this, the current stage was moved to last in the chevron. This has been resolved by adding a new 'when' condition to pzLoadStageStatusDP that will skip the item of pxStageHistory (Alternate stage) if both .pxCameFrom and .pxStageId are same. | Case Management |
| INC-139074 | 587813 | Email handling security updated | Cross-site scripting protections have been enhanced for email activities. | Case Management |
| INC-139861 | 594008 | Cross-site scripting protections added to Case Email | Cross-site scripting updates have been added to rules handling linked email correspondence. | Case Management |
| INC-143025 | 600610 | API performance improvements | Performance improvements have been made for running the get assignment action details API. | Case Management |
Cloud Services
There were no Resolved Issues for Cloud Services in 8.3.5
Conversational Channels
8.3.5 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-143320 | 602281 | Support added for email addresses with hyphen in domain name | When attempting to enter a email with a hyphen '-' in the domain part of an email ID (test_ab@ test-email.com), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress. | Conversational Channels |
Data Integration
8.3.5 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-122072 | 581030 | Delay in writing database template records resolved | After upgrade. a real-time event based campaign with an offer flow that used a database template showed an excessive delay in updating the database template. A queue entry related to "WriteOutboundAgent" was also showing as failed, and analysis of the logs showed that the transaction type was not being set. This was traced an exception during a regular close operation of the result set iterator: the API used to close the transaction contained code specific to PostgreSQL while the site was using Oracle. This has now been resolved. | Data Integration |
| INC-122112 | 599794 | Updated SLA table clearance | After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal. | Data Integration |
| INC-125972 | 604082 | Improved resolved rules cache | When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM. | Data Integration |
| INC-127420 | 568438 | Requestor details shown in Pr_perf_stats table | When using a Custom table with the requestor details inserted in the ApplicationSetup activity, comparing the passivated requestors from standard table Pr_perf_stats showed that sometimes requestor details were not present in table Pr_perf_stats. This was traced to the the column value for standard table being greater than the column value for the columns pxDecryptCount, pxDecryptCPU, pxDecryptElapsed, pxEncryptElapsed, pxEncryptCPU, and pxEncryptCount. Database numeric column size is (9,6) whereas other numeric columns have size (18,6). To resolve this, the table scripts have been modified to increase the column size from (9,6) to (18,6). | Data Integration |
| INC-128250 INC-137235 |
571240 586081 |
Validations and rules tuning | Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved. | Data Integration |
| INC-130176 | 585374 | Removing PageList removes all cached pages | A previous change was made such that when removing a pageList property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a PageList is removed, the system will clear the pageCache of all cached pages in the PageList. | Data Integration |
| INC-131938 | 598478 | Locking and classmap improvements | Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with classmap performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead. | Data Integration |
| INC-133583 | 584923 | Rest connector supports extended chars in attachments | When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding. | Data Integration |
| INC-136817 INC-135065 |
596489 598718 |
Added database query optimization and cache invalidation logging | Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache. | Data Integration |
| INC-138253 | 597571 | Handling added to ensure proper Data-Admin-DB-Table name records | As part of property optimization, After exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase. | Data Integration |
| INC-139297 | 601421 | JSON content type update | An update has been made to ensure the content_type is set to application/json for JSON response. | Data Integration |
| INC-139695 | 593085 | Mountain timezone format updated | If an operator was created with any calendar instance timezone mapped to "Canada/Mountain" and made unavailable for the current period, routing an assignment to that operator using the standard ToCurrentOperator activity resulted in a null pointer error when the Rule-Utility-Function was executed to find a substitute operator. This was traced to the timezone format Input to DateTimeUtils API (parseDateTimeString) having the wrong timezone, for example, 20200819T080000.000 MDT (CA), and has been resolved by modifying the locale XMLs to remove (CA) from zone code so that MDT (CA) is updated as MDT. | Data Integration |
| INC-139802 | 594033 | Extra logging and more resiliency for cleanup daemons | Null pointer exceptions thrown by daemon threads that clean requestors and handle agent changes can result in a high number inactive requestors. Additional logging has been out into place to help capture information to identify the offending data, and master daemons for requestors and for new agents have been made more resilient to any Null pointer exception thrown by the diagnostics code so they do not stop their work. | Data Integration |
| INC-141299 | 593305 | PRTraceServlet security check added | Modifying the Pega application URL with PRTraceServlet displayed multiple user credentials and session information. This has been corrected with the addition of a privilege check in GetConnectionListCommand before allowing the connections list to be fetched. | Data Integration |
| INC-142455 | 602098 | Locking improvements for JDBC Connection Manager | JDBC Connection Manager may cause database connectivity issues for a prolonged period if one of the Data-Admin-DB-Name records is misconfigured. Initializing the data source for DB-Name causes JdbcConnectionManager to acquire a global write lock, which was resulting in all JdbcConnectionManager.get requests waiting during data source initialization even if the get was for a different DB-Name. To assist with this issue, improved locking has been added in JDBC connection manager. | Data Integration |
| INC-142629 | 594555 | Resolved alert from disabled job scheduler | An urgent event alert was seen for scheduler which was disabled in production. This was traced to null pointer exceptions originating in the JobSchedulerLifeCycleManagerImpl call, and has been resolved by fixing a potential null dereference. Additional logging has also been introduced. | Data Integration |
| INC-143461 | 601841 | Updated JSON DT nested page property handling | In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists. | Data Integration |
| INC-143622 | 602980 | Improved privacy for email listener alerts | To improve privacy, the customer 'from' address will be removed from PEGA0011 alerts for email listener processing. | Data Integration |
| INC-144601 | 602424 | Empty addresses removed from email | After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list. | Data Integration |
| INC-146030 | 602605 | Added queue process tracer cleanup on node restart | If a node restart occurred while a queue process trace was in progress, some entries in the tracer distributed map were not cleared properly and a subsequent tracer failure was encountered indicating a current trace by a requestor on same operator Id was already running. This has been resolved by clearing the tracer distributed map on node startup for stale entries associated with this node. | Data Integration |
| INC-146057 | 599808 | Secure access for Activitie | Authentication requirements have been added to Standard activities. | Data Integration |
Decision Management
8.3.5 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-137255 | 584910 | Resolved Cassandra query read/write latency | Read/write latency was seen when certain Cassandra queries were triggered by the system. This was traced to an unusual case where a flush was not done for an exceptionally long time period, and has been resolved. | Decision Management |
| INC-141579 INC-142674 |
591852 594496 |
Enhancement added for node heartbeat recovery process | Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds. | Decision Management |
Low-Code Application Development
8.3.5 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-128923 | 594162 | Cross-site scripting security update | Cross-site scripting protections have been added to OpenNoteDetails. | Low-code app development |
| INC-135349 | 583004 | Unit Test Ruleset rules do not count against Guardrails | Although the documentation indicates that rules in a Unit Testing ruleset should not count against the guardrail score or unit test coverage, when branching a unit test ruleset, the branch did not carry the same unit test flag value as the source ruleset and the rulesets were counted as a result. This has been resolved with an update to ignore testrulesets in guardrail and pegaunit calculations. | Low-code app development |
| INC-139300 | 590273 | Additional security for encrypted passwords | Handling and cleanup has been updated for encrypted values to enhance security. | Low-code app development |
| INC-139337 | 595222 | RefreshRequestors security update | Security improvements have been added for RefreshRequestors. | Low-code app development |
| INC-140266 INC-141296 |
602075 592474 |
Log-access security updated | Access control has been updated for Log-Usage class. | Low-code app development |
| INC-143136 | 604016 | Cross-site scripting update | Cross-site scripting protections have been updated in Designer Studio. | Low-code app development |
Mobile
8.3.5 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-131592 | 583437 | Jsoniter parser upgraded | After upgrade, the pxTextinput property Prompt List was being converted into decimal upon clicking finish assignment. This was traced to the jsoniter parser, and has been resolved by upgrading the parser in the jsoniter library. | Mobile |
| INC-131961 | 571699 | Mobile app correctly determines online status after sleep | After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview. | Mobile |
| INC-135720 | 594794 | Case link shows in Social messages for the old cases | After upgrade from Pega 7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link. | Mobile |
| INC-136091 | 598907 | Activity updated for Mobile attachment access | Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type. | Mobile |
| INC-136768 | 588452 | Question Wizard import will downcase answer types to match system requirements | The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase. | Mobile |
| INC-139160 | 590255 | Case tags made available for search filtering | An enhancement has been added for obtaining the list of cases (of a specific type) based on a tag or case type. Clicking on a tag associated to the case will filter all the cases (of that case type) with that tag, and selecting more tags will refine the filter. | Mobile |
| INC-144311 | 601109 | Updates for nested "Append And Map To" | Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist. | Mobile |
| INC-144566 | 600857 | User lookup list correctly populated when using # tag | When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved. | Mobile |
| INC-146114 | 604413 | Create Survey routes case correctly | The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected. | Mobile |
| INC-146521 | 602657 | Survey Question Page Radio/Dropdown Button retains value | After creating an Interaction from the portal and selecting "Survey", the Survey Question Page using a Radio button/Dropdown button as Question did not retain the value after a selection was made. This has been resolved by modifying the refreshSurvey method in pzsurvey_ui_userscript.js to work with an Ajax container. | Mobile |
| INC-146676 | 601942 | Field Service app localizations updated | Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app. | Mobile |
| INC-148099 | 607290 | Resolved button flicker | The buttons were flickering when moving between screens in an offline-enabled mobile app. This has been corrected. | Mobile |
Project Delivery
There were no Resolved Issues for Project Delivery in 8.3.5
Reporting
8.3.5 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-128880 | 592817 | Handling added for angle brackets in legacy Chart control | When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input. | Reporting |
| INC-137317 | 585404 | Security improved for searches | Authentication requirements have been added to activities associated with searching. | Reporting |
| INC-139700 | 591563 | Shortcut works for copying reports into private rulesets | Copying out of the box shortcuts to other categories in the Report Browser was failing with the error ".pyShortcutName: The rule name pyTimePerStage is a reserved name (starts with px, py, or pz) and is not created in a Pega- ruleset." This was caused by the system trying to create a new rule with a py prefix in a non pega- ruleset, which was a missed use case in the refactoring work of report actions to use the Record API. This has been corrected by moving the report ID generation logic from the activity pzValidateSaveAsInput to a new Rule-Utility-Function in the ReportingUtils library called pzGenerateUniqueRecordName so that it can also be used by pzCopyShortcutPostActivity7 when the shortcut's ID is prefixed with px, py, or pz. | Reporting |
| INC-140701 | 602862 | The Report Resource Limit is applied on Job Scheduler | The Job Scheduler was ignoring the application-wide limit for maximum number of rows to retrieve that was set on the Report > Settings landing page. If the limit was set on the Data Access tab of the report, it was honored. If it was set on the Application settings rule Pega-RulesEngine.pyMaxRecords it was not honored. This behavior was due to pzUpdateSystemSettings being called by pxRetrieveReportData. In pzUpdateSystemSettings, .pyContent.pyMaxRecords was updated to match the value in px.Requestor.pyReportSettings.pyMaxRecords. In some cases, that was not available and the max amount of records was not limited in that case. This has been resolved by updating pzUpdateSystemSettings to pull pyMaxRecords using @getRuleSystemSetting(). | Reporting |
| INC-141322 | 594513 | Resolved drill up doubling the filter box | When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow. | Reporting |
Security
8.3.5 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-133450 | 585994 | Login button hidden after click | When the login button was clicked fast several times, intermittently the login would fail with the blue screen and "Security violation attempting to access requestor" error in the logs. To resolve this, on click of the login button will be hidden to prevent firing multiple login requests. | Security |
| INC-134808 | 590713 | Property check handling updated for Ajax requestor | SECU0001 alerts were seen when submitting a case in the interaction portal. Logging indicated the errors were related to the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties which are included in an Ajax request when they exist in the DOM and the 'pyGeolocationTrackingIsEnabled' when rule is true. The error was traced to a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties have been added to an allow list to handle the unexpected properties check. | Security |
| INC-135437 | 589489 | Export to Excel working for reports with "Display values across columns" | Attempting to use Export to Excel when "display values across columns" was checked resulted in a null pointer error. This was traced to a null page being passed to pzRDExportWrapper, and has been resolved by adding a check for the primary page If it is null, the step page will be used. | Security |
| INC-137873 | 596158 | Java injection security updated | Protections have been updated against a Java injection. | Security |
| INC-137874 | 599130 | Cross-site scripting update for Dev Studio | Cross Site Scripting (Cross-site scripting) protections have been added to Developer Studio. | Security |
| INC-139705 | 595169 | Documentation update for Security Settings for DX API | Information on the pyDXAPIEncodeValues application setting has been added to the Security Settings for DX API article under the Application settings sub-section. The Pega Platform version that supports the pyDXAPIEncodeValues application setting is mentioned in the Supported UI capabilities article. | Security |
| INC-140101 | 597636 | System will attempt to decrypt data ending in "+" | Encrypting and decrypting one specific email address was not working properly when showing on the UI. It was possible to force a decryption using decryptproperty, but Pega generated an error. This was due to the actual encrypted value ending with '+', which conflicted with a system check that skips decryption if the encrypted property value ends with + . To resolve this, the system will attempt to decrypt the property even when encryptedText ends with + . | Security |
| INC-140224 | 604005 | Corrected SAML SSO error | After opening a case from the Pega-FCM portal or after logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint %27pr_data_saml_requestor_PK%27. Cannot insert duplicate key in object". This was a missed use case that happens only under the old SAML configuration, and has been resolved by removing a when condition that checks for stepstatus fail for the pySAMLwebSSOAuthentication activity. | Security |
| INC-142531 | 598438 | Keystore certificate alias updated to support mixed case names | The Java Keystore stored aliases only in lower case letters, but it accepted uppercase letters also during retrieval. This was causing the error "No certificate found in truststore : Azure AD SSOIDPCertStore with Alias : CN=Microsoft Azure Federated SSO Certificate" when the names didn't match. To resolve this, the keystore layer has been modified to support upper case letters in the certificate alias. | Security |
| INC-144591 | 601614 | Oauth and beanutils jars upgraded | The third party Oauth2 jars and commons-beanutils jar have been updated to the latest versions. | Security |
| INC-145033 | 599481 | ForgotPassword responses made consistent | To prevent possible exposure of valid usernames, the ForgotPassword logic has been updated so that it will show the same messages and set of screens to both valid and invalid users if a lost password request is made. | Security |
| INC-148056 | 602837 | Context updated for IACAuthentication activity trace | After upgrade, tracing the IACAuthentication activity was not working. Investigation showed that the context object had a null tracer value, which has been resolved by updating the system so the tracer runs with the correct context. | Security |
System Administration
8.3.5 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-148154 | 602921 | Hot Fix Manager updated to use installation order for schema import | Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around. | System Administration |
User Experience
8.3.5 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-132569 | 595177 | Resolved case detail overwrite | In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section. | User Interface |
| INC-132771 | 584963 | Refresh section of MultiSelect properly handles refresh section | On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls. | User Interface |
| INC-133951 | 584148 | Try catch added for templated refresh when | After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java. | User Interface |
| INC-134634 | 584948 | FSM Mobile app correctly starts phone call after closing Google | When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended. | User Interface |
| INC-135181 | 597424 | Clipboard handling updated to accommodate custom Cosmos portal | After upgrading and moving to Theme-Cosmos, a browser-level refresh on the user portal was not remaining on the same screen that issued the refresh, but rather on the default screen of the user portal. This was traced to a difference in clipboard handling of the Body parameter value for strJSON that was exposed through a customized Cosmos User Portal where Ajax Container was not used but still present in DOM. In order to support this use case, the tab_support file in sendReqToUpdateClipboard method has been updated. | User Interface |
| INC-135523 | 590437 | Tab panel read meaningfully by screen readers | When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby. | User Interface |
| INC-136793 | 585605 | Updates made to display busy indicator correctly in Google Chrome 84 | The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes. | User Interface |
| INC-137100 | 605837 | Added predictive text handler for Japanese on iOS | The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile. | User Interface |
| INC-137324 | 584919 | Corrected tabbing focus when modal flow has 'disable when' | While tabbing through the modal dialog, focus moved to the background screen if there were custom flow action buttons that had a 'disable when' condition. This was caused by the last focusable element being a disabled element, and has been resolved by adding a disabled check in the getLastFocusableElement method that will determine whether element is disabled, and if so it will look for other elements as disabled elements can't be focused. | User Interface |
| INC-137510 | 591295 | CKEditor Source edit with formatting resumes process automatically | Buttons on the harness were freezing after applying format using CKEditor when source mode was turned on in rich text editor. Investigation showed that on clicking the source button, after applying styles, the events were being paused and were not resumed automatically. This has been resolved by adding changes to resume the event queue. | User Interface |
| INC-137785 | 589064 | Removed unneeded scroll bars on optimized table | Horizontal and Vertical scroll bars were seen when using an optimized table in the Case Manager portal even when they were not needed. This was traced to the table having "overflow: auto" set, and has been resolved. | User Interface |
| INC-138309 | 591150 | Added busy state reset to reenable buttons after custom frame cancel | When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons. | User Interface |
| INC-138354 | 594356 | Third party cookies reminder added for Mashup in incognito browsers | When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message. | User Interface |
| INC-138701 | 596612 | Multi Select populates values for Page group | The Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source. | User Interface |
| INC-138803 | 591926 | Mouse event Cross-site scripting updates | Cross-site scripting protections have been added to mouse event attributes. | User Interface |
| INC-138968 | 594170 | ARIA landmarks added to put dynamic layout in tab order | As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc. | User Interface |
| INC-139023 | 591165 | Tab will exit portal side menu | It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed. | User Interface |
| INC-139156 | 592150 | Pasting image lands in correct location | When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich text editor, and has been resolved. | User Interface |
| INC-139328 | 589874 | Corrected Excel table picture being included with rich text editor paste | As an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using rich text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image. | User Interface |
| INC-140482 | 594166 | Handling added for last focused element in custom modal | Using Shift-Tab can take the focus out of the modal window when using a custom modal template without the "X" icon in the header. The issue did not happen when using "tab" key press to traverse the modal. This was a missed use case for the last focused element being div and tabindex as 0 combined with using a custom template which doesn't have close button. This has been resolved. | User Interface |
| INC-142034 | 596085 | Tab moves to next field after autocomplete | After entering the value on an autocomplete field, it took two presses of the Tab key to move to the next field. Investigation showed that on autocomplete keydown of the tab key, there was an event preventing the expected default behavior. This has been resolved. | User Interface |
| INC-142141 | 595676 | Call to OnBeforeWindowClose changed to asynchronous | After accepting a chat and accidentally closing the interaction portal with the active chat, the active record was left in an unresolved state that did not allow bot interaction until the 720 minute bot timeout was reached. This was caused by the pyOnBeforeWindowClose activity not being called as expected, and was traced to Google Chrome blocking the synchronous request needed. To resolve this, the call has been converted to an asynchronous request. | User Interface |
| INC-142248 | 601766 | Added safe check for ActivateTabs | After configuring a data transform action for a close icon to set a requestor level data page value and a parent-level dynamic layout was configured with a refresh when condition to track this Data page property, pzMicrodynamicContainer was throwing a null pointer exception after this refresh occurred indicating the tag name passed to isRegularTarget function was invalid. This has been resolved by adding a safe check to ensure that activateTabs is called only for tab based Ajax containers. | User Interface |
| INC-143795 | 599474 | Acdatasource_driver call updated | When Acdatasource_driver was invoked directly, an exception was generating indicating "This activity may not be called directly from input". This was related to recent refactoring work done, and has been resolved by modifying the code to call the acdatasource_driver activity through pzRunActionWrapper. | User Interface |
| INC-144399 | 599715 | Custom dropdown controls updated for classnames | After upgrade, a customized format for Dropdowns was not picked up. This was due to recent changes made to Class name attributes to ensure they are populated for all controls, and was caused by the CSS selector not picking the necessary DOM element. This has been resolved. | User Interface |
| INC-144600 | 599916 | Skip links enabled for all users by default | In order to improve the UI experience, the isAccessible check for skiplinks has been removed. This allows users to navigate the content of the page using skip links without having to have their access group be set to accessible mode. | User Interface |
| INC-144851 | 604481 | Date Time picker works with locale es_US | When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.). | User Interface |
| INC-145119 | 601712 | Client side validation works with Reference page property | A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator. | User Interface |
| INC-145535 | 600786 | Corrected layout group overlapping content | When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors. | User Interface |
| INC-145902 | 604196 | Corrected tab alignment with when expression | The tab layout group was not aligned properly in the Case Worker portal when using the Tab Layout Group with Enable stretch for the tabs checked and a when expression on one of the tabs. This was traced to the updateStretchTabWidths API not being triggered in the correct context due to a condition resolving as false. This has been corrected by adding an additional condition to enable the correct resolution and context. | User Interface |
| INC-146223 | 604466 | Date column filter shows correct date/time for optimized code | Two issues were seen when filtering a table that had the "Optimize Code" checkbox checked: 1) While filtering the date values in the table, the table showed one day less than the actual date based on timezone differences. When both the operator and server timezones are the same, the issue did not occur. 2) The filter always showed the time value as 00.00 irrespective of the property timestamp value. These were traced to the pyModes being incorrect for embedded properties, which has been resolved. |
User Interface |