SR-124044 · Issue 188405
Save as fixed for French localization
Resolved in Pega Version 7.1.8
Setting localization to French in the Microsoft Internet Explorer browser and attempting a property save generated a JavaScript error. The root cause of this problem was traced to the localized French string value for the English equivalent of dupPropPrompt contained the ' character, which broke the first line of code in RULE-OBJ-PROPERTY PZDUPLICATEPROPERTYMSG. This has been fixed.
SR-124054 · Issue 189568
Simulation delete timing issue resolved
Resolved in Pega Version 7.1.8
When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.
SR-124085 · Issue 184464
Adjusted error handling of "Prebuild Conclusions" during upgrade
Resolved in Pega Version 7.1.8
The "Prebuild Conclusions" task of an upgrade was failing with the error 'ClassNotFoundException'. This was caused by a misconfiguration in the operating environment that led to the jar file that contains the class not being on the classpath during the upgrade. There was a workaround of setting the build.conclusions=false, but a check has been inserted that will skip these error entries and continue building the remaining conclusion entries.
SR-124103 · Issue 185047
Error logging smoothed for service activities-multi threading on multiple nodes
Resolved in Pega Version 7.1.8
When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.
SR-124103 · Issue 185048
Error logging smoothed for service activities-multi threading on multiple nodes
Resolved in Pega Version 7.1.8
When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.
SR-124139 · Issue 186636
Corrected date format error on Data Agents Schedule
Resolved in Pega Version 7.1.8
Post-upgrade in a UAT environment, the Master Agent [Daemon] was not creating the Data Agents Schedule for Rule Agent Queue. This was caused by a month name vs month number mismatch in the YearlyMonth calendar property, and has been corrected.
SR-124151 · Issue 184994
Next button behavior in a modal dialog corrected
Resolved in Pega Version 7.1.8
A workflow issue was found with the 'Next' button on a last row of a repeating grid where clicking on the 'Previous' button would then improperly make available a previously grayed out 'Next' button. Similarly, clicking the 'Next' button on the next-to-last row fired the validation but then disabled the 'Next' button. This was traced to the "NextDisabled" parameter being set incorrectly in case of server side errors, and has been fixed.
SR-124153 · Issue 187971
Revised max datetime value for validation
Resolved in Pega Version 7.1.8
Previously, a date property could have a max set value of 31-Dec-9999. This max date was not working in some time zones due to the input date being converted to GMT for internal operations. This meant that 31-Dec-9999 in some locales was getting converted to 1-Jan-10000GMT, which then failed validation. To correct this, the datetime validity logic has been changed to use "1st Jan 00:00:00.000 10000 GMT" for validation.
SR-124168 · Issue 186995
Application document support added for Word 2007
Resolved in Pega Version 7.1.8
When an Application Document was generated, Word 2007 launched a Microsoft Visual Basic window pop up with the message "Compile error in hidden module: clsPRSessionMgr". The root cause of this problem was a defect in the "Rule-File-Binary" rule WordMacroManagerDot.biw" that supports the 64-bit version of MS Word. This has been fixed.
SR-124198 · Issue 184897
Clarified messages for attachment deletion failure
Resolved in Pega Version 7.1.8
When trying to delete an attachment on the work item without proper authorization, the tracer shows a message being added on TempAttachmentPage in Work- DeleteAttachment activity reading "You are not authorized to delete instance DATA-WORKATTACH-FILE ATPEGA-TASK ". However, this message was not being propagated to the screen and the screen was refreshing as if it worked despite the failure. To clarify the actual results, the DeleteAttachment Activity has been modified to present any messages and to avoid page removal of the TempAttachmentPage and TempLinkPage if there is a message.