SR-C22471 · Issue 370124
Handling added for long names when exporting DataType columns
Resolved in Pega Version 8.1
Values were not being displayed in an exported file for a column with a name exceeding 30 characters. This was traced to the values being mapped to a hashed value that truncated the name and caused the alias to not be found when expanding the data, and has been fixed.
SR-C22549 · Issue 365733
Code modified to avoid Security Analyzer false positive
Resolved in Pega Version 8.1
A false-positive was reported for a security vulnerability in the pzMultiDragDropControlStandard control. Two issues were captured when Rule Analyzer was run using the pyUnsafeURL expression: 1. ActiveXCall, and 2. Activity call in the script. To correct this, code changes have been made to avoid an ActiveX call in the control.
SR-C22575 · Issue 363177
Hours display corrected for readonly custom datetime
Resolved in Pega Version 8.1
If a date time control was set to readonly formatting and the format type was a custom type like '01/01/01 01:00 AM', '01/01/2001 01:00 AM' , the hours were not displaying in 'hh' format but instead used 'h' format. This was a missed use case for custom date/time and has been corrected.
SR-C23090 · Issue 365768
Duplicate check added to property optimization
Resolved in Pega Version 8.1
In previous releases, a property could be optimized only once. A new feature introduced in 7.3 enabled optimization of a property any number of times, but it was missing a duplicate check while modifying the pyOptForClassList property. This caused the class name to be listed two or more times in the 'Optimized for classes' section of the property rule in the advanced tab list. To correct this, a duplicate check has now been added.
SR-C23096 · Issue 367425
Handling added for empty SetTicket parameter
Resolved in Pega Version 8.1
If a ticket parameter to SetTicket activity was passed as empty, the current step was skipped rather than the process staying in the same step. To address this, the SetTicket activity will call an exit activity if the ticket parameter is empty.
SR-C23134 · Issue 362897
Tab delimiter write-out corrected for File Dataset
Resolved in Pega Version 8.1
The File Dataset was writing out "\t" as the delimiter for tab delimited files. This was due to the tab character being escaped and then treated improperly in the parser/serializer, and has been fixed.
SR-C23134 · Issue 362970
Tab delimiter write-out corrected for File Dataset
Resolved in Pega Version 8.1
The File Dataset was writing out "\t" as the delimiter for tab delimited files. This was due to the tab character being escaped and then treated improperly in the parser/serializer, and has been fixed.
SR-C23138 · Issue 367878
PRPushServlet response corrected to 400 when disabled
Resolved in Pega Version 8.1
PRPushServlet is used to establish a WebSocket connection with the Pega server. When server-push is disabled, the Push engine won't get initialized and will return an empty response by logging a warning message ("Request arrived for requestor:[%s]. But PushEngine has not started." ). Unexpectedly, this process was returning HTTP status 200 instead of 400. This has been corrected.
SR-C23153 · Issue 370814
Corrected handling for birthdate of 1970-01-01
Resolved in Pega Version 8.1
Issues were seen when the input date of birth was “1970-01-01” (matching the "epoch date" when time started for Unix computers) in the request of a webservice. When the DSS "disableEpochDate" on "Pega-IntegrationEngine" was set to "true", the date of birth was deleted from the request if it was 1970-01-01. If it was set to "false", other empty Date properties were valued as 1970-01-01 in Stream XML data mapping. To resolve this, the DSS setting will only be considered when the Date/DateTime property value is not empty.
SR-C23157 · Issue 364333
JMSListener modified to support custom connection client ID
Resolved in Pega Version 8.1
If JMSListener was configured for PubSub messaging model with durable subscription, restarting the JMSListener generated a new ClientID that was used to retrieve messages from Topic. This resulted in either some messages being missed or some being processed multiple times. To resolve this, a new configuration/field has been introduced on the JMSListener ruleform that accepts a client ID that can be specified statically/dynamically per listener.