SR-D27041 · Issue 499045
Manual value group addition support available
Resolved in Pega Version 8.3.1
In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.
SR-A101069 · Issue 270616
Fixed dropdown issues when using Google Chrome
Resolved in Pega Version 7.2.2
The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.
SR-A101069 · Issue 269981
Fixed dropdown issues when using Google Chrome
Resolved in Pega Version 7.2.2
The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.
SR-A101069 · Issue 270595
Fixed dropdown issues when using Google Chrome
Resolved in Pega Version 7.2.2
The following issues were noted when using the Google Chrome browser: when selecting values from drop down in collapsible header, the section did not refresh according to selection; when the drop down was expanded, it loaded in front of collapsible header; when trying to select values which were within a collapsible header, the header became collapsed. These issues were due to the function expandHeader not being called in Google Chrome, and the function will now be called accordingly.
SR-B90290 · Issue 338672
Case mismatch fixed for pyDateSetID
Resolved in Pega Version 7.4
The column name for a property defined in Data-NLP-Report-Summary was pyDateSetID, which did not match exactly the property ID of pyDataSetID. This caused issues with Microsoft SQL Server where property names and column names must match exactly. If the UDF functions are present, this is worked around by reading the value from the BLOB. However, if you are running without UDF functions, attempting to access this property generated an error. This case mismatch has been fixed.
INC-175762 · Issue 669398
BulkProcess harness deprecated in favor of BulkProcessing
Resolved in Pega Version 8.7
The harness pzBulkProcess has been marked as deprecated. In place of this, implement the new Bulk Action functionality available using the harness pzBulkProcessing.
SR-B41806 · Issue 304276
Fixed Run Robotic Automation handling for input with quotes
Resolved in Pega Version 7.3.1
Run robotic automation was hanging when any property contained quotes. This has been fixed by adding the "escapeIntoJSONString" function encoding to pzGetRelevantRecordsAsJSON .
SR-B92155 · Issue 345201
ConditionsUtils library present after migration
Resolved in Pega Version 7.4
The ConditionsUtils functions were failing to compile after migration. This was traced to the ConditionsUtils library not having been included in the migration, and has been corrected.
SR-C38902 · Issue 377561
Parameter added to support Hotfix manager access group
Resolved in Pega Version 8.1
Previously, there was no provision for Hotfix Manager functionality to accept the access group as the parameter and run it in the access group context. In addition, Cloud customers were not able to specify a pega.username and pega.password. Attempting to do either of these resulted in an exception. In order to support these uses, a new access group parameter has been added to the prpcUtils.properties for manage hotfix functionality If an access group is provided that will be used; otherwise it will attempt to use PRPC:Administrators, then fallback to using the BATCH requestor’s AG (PRPC:Agents).