SR-C25564 · Issue 366809
Updated locales to properly use Other Currency option
Resolved in Pega Version 8.1
When the Currency control was configured to display "Other currency" symbol value and the property was populated with USD, the property is displayed as 100.00 / USD in the es_CR, es_GT and es_HN locale, but in local format only for the es_PA, es_NI and es_SV locales. This was an issue with the default Currency Symbol values for es_PA, es_NI, es_SV pointing to old ICU2 formats, and has been fixed by changing the currencysymbol attribute in es_PA.xml, es_CR.xml, and es_SV.xml.
SR-C25702 · Issue 370594
REST POST method sets Content-Type and Boundary
Resolved in Pega Version 8.1
When the REST Connector was set to use the JSON mapping mode for request data and a request attachment page was present, the resulting Multipart message contained the mapped JSON in the "PostData" Part, with the Content-Type header of the Part incorrectly set to "text/plain" rather than the correct value of "application/json." This meant that services consuming the request did not know to handle it as JSON. To fix this, the REST Connector engine module and HTTPClientUtils module have been retooled to match the details and also to handle binary content mapped in as base64-encoded string. This can be overridden via a parameter. The "fat channel" now accepts Part objects so that the Connector implementation can craft a Part with all aspects of the Part, rather than providing only a value. The feature has also been enhanced to better handle Multipart request/response cases.
SR-C25702 · Issue 369365
Fixed content-type in Multipart for PostData
Resolved in Pega Version 8.1
When the REST Connector was set to use the JSON mapping mode for request data and a request attachment page was present, the resulting Multipart message contained the mapped JSON in the "PostData" Part, with the Content-Type header of the Part incorrectly set to "text/plain" rather than the correct value of "application/json." This meant that services consuming the request did not know to handle it as JSON. To fix this, the REST Connector engine module and HTTPClientUtils module have been retooled to match the details and also to handle binary content mapped in as base64-encoded string. This can be overridden via a parameter. The "fat channel" now accepts Part objects so that the Connector implementation can craft a Part with all aspects of the Part, rather than providing only a value. The feature has also been enhanced to better handle Multipart request/response cases.
SR-C25746 · Issue 371903
Fixed logic in Decision Table evaluation logic
Resolved in Pega Version 8.1
If a decision table was created with more than 5 columns and more than 1000 rows, trying to evaluate lines 1024 to 1062 (1084 to 1122 etc.), even though those lines matched, resulted in an otherwise value instead of the actual row value. This was caused by a logic error, and has been fixed.
SR-C25788 · Issue 390394
Changed temp directory handling for Export to Excel
Resolved in Pega Version 8.1
In rare cases, using the Export to Excel feature on the report definition viewer resulted in a Java FileNotFoundException. This was traced to process conflicts between the new Export to Excel implementation first featured in 7.3 and the Apache POI used to generate Excel documents by streaming the file to the disk as it is populated. Each worksheet in the document is streamed to its own temporary file. At the end of generation, the Excel document is created by opening the completed temporary files and copying their data into the final document. This way the entire dataset is never held in memory at once unless it is particularly small. However, the temporary file that holds the Data worksheet was in rare cases being deleted while the rows and columns were being populated. This was not noticed by the code until the file was reopened to copy its data into the final spreadsheet. Since it is not necessary to store the temp files in a separate directory (poi files) instead of using the the default configuration for saving temp files, the system will now use the function PegaTempFileCreationStrategy which will create the temp file but not create the temp directory. This means all the generated temp files are stored directly in the temp directory and not in the sub-directory poi files. ExcelReportExporter has also been updated so Apache POI knows to use this class for managing temp files.
SR-C25839 · Issue 366531
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.1
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-C25839 · Issue 356770
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.1
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-C25839 · Issue 366590
Merge Wizard errors fixed, and created rules will use the highest ruleset version available
Resolved in Pega Version 8.1
Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.
SR-C25839 · Issue 368838
Fixed Merge Wizard silent failure and added checks for ":" in RuleSetName value
Resolved in Pega Version 8.1
If an error occurred when using the Merge Wizard, the merge case was resolved-rejected without any reason or error message. This was caused by a hidden “Required Rulesets and Versions” field on the RuleSet ruleform which set the ruleset to application based validation. In addition, some ruleset validation logic was triggering even in ABV mode. To correct this, the precondition in pzOpenAllSourceRuleSets 2.2 has bene changed from "pyIsSourceABV"=="true" to .pyIsSourceABV=="true", and the pzRuleSetNameIsABranch function now has support for handling the null pointer exception when the RuleSetName value is ":". A message will also be logged if the RuleSetName starts with ":".
SR-C26026 · Issue 369003
Report Editor hints updated to reflect report type
Resolved in Pega Version 8.1
In order to clarify use, the formatting hint will be generated differently for List and Summary reports.List report hint: To format, sort, filter, or delete a column: Click on the down arrow next to it to delete the column, to change its format, or to sort or filter its values. Summary report hint: To format, sort, filter, or delete a column: Right-click a column heading or click on the down arrow next to it to delete the column, to change its format, or to sort or filter its values.