INC-163970 · Issue 636137
Expression Builder updated for special character handling
Resolved in Pega Version 8.5.4
If a modulo operator (%) was used in expression builder, the expression showed the correct value when it was submitted (closed) but on reopen the expression was changed and not calculated correctly. If the expression was not reopened then it calculated the value properly. This issue was traced to a server call to pzEvaluatePegaExpression which treated certain values as containing special characters, and has been resolved by updating the handling for this scenario.
INC-164002 · Issue 639913
Decision table null input handling updated for backward compatibility
Resolved in Pega Version 8.5.4
After upgrade, any null values as inputs in the decision tables were skipped if "Allow Missing properties" was not checked. This behavior was different from previous versions. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
INC-164171 · Issue 635868
Support added for connect-SOAP run in parallel mode
Resolved in Pega Version 8.5.4
When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.
INC-164944 · Issue 636292
Logic updated to handle decision trees over 64k
Resolved in Pega Version 8.5.4
Logic updated to handle decision trees over 64kAn exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.
INC-168094 · Issue 642627
Security updated for help URL infrastructure
Resolved in Pega Version 8.5.4
Cross site scripting protections have been added to the help URL infrastructure.
INC-120450 · Issue 561743
Configure view finds existing calculations for properties
Resolved in Pega Version 8.4.2
Modifying a property to ‘calculated: Readonly’ by creating declare expression inside a fieldgroup list (which was created in the data model and refers to a datatype) while adding the fieldgroup list property by selecting from the field in the configure view of a step was not reflected when adding the same list type property inside another step of configure view. Declare expressions were created with page context for embedded fields by default in configure view, but Declare expressions have recently been enhanced and no longer expected to use page contexts. Because Configure view continued to use page contexts, this resulted in calculations that existed not being picked up. This has been resolved by configuring view handling for page list fields specifically to not create new calculations with a page context. Detection of calculations has also been updated to not check for page context to match the recent Declare expression enhancements.
INC-120472 · Issue 571437
Corrected date display on export to Excel
Resolved in Pega Version 8.4.2
Reports which have visible date and Date time properties or values displayed correctly when viewed in PEGA, but when the data was exported to Excel the values were converted to GMT time. Due to this the date fields (with no time stamp) were showing the date less by one day in Excel. This has been corrected.
INC-123033 · Issue 561388
Updated logic for delegating when the RARO exists
Resolved in Pega Version 8.4.2
When trying to delegate a Data Type, the validation error "Update Record Failed: This record is non-versioned and already exists and can not be moved to a different ruleset" appeared. Because data type delegation is dependent upon the existence of a RARO for the delegated data type, when delegating the ruleset of the RARO to accessgroups with the same roles the code was attempting to update the RARO. Updating the RARO determines if the Ruleset of the RARO is unlocked. If the ruleset is locked, then the logic attempts to select a new ruleset, but the RARO cannot be moved to a new ruleset. To resolve this, the logic has been updated so that if the RARO exists, the system will not try to create a new instance.
INC-125822 · Issue 566312
Agile Studio correctly embedding attachments
Resolved in Pega Version 8.4.2
Attachments were not being included in Agile Studio documents for backlogs and sprints as expected. This was traced to the third-party jar "jsoup", which was converting the parameter PegaDocumentObject to pegadocumentobject, causing a mismatch. This has been resolved by adding a check that will replace the converted name with the correct one.
INC-78420 · Issue 566792
Documentation clarified for pxGenerateExcelFile with template values
Resolved in Pega Version 8.4.2
Using Export to Excel created the document, but pxGenerateExcelFile was not replacing template values in the generated output file. To improve the clarity of the necessary configuration, the documentation for pxGenerateExcelFile has been updated to include an example of the usage:This can be used anywhere in platform to export excel file. E.g. - export stories, specifications, requirements etc. Example Usage of properties in template: {.pagelist().property input}\n{.property input}