SR-C76202 · Issue 421391
Updated CSS selector to ensure all buttons are visible during data flow
Resolved in Pega Version 8.1.3
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 · Issue 417569
Support added for parameterized localized strings for headers
Resolved in Pega Version 8.1.3
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 · Issue 416578
Handling added for undefined pxReqURI to ensure UI loading
Resolved in Pega Version 8.1.3
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 · Issue 416407
Improved security for Cassandra/Kafka process
Resolved in Pega Version 8.1.3
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 · Issue 415542
Title of Repeating Layout is passed correctly with ViewAPI
Resolved in Pega Version 8.1.3
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 · Issue 417783
Pega API returns control format for pxButton
Resolved in Pega Version 8.1.3
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 · Issue 417037
Flow actions with validation errors are correctly populated to embedded page
Resolved in Pega Version 8.1.3
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 · Issue 416870
API modified to prevent potenial security issue with JSON objects
Resolved in Pega Version 8.1.3
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 · Issue 417089
Added check for sending email attachments with XML data
Resolved in Pega Version 8.1.3
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 · Issue 418197
REST endoint check added to correct Bulk check-in error
Resolved in Pega Version 8.1.3
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.