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.5.5 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-175630 | 653862 | Application selections only announced when visible | The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus. | Case Management |
| INC-174511 | 653620 | Attachment errors correctly triggered for subsequent copies of the same file | After attaching a file larger than 4MB and triggering a dirty popup error, uploading the same file again did not trigger the error. This was traced to the onChange event of the File Input Tag not being triggered when the same file is attached again, and has been resolved by adding handling for attaching the same file in error scenarios (File Max Size,File Size Zero). | Case Management |
| INC-175151 | 658699 | Bulk Actions filter working for embedded date properties | For Embedded DateTime properties, the pyStringType was returned as "Date Time" instead of "DateTime", causing a mismatch in the filter criteria for Bulk Processing. This has been corrected. | Case Management |
| INC-168368 | 651080 | Correct flow actions loaded in multi-thread portal refresh | The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals. | Case Management |
| INC-172584 | 654923 | Deprecated NewWorkGadget registered for BAC | Logging in through the Administrator portal and launching a new project resulted in a blank screen. Investigation traced this to the Create New Work action called in the NewWorkGadget control; because the NewWorkGadget is no longer used by Pega, it was not registered for use with BAC. To resolve this, validations have been added for Control: NewWorkGadget, and the control has been marked as deprecated. | Case Management |
| INC-174045 | 650735 | DSS added to control merge strategy | The activity page merge option takes merge strategy as input and supports different merge strategy options like 'Replace', 'Update' etc. Previously, V1 DX APIs defaulted to REPLACE as the merge strategy; this has been updated to support both 'REPLACE' and 'UPDATE' merge strategies which can be controlled with the new DSS "v1MergeStrategy". The DSS to customize the merge strategy for v2 APIs is 'v2MergeStrategy', which also takes the values 'REPLACE' and 'UPDATE', which are for merge strategy '1' and '3' respectively. The default strategy from Pega 8.6 forward is 'UPDATE' and any other value other than the above two values will be considered as 'UPDATE'. | Case Management |
| INC-170514 | 653761 | Lock conflict resolved for AssignmentCheck | The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity. | Case Management |
| INC-175882 | 658640 | 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-167606 | 665868 | Updated ConfirmHarness handling for case type creation | If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject. | Case Management |
| INC-171842 | 664385 | Visible element populated for field value controls | When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element. | Case Management |
| INC-174267 | 657129 | Wait action persists when using Urgency Adjustment | When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity. | Case Management |
| INC-169636 | 649730 | WorkObjects security update | Cross-site scripting protections have been updated for WorkObjects. | Case Management |
Cloud Services
There are no Resolved Issues for Cloud Services in 8.5.5
Conversational Channels
8.5.5 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-179722 | 659283 | Added handling for legacy HTML formatting in Email Manager Bot | When implementing Email Manager Bot features, pyBody fields were removing the additional spaces and causing the NLP model to not extract the correct data. Investigation showed HTML formatting from older version of Microsoft Outlook created nbsp; instead of space. This has been resolved by ensuring nbsp is replaced with spaces before calling JSoup clean. | Conversational Channels |
| INC-178990 | 663786 | Added handling for reloading portal while ChatBot is active | An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat. | Conversational Channels |
| INC-169824 | 655331 | Handling added for response command beginning with "call" | There was an issue if a response command in a web chatbot channel started with the word "call". This was due to the storage and handling of the commands in the decision table. There was a workaround of avoiding the use of "call" to start a command, but the issue has been resolved by adding quotes around the decision table result to support this response command structure. | Conversational Channels |
| INC-173193 | 660938 | Resolved exception from isArchived | After update, the message "ERROR - Could not retrieve the database time" was seen. This was traced to the interactions of the isArchived API with a version of Oracle, and has been resolved by adding code to skip the isArchived() API call if pzIsPegaCloud is set to false. | Conversational Channels |
| INC-170135 | 652522 | Rich HTML handling added for outbound email | The HTML content was visible in the received email when replying from the email pane in the existing email interaction. This has been resolved by adding logic to handle rich HTML for outbound email. | Conversational Channels |
| INC-179888 | 663844 | Training data correctly added to model | Negative training data was not getting added to the entity model. This was traced to logic used to remove consecutive spaces which was incorrectly removing new lines and leading to entity detection of entities such as address line. This logic has now been removed. | Conversational Channels |
Data Integration
8.5.5 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-162262 | 658949 | AES call to mbean disabled | Under certain conditions, the AESRemote 'push memory' agent call to the legacy memory management mbean caused unexpected behavior in declarative rules for work running in data flows and queue processors. This has been resolved at this time by overriding the push memory usage agent activity to skip mbean and connect REST. | Data Integration |
| INC-177993 | 657199 | 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-158018 | 633374 | Archiving updated to include pxobjclass in CTE column list | After enabling the case archival feature on a casetype, cases were getting stuck in the Archive-Ready state while being archived, and a 'column not found' error was seen. Investigation showed that the generated SQL statement used to retrieve the resolved case instances used a common table expression (CTE) whose columns were inskey, insclass, and parentinskey, and the query that referenced the CTE was attempting to compare the column pxobjclass when pxobjclass did not exist in the CTE's column list. To resolve this, the CTE column list has been updated to pzinskey, pxobjclass, and parentinskey to prevent the 'column not found error' from occurring, and the query that referenced the CTE was also updated to use the correct column names and aliases. | Data Integration |
| INC-179167 | 659592 | Atmosphere update | The Atmosphere jar has been updated to version 2.4.5. | Data Integration |
| INC-159244 | 627864 | Bulk actions check in preserves declare expression legacy setting | When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set. | Data Integration |
| INC-184668 | 665956 | 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-174694 | 650780 | 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-169116 | 654255 | Correct time zone chosen for fr_Fr appointment function | When using the "fr_Fr" location and and "Europe/Paris" time zone for appointments, a null pointer exception was seen related to the function getStartOrEndDateTime. Investigation showed that the incorrect time zone was being picked from the fr_FR.xml file when parsing the date. To resolve this, 4 letter time zone codes have been moved above the 3 letter time zone codes. | Data Integration |
| INC-147873 | 610865 | Custom header character encoding for Subject added | Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers. | Data Integration |
| INC-178148 | 660926 | Handling added for SSO servlet name | After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly. | Data Integration |
| INC-172859 INC-175343 |
661201 655351 |
Invalid date handling added to Legacy Adapters | Running the Job Scheduler activity failed with the error "not a valid date/time value". Investigation showed this was caused by LegacyPropertyAdapter.isEmpty being returned as true in case of properties having invalid values, and has been resolved by adding handling for an InvalidValueException in LegacyPropertyAdapter and LegacyPageAdapter. | Data Integration |
| INC-161645 | 634639 | Java Bean import updated to handling differences in Java 7 and Java 8 | The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection. | Data Integration |
| INC-174243 | 655885 | Links to specifications persist appropriately | When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected. | Data Integration |
| INC-173392 | 650243 | Metadata space out of memory Healthcheck failure propagates correctly | When an "OutOfMemoryError:MetaSpace" was generated from PRClassLoaderDB.loadClass, the exception was not propagated from its caller method. This has been resolved by adding the hook to call HealthMonitorService().processCriticalError in PRClassLoaderDB.loadClass(). HealthCheck will be set to 'UNHEALTHY' based on errors configured in GenericErrorAnalyzer, which includes an out of memory condition. | Data Integration |
| INC-179025 | 665544 | 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-177470 | 657153 | Optimization prconfig check added for TableInformationMap | A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup. | Data Integration |
| INC-185758 | 668961 | Optimized GenerateID feature for case creation | Enhancements have been added to support high-performance high-volume case ID generation on multiple databases including Oracle , MS-SQL, and Azure. | Data Integration |
| INC-173436 | 648820 | Performance improvement for Application Save: Node Level Data Pages | As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved. | Data Integration |
| INC-163292 | 635839 | Portlet service deprecated | Portlet authentication services have been removed from the standard installation package. The IAC service has been restored. | Data Integration |
| INC-162262 | 654964 | Query added to find time zone for MSSQL database | The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server. | Data Integration |
| INC-174612 | 659251 | 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-176903 | 664988 | Ready to process records count correctly displayed | After update, the QP's ready to process records count was always shown as zero in the Admin studio QP landing page. This was traced to a missing sListMaxResultCount property in the SQL query for qp-partition retrieval; this has been added, and the default value has been changed from 0 to -1 for proper interpretation of results. |
Data Integration |
| INC-172350 | 658276 | Removed duplicate Set-Cookie Secure Keyword | Checking the headers of the login page showed the Cookie Pega-AAT duplicated the Secure keyword. This was traced to the PegaAATCookieWrapper extending the CookieWrapper class and causing the secure flag to be set in both the classes. This did not have a functional impact, but the secure flag set has been removed from the PegaAATCookieWrapper class to avoid duplication. | Data Integration |
| INC-178923 | 660887 | Resolved startup error related to business calendar object | An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first. | Data Integration |
| INC-170551 | 656558 | Rule Assembly update for pxTextInput and pxDisplayText | After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name. | Data Integration |
| INC-170646 | 658306 | Security update for unauthorized URL requests | Updates have been made to improve security around unprivileged users and unregistered requests. | Data Integration |
| INC-182572 | 663555 | Support added for multiple host proxy architecture | When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration. | Data Integration |
| INC-177773 INC-179448 |
665336 664314 |
Tracer protections updated | Cross-site scripting protections have been updated for Tracer. | Data Integration |
| INC-176112 | 656971 | When rule inside a loop correctly picked | While using a 'when' rule inside a loop of a page list, the rule was not being picked during runtime. This has been resolved by adding an update to allow an assembly time class name to be passed into runtime. | Data Integration |
| INC-173895 | 655914 | ZMW added to currency codes | The Zambian Kwacha, "ZMW", has been added to the currencies code list in ENCurriencies.xml . | Data Integration |
Decision Management
8.5.5 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-181401 | 665934 | Added handling for MS SQL datestamp format | When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved. | Decision Management |
| INC-174550 | 658392 | Alternative pyLabel source for Auto-generated Proposition Filter added as fall back | After using save-as to move an offer/action rule containing eligibility criteria into a new ruleset /branch, the criteria disappeared. Proposition Filter has an explicit dependency on relevant records, and in this scenario investigation revealed all of the relevant records had been previously deliberately deleted. Using save-as on auto-generated CDH rules like actions is also not a best practice. To better handle unexpected actions like these and avoid the hard dependency on Relevant Records, when creating the Proposition Filter via the programatic API the system will fall back to reading the label from the sourcePage if is not possible to get the label from Relevant Record. | Decision Management |
| INC-173859 | 652639 | Corrected compilation error for Decision Data component in Strategy | After update, a Decision data component defined in Strategy generated an assembly error when looking for class properties. This was traced to the use of "applies to" Instead of SR class, and has been resolved. | Decision Management |
| INC-169412 | 648881 | Cross-site scripting protections updated for Graph Models | Cross-site scripting protections have been updated for Graph Models. | Decision Management |
| INC-164243 | 657028 | DateTime validation works correctly after importing invalid data | After creating DecisionData (Dev studio) and adding a DateTime property to the form, importing records with invalid DateTime values failed with a validation error on the screen and the message "Error while converting format for data type DateTime property name Test_date_format with value scvf" was logged. Attempting to proceed by correcting the DateTime property and uploading worked, but any subsequent imports in the same session silently allowed invalid inputs to be passed without any validation errors and then showed blank date fields. This has been corrected. | Decision Management |
| INC-181148 | 663164 | Documentation updated for altering data type to Timestamp to avoid duplicate data in Decision Hub | By default, the pxOutComeTime column has a Date data type in the pr_data_ih_fact table. This may cause duplicate data issues. To resolve this, the 8.5 and 8.6 installation and upgrade guides for Pega Customer Decision Hub have been updated to include a new procedure "Modifying column definitions to use the TIMESTAMP datatype in an Oracle database". Performing this procedure will allow users to avoid the duplicate data issue. All documents are available from the Pega Customer Decision Hub product page. | Decision Management |
| INC-178938 | 661497 | Exception handling added for ClipboardPropertyCollection | After upgrading from Pega v7.3 to 8.5, validating the existing strategy logic generated the error "ClipboardPropertyCollection is not a supported ILType". This was traced to the special Pega expression type PropertyCollection not being supported by IL, and has been resolved by adding logic that will throw a more appropriate exception (instead of the generic PRRuntimeException) so the event can be caught by the existing fallback logic. | Decision Management |
| INC-179879 | 663006 | 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-175707 | 655346 | Multi-level strategy gives correct rules during Batch run | When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used. | Decision Management |
| INC-182137 | 662489 | Multistage Prediction Logic improved | When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR. | Decision Management |
| INC-183201 | 664960 | Resolved error during save of a Predictive Model | Attempting to save a predictive model in Prediction Studio resulted in the error ".pyModelProcess.pyShapes(Setmodelcontrolgroup).pyMOName: Cannot generate the component ID from the provided input. Enter at least one alphabetic character." This was traced to previous work done around defining a control group using a property reference, and has been resolved. | Decision Management |
| INC-159836 | 631205 | Resolved unnecessary Apache UIMA Ruta logging | A high level of exception logging related to Apache UIMA Ruta was seen under high loads due to annotations in the standard Ruta scripts; this did not impact execution, and has been resolved so only relevant events are logged. | Decision Management |
| INC-176757 | 657784 | 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-171594 | 656182 | Spell check correctly applied to email body | Spell check was not being applied to email body for text analysis in Email Channel. This has been resolved to work irrespective of case. | Decision Management |
| INC-183431 | 665160 | Strategy execution queries tuned | During NBA 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-170721 | 658959 | Stricter criteria set for reusing an SSAExecutionContext | After a Strategy was configured with an existing Proposition Filter and the Explain Results box was unchecked, executing the strategy resulted in the error "Stack is empty, cannot pop any more frames". Investigation showed that the SSAExecutionContext object was reused across the two criteria evaluation in Proposition Filter rule: this works well as long as the input is the same across the two evaluations. However, the SSAExecutionContext object also stashed a reference to a PublicAPI object which became stale in the second evaluation and caused the empty stack issue for the given scenario. This has been resolved by providing stricter criteria in deciding when an SSAExecutionContext can be reused or not in the case of Proposition Filter rule. | Decision Management |
| INC-177877 | 661178 | 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 |
Low-Code Application Development
8.5.5 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-180603 | 661741 | Added protections for GetSiblings | Cross-site scripting protections have been updated for the GetSibling activity. | Low-code app development |
| INC-178070 | 658677 | Browser invocation allowed for UnlockOperator | Attempting to unlock an operator who was locked out due to security policies was failing. This was an unintended side effect of security work performed earlier, and has been resolved by reenabling 'Allow invocation from browser ' for pzUnlockOperator. This activity requires an authentication check with privilege protection. | Low-code app development |
| INC-174468 | 650944 | Delegated rules search considers localized text | The search / filter box used to look for particular delegated rules on the configuration tab did not consider localization via field values, where the on screen name and description of the delegated rule was localized. This resulted in the search text being compared against the original text (.pyAdviceText and .pyDescription) used for the name and description at the time the rule was delegated, but not with the localized text that actually appeared on the screen. This has been resolved by updating the pzPopulateDelegations activity to filter by localized values of pyAdviceText and pyDescription. | Low-code app development |
| INC-182150 | 669851 | DSS added to control Pega Version Banner | Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist. | Low-code app development |
| INC-171257 | 651732 | Expanded results for Proposition Filter Relevant Record Properties | Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown. | Low-code app development |
| INC-165256 | 657036 | Improvements for Offer Eligibility rules loading time | After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required. | Low-code app development |
| INC-180468 | 659924 | JAWS correctly reads work group header | While creating the groups within the organizational unit, JAWS was reading the name of the frame as "Process Work Area" instead of "Create Work Group" and "enter data" instead of the name of the edit field with edit instructions. This has been resolved by adding a property to the short description label so it contains the instance type that is being created. | Low-code app development |
| INC-164439 | 657994 | Setting added to customize using blank Map values | After upgrade to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false". | Low-code app development |
| INC-181091 | 662779 | Strategy rules open from proposition filter after update | After update, strategy rules could not be opened from the proposition filter. This was caused by the pxInsName property being populated only when a strategy rule gets selected/configured from the CB gadget. For upgrade scenarios where the condition is already configured with a strategy rule, the pxInsName property will be missing. To handle this upgrade use case, the "Rule-open-by-keys" action will be used instead of "Rule-open-by-name", as rule keys are always present while pxInsName gets populated for only new configurations. | Low-code app development |
| INC-174435 | 659481 | 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-179111 | 659476 | Toolbar delete handling modified | After upgrade from Pega 7.4 to 8.5, the toolbar delete button behavior was different. Previously, the pzRuleFormToolbarDeleteRule section rule invoked RuleFormMain on refresh, but the updated version was calling RuleFormHeader, preventing the deletion of the assignment from the class instance. This was an unanticipated edge case and has been resolved by updating the action in the button to refresh the section RuleformMain instead of header. | Low-code app development |
| INC-168914 | 659661 | Updates added against Cross-site Scripting | Cross-site Scripting (XSS) protections have been updated for the UI. | Low-code app development |
Mobile
8.5.5 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-167139 | 658620 | Functions are packaged with "--" suffix | Validation rules were not executed as expected. Investigation showed this was caused by functions referenced in the validate rule through a function alias being packaged without the "--" suffix (for example isNameInvalid--(String) was packaged as isNameInvalid). This has been corrected. | Mobile |
| INC-175000 | 657005 | Handling added for Address Map control in Microsoft Internet Explorer 11 | Microsoft Internet Explorer 11 does not support Class, async, await and arrowed functions due to not implementing the necessary EC6 features. This caused Address Map Control to not work in this browser because pypega_map_googlegis js creates a js class. To resolve this issue, alternate methods have been added for use with Microsoft Internet Explorer 11. | Mobile |
| INC-183559 | 664812 | 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-172124 | 651291 | Improved Operator ID selection in Mobile Logs Retrieval section | Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected. | Mobile |
| INC-179175 | 665173 | Mobile barcode scan sets value with correct context | After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers. | Mobile |
| INC-166048 | 659533 | Navigation icons added for use in offline mobile | When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following: webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg |
Mobile |
| INC-180233 | 660580 | 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-175684 | 658696 | Parameterized data pages updated on record change | Changing source data page records without changing the parameter value was not updating parametrized data pages. This has been resolved by updating the system so the parametrized data page populator function is now called every time the page is accessed. | Mobile |
| INC-172315 | 652602 | Resolved intermittent attachment save error | A Flow Action error was intermittently being displayed when saving attachments. This was traced to the activity pzUploadAttachmentToDocument-->Step 25 which uses the step page CallExtensionAct which can cause a page null exception if it is not initialized, and has been resolved by adding a Page-New step to initialize the page. | Mobile |
| INC-168290 | 663426 | 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-160485 | 655296 | Trailing "/" added to public links for SSO use | Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it. | Mobile |
| INC-183864 | 666185 | 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 |
Project Delivery
8.5.5 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-168254 | 659299 | Documentation updated for accents and special characters used in search | The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character. | Project Delivery |
Reporting
8.5.5 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-176385 | 657669 | Corrected blank lines for hidden report filter criteria | When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid. | Reporting |
| INC-175797 | 662049 | 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-179362 | 658630 | Display limitation removed for scheduled reports | When looking at Configure >> Reports >> Scheduled Reports only 50 reports were shown across two pages instead of all of the reports retrieved by pzGetScheduledTask. This was a limitation set in pyScheduledTasksGadget, and has been removed. | Reporting |
| INC-181394 | 662099 | Handling added to avoid incorrect manifest count | Extracted Record counts in the manifest file were incorrect if any updates were made during the extraction process. This has been resolved by modifying the code to prevent the issue. | Reporting |
| INC-160190 | 658124 | Logic updated to allow page property and declare index with the same name | A Property which was in a page list which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid. | Reporting |
| INC-176158 | 664346 | Max number of rows setting properly honored | The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case. | Reporting |
| INC-166120 | 657054 | 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-174756 | 650538 | Queue processor correctly moves items to Broken Items | When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types. | Reporting |
| INC-182375 | 664342 | Report filter description correctly displayed | When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic. | Reporting |
| INC-175622 | 652277 | Screen reader announces report names | An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly. | Reporting |
| INC-176205 | 655937 | Secure shared link generation added to scheduled reports | When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function. | Reporting |
Security
8.5.5 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-179360 | 662180 | 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-169186 | 655536 | Disconnect button availability extended | A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page. | Security |
| INC-171875 | 653891 | Skip restored for browser request CSRF token | Many SECU0008 alerts were seen in the production logs. This was the result of a CSRF token check on requests without pyActivity or pyStream, and has been resolved by restoring a conditional skip of the check as those other browser requests do not contain a CSRF token. | Security |
| INC-174321 INC-175058 INC-175706 INC-179188 INC-180858 |
664237 660935 659529 661955 660801 |
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 |
System Administration
There were no Resolved Issues for System Administration in 8.5.5
User Experience
8.5.5 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-157404 | 630693 | Adaptive Model report information exports correctly | Clicking export to Excel or PDF in the Prediction Studio Adaptive Model report was not working. Investigation showed the first double quote of the propositionName was getting replaced from & quot ; to "", which resulted in an error while performing openUrlWindow action. This has been resolved by adding a new helper handler, while creating context menu using Handlebars. | User Interface |
| INC-177852 | 658652 | Added UI handling for error message on Delegated data table | It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll. | User Interface |
| INC-178116 | 660567 | Article on configuring display options for a harness updated | The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio. | User Interface |
| INC-175990 | 652086 | Browser check added to ensure on-click event trigger | Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check. | User Interface |
| INC-173944 | 660182 | 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 Interface |
| INC-173345 | 655037 | Check added for empty geolocation values | Latency issues were traced to Geolocation-related errors in the log files. To improve performance, changes have been added to check for empty pyLatitude and pyLongitude before adding in the postdata of an async request. | User Interface |
| INC-184419 | 668753 | Checks added to prevent EditingMode null value | When trying to open a section rule in developer portal in Pega Cloud, "Error" was displayed instead of the section details. Investigation showed the pyEditingMode property was present but did not have a value, and this has been resolved by adding checks to the UpgradeSequoiaGrid activity to ensure the pyEditingMode of "" does not invoke a data transform of that name. | User Interface |
| INC-179664 | 661111 | Child Case comments pop-up opens as expected | Comments on the header level were opening correctly, but the comments pop-up for the child case tab was not. This has been resolved by adding a safe check for the eventTarget.closest method. | User Interface |
| INC-155406 | 638705 | Clipboard security updated | Security has been enhanced for clipboard properties by restricting registration for readonly properties. | User Interface |
| INC-178365 | 659041 | Corrected tab thread handling for modal close | Clicking Grid item in My Opportunities tab did not open the section in that tab but rather opened another tab and showed the section of that tab. This was traced to pxReqURI not getting reset by the modal close, and has been resolved. | User Interface |
| INC-175394 | 661457 | 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 Interface |
| INC-163644 | 652966 | Error message handling added for nested page lists | When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors. | User Interface |
| INC-172483 | 651709 | Filtering updated for UI markup | Filtering has been added to the UI code to preserve the browser display appearance but remove inappropriate or potentially insecure markup. | User Interface |
| INC-171352 INC-175322 |
653690 658649 |
Focus set correctly on the modal window in theme-Cosmos | in theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly. | User Interface |
| INC-179683 | 664450 | 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 Interface |
| INC-185847 | 668984 | Handling added for disabling weekends when no weekends are available | A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance. | User Interface |
| INC-179478 | 662928 | Handling updated for progressive load on scroll in repeating dynamic layers | When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate. | User Interface |
| INC-165964 | 656813 | Harness context set for modal dialog on interaction portal | An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct. | User Interface |
| INC-178639 | 658053 | Improved accessibility for Autocomplete Role | Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode. | User Interface |
| INC-180712 | 664782 | 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 Interface |
| INC-166858 | 664459 | Improved text accessibility for screen zoom | Under the specific conditions of a very large zoom level and low screen resolution, the inner menu's height was reduced to 0. This has been resolved by setting a minimal height for the inner menu item element to prevent it shrinking to 0. | User Interface |
| INC-181534 | 663518 | 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 Interface |
| INC-176734 | 655176 | Invalid manual time value stops progress and displays error | When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid. | User Interface |
| INC-177263 | 659175 | isFutureDate edit validation fires correctly | The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date. | User Interface |
| INC-171663 | 655244 | MashUp dynamic parameters article updated | The documentation for MashUp best practices has been updated to clarify that dynamic parameters sent from the client side using "pega.web.api.setAuthenticationParameters" API will be sent as part of the query parameters and won't be part of the encrypted hash as this hash is generated on the server end while generating the mashup code in the mashup channel. | User Interface |
| INC-179883 INC-187057 |
661617 | Pega reference tags persist | Cross-site scripting protections have been updated to allow Pega reference tags. | User Interface |
| INC-174020 | 650889 | Performance improved for Directed Web Access (DWA) | Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance. | User Interface |
| INC-173238 | 656503 | Restored missing API call for icon navigation | After logging in and searching for a bond, navigating to the home page without clearing the search string from the bond screen resulted in a pop-up warning to remove unsaved changes. Clicking on OK and then attempting to click on the list index number available below the table resulted in an error. Investigation showed pzCTkn was missing for the API calls triggered by clicking on the icon; this has been resolved by updating the pega_yui_connection.js file. | User Interface |
| INC-175814 | 657821 | Runtime edit saves section to correct class | When the active thread had an Ajax container embedded in it and a runtime edit was made of a section in the Ajax container thread, the section was saved into the parent thread's work object class. This was an unsupported use case, and has been resolved by adding support for runtime editing of sections from an embedded Ajax container. | User Interface |
| INC-173382 | 653441 | Security update for previews | Security updates have been made around the sanitizing of preview streams. | User Interface |
| INC-176403 | 653574 | Security updated for buttons | Cross-site scripting protections have been updated for Button controls. | User Interface |
| INC-164924 | 639019 | Serbia added to country codes list | The CountryCode for Serbia (SRB) has been added to the existing country codes. | User Interface |
| INC-176342 | 654507 | Summary Tabs correctly sync after case refresh or submit | The right side display showed the corresponding section as expected after selecting any last tab, but after a case refresh the right side of the summary tab highlighted the first summary tab's section while the focus remained on the previous selected tab. This was traced to the setActiveTab API triggering pega.ui.templatenav.toggleLayoutGroupTab with incorrect parameters, and has been resolved. | User Interface |
| INC-184311 | 667268 | 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 Interface |
| INC-172178 | 655020 | TransID updated to trim spaces | While preparing newTransID from a response, special characters slipped into "newTransID" param value and generated an error. This has been resolved by updating the system to trim spaces from newTransID. | User Interface |
| INC-176429 | 654752 | Values updated in Local action correctly reflected in the UI | After update, values were not updated in the UI after being modified in a local action which targeted a modal dialog and had some text fields on overlay with validation messages placed using Property-Set-Messages. Analysis revealed that the ReloadSection was not getting called correctly in this scenario, and has been resolved by changing the nullify method to pega.u.d.cleanUpHarnessElements(null, [containerBody]); . | User Interface |
| INC-169866 | 653547 | View content type updated to FIELD | After upgrade table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after upgrade to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views. | User Interface |