INC-194269 · Issue 681046
Added handling for Create Source and Target properties of Date
Resolved in Pega Version 8.7
A report definition was not displaying results after update, and a stack overflow was reported. This was a missed use case for Create Source and Target properties of Date, and has been resolved by adding a boolean flag to avoid autochain during validations when data type is Date.
INC-172546 · Issue 652880
Resolved classcast exception with assembled HTML controls
Resolved in Pega Version 8.7
A classcast exception was being generated on login. Investigation showed the Static Assembler was unexpectedly using a different Assembler to assemble the Html control rule. Standard behavior is that StreamBuilderAssembler assembles controls of type StreamBuilder and ControlAssemblerForVTable assembles controls of type ControlBuilder. In this case, static assembly for HTML controls using VTable was performed using StreamBuilderAssembler, causing a classcast exception when using VTable because the instance of the generated.html class was incorrectly inheriting from StreamBuilder (the parent class of ControlBuilder) instead of ControlBuilder which is the specified interface in the generated.html Java code. This has been resolved by updating the system to skip rules of type 'Rule-HTML-Property'(control) during Static Assembly.
SR-D45646 · Issue 516176
Flexible decoding for mported files
Resolved in Pega Version 8.4
When importing CSV files, special characters appeared as ??? instead of "éèù ...". This was traced to the system using UTF-8 as default format to support all character sets including multi-byte (accented) characters while Excel uses ANSI encoding, creating an encoding incompatibility. To resolve this, an update has been made so the system will read the encoding from the source/property and pass it to InputStreamReader instead of always hard coding UTF-8.
SR-A20048 · Issue 237600
Error message for BIX DDL schema updated
Resolved in Pega Version 7.2.1
Attempting to create BIX DDL through the Designer Studio led to the error message 'No Instance found in the database' when an invalid schema path was used. This error message has been modified to more specifically identify the problem to assist in troubleshooting.
SR-D27540 · Issue 502969
Null check added for ObjClass filter value
Resolved in Pega Version 8.4
When a report definition was run with "Starts with" as a filter condition and "Use null if empty" was not checked, the message "An error occurred during resolving the report definition - null java.lang.StringIndexOutOfBoundsException" was logged. This did not appear if the filter condition was "is equal" and "Use null if empty" was checked. To resolve this, the system will check for a null or empty value on pxObjClass filter values before processing it for class descendants.
SR-D64570 · Issue 528960
Thread deadlocks during RAP imports resolved by reusing query results
Resolved in Pega Version 8.4
When using a time-intensive large query to build a cache to hold complex property references, multiple threads on a single tenant executed this query in a sequential manner and thread locking problems were seen. To resolve this, an update has been made so that for the same tenant, only one thread will run the query. All other threads waiting to acquire the lock will not execute the same db query but will instead make use of the result fetched by the first thread.
SR-D50436 · Issue 513850
Case creation service activity unauthorized response modified
Resolved in Pega Version 8.4
When unauthorized users accessed the URL for creating a case, a blank screen appeared instead of the user being routed to a login screen. This was due to the system returning an HTTP 400 error instead of HTTP 401 response, and was traced to the introduction of an anonymous user type in the authentication activity (Authentication service in the service package). Case creation REST service uses pzCreateCase activity to create the cases, but before introducing the anonymous user type it was exiting from the authentication activity and did not call pzCreateCase. This was traced to the error handling relying on a field value to be in English when instead the site had localized the value, causing a mismatch which did not generate the necessary failed status. To avoid this, the system will now use the new pxStatusFlowSecurity process engine status instead of relying on a text match to determine this error.
SR-A17004 · Issue 239165
Silverlight updated for URL encryption
Resolved in Pega Version 7.2.1
If URL encryption is turned on in an environment where the Silverlight version of the WordMerge feature in use doesn't support encrypted URLs the error "Silverlight Control ERROR in 'GetAbsUriAllCookies': Cannot find absolute server URI when trying to launch word from within their application" was generated. The system has now been updated to detect the use of URL encryption in Silverlight via out-of-the-box JavaScript APIs and the URLs will be accordingly encrypted. The Silverlight Prerequisites installer has also been modified to include the latest certificate.
SR-D48010 · Issue 514983
Unit testing validation relaxed for external input strategy
Resolved in Pega Version 8.4
When trying to test a strategy, the testing transform had to exist in the same ruleset/version as the strategy or it would not resolve. Investigation showed that because the artifacts were in a different ruleset and version build on top of the application that the testing strategy belongs to, validation failed because it was using the platform based ruleset validation. This was a missed use case, and has been resolved by relaxing the validation for external input strategy so it does not take into account the ruleset and version of it. This same change has been applied for referenced data transforms.
SR-D51353 · Issue 516914
Unit testing validation relaxed for external input strategy
Resolved in Pega Version 8.4
When trying to test a strategy, the testing transform had to exist in the same ruleset/version as the strategy or it would not resolve. Investigation showed that because the artifacts were in a different ruleset and version build on top of the application that the testing strategy belongs to, validation failed because it was using the platform based ruleset validation. This was a missed use case, and has been resolved by relaxing the validation for external input strategy so it does not take into account the ruleset and version of it. This same change has been applied for referenced data transforms.