SR-127961 · Issue 192637
Corrected reference name for doc attached to work object by CreateMergedWordDoc
Resolved in Pega Version 7.1.8
When using the CreateMergedWordDoc flow action to create a document and attach it to the Work Object, the display showed the label used in "pyNote" as the document name. However, opening the document opens it under the category name. This was caused by a mismatch in the handling and has been corrected.
SR-128433 · Issue 194694
Added template to handle certificate needed by Word MacroManager
Resolved in Pega Version 7.1.8
Because the Word macrocode must be signed with a current certificate, a Signed and timestamped template has been added.
SR-128580 · Issue 199345
Localization added for Audit screen
Resolved in Pega Version 7.1.8
Localization was missing from the 'Complete Task' section of the Audit screen. This has been added.
SR-128620 · Issue 193739
MapCases error resolved with blank page check
Resolved in Pega Version 7.1.8
The MapCases function was generating sporadic errors at a Wait Shape or after Updatestatus that required a logout/login before it was possible to proceed with the Case. MapCases runs tools.findPageByHandle(coverinskey) which can lead to an empty page being returned by the engine if one exists, leading to this error; a blank page check has been added that will then use the default work page if the cover key is empty.
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-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-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.