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-129687 · Issue 195885
Updated locale clock handling for Java 7 and PAL
Resolved in Pega Version 7.1.8
Java 7 changed how locales are handled, and the two different NumberFormat classes within PRPC were sometimes leading to errors including blocking access to PAL. In particular, the way PAL set wall clock time was not compatible, and the system has been updated to parse it correctly with the new format.
SR-129690 · Issue 197180
BIX extracts made consistent independent of run method
Resolved in Pega Version 7.1.8
The property format outputted by BIX was different when BIX was run via the command line versus running it from an extract rule in the application's user interface UI. This was traced to running from the UI the batch requestor as unauthenticated and properties created in application rulesets not having property information: the XML page did not have pxObjClass set, hence the property info was null and formatting was ignored. To resolve this, the current requestor will be used (which is properly authorized), and If it is null, then a new app requestor will be created.
SR-129714 · Issue 198126
Added ability to access operator with deleted division/org
Resolved in Pega Version 7.1.8
When an operator as associated with a division and that division was deleted, the existing operator record could not be opened in the developer portal due to a validation error (in this case, associated with a missing division). While there are validation checks associated with deleting organizational units and divisions that safeguard against deletion, it was still possible to delete a non-empty division directly. When this occurred, the operator ruleform could not be opened due to being in an invalid state. Handling for this has now been added, and an operator record can be opened in DS even if the corresponding org/org unit/div has been deleted.
SR-129722 · Issue 197103
Removed extra white space in Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, extra white space appeared above the 'next' button when declare expression was fired in a screen flow which grew with each declare firing. This has been corrected by updating the last condition to check for the 'display' property.
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-129725 · Issue 198663
Enhanced SLA reporting available
Resolved in Pega Version 7.1.8
In order to facilitate detailed reporting on bad SLA items, the following rules have been added: 1. Class to EMBED-QUEUEERRORDETAILS to contain error properties. 2. Page list type property .pxQueueErrorDetails in System-Queue- class. 3. Text type property pxErrorMessage in EMBED-QUEUEERRORDETAILS class. 4. Datetime type property PXERRORDATETIME in EMBED-QUEUEERRORDETAILS class.
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-129768 · Issue 200019
Resolved error saving to lower version unlocked ruleset
Resolved in Pega Version 7.1.8
An error was encountered when attempting to save a rule in an unlocked lower version if a higher level locked version existed. This has been corrected by removing a redundant post condition in the activity Rule-RuleSet -> pzGetOpenRulesetVersions.
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.