INC-184798 · Issue 703269
PRconfig added for JVM user/password
Resolved in Pega Version 8.7.1
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-194348 · Issue 703374
Resolved multiple copies of Pega0050 alerts
Resolved in Pega Version 8.7.1
The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.
INC-195580 · Issue 684492
Delay Factor updated to allow values < 1.0
Resolved in Pega Version 8.7.1
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.
INC-196478 · Issue 683130
CORS policy updated for GET streams
Resolved in Pega Version 8.7.1
CORS (Access-Control-Allow-Origin) support has been added to handle Stream calls during GET requests.
INC-163791 · Issue 704029
Simplified default reference time calculations
Resolved in Pega Version 8.7.1
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-163791 · Issue 704030
Simplified default reference time calculations
Resolved in Pega Version 8.8
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-184964 · Issue 705932
TextMask_Encrypted rule added for use with Oracle
Resolved in Pega Version 8.8
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-186897 · Issue 681030
DSS DisableAutoComplete setting honored
Resolved in Pega Version 8.8
Setting DisableAutoComplete DSS was not working as expected. This was traced to the system not being able to read the DSS value due to timing related to database startup, and has been resolved by directing the system to read the setting in PREnvironment.java instead of from the prconfig.
INC-191404 · Issue 689095
Tracer settings made configurable for queue processor
Resolved in Pega Version 8.8
An enhancement has been added to allow configuring tracer settings for the Queue Processor module.
INC-200030 · Issue 698955
Handling added for external Kafka authorization exception
Resolved in Pega Version 8.8
When using external Kafka for stream service, the dataflow was failing with the error 'QueueProcessorDataSubscriberException' when topic create permission was missing. As a workaround, the topics could be pre-created, though a "Topic already exists" warning was generated. To resolve this, the cluster-wide right that a producer needs, IdempotentWrite, has been added. For more information please refer to the link https://docs.confluent.io/platform/current/kafka/authorization.html