INC-201625 · Issue 698655
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.
INC-202447 · Issue 698659
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in
INC-202480 · Issue 699082
Resolved report filter section freeze
Resolved in Pega Version 8.6.4
When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.
INC-205075 · Issue 698741
Updated variable handling for filter logic to avoid reuse
Resolved in Pega Version 8.6.4
When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in
INC-209399 · Issue 708570
Handling added for indexing items exceeding Kibana max size
Resolved in Pega Version 8.6.4
Indexing cases was generating errors from Kibana indicating "Failed to index document: java.lang.IllegalArgumentException: Document contains at least one immense term in field="_m_MailBody" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped." To resolve this, if an embedded property exceeds the max length defined by Kibana, it will be truncated at 32k bytes in order to allow indexing to proceed.
INC-211726 · Issue 705071
Parameter logic updated for metrics activity counter
Resolved in Pega Version 8.6.4
An error was causing the PushCDHMetrics agent to fail. This was traced to an undefined parameter in the activity which was used as a counter, and has been resolved by replacing it with a local variable of type integer. In addition, an agent has been added to support publishing the model metrics.
INC-163791 · Issue 704028
Simplified default reference time calculations
Resolved in Pega Version 8.6.4
After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).
INC-184798 · Issue 703268
PRconfig added for JVM user/password
Resolved in Pega Version 8.6.4
The setting Dcom.sun.management.jmxremote.local.only=true has been added for use when JMX authentication is enabled by providing jmxuser/password through prconfig.
INC-184964 · Issue 705934
TextMask_Encrypted rule added for use with Oracle
Resolved in Pega Version 8.6.4
When a property was being encrypted by propertyEncrypt access control policy and masked by propertyRead access control policy, it showed a "@@getMaskedValueOfText" error. This has been resolved with the addition of a new rule pxTextMask_Encrypted for Oracle product type which will remove extra spaces from the SOURCE string to handle ORACLE specific usecases.
INC-195580 · Issue 684493
Delay Factor updated to allow values < 1.0
Resolved in Pega Version 8.6.4
After modifying the "Delay factor" parameter on a queue processor rule and and clicking the "Save" button, refreshing the page caused the value of the "Delay factor" parameter to change. This has been resolved by updating the delay calculation strategy to support factors < 1.0.