Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
For information on downloading this patch, see Pega 8.8.2 - Patch Release Available.
Low-code Application Development
Case Management
8.8.2 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-229623 | 763198 | App Studio case type creation chooses correct ruleset | When the application ruleset had versions such as 01-01-01 and 01-99-01 and 01-99-01 was unlocked, during the case type creation App Studio was always selecting the 01-99-01 version to create the rules even though the application rule had restricted the version to 01-01. Analysis showed the activity PZCREATECASETYPEWRAPPER step 8 was using the GetRuleSetVersion function to get the ruleset version to save all the rules and was always returning the highest unlocked ruleset present for a ruleset. This has been resolved. | Case Management |
| INC-239347 | 772003 | Improved accessibility for Case Manager | Role ="Main" was configured at two places in the DOM for Case Manager which resulted in a structural error in Accessibility Inspector. This has been resolved by modifying the accessibility of Aria's role from Main to Presentation in the pyCaseManager7 section. | Case Management |
| INC-245267 INC-243845 |
759519 767846 |
Flow error resolved for Split for Each | After completing the assignments in a screenflow launched from a Split for Each utility, a validation error was generated when a second user clicked on the breadcrumb to change to another assignment within the screenflow. This was a missed use case related to the GoToPreviousTask activity (which calls jumpToTask) not getting the correct flow name and task name parameters to navigate due to the split. This has been resolved by adding the new property pxSubscript which holds the flowname with subscript for split flows on pyFlowData. | Case Management |
| INC-249902 | 772469 | DSS added for MaxChildCasesToBeProcessedInDependency | DSS added for MaxChildCasesToBeProcessedInDependency Very slow Wait shape processing performance was seen when there were more than 499 child cases in a parent case. This has been resolved by adding a DSS to control the processing of dependent cases where Current AG is same as Dependent AG. Use "MaxChildCasesToBeProcessedInDependency", and provide the value for maximum number of cases to be processed in same thread. By Default the value is set to 499. |
Case Management |
| INC-252536 | 772093 | Status visible in history after field auditing | After performing field auditing for the pyStatusWork property and changing the status of the case, the field audit of the case history showed the old value in the UI even though the the D_pxFieldHistory data page had the new value. This was due to some non-autogenerating code present, and has been resolved by reworking the visibility conditions in pyDynamicNewValue and pyDynamicOldVlaue and adding StatusWork in the pyIsControlHandled rules. | Case Management |
| INC-253340 | 771195 | BAC attachment issue resolved | Clicking "Attach Content" was not bringing up the dialogue box to attach content. Network call logs showed "HTTP 403 error" and a SECU0019 alert was observed. This was an issue with BAC, and has been resolved by registering the AttachmentForECM local action in the Work- .pyAdvancedAttachmentMenu navigation menu. | Case Management |
| INC-255107 | 777491 | Added update/delete assignment exception handling for bulk approval | When using bulk approval for pending approval cases, the flow was not resuming after a wait shape. This has been resolved by adding exception handling in the pzUpdateAndDeleteAssignments activity. | Case Management |
Cloud Services
8.8.2 Resolved Issues for Cloud Services
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-247059 | 761724 | M3 session stopped when node is disconnected | If a node was in the middle of the shutdown process and the logging subsystem already halted, a null pointer error occurred due to the M3 thread waking up every minute to log the JVM metrics. This has been resolved with an update which will stop the M3 session whenever the node is checked and disconnected. | Cloud Services |
Conversational Channels
8.8.2 Resolved Issues for Conversational Channels
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-249636 | 769492 | Consistent Data extraction from emails | When extracting key-word based data from emails, the data extracted from the body or the subject of email was different than the data extracted from the attachment of the email. Investigation showed pyResolvedValue was not passed to D_pzEntityPropertyMap from pyEntities during attachment analysis, causing the case property to take pyValue instead of pyResolvedValue. This has been resolved by adding pyResolvedValue from attachment analysis to D_pzEntityPropertyMap. | Conversational Channels |
| INC-256209 | 777216 | Resolved datapage error when opening channel email | Each time an email from an email channel was opened, the error "Required parameter 'cid' for data page 'D_pyAttachmentCacheByCid' cannot be blank" was logged. This was traced to using the data page as a step page in the same step when checking for null parameters, and has been resolved by removing the data page as step page. | Conversational Channels |
| INC-256526 | 777167 | Service case correctly created for email with extended subject line | When the subject on an email was very long, the email triage (ET) case was created but the corresponding service cases were not. This was traced to the subject line being truncated and assigned to pyLabel for the ET case creation while pyWorkPage.pyInbound.pySubject, which held the non-truncated value, was used while creating the service case. This has been resolved by adding .pyLabel to CreateWorkFromMail of Work- class. | Conversational Channels |
| INC-257145 | 781025 | Corrected extraneous final comment appearing in chat transcript | Downloaded chat transcripts had an additional message from the chatbot, "Sorry, I did not understand that", after the system message "System: The conversation has disconnected". This has been resolved by adding a new check to skip processing an outbound message when a customer has ended the session event. | Conversational Channels |
Data Integration
8.8.2 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-222857 | 743252 | Resolved null pointer error for OpenAPI import | A null pointer exception was generated when attempting to import OpenAPI specification to integrate with the REST API to generate and map request and response for all REST service methods. This has been resolved by adding a null check to propsMap which gets properties from Schema in OpenAPIReaderImpl class. | Data Integration |
| INC-226843 | 778722 | Updated clearance of stale passivated search data | After performing a search, expanding one of the search results in the work table, and then passivating the session, reactivating the session later and performing a new search populated the table with new results as expected, but expanding an item showed the previously expanded search result instead of the new one. This was caused by stale data holding a page with the name which was passivated but not yet activated, and has been resolved by explicitly removing the passivated page from the mPassivatedPages set. | Data Integration |
| INC-228124 INC-250963 INC-252455 |
771912 767025 768794 |
File Listeners correctly process files from external S3 | File listeners were not correctly processing files from S3 storage. This was traced to a null pointer exception in the S3Factory.getTImer method, and has been resolved. | Data Integration |
| INC-230648 | 777807 | Diagnostic logging added for preprocessing deferred operations | In order to assist with identifying potentially corrupted underlying properties triggering a runtime exception when performing a transfer from the worklist to the work queue, additional diagnostic loggers have been added to DirectStreamEncoderV7.java. | Data Integration |
| INC-232467 | 767040 | DSS added to control access to lower versions of Rule-Utility-Functions | Some functions which belong to a different application were accessible in activities and started giving an error after deployments to other environments. To address this, the DSS RufFilterByRulesetVersion has been added. The default is 'false' to maintain the current behavior of allowing access; setting it to 'true' will restrict access to Rule-Utility-Functions present in lower major version rulesets. When the value is changed from false to true a server restart is required. | Data Integration |
| INC-236049 | 766906 | invokeXMLParseRule updated to ensure activityParamPage correctly initialized | After update, a "java.lang.ClassCastException: java.lang.String incompatible with com.pega.pegarules.pub.runtime.ParameterPage" error resulted when calling a connect java rule to fetch data and store it in a data page which was then invoked from another activity called from a flow. Resubmitting the same flow without changing anything worked as expected without error. The issue only occurred when using the Apply-Parse-XML step with a blank ElementName parameter, and was traced to an issue with the parse rule code flow logic where the activityParamPage param was not initialized correctly in every code path. This caused the error when the value had already been set to an incompatible type. To resolve this, the common code for the two invokeXMLParseRule methods has been merged to ensure both add activityParamPage to the paramPage. | Data Integration |
| INC-237985 | 775556 | Suppressed unnecessary SOAP exception | SOAP service invocations were intermittently failing with the message "Content-Type HTTP header is missing". The Content-Type header is only used as a means to determine the SOAP service method name, which can also be derived from the endpoint URL or the SOAP body. To address this, the SOAPService code has been modified to suppress the exception that was being thrown when there was neither a SOAPAction or Content-Type HTTP header value. If actionToken is missing, the action can be taken from the HTTP body. The system will still generate an exception later if it cannot derive the SOAP method name from other parts of the request. | Data Integration |
| INC-239789 | 773083 | LRUMap removed to resolve listener null pointer error | The email listener was running but not picking up and processing the records even there were few unread mails in the inbox. The "Last access" was updated periodically as if the listener was monitoring the inbox even though emails remained unprocessed. This was traced to a null pointer exception when retrieving the fresh access token, and was caused by the MSGraphEmailClientProxy class where LRUMap was being used with max size of 50 in a synchronized way. The max limit of the map was exceeded, causing deletion of entries (auth profile name with an object for locking) which led to a null pointer error being thrown while synchronizing on a null object. This has been resolved by removing LRU Map as its hard limit caused an error, and by adding handling that will put the listener to sleep when encountering unknown exceptions. | Data Integration |
| INC-239993 INC-240101 |
769234 769231 |
Corrected From address value when using MSGraph | When viewing an email attachment pop up in MSGraph, the From address was not displayed correctly. This was traced to an incorrect value of the pyFrom parameter due to the principal name value in the email account rule being configured with application settings, and has been resolved. | Data Integration |
| INC-240298 | 766841 | Corrected harness refresh in Ajax container | Harness refresh was not working in Ajax container tabs. Investigation showed "main" was undefined due to the system not creating the form element when there was only one fieldset in the container, and this has been resolved by updating the submitWhenFail method in pzpega_ui_doc_submit. | Data Integration |
| INC-240745 | 754795 | Currency code added for Sierra Leone | Support has been added for the new Sierra Leone currency code, SLE. | Data Integration |
| INC-241055 | 759632 | Reset flag to resolve delegated rules issue | After editing delegated data type and the closing screen, favorite rules were not opening properly and the UI was not displayed correctly. Investigation showed that when editing a delegation data type row, clicking on the close button of the window without saving or cancelling or clicking any where in the screen caused the flag D_DelegationConfig.pyIsFromManageChangeLP to not reset to false, impacting the other rules when opened directly. This has been resolved by adding an update to reset the above flag to false when the close icon is used in this scenario. | Data Integration |
| INC-243067 | 764730 | Message IDs correctly appended when using MSGraph | After switching to MSGraph, the Message-IDs were not appended to the References header for reply, reply all, and forward, causing an issue when identifying whether a work object already associated with the existing thread was in the system. This was traced to a difference in message ID formats between MSGraph and IMAP, and has been resolved by overriding the updateMessageID() method of MimeMessage class. | Data Integration |
| INC-243285 | 764833 | Logic updated to handle digital certificates in MSGraph | When using MSGraph, attachments were not being stored if they contained a digital certificate. This was traced to the system failing to extract attachments from email with mimetype application/pkcs7-mime, and has been resolved by updating the logic to handle application/x-pkcs7-mime or application/pkcs7-mime attachments. | Data Integration |
| INC-244872 | 764103 | MSGraph REST API support | Support has been added for the MSGraph REST API client to send attachments which are greater than 3MB. | Data Integration |
| INC-245088 | 765265 | Corrected execution calculation for CleanupServiceMonitorInstances agent | When using the pzCleanupServiceMonitorInstances agent to delete the service invocation history records which are older than the specified value in DSS- service/MonitorInstanceTTLMins (in mins), setting a value greater than 35791 minutes caused the time to be miscalculated. This has been resolved by updating the data type from int to long. | Data Integration |
| INC-247166 | 766059 | Export allows comma separated filter values | Delegated table records were not exporting when there was more than one filter value in the search box. This has been resolved by removing the replace function to enable exporting the record from data type with comma separated fields. | Data Integration |
| INC-247173 | 766515 | Atmosphere jar updated to resolve screen pop failure | The PegaCall application was receiving screen pop requests from the telephony systems, but there was an intermittent issue with generating a screen pop to the user. No error was generated. This was traced to a null pointer exception related to Atmosphere which was removing the necessary resource for the screen pops from being delivered, and has been resolved by upgrading the atmosphere jar version. | Data Integration |
| INC-248011 INC-246686 |
772043 775913 |
DSS added to skip corrupted BLOB property | It was not possible to open the records if a BLOB contained a corrupted property. To address this, DSS settings have been added which will allow conditional bypassing of a corrupted property during BLOB deserialization. a. Dynamic System Settings short description : propertiesToIgnoreDuringBlobDeserialization Owning ruleset : Pega-Engine Setting purpose : propertiesToIgnoreDuringBlobDeserialization Value : Corrupted property name b. Dynamic System Settings short description : dumpBlobOnDeserializationException Owning ruleset : Pega-Engine Setting purpose : dumpBlobOnDeserializationException Value : true A restart is required. |
Data Integration |
| INC-248681 | 774816 | Correspondence circumstance evaluated incorrectly | When using a circumstanced correspondence template, the base version was retrieved when creating the emails. After re-saving the circumstance definition used for the correspondence template, the correct correspondence template was selected during the email generation. This was traced to the circumstanced definition being filtered during the application calculation, and has been resolved. | Data Integration |
| INC-249800 | 768003 | Exception handling updated for PRPulseTRREQProcessor | When the PRPulseTRREQProcessor.prprocessMessage method is run, the node.handleTerminateRequestorRequest can throw a com.pega.pegarules.pub.context.StaleRequestorError exception. StaleRequestor handling has now been added to PRPulseTRREQProcessor in order to ensure the System Pulse thread which dispatches pulse messages continues to function properly. | Data Integration |
| INC-249832 | 768723 | Changed log level to debug for withdrawn rule | Logs were filling with the error "Failed to find a 'RULE-DECLARE-EXPRESSIONS' with the name 'PYLABEL'". This was due to the rule being searched in child class where it was not present and in its parent class where it's withdrawn. To resolve this, the logger level has been changed from error to debug in VirtualTableCandidateRuleResolverImpl.java. | Data Integration |
| INC-252186 | 772088 | String.FormatMessage() also searches class name | Previously, the @String.FormatMessage() rule only searched message rules in the @baseclass. This has been expanded with the addition of code to retrieve the message class name from the message key in MessageEvaluator#getLocalizedText(). If the message key has a class name, then the @String.FormatMessage() function will return the expected message. | Data Integration |
| INC-252652 | 770335 | CompareTwoValues Rule-Utility-Function refactored for performance | Slowness during PegaMKTContainer API calls was traced to the CompareTwoValues Rule-Utility-Function comparing all different data types, starting with a Date and Timestamp comparison that consumed excessive CPU cycles. To resolve this, CompareTwoValues has been refactored to improve efficiency and performance. | Data Integration |
| INC-252658 | 777587 | Localization added for en_MO | Support has been added for the Asia/Macau (en_MO) locale. | Data Integration |
| INC-254329 | 774884 | Archival indexer performance improvements | The indexer job in archiving and purging was taking an excessive amount of time when maxIndexerRequestors=1. This delay was traced to forward chaining being enabled, and has been resolved by disabling forward and backward chaining for the archival and search indexer to improve performance. Chaining isn't needed since there are no changes made to the case. | Data Integration |
| INC-254760 | 778696 | Handling updated for Europe/Amsterdam calculated date time | When using the getAsBusinessTime() function with the timezone set to Europe/Amsterdam, the calculated date time was returned as 20221230T080000.000 GMT+01:00, but setting this value in a DateTime property did not include the +01:00 at the end of the string and the property value became 20221230T080000.000 GMT, which was incorrect. This was traced to the parseInternalDateTime function ignoring the offset value for backward compatibility, and has been resolved by adding the Europe/Amsterdam timezone to the en_US and nl_NL locales to generate timezone codes without offset values. | Data Integration |
| INC-255906 INC-257221 |
778556 780058 |
Archival process made more resilient | The PegaPurger was failing with the error “NullPointerException / Unable to Execute the activity for purging". This was traced to an ArrayList which wasn't thread safe, and has been resolved by using a SynchronizedList to avoid null pointer. Additional improvements have also been added to the archival process to make it smoother and more resilient. | Data Integration |
| INC-255933 | 81133 | Savable data page caching updated to improve performance | Network calls were issued every time a data page was loaded even when the data page was marked as requestor level and reload once per interaction was unchecked. This caused a significant performance impact. To address this, savable data pages are now cached by default and a DSS has been added to allow modifying the caching parameters or turn off caching completely. For available settings, please see https://docs.pega.com/bundle/platform-88/page/platform/data-integration… | Data Integration |
| INC-257572 | 781879 | LoggerContext initialization updated | SoapAppenderPega was failing to initialize or was stopping unexpectedly. This was traced to a null pointer exception and has been resolved by updating the LoggerContext initialization to check whether it has been initialized with class loader by default, and if not it will initialize LoggerContext again with class loader. | Data Integration |
| INC-257632 | 781172 | Expunger updated to handle on-premise | When running Pega Infinity on-premise the error "Issue retrieving reference file://pegacloudfilestorage:/archive/archivedclasses/Pega-DM-Simulation-Bias" was generated by the internal.RepositoryManagerImpl function. This was caused by pyPegaExpunger running pzPerformExpunge by default despite there not being a cloud storage component designated. This has been resolved by updating Expunger for on-premise scenarios. | Data Integration |
| INC-294170 | 80645 | MSGraph integration allows proxy endpoints | In order to better control access, support has been added to route internet facing HTTP endpoint interactions for MSGraph email integration to use a configured proxy end-point. More information is available at https://docs.pega.com/bundle/platform-88/page/platform/data-integration… | Data Integration |
| INC-89249 | 79819 | Google Cloud Storage (GCS) support updated | Previously, errors were seen during certain functions when using Google Cloud as a repository. To address this, an update has been made to improve integration for storage and retrieval. Please refer to the available documentation for "Configuring a Google Cloud repository" for more information about the updated procedure for using this service. | Data Integration |
| SR-D13375 | 484792 | Added handling for null requestor returned to ManagementDaemon | An invalid parameter exception was raised by the ManagementDaemon executing checkRequestors method. This occurred when the requestor argument, retrieved by the ManagementDaemon, was attempting to determine whether a PEGA0019 alert should be emitted in case of a long running requestor, but the NodeRequestorMgt.getRequestorNames() implementation returned non-existing application requestors. This has been resolved by adding handling for InvalidParameterException in cases where the requestor is deleted before the job is executed on it. | Data Integration |
Decision Management
8.8.2 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-235496 | 766562 | When rule added to control attachment thumbnail generation | In some circumstances an unauthorized user may be able to view the thumbnail generated for an uploaded attachment. To address this, the when rule pycangeneratedocumentthumbnail has been added which can be used to prevent thumbnail generation. The default value is true, which will allow thumbnail generation. | Decision Management |
| INC-243039 | 756041 | HealthCheck logging improved | In order to assist with resolving node issues, when the Pega HealthCheck monitor daemon evaluates a cluster node member as non-responsive or slow responsive, the HealthCheck monitor will include the runID information in the logfile message. | Decision Management |
| INC-245799 | 764375 | Updated action rule validation check | Check-in of the action rule was failing due to the wrong configuration of the eligibility criteria. This was caused by private checkouts intermittently not being released correctly if validation failed during rule check-in. This was a missed use case, and has been resolved by correcting the validation of action rules during CR submit. | Decision Management |
| INC-247517 | 764156 | Corrected dirty pop up message incorrectly displayed | The dirty dialogue was being thrown upon commenting on a Pulse post, even when there were no unsaved change in the form. Investigation showed the method "pega.u.d.clearDirtyState" was not being called when posting a comment in the Pulse, only when making a post. This was a missed use case, and has been resolved by adding the clearDirtyState function after posting a reply. | Decision Management |
| INC-247763 | 769869 | Security updated for input text | Sanity checks have been added for spaces, documents and cases to improve security. | Decision Management |
| INC-248221 | 767225 | Distribution simulation results cleaned up on resolution | Simulation results were not cleaned up from the database table-type output destination when a simulation was withdrawn/resolved. Over time, using the same output destination for simulations led to a large number of records in the database table and subsequent reports run on that table were timing out. To resolve this, a new activity has been added to truncate simulation results on case resolution. The pxCleanUpSimulationResults API used for one-time clean up of results for resolved simulations can also be used to clean up older runs. | Decision Management |
| INC-249244 | 764245 | Prompt class value correctly propagated to ConditionBuilder page | When opening the expression builder from source (right) expression field in the Data Join property panel, the wrong page context was used by the expression builder. This was due to previous work which changed the promptclass parameter such that the primary class used by the Expression Builder is now the primary class of the strategy instead of the appliesToClass of the component or page selected in the data join component. To resolve this, a data transform has been added to propagate the prompt class value from the Component page to the ConditionBuilder page. | Decision Management |
| INC-249829 | 764845 | PEGA0075 alert more detailed | The PEGA0075 alert has been updated to include Query info (to identify the involved column family), Requestor ID, Interaction number, Correlation id, and PAL data. | Decision Management |
| INC-250008 | 767821 | Updated exception handling for empty partition key | No results were shown after a dataflow run, and a DdsBatchOperationException was logged at the compose shape in the dataflow. This was traced to the DDS DataSet returning empty results instead of throwing an exception when given an empty partition key, and has been resolved. | Decision Management |
| INC-251504 INC-256560 INC-256560 |
773156 778025 780839 |
Resolved memory issues related to ADMSnapshot agent | Production utility nodes were terminating due to out of memory errors. This was traced to the RULE-OBJ-ACTIVITY DATA-DM-SUMMARY PYSAVEWEEKLYANDMONTHLYSNAPSHOTS activity, used in execution monitoring to aggregate weekly and monthly data. Investigation showed the merge operation of a numeric summary for each predictor was added to the list, increasing the size. When this was serialized into JSON and de-serialized again, it occupied a lot of heap memory for each predictor which then affected the utility nodes' heap memory. To resolve this, a compress call has been added to summaries post-merge for daily, weekly, and monthly snapshots. | Decision Management |
| INC-252956 | 778804 | NBA_TopLevel Strategy Proposition Filters updated for optimization | The expression parsers for EmailTreatmentEligibilityRule and MobileTreatmentEligibilityRule have been updated to handle multiple ORs, allowing them to be optimized. | Decision Management |
| INC-253588 | 775763 | Security updated for Pulse text | Sanity checks have been added for Pulse text to improve security. | Decision Management |
| INC-254828 INC-252654 |
777290 778148 |
Warning logging updated for Avro schema | After creating a dataset with the Avro schema, the Kafka save operation created extremely large log files which led to system performance issues. This was traced to warning messages generated for non-mandatory fields, and has been resolved by discontinuing logging exceptions on null values for Avro schema. | Decision Management |
| INC-256236 | 779524 | Zero results for user tag will display as (0) | On the tag navigation tab, the display indicated ( -- ) if the current user did not have any recently entered tag. In earlier versions of Pega this was indicated as (0). This difference was due to a change in the implementation for D_MostRecentlyUsedTagsForResource which resulted in the ( -- ) if the report definition did not have any pxresults and no value was set for Primary.pxResultCount. This has been modified to display (0) by updating property-set to default pxResultCount to 0 in pyGetTagsAcrossWorkpools activity. | Decision Management |
Low-Code Application Development
8.8.2 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-232907 | 776589 | Added handling for service-HTTP locking error | Operator via service HTTP was unable to check-in its own checked out record, generating the error "Update record failed: .pyRuleSet: You are not the owner of this checked out rule." Investigation showed pxThread.pxSecuritySnapshot.pxPersonalRuleset changed in the middle of processing. This has been resolved. | Low-Code App Development |
| INC-237496 | 766394 | Corrected overlay context loss in Cosmos | Attempting to add a condition in the eligibility criteria for a Next Best Action in the Cosmos portal caused the field to refresh and remain blank. Investigation showed there was a loss of context for overlays, which has been resolved by moving the hidden layout to the last dynamic layout in the pzInnerEmbedConditions section. | Low-Code App Development |
| INC-237925 | 768607 | Corrected validation rule resolution after modification | A validation rule showed OR in the statement but validated at runtime as an AND condition. This happened only when the second condition was given as AND, then one more condition row was added as OR, and the second condition was deleted, and has been resolved by updating the pzBasicValidWhen section to remove the pzSwitchOperation activity call on refresh of pyCondValueCategory. | Low-Code App Development |
| INC-239887 | 766720 | Manual results pages will have ObjClass explicitly set | After defining multiple case types, for example CaseTypeA and CaseTypeB, as related cases for another case type such as CaseTypeC, trying to add CaseTypeA as a related case to CaseTypeC using the related case functionality generated an exception on selection of CaseTypeC in the first dropdown. This was traced to pxObjClass, which is required for Obj-Sort to function, not being set automatically due to data page / activities. This has been resolved by ensuring pxObjClass is set when creating pxResults pages manually. | Low-Code App Development |
| INC-243595 | 761318 | RecordInner updated to check Rule-RuleSet- during new component save | After opening Designer Studio -> Application ->Components and creating a new component, adding label and version and attempting to submit resulted in the message "Error- No open ruleset versions available". This has been resolved by updating pxUpdateRecordInner and pxCreateRecordInner to check for Rule-RuleSet- instead of only looking at Rule-RuleSet-Branch so that a version is not required for ruleset instances themselves. | Low-Code App Development |
| INC-246401 | 779554 | MaxRecords default raised to handle a large number of skins | After performing a major ruleset skimming, a warning appeared indicating that a skin was not available in the application even though it existed in a new ruleset version which was in the application rule resolution. This was traced to the "pyMaxRecords" parameter being set with a default value of 50 during query execution, and in those first 50 results, the skin rule from highest version was not available due to there being over 100 skin rule instances in different major versions in the app. To resolve this, the default has been modified to listPg.putString("pyMaxRecords", "10000"); for CheckForWarnings in Rule-Application to handle cases where there are a large number of skins. | Low-Code App Development |
| INC-248341 | 764942 | Corrected Expression Builder error when opening from Decision Table | Opening any delegated decision table from the UI and then opening the Expression Builder generated a pop-up message. Clicking on "OK" closed the pop-up but a new page showing an error message was opened. A security trace showed the activity pzCreateNewTempPage did not have the necessary registration in the pzEBHiddenElement control, and this has been resolved. | Low-Code App Development |
| INC-250133 | 773512 | Added startingWorkHandle check to enable case unlock | Using the DXAPI to get screen definitions and submission on an assignment submission resulted in a 400 HTTP error and the message "ValidationMessage:Unable to unlock [case id#]". Investigation showed this was due to a missing reference to "startingWorkHandle". To resolve this, the performB2BAssignmentCheck activity has been updated to add a precondition to check that Param.startingWorkHandle is not null. | Low-Code App Development |
| INC-250717 | 775091 | Decision table export corrected | After update, the decision table export functionality was not working. However, if a trace was started the functionality worked without any issue. Investigation showed there was a timing issue with the removal of the iframe before actual download of the document. This has been resolved with the addition of a timeout in pzRuleDeclareDecisionTableStandard.js to ensure the document is downloaded. | Low-Code App Development |
| INC-253430 | 774564 | Resolved name conflict in Expression Builder | After update, attempting to edit an existing expression caused it to disappear from the Expression Builder in the decision tree. The error "Data Transform not found" appeared. Investigation showed there was a name conflict during resolution due to the system attempting to populate the class name instead of the expression condition. This has been resolved by updating the function names in OpenRuleAdvanced_OverLabel to rename functions declared in this control but called from other places with the suffix "_OverLabel" so the Javascript call is not overwritten with the function of the same name from other controls. | Low-Code App Development |
Mobile
8.8.2 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-223328 | 736535 | Mobile app push notifications history updated | The history table of mobile push notifications remained empty after sending a push notification if the history table had over 1000 records. Investigation showed push notifications are taken in inpxGetPushHistory using Obj-Browse and then filtered in Java step by appID so the oldest push notifications were listed first, and the list of instances did not show the pagination even though it existed. To resolve this issue, the sorting in push optimization has been modified. | Mobile |
| INC-238299 | 752473 | Server response filtering updated | To improve security, additional filtering has been added to the server response. | Mobile |
| INC-244702 | 770311 | Corrected Assign Mismatch error on Mobile | After a new comment was added to a work object on Mobile, the assignment status was set to "ERROR: ASSIGN MISMATCH" and it was not possible to perform any action or advance any further. This was traced to a security issue related to the the Assign-acquireworkobject activity, and has been resolved. | Mobile |
| INC-247240 | 763799 | Value updated for Development/Sandbox APS certificates | Apple has changed the value of the Common Name (CN) attribute for Development/Sandbox APS certificates. Support has been added for this new format in the pzOnCertificateChange activity. | Mobile |
Project Delivery
8.8.2 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-229116 | 742054 | Transport Layer Security (TLS) documentation updated to clarify additional steps after update | In some cases, customer search failed to work after updating from Pega Platform version 8.4.6 or earlier to version 8.7.2 or higher. In Pega Platform version 8.7.2 or higher, Rest Connect causes this issue when the lowest allowable SSL/TLS version is set to TLS version 1.0. To address this, the Transport Layer Security (TLS) best practices documentation has been updated to clarify that the rule form for outbound connections must be edited to use the appropriate protocol supported by your Pega application's underlying Java version, preferably TLS 1.2 if the server supports that version. | Project Delivery |
| INC-236160 | 741166 | Clarification for mobile app update best practices | The documentation related to best practices for updating mobile apps has additional information to clarify that when creating a new authentication service name, it should not be created with an existing authentication service name. Pega Platform includes different authentication services out-of-the-box in different releases. When you update Pega Platform, your existing authentication service name must not conflict with the out-of-the-box authentication services of the newer Pega Platform version. | Project Delivery |
| INC-242183 | 757210 | Mask property visibility documentation updated | The documentation for mask property visibility for users has been updated to clarify that when masking an embedded property, the ABAC property read policy must be configured in the work class where the embedded property is being referred and not in the class where the leaf property exists. If configured improperly, the application can display the masked property to unauthorized users. For example, if using an embedded property called WorkPage.Customer.Name, the ABAC property read policy must be configured on the WorkPage class and then the embedded property is added in the masked properties list instead of the class where the leaf property Name is defined | Project Delivery |
Reporting
8.8.2 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-189766 |
676262 | Search thread timeout adjusted to 30 seconds | Searches were not working and general performance issues were seen on the nodes. A review of logs showed that there were requestorLockExceptions and thread dumps indicated there were problem threads waiting for search result. To prevent this, the search timeout has been adjusted to 30 seconds. | Reporting |
INC-251270 |
778980 | Dev Studio search works with ABAC | When ABAC was enabled, a null pointer exception was generated in ClassMapImpl when using Dev Studio search. This was caused by a null value for PegaSearchContent.className passed to the method FilterValueResolver.resolve(), and has been resolved. | Reporting |
| INC-231890 | 740604 | DSS added to control empty value display on export to Excel | A DSS has been added which allows customizing the export to Excel function to use zero for the decimal instead of showing an empty value. Set ExportToExcelDecimalUseZeroWhenEmpty to true to override the default behavior of zero values being blank. | Reporting |
| INC-233990 | 744707 | Handling added for special characters in tab name | After update, a Report name with special characters showed the ASCII values in the tab names. This has been resolved by decoding the HTML in javascript using a javascript function before setting the title. | Reporting |
| INC-241251 | 753497 | Report filter categories correctly localized | The filter category displayed in the header of the reporting landing page was not being localized. This was traced to an error in the "FieldValueKey" parameter in the pzGetStyledLocalizedText control, and has been corrected. | Reporting |
| INC-242955 | 757160 | Dev Studio search updated | Search in Dev Studio was not working as expected after update. To resolve this, search has been updated to accept a regex expression containing two hyphens for work ID pattern check. | Reporting |
| INC-250412 | 777460 | Corrected Report Viewer error | After update, the Report Viewer tab had a difference in the Group Results options of a new report definition and the error "pyReportDefinition: "pxRequiredSkill" This property does not exist or has no column mapping" was generated. This occurred when Filter Caption Settings was set to "Apply Caption to Left Side of the condition", and was traced to the "strFieldName" value in RRFilters_Logic being overridden. To resolve this, a new variable has been added to the RRFilters_Logic control to preserve the value. | Reporting |
| INC-251114 | 780106 | Corrected DateTime report filtering | The DateTime filter was not working for a report on the user portal. Investigation showed there was a case mismatch which caused the datatype to not satisfy the filter conditions for pzpopulateselectedvalues. This has been resolved by setting the filter value to Range. | Reporting |
| INC-252882 | 773408 | Handling added for maintaining count during BIX extraction | The number of records in the XML BIX extract did not match with the pxTotalClassInstanceCount of the Manifest file. This issue occurs only when there are any updates during the extraction process, and has been resolved with an update which will show the actual processed records count in BIX extraction Manifest file. | Reporting |
| INC-254593 | 777250 | DSS added to control date identification on BIX file | After upgrade, custom application behavior was not working as expected due to BIX file names having YYMMDD appended to the extraction name, for example Work_ExtractCase_00To04_1.zip under the previous version and Work_ExtractCase_00To04_221214_1.zip under the upgraded version. This date appendix was previously added to ensure the file name generated should be unique. To address this, the removal of the date from the extracted zip file name before placing in the FTP location may be controlled through the DSS setting BIX/ignoreExtractDateInZipFileOnCloud. | Reporting |
| INC-257867 | 780703 | Added accessibility for grid/list toggle | The grid/list toggle on the Cosmos reports browser was missing a label for the currently selected toggle and an accessible cue as to the current state (which option is selected). This has been added. | Reporting |
Security
8.8.2 Resolved Issues for Security
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-251088 | 770179 | "None of" added to access control policy conditions | Support for the "None of" has been added in order to support using ABAC and access control policy conditions to suppress resulting values from logged-in users visibility. The comparison value supports string, decimal, double, integer data types and consists of a comma-delimited list. The comparison value also supports value-list or page-list. The list of String values should be given inside a pair of double quotes for example: “BRAZIL,CANADA,FRANCE,GERMANY,SOUTH AFRICA,UK,USA”. The condition is satisfied if an element of the list within the Apply To property value is not an element in the list within the comparison value. | Security |
| INC-252607 | 768827 | Updated EndSession request encryption for basic logoff activity | Clicking on logoff generated an error. The error also appeared when valid MAF credentials were entered and the cancel button was clicked. This was traced to the logoff URL being encrypted with an old URL encryption mechanism, and has been resolved by ensuring the logoff URL uses the latest URL encryption mechanism. | Security |
System Administration
8.8.2 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| INC-243066 | 771239 | Corrected inconsistent production level for PDC2 | Per operational standard, the Pega Predictive Diagnostic Cloud environment (PDC2) has production level set to 5 via the setting DNodeSettings=identification/productionlevel=5. In the course of performing other work, it was found that several functions were actually using ProductionLevel=2 (development) rather than ProductionLevel=5. Investigation traced this to a cached copy of the Data-Admin-System record which asserted production level = 2 in some areas even though this should have been overridden. This has been resolved with an update to ensure ProductionLevel is correctly read from PRNode. | System Administration |
| INC-247586 INC-243512 |
763564 765343 |
Corrected tracking of MFA verification attempts | When using multi-factor authentication where a verification code is sent, it was possible to override the three strikes rule and re-enable the resend verification button by refreshing the browser. This has been resolved by adding a parameter in the requestor page of the pzHandleMFA activity which will hold the pyCount and be checked on browser refresh. | System Administration |
| INC-247916 | 770110 | Job scheduler will use current time to avoid DST offset | Job scheduler was running jobs twice after the change for daylight savings. This has been resolved by using currentTime.get(Calendar.DST_OFFSET) rather than referenceTime to reduce the potential offset mismatch. | System Administration |
| INC-249284 | 771082 | Handling added for null CreateDateTime value | Job schedulers were not running due to pxCreateDateTime being null in the pr_data table. This has been resolved with an update which will add the pxCreateDateTime value to instances of tables where it is missing. | System Administration |
| INC-249918 | 768618 | BCEL library updated | The Apache Commons BCEL library has been updated. | System Administration |
| INC-255699 | 777626 | QueueProcessorMaintenance alert threshold raised to 15 seconds | Previously, the Rule-Async-JobScheduler for QueueProcessorMaintenance was configured with a 5 second threshold, causing excessive alerts due to the actual value range on average being 6 secs with occasional spikes to 10 or 12 seconds. To address this, the alert threshold has been extended to 15 seconds. | System Administration |
User Experience
8.8.2 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
INC-237999 |
761906 | Layout renders with combined visibility and expand conditions | Visibility expressions were not working and that particular layout was not rendering when there was a combination of a visibility expression and expand layout. Either condition rendered correctly when alone, but not in combination. This was traced to the expandParam containing ".", which generated an exception when using non-template mode, and has been resolved. | User Experience |
| INC-204349 | 704561 | Updated check for portal name with search | After update, using search from a Cosmos portal landing page launched the results in a new tab, and the logoff menu did not show which portal was being used. This has been resolved by updating the 'when' rule to check if pxThread.pxPortal contains the portal name rather that testing for equality. | User Experience |
| INC-222731 INC-245380 |
734965 765373 |
Refresh corrected for iPad | Performing a screen refresh after completing a case by swiping down or clicking the client icon was not working on newer model iPads. This was traced to the overflow property being set to hidden on the body tag, and has been resolved by adding overflow auto for iOS tablet devices. |
User Experience |
| INC-231096 | 775978 | Corrected inheritance section refresh / call data transform logic | When a button was pressed in the UI to refresh the section and apply the data transform RequestSignature, which exists in both the Work and Work-Signing class, the data transform resolved correctly to the one in Work-Signing class. However, when using the DX API PUT /assignments/{ID}/actions/{actionID}/refresh endpoint, RequestSignature from the Work class is invoked. This was traced to an error in the DX API code which caused the data transform to be called from the wrong class. To resolve this, the inheritance logic for DT/ACT for a refresh in an inherited section has been updated. | User Experience |
| INC-231696 | 769656 | Added forceReconnect to address telephony error | While using telephony, a pop-up appeared intermittently indicating "Reconnecting" when an agent was on a call or idle for specific time (more than 30 mins). To address this, support has been added to use pega.u.MessagingManager.forceReconnect in handleWebSocketError. This API will be used by Pega Call to reconnect the websocket when pega.u.clientEvents.WS_ON_CLOSE is registered. | User Experience |
| INC-234202 | 763982 | Navigation items highlighted correctly when using render as single page | If "render as single page" was unchecked in the user portal, clicking on any navigation item or opening a work object from the left navigation panel caused the whole page to reload and the wrong item was highlighted in the navigation menu.This has been resolved by updating constructMetadataObject to consider context. | User Experience |
| INC-235733 | 770106 | Radio button support added for Nuance Dragon | To improve accessibility, support has been added for using Nuance Dragon to activate radio buttons by adding the necessary CSS styles to the radio button inputs. | User Experience |
| INC-240757 | 754424 | Localization check added for sourced dropdown values | When dropdown values were sourced from a data page using a report definition, the values were always localized even if the localize box was unchecked. This was due to the values being stored in Data Type when the localize checkbox controlled labels and read only text. This has been resolved by adding a check for bLocalize in Context Processor. | User Experience |
| INC-241805 | 756269 | Tab layout uses template mode when using defer load | When using defer load, the multiselect dropdown was rendered in readonly mode. Investigation showed that when the defer load checkbox was checked for section include of tab group layout, it generated non-template markup. This has been resolved with an update which will render the tab layout in template mode when using defer load. | User Experience |
| INC-242855 | 768286 | Documentation updated to include validateHiddenField DSS setting | Documentation has been updated to note that the validateHiddenField DSS setting for Theme Cosmos and other section-based applications will control whether the application validates fields that are hidden through visibility rules. By default, validateHiddenField is set to true, which means that the application fields are validated for completeness even if they are not displayed in the form. This functionality can be switched off by changing the setting value to false. | User Experience |
| INC-242985 | 757459 | Icon helper text read by JAWS | Tooltips were read by JAWS when the helper text was configured on an input but not when the text was configured on an image. This has been resolved with an update which will announce the helper text value when focus is brought to an icon in browse mode. | User Experience |
| INC-243277 | 756360 | Display of navigation link label corrected | The label of the screen flow's navigation link was intermittently displayed in an incorrect location when steps in a multi-step form in a stage were configured with a decision shape and steps were routed based on the decision result. This has been corrected. | User Experience |
| INC-243935 | 769202 | Minimize button working in Rich Text field | When using a section containing a repeating dynamic layout with drag and drop capability enabled on a Rich Text Editor, all of the buttons on the edit bar were disabled after using maximize. If the "Enable drag to reorder items" checkbox was unchecked, the minimize and maximize worked correctly. Investigation showed the sortable library injects event handles when the maximize icon is clicked, and these handles are added to the document element. Upon clicking of minimize, the correct target was not picked for the action because of the additional event handlers attached. To resolve this, a condition has been added for the Rich Text Editor in the sortable.js file to handle minimizing the rich text field. | User Experience |
| INC-243995 | 759019 | Corrected tab focus after using group-by | When interacting with grid operations such as creating groups and hiding columns using only the tab key, tabbing again once the actions were complete refreshed and focused on the beginning browser bar instead of the table as expected. Investigation showed that the button from which the popover was launched was no longer present in the screen once the grouping was completed, causing the focus to move to the browser. This has been resolved by overriding focus to a visible group-by button when the toolbar is refreshed or a button is changed due to an action in the popover invoked by the group-by button. | User Experience |
| INC-245431 INC-246531 |
764786 778035 |
Mashup loads correctly with setAuthenticationHeaders | Mashup was not loading correctly when using the pega.web.api.setAuthenticationHeaders function to set an authorization header. This has been corrected. | User Experience |
| INC-245567 | 762499 | Corrected error message handling for on-change | If there was a validation error message on a field generated by on-change of some other field, the validation message went away when the field was clicked even though there was no data change. The error message persisted on the clipboard, but was removed from the UI. This has been resolved by changing the order of the condition check for calculate expression. | User Experience |
| INC-245664 | 766612 | Adjusted display of "Case created by" to handle long name value | After creation of a case through the email listener, the "Case created by" detail was spanning out of the tile. This was caused by a long value for pxCreateOpName, and has been resolved by allowing it to break for the display. | User Experience |
| INC-245819 | 766348 | Updated visibility condition logic | After update, a visibility condition that contained references to D_CaseAssignments that was set to any stage-wide local action made all local actions not visible in the Actions menu. This was traced to the condition returning as false during runtime, and has been resolved by updating the logic in the pzPopulateAssignments activity. | User Experience |
| INC-246171 | 774008 | Tooltips localized | Localization has been added to the Pega breadcrumbs browser tooltips. | User Experience |
| INC-246207 | 765049 | Corrected tab focus for iframe | The interaction driver on the add task and close button was missing tab focus. This was traced to a missing tabindex for iframe, and has been resolved with an update which will check if the content has iframe; if so, tabindex will set to iframe else the existing flow will continue. | User Experience |
| INC-246980 | 765284 | Null checks added to resolve null deference alerts | Null dereference is low risk in general in Java applications because no memory corruption can occur. Pega rules or variables will not be null at runtime during rule execution and thus a null pointer exception will not be thrown. However, the initialization of these may be detected by a scan which documents the theoretical possibility of not being initialized at runtime. To resolve these scan reports, null checks have been added to some identified areas related to dropdowns and checkboxes. | User Experience |
| INC-247813 | 762274 | New window opens correctly from global search bar | No content was displayed when a new window was opened from the global search bar in the user portal application header. This was traced to a mismatch in parameters for the harness action, and has been resolved. | User Experience |
| INC-247967 | 764665 | Expanded Create menu item will not take submenu color | Changing submenu item colors for the "Create case menu" menu format caused the expanded Create item to take this color as well. This has been resolved by hardcoding the color styling. | User Experience |
| INC-248044 | 768776 | UI action from Mashup Screen corrected | After upgrade from Pega 8.3 to 8.7, a BAC/SECU0019 error was reported when launching harness in Mashup. This was traced to the use of a dynamic container with multi-document mode, which is an unsupported configuration for Mashup due to the BAC features introduced in Pega 8.5. Switching to a dynamic container with single document mode resolved the security issue, but using the close / cancel button on a work object in Mashup was not returning to the home page and there were resize issues due to Mashup not having extensive support for a dynamic container with single document mode. This has been resolved. | User Experience |
| INC-248452 | 766596 | Corrected rounding precision issue | A rounding error appeared during multiplication of some numbers. This was traced to precision settings for the fields and has been resolved by using toFixed in specific circumstances when the actual decimal precision is less than configured. | User Experience |
| INC-248692 | 765252 | Number controls honor custom width | After update, decimal properties with integer control were ignoring all custom width settings. Investigation showed the generated style was ' 'width instead of just width, and this has been resolved by modifying the style from "''" to '"" in order to fix the custom width issue for number controls. | User Experience |
| INC-248981 | 764956 | Screen reader correctly announces accordion button status | When a layout group(accordion) was overridden in the application skin and the checkbox was checked for "Collapse all panes on load", the panes were collapsed on load but the screen reader was announcing the state of a button as expanded even though it was collapsed. This was traced to the aria-attribute handling, and has been resolved by adding a multi-accordion identifier and updating the logic in layout group js to toggle multi-expand accordion independently. | User Experience |
| INC-249197 | 775842 | Added special handling for Asia/Jakarta dates | For timezone 'Asia/Jakarta', when the date '01/01/1964' is selected, the date is changed to 1 day less (31/12/1963) . This is an issue particular to this locale, caused by a time zone change from GMT+7:30 to GMT+7 at the end of 1963-12-31(GMT+7.30). This means the moment 1964-01-01T00:00:00 in GMT+7.30 is also 1963-12-31T23:30:00 in GMT+7. To resolve this, an update has been made which will convert using Date.UTC before applying the timezone for the dates in question. | User Experience |
| INC-249243 INC-258056 |
765690 781057 |
Corrected keyboard focus in modal window | When a flow action was configured to hide the default action button sections and then launched in a modal window, using the tab key moved the focus out of the modal window and into the background sections. This has been resolved. | User Experience |
| INC-249417 | 764839 | Updated regex for button labels in case creation screen | After upgrade, adding “&” before the letter in a button label no longer worked to create a keyboard shortcut for the button, for example using “Submit & E&mail” in Fieldvalue (pyButtonLabel) resulted in “Submit & E&mail” rather than the expected “Submit & Email”. This was caused by the system restricting two ‘&’ symbols in template mode, and has been resolved by replacing double backslash (\\d) with single backslash (\d) in the regex. | User Experience |
| INC-249703 | 768022 | Main navigation submenu icons display correctly | After adding two or three sub child Menus to the "pyCreateCaseMenu" with different Icons, selecting the child menu caused the menu name to get padding on the left and the icon for the child was stacked on top of the main icon at the top. This has been resolved by modifying pzPega_menu_item_icon_template.js and pz-cosmos-ui-portal.js so the items are displayed correctly. | User Experience |
| INC-249749 | 777858 | Screen reader focus correct when error icon displayed | The NVDA Screen reader focus was not correct after clicking submit when validation was not met. This was a missed usecase for an error icon on top of the field which prevented the focus moving to the first invalid element in the modal. This has been resolved by updating the focusToFirstInvalidField function in pzpega_ui_doc_focus to correctly handle this scenario. | User Experience |
| INC-250022 | 766729 | Loading text made available for customization or localization | When the dashboard of a user portal was being loaded, a hardcoded "loading.." string in English appeared and disappeared. This was coming from the final rule PegaCompositeGadgetMgr[Final] and was hardcoded and not localized. This rule has been modified to accommodate the localization or removal of the loading string completely by using the field value for "Loading". | User Experience |
| INC-250615 | 777281 | Tab name handling updated to support symbols | After upgrade, creating a case in a user portal that used an AJAX container resulted in symbols like '(' and ')' in the tab name being replaced with junk characters. This has been resolved by modifying the setTabName function in pzpega_ui_mdc_tabs.js. | User Experience |
| INC-251168 | 775046 | Updated breakout encryption for offline mobile app | After implementing BAC security and setting the when rule pyBlockUnregisteredRequests to 'true', any offline mobile AJAX calls with Executebreakoutcall failed. Investigation showed the pzOSCOBreakoutWrapper dispatcher itself was throwing an unregistered error.This has been resolved by encrypting the OSCOBreakout activity. | User Experience |
| INC-252009 | 776213 | Corrected PST datetime converting to GMT and then to CST | When a user in the PST time zone selected the current PST time for a submission, the value was being converting to GMT in the CST server time zone instead of PST user time zone, causing a validation failure that the date cannot be in the future. This has been resolved by updating pega_ui_calendar and pega_ui_formatdatetime handle this scenario. | User Experience |
| INC-252723 | 772303 | Able to select localized date values | Logging in using the French locale and selecting the date was generating an error. This was traced to a localization issue with strings having single or double quotes and has been resolved by adding handling for escaping single and doubles quotes in the Smart Tip message rule field generation. | User Experience |
| INC-252879 INC-250977 |
771304 778746 |
PD4ML updated | Issues with formatting PDFs have been resolved by updating the PD4ML jar to version 4.0.13fx6. | User Experience |
| INC-252957 | 780597 | Correct buttons displayed for local action in screen flow | After creating a case type which included a screenflow in the case lifecycle along with case-wide actions, progressing the case to step 2+ in the screenflow and selecting a case-wide action displayed the Back button instead of Cancel. This was an issue with pyCaseActionAreaButtons when using a case-wide action while the case is in a screen flow, and has been resolved by adding a new visibility condition for Cancel/Back buttons which will avoid showing screen flow buttons in case-wide actions. | User Experience |
| INC-253043 | 770870 | Tab key focus added to Operator icon | To improve accessibility, styles have been added to the user/operator icon to support keyboard tab focus. | User Experience |
| INC-253092 | 771594 | Corrected highlight persistence | When using a field with control Currency, entering a value into the field and highlighting it using the keyboard input ctrl + a / cmd +a added the highlight, but when the ctrl +a / cmd +a was released the highlight was removed. This has been resolved by adding an additional check for selection. | User Experience |
| INC-253692 | 773878 | AJAX container correctly shows busy indicator | The busy indicator was not appearing during a long finish assignment processing wait when using an AJAX container. This was caused by the condition to display the busy indicator only checking for document.forms.length (DC), whereas in case of an AjaxContainer, elements will present in fieldset instead of form. This has been resolved by updating the check to work for both DC and AJAC containers. | User Experience |
| INC-253866 | 776449 | Added handling for missing InstanceID | Based on a search, data from 8-10 different case types was fetched and displayed in 5 different hierarchical tables. One of the tables had a retry link column; on click, a local action opened which could be submitted. When there were a large number of records, the submission took a long time but no busy icon appeared. Investigation showed this only happened with hierarchical tables and not with optimized tables. The intanceID was not getting generated for the hierarchical table, due to which the grid object was stored with an undefined key by replacing the existing grid object and storing the last table object details in the metadata. To resolve this, pyInstanceID will be set on the componentInfo object to get the correct IDs for the treegrid during registration. | User Experience |
| INC-253940 | 775005 | Currency Control alignment corrected | The currency symbol position was not calculated properly and was misaligned when placed on the left side of the span element. This has been resolved by changing styles to support height change so the currency symbol is displayed as expected. | User Experience |
| INC-253992 | 775255 | Filter pop up displays correctly for absolute position | The filter pop up was not displayed properly in reports when the parent container position was absolute. This was due to a missing condition check, and has been resolved. | User Experience |
| INC-254668 | 773111 | Handling added to correct Moment DST offset for dates after 2037 | When a datetime of greater than 2038/01/01 00:00:00GMT was read from the clipboard In certain timezones, 1 hour was incorrectly removed as a DST offset by the third-party Moment JS. In cases where the time was set to midnight, this resulted in the displayed date being 1 day early. This issue only affected datetime values and can be avoided by using a date value instead. To resolve this, handling has been added for correctly returning the moment object if the year is greater than 2037 for a datetime control with date property. | User Experience |
| INC-255216 | 776252 | Corrected decimal formatting display | Issues with formatting a decimal value were seen after update. The error '<Number>' is not a valid decimal value was traced to the system enclosing quotes in a decimal input property after submit. This has been resolved by correcting the value formatting if the last character is a separator. An issue with the "$" value not being visible when an error message is displayed has been resolved by allowing updating of the date-value for backspace and delete. | User Experience |
| INC-255697 | 780077 | Active when condition restored for read-only harness | The Active When condition in the Navigation rule was not working for a read-only harness when navigating through the screens, leading to the current step in the navigation menu not being highlighted. This was an inadvertent side effect of work done on the "pzpega_control_menu" rule which has been reverted to restore the previous behavior. | User Experience |
| INC-256304 | 778347 | Layout header property read by screen reader | After adding "Include icon or value" to a layout header, a property or constant was not being read by the screen reader in browse mode with arrow keys. This was caused by the aria-label that was being applied to the button element overriding the constant text property and causing it not to be read by screen readers, and has been resolved by removing the aria-label from layout_header_content for a collapsible dynamic layout. | User Experience |
| INC-257175 | 778982 | Selections not cleared on adding search filter | After performing a search, applying filters caused the selection to be cleared. This has been resolved by removing filterexpression and search from the dependency of clearSelectedRows. | User Experience |
| INC-258212 | 781041 | Corrected Expand-Collapse icon accessibility | When an optimized table is configured with grouping enabled, Pega renders group headings with a button that can expand or collapse a particular group. After update, the top-most button (expand/collapse all) was not accessible using keyboard navigation when using Microsoft Edge. This has been corrected. | User Experience |
| INC-258275 | 781098 | Improved checkbox accessibility for repeating dynamic layout | Table filter checkboxes did not have the correct label and state for an accessibility reader to read-out, causing the state of the checkbox and the context of the checkbox to not be announced. This has been resolved by changing the repeating dynamic layout navigation mode to "Use form navigation (by tab)". | User Experience |
| INC-258427 | 780417 | Corrected typo in toLowerCase function | The processHarnessType.toLowerCase function in the ui_doc file has been updated to correct a misspelling in the code. | User Experience |