SR-C88178 · Issue 429527
docx4j jar updated for compatibility with Office365
Resolved in Pega Version 8.1.4
After generating a docx file with Office365, an error appeared indicating the document had invalid XML data and couldn't be opened. Once the error message was dismissed, the file could be opened normally. This was caused by an incompatibility between Office365 and the Plutext docx4j jar, and the Plutext jar has now been updated to version 6.1.1 to resolve this issue.
SR-C88236 · Issue 428788
Debug logging added to HTTP API for improved diagnostics
Resolved in Pega Version 8.1.4
Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue.
SR-C88309 · Issue 426998
Tooltip added for data table refresh icon
Resolved in Pega Version 8.1.4
An enhancement has been added to provide a tooltip for the refresh icon during data table edits.
SR-C88776 · Issue 428380
Added check for blank Value List Property referenced in Dropdown Control
Resolved in Pega Version 8.1.4
When a value list property was referred in the Dropdown control, the dropdown was shown as empty. This was traced to a property of type value list / value group, ClipboardProperty.getName() api returning as empty. To resolve this, a check has been added to ensure the value is populated with the correct property name if it is blank.
SR-C88882 · Issue 431069
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.1.4
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.
SR-C88948 · Issue 426227
Command-line BIX extract properly exits with failure status if the rule is not found
Resolved in Pega Version 8.1.4
Running a BIX extract from the command line was returning 0 for both success and failure. This was caused by the error message in this scenario not properly setting the flag if an extract rule did not exist, and has been corrected to ensure the command exits with status code 1 if it is not able to get the list of extract rules.
SR-C89013 · Issue 427677
Added skip for unneeded old validation from revalidate and save Service REST
Resolved in Pega Version 8.1.4
An error on the revalidate and save of a Service REST rule has been resolved by skipping unneeded old Service REST validation present in the system.
SR-C89156 · Issue 429486
Blank paramter passed as inshandle invokes NoWorkID harness instead of exception
Resolved in Pega Version 8.1.4
In releases prior to 8.1, the Obj-Open-By-Handle method was used to set an ActivityStepStatus error if a blank parameter was passed as inshandle. The activity step 8 would show as failed and invoke the NoWorkID harness. As of Pega 8.1, the code was refactored and modified to throw an InvalidArgumentException and quit the activity. In order to ensure better backwards compatibility, the error handling has been reset to show the NoWorkID harness when instanceHandle is empty.
SR-C89250 · Issue 429743
Guardrail score ignores test rulesets
Resolved in Pega Version 8.1.4
Test rulesets for a branch were unexpectedly being considered when calculating the Guardrail score. This has been corrected.
SR-C89316 · Issue 426078
Lower major ruleset versions will not be considered during design time validation
Resolved in Pega Version 8.1.4
After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.