SR-129211 · Issue 195705
Ensured expected deadline priority styling in workbasket
Resolved in Pega Version 7.1.8
The WorkBasket summary for the current WorkGroup on the Case Manager Portal was going straight from "normal" (green) styling to "urgent" (red) styling once one of the assignments in the WorkBasket went past Goal but had not yet passed Deadline. The intended behavior should show a "medium" styling until such time as one or more of the assignments is past Deadline. Once past Deadline, the styling should then be "urgent". The incorrect benavior was caused by an ordering problem in the Deadline and GoalTime columns, and code has been inserted to ensure proper behavior.
SR-129249 · Issue 194654
Accessibility added to pxDataField and VisualizeAttachingScreen
Resolved in Pega Version 7.1.8
Accessibility has been added to the out-of-the-box functions pxDataField and VisualizeAttachingScreen.
SR-129592 · Issue 196979
Scheduled report now checks default max records value
Resolved in Pega Version 7.1.8
When scheduling a report definition, the default value for max records to export was ignored when run by a scheduled task agent but used if the report was run manually. This value is normally set to 10,000 in the system settings and should be the default unless an override value has been entered for "Maximum Number Of Rows For Export" on the Data Access tab. To correct this issue, the pzRunScheduledShortcut activity has been updated to use the default if no value has been entered.
SR-129611 · Issue 197287
Corrected CheckPrivilege function in BulkAssign
Resolved in Pega Version 7.1.8
The RUF pxCheckPrivilegeInWorkClass (called from OpenAndLockWork) was changing the name of the newAssignPage, causing downstream failure of pzBulkProcessItems. The error occurs when a Bulk Transfer operation is performed and the user does not have the proper Role, resulting in a call to the canPerform Access When Rule that then led to pxCheckPrivilegeInWorkClass changing the name of the step page. To fix this, the parameter will be assigned to the "newAssignPage" or primary page in the OpenAndWorkLock activity.
SR-129723 · Issue 200683
Added ability to customize pyMessageKey column of a history record
Resolved in Pega Version 7.1.8
In order to allow customization of the pyMessageKey column of a history record, it is now possible to call the extension activity pyAddWorkHistoryDefaults in Flowvwhen the work page is not null.
SR-129733 · Issue 199324
Enabled word wrap for RD export to PDF
Resolved in Pega Version 7.1.8
After export to PDF from RD, values were getting truncated or being displayed under the column and the column alignment was disrupted. Word wrap has been enabled to fix this display issue.
SR-129876 · Issue 198152
Modified filename verification for Pulse
Resolved in Pega Version 7.1.8
A problem was encountered when uploading files from Pulse if the filename contained special characters. A legacy verification method existed that tested the validity of the filename by creating and then deleting a test file, but that encountered errors when the file system was not writable. To avoid this issue, the validation method has been updated to check for special characters in the file and then decide the file name validation.
SR-129891 · Issue 198738
Reworked decision table cnflict check logic
Resolved in Pega Version 7.1.8
In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. To void this, the system will skip the conflict check for Columns if the property type cannot be determined, eg: column type contains expressions.
SR-127452 · Issue 192406
Case match duplicate check resolved
Resolved in Pega Version 7.1.8
A case match rule to check for duplicates with adding an expression in weighted condition was giving a runtime error due to incorrect page referencing in java step of activity 'RunDuplicateCasesReport' that was attempting to obtain the property from the RD page (which was using a different structure). The page reference has been updated to correct this issue.
SR-128430 · Issue 194956
Pagination removed from OwnersList to facilitate large category lists
Resolved in Pega Version 7.1.8
After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.