SR-C21996 · Issue 366632
Error message clarified for unauthorized record deletion
Resolved in Pega Version 8.1
When there was an unauthorized attempt to delete records from a delegated data type, the error message appeared stating “A commit cannot be performed” instead of displaying an authorization error. This has been corrected.
SR-C22087 · Issue 368240
Resolved Oracle connection reset in migrate.sh
Resolved in Pega Version 8.1
Running the migrate.sh script to generate and apply rules schema objects against an Oracle database was failing. This was an issue with how the newer versions of the Oracle JDBC driver use entropy: by defaulting to using /dev/random, when running in an environment where there this is not a lot of noise the entropy pool will eventually be empty and the connection will be reset. Earlier versions of the Oracle JDBC driver did not see this issue. Previously, Pega added added a urandom setting to the migrate and prpcUtils scripts for Oracle/UNIX environments to avoid the connection reset issue. This urandom setting has now also been added to setupDDL.xml to resolve the schema objects issue.
SR-C22461 · Issue 363990
JobID status now considers In-Progress
Resolved in Pega Version 8.1
When checking the status of a particular JobID, getStatus returned overall Build status as FAILED when the Job Status is actually in IN-PROGRESS. This was due to Jenkins treating non-zero returned values as job failure and setting the status of the Jenkins Job to Failed although the in-progress job may yet run to successful completion. In this case, both http status code and job status were considered while evaluating the build status, but the job status IN-PROGRESS was not considered. This has been corrected.
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.