SR-D24750 · Issue 501746
Resolved importing PublicFormat file using RuleFromFile Wizard
Resolved in Pega Version 8.2.3
When attempting to create a flow from a Public Format XML file using the Rule From File Wizard, the following error was seen: "Problem invoking function: pega_procom_harvest.performXSLT--(String,String,boolean,HashStringMap)". This was caused by a mapping failure related to the pyComments property in baseclass pega social functionality, and has been resolved with the addition of a new page group property pyComments of type "Data-MO-Annotation-Comment" which applies to "Embed-Rule-Obj-Flow-ProcessModel".
SR-D52723 · Issue 516091
Data join conditions representation updated to avoid overwrite
Resolved in Pega Version 8.2.5
After upgrade, a Data join component on the Strategies was not working as expected, especially the ones using the DateTime function. If the data join conditions were swapped, i.e the DateTime function was not the last criteria, the strategy outputs were correct.Investigation showed that the implementation used a map to represent pairs of left and right expressions which caused conditions rows with the same leftExpr to end up overwriting one another. This has been corrected by fixing the representation of conditions of a Data Join to a list of tuples which eliminates the possibility of one condition overwriting a previous one.
SR-D24750 · Issue 501745
Resolved importing PublicFormat file using RuleFromFile Wizard
Resolved in Pega Version 8.3.1
When attempting to create a flow from a Public Format XML file using the Rule From File Wizard, the following error was seen: "Problem invoking function: pega_procom_harvest.performXSLT--(String,String,boolean,HashStringMap)". This was caused by a mapping failure related to the pyComments property in baseclass pega social functionality, and has been resolved with the addition of a new page group property pyComments of type "Data-MO-Annotation-Comment" which applies to "Embed-Rule-Obj-Flow-ProcessModel".
SR-D52723 · Issue 516090
Data join conditions representation updated to avoid overwrite
Resolved in Pega Version 8.3.2
After upgrade, a Data join component on the Strategies was not working as expected, especially the ones using the DateTime function. If the data join conditions were swapped, i.e the DateTime function was not the last criteria, the strategy outputs were correct.Investigation showed that the implementation used a map to represent pairs of left and right expressions which caused conditions rows with the same leftExpr to end up overwriting one another. This has been corrected by fixing the representation of conditions of a Data Join to a list of tuples which eliminates the possibility of one condition overwriting a previous one.
INC-184790 · Issue 666123
Details added to pxLogMessage History tab
Resolved in Pega Version 8.5.6
Usage and Description details have been added to the History tab for the pxLogMessage Rule-Utility-Function, as below: Description: Logs message for the logger Rule_Utility_Function.pxLogErrorMessage.Default with specified level. Used for error handling in response data transform in a data page. Parameters : sMessage - Specify the log message cLevel - Specify character to indicate log level, as below 'd' to DEBUG 'i' to INFO 'f' to forced INFO 'w' to WARN 'e' to ERROR This will return true or false depending on whether it logged or not.
SR-127173 · Issue 192701
Resolved save error for custom date format
Resolved in Pega Version 7.1.8
A custom date entry given Display mode 'Text Input + Calendar' and the option 'Display value using read-only formatting' and using the format dd.MM.yyyy returned the error 'Entered date value is Invalid' when attempting to save. This was an issue where the processOnBeforeSubmit function code exists to replace the client formatted value with the value which need to be submitted but doSave was using the submitWhenFail API where it has its own logic to process elements. To resolve the issue, the system will call a common function from both places to obtain the proper setting.
SR-A22993 · Issue 247098
Date format and alignment updated for Export to Excel
Resolved in Pega Version 7.2.1
When using Report Definition for a case search with the out-of-the-box excel export, formatting one of the DateTime type properties to display only the date portion in the exported report was not working as expected in the repeated-grid while it did work properly in report definition export function. The problem existed in the generation for the Report Definition itself due to the control formatting the data to be mm/dd/yyyy without the days even though the data type is a datetime, and the function has been updated to pass "date" as the datatype when a datetime is being formatted as a date.
SR-C18978 · Issue 358377
Fixed exception for empty offline property value
Resolved in Pega Version 8.1
Using a localized value with property reference caused a script error in the _resolveParams function of pzpega_offline_localization file when there were no property values in offline. This has been corrected.
SR-D70674 · Issue 535483
Handling added for mobile upload of filename containing dots
Resolved in Pega Version 8.2.6
An issue with uploading a file name containing dots (such as 2019.12.12) while using the mobile browser has been resolved by updating the AttachFile activity in the propertyExist function.
SR-D70674 · Issue 535482
Handling added for mobile upload of filename containing dots
Resolved in Pega Version 8.3.2
An issue with uploading a file name containing dots (such as 2019.12.12) while using the mobile browser has been resolved by updating the AttachFile activity in the propertyExist function.