SR-A91639 · Issue 260831
eForm PDF displays Japanese characters
Resolved in Pega Version 7.2.2
When trying to generate a PDF document using eForm PDF, Japanese characters were not displaying in the corresponding mapping field. This has been fixed by adding input parameters to get font details in the GenerateEForm activity and embed the font information in the PDF itself.
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-B14288 · Issue 289182
Command line BIX extract works as expected for -l option
Resolved in Pega Version 7.3
When a BIX extract was generated using rule XML of the extract rule (-I) from the command line, the manifest generated had "pxExtractIdentifier" in an unexpected format. The command line option has now been modified to generate the extract with the correct pzInsKey of the rule.
SR-B32839 · Issue 292388
Performance improvements for headless decisioning
Resolved in Pega Version 7.3
Performance issues were seen in Service Pega 7.2 related to scaling vertically when used for in a headless decisioning scenario. The code has been refactored to remove redundant calls to requestors in ServiceAPI, HttpService, SOAPUtils and SOAPService as well as additional classes and other classes to correct this.
SR-B34157 · Issue 296637
Resolved LDAP user logout error
Resolved in Pega Version 7.3
When LDAP customer authentication was used with the 'UseSSL' flag checked in the authentication configuration, the Presence login event was not being triggered and caused an error during logoff. To correct this, updates have been made to ensure Presence login events are triggered every time after successful authentication.
SR-B7225 · Issue 277783
BIX documentation updated for Extract Rules
Resolved in Pega Version 7.3
The documentation outlining best practices for using BIX has been updated to reflect that when extractions are being run asynchronously there must be enough threads for each of the concurrently running extractions. The section "Running an Extract rule using a Pega 7 Platform agent" has been updated to read: "Number of concurrent extracts scheduled has to be limited based on the prconfig "agent/threadpoolsize." Set the prconfig setting agent/threadpoolsize to the max number of concurrent extractions you will be executing. The default value for this setting is 5 and the maximum value is 10.
SR-B43331 · Issue 302897
Help file updated for consequences of "Ignore Locale" setting
Resolved in Pega Version 7.3
Issues with date values were encountered in set ups where a localized Language Pack had been installed and developers used the "Operator Ignore locale preference" in Designer Studio in order to have Designer Studio in English. While the user portal was correctly translated and European format dates were accepted, an error stating "date is not a valid date value" would appear when a date time field was updated or a new ruleset was created. In order to ease the use of the setting, the help files have been updated to clarify that the "Ignore Locale" option on the Operator screen causes ALL locale settings to be ignored and the default en_US settings to be used. In addition to the display language, these settings include date, time and number formats.
SR-A22699 · Issue 248560
RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected
Resolved in Pega Version 7.2.2
The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.
SR-A92387 · Issue 261229
Guardrail warning for offset/length removed from MapStructure rule
Resolved in Pega Version 7.2.2
In Map Structured rules, a guardrail warning was coming up for every row which had non-continuous length due to excess offset. This warning was generic without specifying the row number, and every time an attempt was made to justify the warning it was unrecognized and generated another warning. This left the rule with unjustified warnings on saving. As this rule is used often for generating excel sheets and formatting data neatly, it is not possible to provide the offset and length as expected by the Map Structured rule and there was a huge impact on the compliance score of applications when there was more than one Map Structured rule. As this is a common use case, the guardrail warning has been removed.