INC-133583 · Issue 584923
Rest connector supports extended chars in attachments
Resolved in Pega Version 8.3.5
When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding.
INC-143461 · Issue 601841
Updated JSON DT nested page property handling
Resolved in Pega Version 8.3.5
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-139297 · Issue 601421
JSON content type update
Resolved in Pega Version 8.3.5
An update has been made to ensure the content_type is set to application/json for JSON response.
SR-D42670 · Issue 510185
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.1.7
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
SR-D21555 · Issue 501107
Resolved command line BIX/PRPCUtils creating unreachable nodes
Resolved in Pega Version 8.1.7
BIX and PRPCUtils scripts were creating nodes that showed as unreachable or that were never cleared. This was traced to a code change that resulted in nodes starting as stream nodes unless given a node type or DSS settings, and has been resolved by setting the asyncExecutor/enable setting value as false in the prconfig.xml. The BIX command line JVM argument should also be set to NodeType=BIX.
SR-D46159 · Issue 510973
Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status
Resolved in Pega Version 8.1.7
Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.
SR-D45600 · Issue 510385
pzIsACoverageSessionActiveForThisRequestor moved to @baseclass
Resolved in Pega Version 8.1.7
When logging out, the error "com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-WHEN' with the name 'PZISACOVERAGESESSIONACTIVEFORTHISREQUESTOR' that applies to 'Code-Pega-List' appeared. This was a log errors issue caused by a 'when' rule not being found due to the temporary Pega step page matching with a locally created page, causing the rule resolution of the 'when' rule to fail. To resolve this, the 'when' rule pzIsACoverageSessionActiveForThisRequestor has been moved to @baseclass.
SR-D25753 · Issue 499269
Added WebSphere Liberty Profile to BaseEnvironment.guessServerEnvironment
Resolved in Pega Version 8.1.7
While trying to add a node to Decision data store nodes via Designer Studio > Decisioning > Infrastructure > Service, the error "Service DDS:** java.lang.NullPointerException" was seen, and it was not possible to add a node or save any configuration. This was caused by an incomplete profile for Websphere Liberty, causing the com.pega.pegarules.priv.context.BaseEnvironment.guessServerEnvironment() API to return 'unknown' as the answer when WLP was used. This has been fixed, and the API will return "Websphere" for Websphere liberty profile as well.
SR-D50161 · Issue 514875
Auto populate disabled during redux page conversion to prevent concurrent modification exception
Resolved in Pega Version 8.1.7
Running a standalone data page sourced from a look up of a class was failing sporadically with a concurrent modification exception. The Data page was backed by redux pages: this meant that when the page fetched from data source was converted to redux page, it was iterating through all properties in the mContent of the page and trying to convert those to redux properties. During this process, when any auto populate property was encountered it was getting triggered and modifying the mContent, resulting in a change in iterator. As a result, when the Iterator was trying to fetch the next element, the concurrent modification exception was thrown. To resolve this issue, auto populate has been disabled during redux page conversion to avoid unnecessary problem during data page load.
SR-D29034 · Issue 500682
Added support for JSON mapping of deep nested pagelist objects
Resolved in Pega Version 8.1.7
An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.