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.4.6 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-173068 | 654064 | HTML tags escaped in Audit History field values | The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@#$ %^& amp;*&# 40;&# 41;_&# 43;.". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history. | Case Management |
| INC-175882 | 658642 | Updated bulk action audit history logic and security | After update, using the standard bulk action feature did not record an audit history entry for the SLA action on a case. This was traced to changes made around authorization for opening worklists when using pzBulkProcessItem that limited the audit history to reassign, transfer or transfer assignment, and has been resolved by updating the login the Work-pzBulkProcessItem activity. In addition, the Require authentication to run checkbox has been enabled on the Security tab of the activity, and the Allow invocation from browser checkbox has been disabled. | Case Management |
| INC-177183 | 660537 | Refresh assignment checks updated | Additional privilege checks have been added to refresh assignment. | Case Management |
| INC-178650 | 673550 | Cross-site scripting protections updated | Cross-site scripting protections have been updated around the DisplayAttachment function. | Case Management |
| INC-183947 | 673735 | Query split added to handle Oracle expressions limit | The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle. | Case Management |
| INC-184271 | 668414 | Portal Header persists appropriately | The Portal header was disappearing immediately after case attachments were opened from the right sidebar and did not reappear even after refresh. This was traced to the absence of pd(event), and has been resolved by adding pd(event) to the onclick attribute in the anchor tag in the attachment UIKit rules. | Case Management |
Cloud Services
There were no Resolved Issues for Cloud Services in 8.4.6
Conversational Channels
8.4.6 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-154254 | 632638 | Correct Email Bot training text highlighted | When a piece of text was selected and tagged against an entity while training the Email Bot, the entity selection was misplaced and partially covered the actual text selected. The incorrect selection was then carried forward to the training data spreadsheet. To resolve this, rule changes have been made that will update HTML entities to HTML encoded forms. | Conversational Channels |
| INC-175994 | 667483 | Removed redundant Microsoft Outlook email interaction chain | When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client. | Conversational Channels |
| INC-187031 | 676245 | Topic handling updated for behavior tab | While submitting topics configured on the behavior tab of the chat channel, duplicate records were created and a null pointer exception was generated. Investigation showed this was due to a difference in Topic handling between the email channel and the chat channel in a modal window, and has been resolved. | Conversational Channels |
Data Integration
8.4.6 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-156674 | 660956 | Handling added for reactivating combined Passivation and AccessGroup timeout | Refreshing a passivated browser window in Dev Studio for an operator with a combined access group and passivation timeout was resulting in a blank screen after re-authenticating. InvalidParameterException and InvalidReferenceException messages were logged. Research showed this was caused by a missing pxPortal property on the pxThread page along with missing Application and Accessgroup pages. While refreshing the browser along with the top URL, there will be few requests with tab threads calling activities such as deletedocumentpg and SetProcessWindowName because there was an unload. Because these requests reached the server before re-authentication, the threads proceeded to the activation flow, causing properties such as pxPortal, Application, and Accessgroup pages to be removed from the thread page and requestor page according to the condition that the requestor was not yet authenticated. To resolve this, the logic in session.internal.authorization.context.BasicApplicationContextImmutableImpl#applyApplicationProperties has been updated to skip removing application page properties from the thread page in this combined Passivation and AccessGroup timeout scenario. | Data Integration |
| INC-163292 | 635837 | Portlet service deprecated | Portlet authentication services have been removed from the standard installation package. | Data Integration |
| INC-165722 | 636327 | Stack trace logging enhanced for engine startup issues | Enhanced stack trace logging has been added to capture additional information when the application is unable to start and no PegaRULES logs are generated. | Data Integration |
| INC-170458 | 667374 | Handling updated for queue processor locks | The Final activity mentioned in the processing epilog of the Service File rule was not being consistently called from File Listener, causing some of the cases to become stuck and not continue to the next stage. Investigation showed that if the lock was held by the queue processor requestor, the system was unable to obtain the lock but still proceeded to update the LogServiceFile page and persist it. This resulted in overwriting changes made on the LogServiceFile page by the requestor, resetting the completed-batches-count set back to 0. To resolve this, RuleServiceFile -> updateLSFBatchCounts() will call the overloaded lockAndLoad() method in LogServiceFile that accepts a parameter called lockAttempts. This will attempt to obtain a lock for a given number of times before throwing an exception. | Data Integration |
| INC-174612 | 659249 | Queue Processor threads explicitly cleared before new interaction | Queue Processor was not clearing already evaluated freshness caches before running an activity, potentially causing a stale data page to be processed. This has been resolved by explicitly clearing the thread on a new interaction by invoking ((IPRThread) thread).clearOnNewInteraction. | Data Integration |
| INC-177773 | 665339 | Tracer protections updated | Cross-site scripting protections have been updated for Tracer. | Data Integration |
| INC-177993 | 657201 | Archival IndexManagerService performance improved for very large tables | Archival IndexManagerService was taking an excessive amount of time to run updateStatusForCasesWithInconsistentArchiveStatus(), a method which checks the parent case's archival status and compares it to all its children (cases & dependencies) statuses and flags parent cases with statuses that do not match. This check is done on all parent case instances that are in the indexer stage, and intermittently timed out and failed on a pr_metadata table containing over 5,000,000 records. This has been resolved by splitting the inconsistent check into smaller tasks and addressing potential parent/child/dependency relationships that can occur in the pr_metadata table. | Data Integration |
| INC-179025 | 665547 | Null check added for getTargetNodeUUID | A null pointer error was seen from the tracer during a security scan. This has been resolved with the addition of a null check for TracerRequest.getTargetNodeUUID. | Data Integration |
| INC-179166 | 676526 | Correspondence rule finds updated content | Activity Method Property-Set-Stream retrieved the older content of Correspondence when triggered via Queue processor. Restarting the queue processor resolved the issue until the next correspondence update, and then the cycle repeated. This has been resolved by adding an explicit thread cleanup to remove cached rules. | Data Integration |
| INC-180184 | 665092 | Assistance and diagnostics added for issue with opening imported 'when' | After update, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again. | Data Integration |
| INC-182537 | 667593 | French added to Locale List Separator | Exporting data to Excel in CSV format resulted in text with French accent characters such as "Décision pour une nouvelle demande de règlement" to appear as random characters, and columns were not being split. This has been resolved by adding a record for the French locale in the pzGetLocaleListSeparator decision table rule. | Data Integration |
| INC-182959 | 668738 | SQL queries modified to use qualified table references | Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references. | Data Integration |
| INC-182984 | 665940 | Accessibility label added to delete column header of delegated data table | After delegating a data table, the header row of the delete column added to the grid was empty and JAWS was reading "HEADER". This has been resolved by adding a label for the delete column which will also be displayed in the delegated rules in the case manager portal. | Data Integration |
| INC-184031 | 667219 | SSLContext created using protocol from REST connector rule form | After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead. | Data Integration |
| INC-184668 | 665959 | Check added for null mColumn values while estimating size | A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check. | Data Integration |
| INC-184669 | 666183 | Locking issue resolved for passivating requestor | A null pointer error was seen when passivating a requestor related to AbstractPassivationStorage.deleteAssociatedRequestorContents. This was traced to the lock to being called on the app requestor and not properly released. This has been resolved by ensuring the lock will be cleared when the Requestor is destroyed/returned. | Data Integration |
| INC-187553 INC-188143 |
675431 674974 |
Service Email handling updated for MSGraph "From" address | While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally. | Data Integration |
| INC-187628 | 670753 | Check added to ensure read locks are released | Read locks were not being properly released if a thread was holding a read lock and the system encountered an issue such as an out of memory condition. To resolve this, an update has been made to DeclarativePageDefinitionCacheImpl which will check whether a thread holds any read lock before trying to acquire a write lock, and if so release all the read locks held by that thread. | Data Integration |
| INC-189580 | 672855 | Cleanup added for disabled/deleted operator passivation data | In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data. | Data Integration |
| INC-193442 | 679180 | ServicePackage thread handling improvements | Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler. This also resolves a 504 Gateway Time-out error intermittently seen while trying to open the URL of the Pega application. | Data Integration |
Decision Management
8.4.6 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-174781 | 655123 | Kerberos authentication added for external Cassandra | Support has been added for Kerberos authentication with Cassandra. | Decision Management |
| INC-175207 | 664362 | Added handling for DSM Services stuck in leaving status after database outage | During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update has been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage. | Decision Management |
| INC-176757 | 657786 | Interaction History properly saved when running strategy on a different data flow | Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved. | Decision Management |
| INC-177877 | 661175 | Write lock check added to avoid thread contention | After updating the Pega platform and NBA Designer, a significant drop in performance for multilevel strategies was observed. Investigation showed that invoking a sub strategy containing external input intermittently caused a thread contention issue related to write lock. This was traced to overzealous write locking of a component where only a read lock for the thread was required, and has been resolved by adding a verification check to determine whether a write lock is necessary for a given operation before acquiring it. | Decision Management |
| INC-184099 | 664855 | Localization added to DelegateDescription | Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription. | Decision Management |
| INC-185045 | 672419 | Performance improvements for action check-in | The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation. | Decision Management |
| INC-186437 | 669187 | Updated entity attachment extraction tokenizers | After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces. | Decision Management |
| INC-186889 | 674016 | Unused DSS compiledExpressions now defaults to false | After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue. | Decision Management |
| INC-187070 | 672107 | Strategy execution queries tuned | During Next Best Action strategy execution, interaction history summaries were queried multiple times for a single strategy execution. To improve this function, the isChanged query will now be executed once after system startup if there are no changes instead of being executed every time the Aggregates DataSet BBK is executed. If the same Aggregates query is made multiple times as part of a Strategy in a REST request (i.e. likely multiple ADM models in a MakeDecision call), only one Aggregates BBK call will be made. | Decision Management |
| INC-189136 | 679518 | Dataflow with report definition source repaired | After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException. | Decision Management |
| INC-192102 | 676362 | Performance improvements for stale thread warnings | Stale thread warnings were causing performance issues during dataflow run execution. Stale thread/slow component warnings are added as part of the dataflow execution when a processing thread takes more than 5 minutes to process a single dataflow record. The stacktrace of the dataflow thread is added as part of the warning for debugging purposes, but in some scenarios the stacktrace can become very large. This has been resolved by removing the stacktraces from the warning, improving the query logic, and adding the run ID to the exception method to assist if there is an error. | Decision Management |
Low-Code Application Development
8.4.6 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-174435 | 659479 | Survey Complex Question Definition properly displayed | Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab". | Low-code app development |
| INC-175533 | 678911 | Improved Page compare for page groups | Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes. | Low-code app development |
| INC-180603 | 661739 | Added protections for GetSiblings | Cross-site scripting protections have been updated for the GetSibling activity. | Low-code app development |
| INC-182248 | 665782 | Added logic to handle manual validate rule creation | Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case. | Low-code app development |
| INC-191567 | 676158 | New application wizard security updated | Security around displaying and running the new application wizard has been enhanced. | Low-code app development |
Mobile
8.4.6 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-180233 | 660577 | Offline.Rulecache UI module capacity increased | Clicking the save button on a modal window caused the application to freeze and all the buttons were disabled. This was traced to the pega.offline.rulecache UI module having a default hard limit of 500 rules. Once the hard limit was reached, the system intermittently silently refused caching additional rules depending on the amount of rules packaged or the order in which the rules are loaded to the cache. To resolve this, the system has been updated to only log a console warning once the maximum threshold is reached, allowing the application to operate normally and at the time inform about the potential impact of having too many rules in memory. | Mobile |
| INC-181126 | 663304 | Signature Accept callback fires correctly in offline app | Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app. | Mobile |
| INC-183559 | 664815 | Handling added to process Actions chunks on multiple nodes | If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks. | Mobile |
| INC-183864 | 666188 | Updated RequestorInitialize to improve performance | After updating, initial user logins were taking an excessive amount of time. This was traced to the standard rule "RequestorInitialize", and has been resolved by updating the implementation. | Mobile |
| INC-185434 | 674055 | Page group property passed correctly for complex questions | When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox. | Mobile |
| INC-185950 | 669196 | Withdraw task notification uses correct email sender | When withdrawing a Task, the withdraw email was sent from the default email box instead of the expected Application default email box. This was traced to the 'pyTaskDeleted' (notification name for withdraw task) value not being present, which meant the system fell back to the task 'pyTaskAssigned' notification name. To resolve this, an update has been made to have pyIsPulseNotificationDefinition return true for a pyTaskDeleted notification. | Mobile |
Project Delivery
8.4.6 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-167254 | 651529 | Reports database configuration documentation updated | Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database. | Project Delivery |
| INC-177323 | 672423 | Search string wildcard use documentation updated | The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string. | Project Delivery |
| INC-190130 | 678543 | Help information updated for using Elastic Search with Report Definition | The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://community.pega.com/knowledgebase/articles/system-administration… |
Project Delivery |
Reporting
8.4.6 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-145293 | 610934 | Additional diagnostic logging added for ElasticSearch startup issues | The PyIndexerState was stuck in Starting status during node initialization. This issue could occur if the filesystem became hung due to network level issue while scanning entries from /etc/mtab, resulting in a lock which was not released correctly. In order to better determine which node entry in a cluster may be responsible for the hang, an update has been made which will use a temporary virtual environment to repeat the part of the initialization phase responsible and generate additional logs for debugging. To activate this, the PegaSearch.Diagnostics logger must be set in DEBUG mode. This duplicated virtual initialization will not interrupt the normal initialization. | Reporting |
| INC-153849 INC-185727 |
641921 668212 |
Updated replica management for search clusters | When using a cluster with two Universal nodes in the cluster, a daily restart process where the second node was not started until the first was fully up resulted in Search initialization failing for the first node while becoming active on the second node. This was traced to the methods used in increasing and decreasing replicas. This has been resolved by revising the handling of ElasticSearch node lifecycle and replicas through a new option "Dindex.searchNodeCount " which includes a specification for the number of expected search nodes. If this option is not present, the old method will be used. | Reporting |
| INC-166120 | 657056 | Parameter added to prevent name localization in Dev Studio Reports | Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup. | Reporting |
| INC-174686 | 670541 | Handling updated for INativeSQLBuilder with ABAC enabled | When trying to import into a data type, the error "Exception occurred during data import pxW-886: java.lang.IllegalArgumentException: INativeSQLBuilder not initialized properly" was generated. Investigation showed that when Add or Update was chosen with ABAC enabled during import, a null pointer exception occurred while getting the class definition. This has been handled by adding an extra null condition check. | Reporting |
| INC-175797 | 662047 | Date/time filter works in source column | The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time". | Reporting |
| INC-185565 | 667510 | Helper text added to improve close icon accessibility | After opening a report, the "X" close icon was not read by JAWS and was not functional when JAWS was running. Investigation showed that the ReportEditorHeader section did not have Helper Text for the Close icon; this has been added to improve accessibility. | Reporting |
| INC-185789 | 672148 | Button code updated for report filters using modal templates | When the format of 'Simple' button was changed for focus, the button created did not return the expected results. This was traced to the 'Cancel' button in Reports -> Filter being created using outdated code from the pzReportConfigApplyCancel section, and has been resolved by updating the pzReportConfigApplyCancel and pzModalTemplateAppearance sections and upgrading the buttons. | Reporting |
| INC-187245 | 670014 | Grouping Checkbox visible for drill down reports in Cosmos | When using the Cosmos theme, selecting the "Column headings and summary/sort options" as Header display in the Report Viewer drill down resulted in checkboxes not being visible under the Grouping Options for the summary pop-up. This has been resolved by adding CSS in pzReportsExpressStyles to give a default width for checkboxes. | Reporting |
Security
8.4.6 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-175706 INC-181812 INC-180858 |
659527 667198 660798 |
SSLContext created using protocol from REST connector rule form | After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead. | Security |
| INC-179360 | 662178 | Check added for allowed editing with CSRF | After enabling CSRF, it was not possible to edit a data table used to define ACL rules due to security preventing the adding/editing of rows and user group entitlements. This has been resolved by using browser FingerPrint validation to check whether an activity is in a secured list and skipping validation for allowed activities. | Security |
| INC-180275 | 666457 | Collaboration control hidden if data type is delegated | When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false. | Security |
| INC-180594 | 670956 | Filtering added for DisableDormantOperators | When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users. | Security |
| INC-185362 | 668827 | Keystore update properly revises the cache | A keystore updated with the latest certificate was not getting reflected in the runtime and the old certificate was getting picked. In a multi-node environment when the new JKS is uploaded in one node, the changes are expected to be communicated to other nodes so that the cache can be cleaned up. In this case, investigation showed that the keystore label was in uppercase and the cache entry was not correctly removed. This has been resolved by adding an update that will convert the cache key to lowercase and maintain uniformity to ensure proper cleanup. | Security |
| INC-186512 | 669380 | Password security enhanced | Security and authentication have been enhanced for password handling. | Security |
| INC-188889 | 675582 | New application wizard security updated | Security around displaying and running the new application wizard has been enhanced. | Security |
System Administration
8.4.6 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-174321 | 664240 | SSLContext created using protocol from REST connector rule form | After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead. | System Administration |
| INC-184756 | 667323 | Static assembler correctly creates temp directory | Static Assembly CLI was failing while creating a temp directory. This was traced to an issue with staticAssembler.xml, and has been resolved. In addition, security improvements have been added to the XML transformer. | System Administration |
| INC-190722 | 676403 | Ruleset Restoration Utility repaired | Attempting to use the standard Ruleset Restoration utility after update was resulting in a "Status:fail Operator:Unauthenticated or not available Node:No ID available" error message. This was a missed use case for the refactoring done around importing rules, and was caused by the utility calling the deprecated Importable.isValidImport() method. This has been resolved by updating the import activity to restore its functionality. | System Administration |
User Experience
8.4.6 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-164775 | 681241 | Web page generation security updated | Cross-site scripting protections have been enhanced around web page generation. | User Experience |
| INC-165992 | 657692 | Table Filter save uses correct harness | After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance. | User Experience |
| INC-170918 | 653218 | DateTime property handling revised for future date with daylight savings time | A DateTime property was changing each time the local action refreshed. Investigation showed this was a missed use case related to recent work to correct an issue with a 1 day discrepancy for non-template DateTime. The previous update to use the default time zone when generating markup in non-template for the date property while the datetime property uses the server time zone has been further refined to handle formatting the date time when the year is greater than 2037 and combined with daylight savings time. This will be resolved by setting the correct date before returning the moment object if the year is greater than 2037 for the date time control using display mode as date. | User Experience |
| INC-173944 | 660179 | Cancel button on embedded GridRow cancels single action | When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled. | User Experience |
| INC-175394 | 661454 | Date Time format corrected for Chinese locale | The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone. | User Experience |
| INC-177019 | 662706 | Corrected styling for layout group section navigation | When a layout group was added to a section after updating, the group was shifted when the left arrow key was pressed. This was traced to the use of arrow keys for navigation calling the focus() method and causing the scrolling. Although it is recommended to use a Tab Group control in this configuration, the shift issue has been resolved by updating the styling in the layout group. | User Experience |
| INC-178024 | 666418 | Timeline correctly shows events in local time zone | The DateTime value shown in the DateTime control and Timeline control were different from each other when using a locale setting. For example, a DateTime value which was within British Summer Time (BST) displayed as BST in the DateTime control correctly but displayed as GMT (one hour earlier) in the Timeline control. A site configured with the fr_FR locale in Europe/Paris time zone showed an incoming call interaction at 09:30 AM local Paris time while it appeared as 07:30 (GMT time) on the screen. Investigation traced this to the Pega date time formatter not being used when calculating event times, causing events to display in GMT and not in the local time zone. This has been resolved by ensuring the Pega date time formatter is added to the timeline component to display events in the local time zone. | User Experience |
| INC-179683 | 664453 | Handling added for decoding file names containing umlauts | Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters. |
User Experience |
| INC-180712 | 664785 | Improved accessibility for utility pane | JAWS was not reading the items on the utility pane, and performing any action using the keyboard controls with JAWS running in the background did not open the actionable item. To resolve this, the Utilities panel has been configured with tablist role instead of combobox, and Header buttons titles have been changed to be more descriptive. | User Experience |
| INC-181534 | 663517 | Information added for ckeditor plugin availability | Documentation for adding external plugins to the rich text editor has been updated with additional information regarding available plugins for ckeditor. | User Experience |
| INC-184109 | 671194 | Handling updated for customDateTime formatting | When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved. | User Experience |
| INC-184311 INC-184443 |
667471 668438 |
Time value handling updated for IW locale | The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved. | User Experience |
| INC-185563 | 670847 | "Manage content" dialog box tab index is consistent | The tab ordering for the "Manage content" (document upload) dialog box was not consistent. This has been resolved by updating pzModalTemplate to list the submit, cancel, etc, buttons in a consistent order. | User Experience |
| INC-189047 | 674761 | Session timeout adjusted for use with Apple Safari | A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility. | User Experience |
| INC-192075 | 680775 | Required field error message shown for Anypicker control | Certain Anypicker controls set to required were not showing the expected error message "Value cannot be blank" in the UI when the field was submitted as blank. This has been corrected. | User Experience |
| INC-192812 | 677347 | Property mapping with autocomplete control corrected | Selecting from a list populated by autocomplete did not set the property value on property(ManagerialUserGroupLabel) which was mapped to the autocomplete control. This was traced to modifications made earlier which were intended to improve the handling for populating properties with keyboard controls, and has been resolved by reverting the previous changes. Future work is planned around the original keyboard control issue. | User Experience |