SR-132919 · Issue 201479
REST querystring not forced to lower case
Resolved in Pega Version 7.1.8
A Rule-Service-REST.validate activity which forced the query string to lowercase was leading to REST services are not receiving the input values in case of capital or camelCase query strings. To resolve this, the code that fetches querystring name for REST will not convert it to lower case.
SR-128332 · Issue 199072
Added detection for WSDL import failure
Resolved in Pega Version 7.1.8
Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.
SR-129312 · Issue 198553
Corrected HTML display of characters in reply emails
Resolved in Pega Version 7.1.8
HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.
SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
INC-107737 · Issue 544662
Oracle handling updated for upgrade DDL
Resolved in Pega Version 8.6
DDL generated for a Pega upgrade displayed the error "ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP" when trying to install. This was traced to a change made by Oracle for optimization, and has been resolved by updating the handling for primary key constraint and the corresponding index name.
INC-121480 · Issue 595823
EnableRedirects property added for REST connections
Resolved in Pega Version 8.6
When implementing a connector with the header “Location” which contains a redirect URI, a 303 response code was expected. Instead, a 400 or 404 error was generated. It was not possible for developers to process the code per their logic in Activity as Connect REST processed 303 responses automatically - i.e. there was no intercept points to implement the suggested approach. To resolve this, the new property "Rule-Connect-REST.pyEnableRedirects" has been added along with a checkbox for the property in "Rule-Connect-REST.pyService" in "Connection" section. Logic has been added in RESTConnector.java to take value of this property and set it on the HTTPClient being used, and a method has been added to HTTPClient interface and ComponentsHTTPClient to use the new value being passed. The default behavior is the same for the REST Connector, but a client can uncheck a checkbox on the REST Connector ruleform to stop the HTTP client from automatically following any compatible 3xx responses.
INC-122112 · Issue 599792
Updated SLA table clearance
Resolved in Pega Version 8.6
After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal.
INC-125258 · Issue 601606
Documentation updated for troubleshooting rules counts
Resolved in Pega Version 8.6
The troubleshooting documentation has been updated with extended information regarding correcting incorrect rule counts in dashboards and reports.https://community.pega.com/knowledgebase/articles/pega-platform-troubleshooting/troubleshooting-incorrect-count-rules-dashboards-and-reports
INC-125633 · Issue 589578
Optimizing helper class enhanced to handle external databases
Resolved in Pega Version 8.6
Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".
INC-125972 · Issue 604081
Improved resolved rules cache
Resolved in Pega Version 8.6
When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.