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 formatted 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.)
| Ticket # | Issue # | Title | Description | |
|---|---|---|---|---|
| SR-C60247 | 413680 | pzRuleFormToolbarPopulateActions works when @ is present in the operator ID | Using pzRuleFormToolbarPopulateActions to get all the versions of the rule was not working as expected if the '@' symbol was present in the user ID. This was caused by the Rule-.pzRuleFormToolbarPopulateActions activity not forming the private rules correctly in this use case, and has been fixed. | |
| SR-C65381 | 415189 | Added check for pyType when refreshing the Declare_pyDisplay Page | The standard behavior of clicking a link in the left navigation of the Pega Diagnostic Cloud manager portal is to open a new thread which automatically adds/updates the Declare_pyDisplay Page. However, in some circumstances opening the work items and clicking the navigation link followed by a refresh/F5 from the Google Chrome browser caused the Declare_pyDisplayDatapage to become corrupted and either froze the screen or caused a new popup window to open. This was traced to a situation where the parameter "pyType" was not present in one of the cases, causing the system to rely on "harnessName" instead. To resolve this, a check has been added that will retrieve pyType from the docObj parameter page of the pzpega_ui_dynamiccontainer.js file if needed. | |
| SR-C67397 | 416252 | Added check for missing rule data when using abstract class in CSS | Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page. | |
| SR-C68069 | 416698 | Page group use added to referenced properties context for RDL | After upgrade, a stack mismatch error was generated by a previously-working configuration that used a nested RDL with a section under Work- class that itself contained an RDL with Data- property that then included a section from Data -- class which contained another RDL that referred to the Work- Page Group. This error was caused by the use case of page group being missed during implementation of referenced properties in ContextProcessor processListNode, which has now been resolved. | |
| SR-C68134 | 423618 | Support added for configuring key stores using prconfig or system properties | Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties: -Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword |
|
| SR-C68993 | 416163 | Expression exngine correctly evaluates boolean type property with expression | When using a dynamic layout with a visibility condition expression and 'Run Visibility Condition on client' checked, a condition such as .VehicleDetails != '' && .VehicleDetails = true was not being evaluated as expected after upgrade. This issue was related to changes made to the expression engine to get the initial evaluation result at the server side, and was caused by a missed use case for a boolean type property with expression. This has been corrected. | |
| SR-C69441 | 415967 | Copy/Merge Wizard ProcessRequest will create new rule instead of modifying the old | When using the Copy/Merge wizard to move the rules from one ruleset to another with the "Delete Source RuleSet(s) upon completion of merge" option set to YES, the SECTION rules were still being referred even though the target ruleset was not part of the application stack. In the Tracer, it could be seen that the rule appears in the source ruleset version even though the ruleset did not exist, and attempting to open the rule from tracer or from Live UI caused it to open in the Target ruleset version (which was not part of application). This was traced to the system not updating the cache, leading to RULE-OBJ-ACTIVITY PEGAACCEL-MANAGEMENT-REFACTOR-RULESET PROCESSREQUEST applying an incorrect strategy when updating the rule and rulesets. Because the original rule was never invalidated, its shortcut and entry remained and any references to it weren't updated. To correct this issue in a comprehensive way, the ProcessRequest has been modified to create a new rule instead of modifying the old rule, and pxCreateDateTime will be added to the rulepage before saving. | |
| SR-C69567 | 409190 | ICMP ping flag enabled and Hazelcast alerts/info messages added | Hazelcast Professional Services recommends enabling ICMP ping as a method to detect network failures more quickly. This can also help to determine whether a failure is due to a network outage: if the ICMP ping is successful but the heartbeat timed out, that may be an indication of a unresponsive (GC pause, long running process, etc) node. To facilitate this use, the ICMP ping flag can now be used in conjunction with enabling ICMP ping on EC2 through the security group and enabling ICMP in the Hazelcast configuration. In order to facilitate determining root causes for Hazelcast errors in the logs, the following alerts and info messages have been added: Actionable Events (Alerts): Each of these events is worth noting an alert for. An action may be necessary. - [Partition] Lost - A partition was lost. Possible data loss has occurred - [Lifecycle] Merge Failed - A member’s attempt to merge with the cluster has failed - [Migration] Migration Failed - A partition migration has failed Non-Actionable Events (Info): These events are of interest but don’t require any actions. - [Membership] Added - A new member was added to the cluster - [Membership] Removed - An existing member has left the cluster - [Lifecycle] Merging - A member is merging with the cluster - [Migration] Started - A partition migration has started - [Migration] Completed - A partition migration has completed - [Lifecycle] Shutting Down - A member is shutting down |
|
| SR-C69729 | 414921 | Improved security for XXE | Several updates have been made to improve security against External Entity Injection. | |
| SR-C70602 | 415503 | Changed async loading when attaching Files with PegaCloudFileStorage to address 3rd party PEGA0046 error | When using PegaCloudFileStorage, a PEGA046 alert was observed when attaching a file to a work object. This was a cosmetic issue that did not affect functionality, and was traced to the use of an external logging system that is not part of the standard system development for Pega. In order to remove this alert, Step-5 (Load-DataPage) of Data-WorkAttach-File.pzSaveToRepository activity has been removed as asynchronous loading of D_pxNewFile data page is not required. | |
| SR-C70867 | 414703 | Resolved focus for new Microsoft Internet Explorer windows in Citrix environment | When opening a new Microsoft Internet Explorer window in the Citrix envirnoment, the window would open in the foreground and then immediately shift to the background. Investigation showed that when a menubar item was clicked, there was a call to show submenus in a settimeout of ZERO which implicitly did a focus on the menu item. Though the focus on the menu item happens after the window.open (action) is called, for in-house cases the focus occurs before the window is completely opened. However in this case, this focus was delayed and the new window was sent to the background. To correct this, the system has been updated so it will not perform focus on the menu item if the document itself is not in focus. | |
| SR-C71043 | 416762 | pzSendEmail returned to revious behavior of sending separate emails to work parties | After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity. | |
| SR-C71053 | 413209 | Added handling for defer-loaded dynamic layout inside a flowaction grid | When using a grid configured to show the details in expandable rows and the inner grid was a work bound grid, trying to expand the rows only showed the "Loading ..." message and never completed. This was traced to a missing use case for having a defer-loaded Dynamic layout which wraps the grid inside a flowaction embeddedpane grid, and has been corrected. | |
| SR-C71070 | 417207 | UI-Toolkit updated to resolve issue with fields overlap in dynamic layout collapse header | The UI-Toolkit has been updated to resolve an issue with Dynamic layout where using a Collapsible Header that has multiple fields to be displayed resulted in the fields overlapping or being mis-aligned. | |
| SR-C71520 | 415399 | Robot Manager portal re-launch correctly renders the last active screen | Two problems were seen with Robot Manager: 1) Opening Robot Manager and then navigating to Workgroup drill-in screen worked as expected, but when the portal was closed and re-launched from Designer Studio, the last active screen (workgroup drill-in) was rendered but with no valid data in it. 2) Opening Robot Manager from email notification worked the first time, but when the same button from the same mail was clicked, the last active screen was rendered with blank or no valid data. This was caused by preActivity and preActivityParams not being sent in the doUIAction call during re-launch of the portal, and has been fixed. |
|
| SR-C72252 | 415224 | isAncestorOf function now checks whether a child class is defined in the tenant layer | After upgrade, the isAncestorOf function was not returning the correct result. Checking the inheritance path for the tenant work class showed the shared layer work class, but after upgrade of the tenant layer, the IsAncestorOf function returned false and the functionality that uses isAncestorOf function failed if the parent class was in the shared layer and the child was in the tenant layer. To correct this, the logic has been updated so that rather than always checking in the shared layer, the system will check whether the Descendant class is defined in the tenant first. | |
| SR-C72385 SR-C77994 |
414868 419284 |
Resolved ClassCast email exception caused by duplicate javamail class loading | A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders. | |
| SR-C73425 | 413723 | Fixed error when trying to discard a circumstanced Report Definition rule | Attempting to discard and delete a circumstanced Report Definition rule resulted in an error on screen, in the tracer, and in the log file. This was caused by the system being unable to identify a reserved property when circumstanced on an embedded page or primary page. To correct this, the saveCircumstanceIndex rule of Rule- activity's first step has been modified to get the circumstanced property for this use. | |
| SR-C74047 | 416353 | Automatic Cloud Terminations updated with retry logic and exception handling for nodes being disconnected while in use | Agents were being disabled when a node was about to be shut down and the lock operation timed out. This was traced to an issue where the Hazelcast operation timed out trying to communicate with a node that had not yet dropped out of the cluster but did shortly after, and was due to the refactored code around delegating to a cluster component missing a lock method. In order to ensure the cluster component handles such exceptions gracefully, the lock operation now contains retry logic along with exception handling that will return 'false' instead of raising an exception. | |
| SR-C74151 | 412493 | Made mobile file attachment sync more robust for low bandwidth situation | When using the iOS Mobile Offline application with 'make attachments available offline' checked, low bandwidth on the network could cause the attachment sync to fail and cause the queue to get stuck. To prevent that, rather than return a Socket Timeout the system will return an error code that will cause the file upload to continue instead of rejecting it. | |
| SR-C74176 | 419497 | AdminUser login corrected for WebLogic | After a successful deployment of Pega on WebLogic 12c Application Server, the server started up without problem and the login page appeared as expected. When attempting to login to the application using the administrator account, the login failed and displayed the error "java.lang.IllegalArgumentException: Header:Location Cannot contain CRLF Charcter" in the browser. This as traced to the URL not being generated correctly due to the padding in the encoding rejecting any CRLF character in the URL, and has been corrected. | |
| SR-C74967 | 419160 | Delete and change comparisons updated to support multi-tenant environments with shared classes | When creating tenants in paex49, many of the rules did not actually complete importing into the tenant, and when creating new cases, some pages were getting instantiated as classless. This issue was seen only in multi-tenant environments when the same class was present in multiple tenants. Given a Pega class present in multiple tenants, making changes to that class for one tenant triggered invalidation of the dictionary cache that maintains a map with class name + tenant id as key and ClassInfo object as value because of the comparison method used. As a result, dictionary invalidation from one tenant could clear the entry of other tenant and cause the current tenant cache entry to become stale. To address this issue, the system has been updated to remove an entry for a class in tenant context based on key. | |
| SR-C75205 | 418809 | Invalid text entry in Date control field now returns current timestamp | Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting to return the timestamp in case the entered text value is incorrect. | |
| SR-C75278 | 415762 | Extension added to wrapper activity to allow skipping completed assignments | The withdrawal of the pyPopulateCaseContentsWrapper activity rule from the PegaCardSd ruleset caused the wrapper activity in Pega-EndUserUI to be utilized instead, but that activity included a different behavior which resulted in the Completed Assignments checkbox being set as 'true' during processing instead of staying 'false' unless checked by user. This resulted in additional assignments showing when previously only open assignments would show as default. In order to correct this, a new extension "DT(pyPopulateCaseContentsWrapperExtension)" has been provided to set the required fields in order to skip fetching the completed assignments. To utilize this, set the pyShowCompletedAssignments property to true in the extension DT to hide the assignments. | |
| SR-C75566 | 420774 | Added null check to avoid DisplayCardAccountHeader rendering issue | When the out of the box section DisplayCardAccountHeader was created by View editor and then converted to full section editor, the embedded sections were empty or not seen. This was traced to the design view javascript hitting an error which caused the design view rendering to fail. To correct this, pzpega_ud_gridlayout_model has been updated to wrap the line in question with a null check and set the value to empty string if it doesn't already exist in the model. | |
| SR-C75930 | 416831 | Security Event log enhanced to use 24-hour format for timestamps | Previously, the Security Event log used timestamps in the 12-hour format. An enhancement has now been added to use the 24-hour format to clarify the timing of events. | |
| SR-C76041 | 415955 | Corrected currency format for it_IT locale | For few locales, the formatting API was returning the number with leading white space. This caused the localeNumFormat to not be properly set. To correct this, the leading space will be trimmed before creating the 'localeNumFormat' parameter. | |
| SR-C76155 | 415815 | Class structure tree correctly repaints when scrolling in Google Chrome | When expanding the Class Tree Structure and then selecting a class relatively low down in the list, the screen was not repainted after scrolling back up when using the Google Chrome browser. It was possible to force a repaint of the tree structure by clicking on an item in it. This was traced to the app explorer tree-grid (cell) having section includes which used deprecated free-form layouts (which are table based). To resolve this issue, the app explorer leaf node has been converted to display in dynamic layout and app explorer child nodes will repaint even after expanding to a child level. | |
| SR-C76202 | 421391 | Updated CSS selector to ensure all buttons are visible during data flow | The restart/refresh buttons were not visible when running the data flow, and if some records were processed, they were not displayed in the result window. This was traced to the test selector not being accessible for all the access groups, preventing the progress page from being refreshed. The system has been updated to use a normal CSS selector to resolve this issues. | |
| SR-C76394 | 417569 | Support added for parameterized localized strings for headers | Support has been added for parameterized localized strings in headers by way of getLocalizedTextForParameterizedString. This can be used for the field values of LABEL and header text. | |
| SR-C76861 | 416578 | Handling added for undefined pxReqURI to ensure UI loading | The Declarative Expression Network Viewer did not provide a text input box to enter in the property values and then update the network with these new values. This was traced to a failure in the UI loading caused by pxReqURI being undefined, and has been corrected by modifying the DeclarativeNetworkWithValues section to handle this condition. | |
| SR-C77062 | 416407 | Improved security for Cassandra/Kafka process | In order to improve system security for Cassandra and Kafka processes, the binding for the Kafka JMX port will only be applied to 127.0.0.1, and the JMX addresses have been made configurable. | |
| SR-C77072 | 415542 | Title of Repeating Layout is passed correctly with ViewAPI | When using a section with a repeating dynamic layout and a header (title) set with a property that had value, using the view API displayed a title which showed the property name instead of the value. To correct this, RDL has been updated to use a title and include support for text/property/fv and localization. | |
| SR-C77088 | 417783 | Pega API returns control format for pxButton | When using the Pega API to get action details applied to an assignment (using the API GET {{url}}/assignments/assignmentID/actions/actionID), the control format value was not returned by the API for pxButton controls and other non input type controls like pxLink. It did work for input type controls like Text Input and Dropdown. This has been fixed by adding support to the control format for modes(1) and modes(2). | |
| SR-C77100 | 417037 | Flow actions with validation errors are correctly populated to embedded page | After upgrade, a pyFlowData page was not populating an embedded pyFlowActionsInError page with the list of flow actions with validation errors. This led to the AddRuntimeInfo activity (called from step 8 of GetFlowData activity) to fail in setting the correct step status (pyStatus) as “error”(under pySteps embeded pages of pyFlowData page). Any additional logic based on this status value then failed because of the incorrect status. This was traced to a missing call to the researchPropertyReference API in pzGetActiveValue RUF.changes, and has been corrected. | |
| SR-C77106 | 416870 | API modified to prevent potenial security issue with JSON objects | A potential security issue was found where the Pega API allowed a different JSON object to be posted back than had been retrieved. This has been corrected. | |
| SR-C77107 | 417089 | Added check for sending email attachments with XML data | When using SendEmailNotification to send an email with an attachment, the attachment was added but had no content when the email was received. In this case, if the property pyRemoveXML was true and if the email attachment content had XML data and did not contain a <pagedata tag, then the removeXML() method was returning "" as the email attachment content. This has been fixed by adding a check so if the property pyRemoveXML is true and if the email attachment content has XML data and doesn't contain the <pagedata tag, then it will return the original content itself. | |
| SR-C77145 | 418197 | REST endoint check added to correct Bulk check-in error | After integrating Agile Studio into a development instance application, trying to perform a Bulk check-in of the rules without selecting a task ID in the "Work item to associate" drop down list failed and generated an error in the logs. This was caused by an incorrect condition validation before making the REST call, and has been addressed by checking whether the REST endpoint is blank or not. | |
| SR-C77459 | 416898 | Report tab names are correctly maintained after refresh | When multiple reports are opened and the browser is refreshed, the tab names/labels failed to show up on reload. This was caused by an error in the method used to set the tab label, and has been corrected. | |
| SR-C77533 | 416618 | Added null check for ApprovalFlowName in pre-processing activity of "pzApprovalPreProcessing" | When a "pyApproval" flow action was configured in one of the assignments of a case Type for Approval action by the manager, the error message "The Flow Action pre-processing activity pzApprovalPreProcessing failed: The reference .pxFlow().pyFlowParameters.pyApprovalSectionName is not valid. Reason: Empty subscripts are not valid for the element : pxFlow" appeared when the Approval section was displayed. To correct this, a null check has been added for an empty ApprovalFlowName in step 1's second property set and transition step. | |
| SR-C77625 | 415580 | Cassandra retry policy enanhancement | When configuring the datastax client for Cassandra, it is possible to specify a retry policy. By default the DefaultRetryPolicy is used. While a retry was always attempted on client timeout with this retry policy, a retry on server timeout was only attempted in a limited set of circumstances. This code indicates that for a retry: - The number of received responses is at least the same as the number of required responses - The retry will be done to the same node, not a new node This use makes sense if consistency is set to QUORUM or higher, but it does not make sense for consistency ONE. To resolve this, a new retry policy has been added which will retry in this scenario a configurable number of times. The retry policy and the retry count will be controlled by prconfig settings: prconfig/dnode/cassandra_custom_retry_policy/default - True/False (default: False) prconfig/dnode/cassandra_custom_retry_policy/retryCount/default - >= 0 (default:1) |
|
| SR-C77633 | 415455 | Report definition rules correctly revalidate and save in Bulk wizard | Report definition rules were failing on re-validate and save from the Bulk Actions wizard. This was caused by pzCopyPySource attempting to set a blank value, and has been corrected. | |
| SR-C77856 | 419438 | Enhancement added to get archive details as response on getStatus API call with external repository | Previously, getStatus service did not return the repository location of the exported zip file if export to repository was passed true with repository name. An enhancement has been added to also get repositoryLocation with a getStatus service call if exportToRepository was true in the export operation and the archive has been successfully exported to the repository. | |
| SR-C78045 | 415132 | Check added to resolve teradata empty batch error | ExecuteBatch in Teradata was failing if there were no calls to addBatch prior to it, a different behavior than is seen in other databases. This has been corrected by adding a condition to check if there are any statements added to the batch before executing the batch. | |
| SR-C78179 | 417563 | Helper text/tooltip field returned to the view API | Previously, the helper text, format type and Read/Write classes were not passed to the view API. Because these fields are needed to understand correctly what type of field to render and execute basic input validations at the front end side, the helper text value will now be provided as a tooltip. | |
| SR-C78227 | 418103 | pxCheckbox label returned from the User Experience API | While calling the API to get the view of the screen as a JSON format, pxchecbox type of controls were not returning the label of the field. This has been fixed with the addition of a checkbox to the list of labels from modes. | |
| SR-C78352 | 417618 | Transform on an onclick event refresh added to DT | When calling the refresh method, the transform on a onclick event refresh was not invoked. Support for this refreshSection action has been added for running data transform and activity. | |
| SR-C78362 | 415982 | Preprocessing added to GET assignments and cases | When the /assignments/{ID}/actions/{actionID} API was called, the result of the flow action did not include either the data transform nor the activity from the preprocessing section. The system has now been updated to run preprocessing for GET /assignments/{ID}/actions/{ID} and GET /cases/{ID}/actions/{ID}. | |
| SR-C78402 | 417491 | Added Page clear messages for Record Editor to clear stale errors | An error message appeared correctly if the validation failed after editing a record, but refreshing the row caused the error message to be removed. The same error message appeared again if any filter was applied on any column. This has been fixed by adding Page clear messages in post and pre activities of pzRecordEditor. | |
| SR-C78664 | 417565 | Container format for dynamic layout configuration passed to the view API | The layout format field for the dynamic layout configuration was passed to the view API as "groupdFormat", but the container format remained unchanged. This has been corrected. | |
| SR-C78857 | 416254 | Hover text no longer blocks agent selection | Show smartinfo was rendering the information on top of the target dynamic layout, hiding the entire content of the layout. To fix this issue, Show SmartInfo has been reconfigured as on hover of node label instead of dynamic layout. | |
| SR-C79032 | 417173 | Pulse outgoing email character limit removed | Previously, only the first 2000 characters of a Pulse entry would be displayed in the email notification. An enhancement has now been added to remove that limit and display the entire Pulse text in the related email. | |
| SR-C79205 | 416400 | OnChange event only triggered on date field when value changes | After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event. | |
| SR-C79302 | 416825 | Added backwards compatibility for ValidateDelete in Records Editor | Due to a missed use case, ValidateDelete was not being called from the new records editor. This has been corrected by adding the step to call ValidateDelete in pzDeleteRecord activity. | |
| SR-C79306 | 417260 | Visibility consition added for checkbox used to skip validation for rules import | An enhancement has been added to show or hide the the validation checkbox in Import Wizard by way of the new property 'pyDisableSkipValidate'. This adds a visibility condition for the checkbox used to skip running rule validation in pzImportRecords. | |
| SR-C79560 | 417567 | Editable format configuration passed through DX API | The editable format configuration of the OOB controls was not being passed through the DX API. In order to present the information in the right format as well as reduce the amount of roundtrips to the server to validate inputs, support has been added for modes(1) and modes(2) in editable and readonly formats. | |
| SR-C79696 SR-C82530 |
417542 420609 |
Atmosphere XSS Vulnerability fixed | Atmosphere has been updated to close a potential XSS vunerability. | |
| SR-C79731 | 417958 | TestID remains unique in grids | To support automated testing, testID will maintain unique IDs for grid rows and RDL rows. | |
| SR-C79762 | 419158 | Decision table decision shape produces correct connector | After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected. | |
| SR-C79941 | 416722 | Corrected JSON for eventType DisableOperators in the security event log | An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed. | |
| SR-C80050 | 417604 | Schema name made consistent for DDL generation | A platform upgrade failed if there were application schemas configured with a table configuration that specified a schema other than the rules schema. This was an issue caused by the generated DDL having the incorrect schema name for the table due to the name being hard-coded in the Data-Admin-DB-Table entry definition. The system was using this schema name to find the table and generate the correct changes, but the SQL statement used the table from the database connection instead of the override. When the XML that represents the difference between the "source" and "target" state is generated, the system is supposed to replace the schema name with the target schema name. However, if the source schema name is blank that step was skipped in order to defer to the connection for shipped tables. In order to ensure that the system can generate the correct DDL and complete the upgrade, the system will now always replace the schema name regardless of the source or target value. | |
| SR-C80076 | 419094 | Added check before deleting pxObjClass to avoid agent runtime exceptions | When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted. | |
| SR-C80084 | 417239 | Target connectivity preference updated in Revision Manager to address deployment error | Using the deployment page to deploy a revision or migrate it to a target environment was failing. This has been resolved by correcting the target connectivity preference in the connector rules. | |
| SR-C80215 | 421850 | Migrated Data Flows open correctly from the data flow landing page | After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected. | |
| SR-C80958 | 419200 | Added check for appname to avoid HarnessFail execution error on Mashup reload | A HarnessFail execution error was occurring on Mashup reload. This was caused by the appname being appended twice during the reload, and has been resolved by adding a check to the _finalizeNavURL method in the PegaCompositeGadgetMgr.js file to remove appName if it is present in the URL to prevent duplication. | |
| SR-C81111 | 417909 | Performance improvements made for IH summary use | Enabling IH summaries in an adaptive model or using them in a strategy was impacting performance by as much as 300 milliseconds. Improvements have now been made to streamline Cassandra node health checks, to eliminate unnecessary duplicate calls to the DB, and to stop the DSS from being read on each single case dataflow execution. | |
| SR-C81262 | 418057 | Failed delete instances now correctly logged | After configuring rule-access-when on delete instances for a data class, the failed instances were not shown in the error log file. This has been resolved by correcting the path of the error CSV file in the pzDeleteRecords activity. | |
| SR-C81829 | 419228 | pxCoveredCountOpen value decrease corrected | When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted. | |
| SR-C81857 | 420240 | Enhancement added to support dropdown with page list property | To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete. | |
| SR-C81946 | 418711 | Maintenance function operator ID will not persist in the system | After a hotfix maintenance activity, an audit revealed that an extra operator created for the purpose called CloudMaintenanceUser persisted in the system. The code has now been updated to bypass saving operator records marked with pzPersistOperator="false" on user initialization; the CloudMaintenanceUser will be created with this property set to false, and updating this operator will be skipped during unauthentication. | |
| SR-C82244 | 421174 | Enhancement made to allow passing of URL in actionset via the DX API | When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached. | |
| SR-C82408 | 422328 | Repaired instance insertion for REST connection invoked via Queue | After upgrade, the REST connection invoked in an activity which in turn called OOTB ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution. | |
| SR-C82480 | 421488 | Column Headers properly aligned after expand/collapse of Tree Grids | When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row. | |
| SR-C83808 | 421299 | FIRST aggregate in bucketed window fixed | FIRST aggregates were not giving the correct results if used in a Sliding Time window together with an average aggregate. This was traced to an incorrect implementation of FirstAggregatorHolder.substractAggregate which used propertyIndex to get aggregate value (which was not correct in this context), and has been fixed by using the correct index in FirstAggregatorHolder class. |
|
| SR-C83915 | 421169 | Enhancement added to support property reference name for section include | When requesting the view of a section from a repeating dynamic layout where the name of the section is taken from a property, the DX API returned an error on the tracer indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)". This has been resolved by adding an enhancement to support using a property reference for section include. | |
| SR-C85035 | 421948 | Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView | Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present. |