SR-113557 · Issue 167227
Dynamic Select correctly expands drop downs with IE
Resolved in Pega Version 7.1.7
While using the WorkBasketGadget with dynamic select, drop downs were not expanding to the full width of the field value and parts of the values were hidden. This was caused by an IE bug. The WorkBasketGadget rule has been modified to overcome the issue.
SR-113726 · Issue 162821
Problems exporting Requirements/Specifications to Excel using JBOSS 6.1
Resolved in Pega Version 7.1.7
When using the JBOSS 6.1 EAP Application server, exporting Requirements/Specifications to Excel using the 'Export to Excel' action generated the message "Error in parsing Excel file". This was caused by a change in the JBOSS class loading mechanism that resulted in a class cast exception due to multiple class loaders loading the same class from different sources. The handling of .jar files has been tuned to ensure proper class loading.
SR-113830 · Issue 164768
Smoothed handling of rulesets with duplicate names
Resolved in Pega Version 7.1.7
When doing a "Save As" of a rule, the ruleform converts the entry in the description field to uppercase. If there is already a previous version of the rule with a name in lowercase, it was possible for the rule to exist with both a lowercase and uppercase name. While Rule Resolution worked, this case difference could cause a scenario where not all versions of the rule were visible when doing a rule search, viewing rule history, or looking up previous versions of the rule. The rule retrieval logic previously used RuleName; to ensure proper rules are being picked up, this has been changed to use the rule ID.
SR-114184 · Issue 162116
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114543 · Issue 163265
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114312 · Issue 174692
Check added to handle invalid input in the year field for datetime
Resolved in Pega Version 7.1.7
Previously, when a date time property was provided with an invalid year containing more than four characters (such as 20142014), the date defaulted to 12/20/8963 when the form was submitted. A check has been added to catch dates of more than four digits when attempting validation.
SR-114479 · Issue 165273
Corrected locking for custom Access Roles
Resolved in Pega Version 7.1.7
After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed.
SR-114545 · Issue 164887
Increased limits for Bulk Processing
Resolved in Pega Version 7.1.7
When attempting to filter cases for Bulk Processing, the Property-List LookupList activity only requested a maximum of 2500 records. This caused an issue with class inheritance chains that contained more than 2500 property records, as those excess properties were not being used to filter within Bulk Processing area. To remedy this, the activity now allows a maximum of 10,000 records for Bulk Processing.
SR-114723 · Issue 166462
Portal calendar display corrected
Resolved in Pega Version 7.1.7
No data was visible for the daily or weekly view when displaying the Calendar on the Portal. This was caused by the height of the time frame for Daily/Weekly being set to a fixed value, causing events which fall under 11PM-12AM to not be displayed properly. In addition, the cell width for monthly view was also set to a fixed value, causing it to show only 4 events and hiding the 'show more' option. To correct this, the Day/Weekly view now includes double height to show all events, and the Monthly view displays 3 events and correctly includes the 'show more' option.
SR-114728 · Issue 166514
Resolved locking problems with doubled flow submissions
Resolved in Pega Version 7.1.7
If a Page validation message was present and an additional flow action was submitted through a second action menu, a "Lock Lost" message was generated. This was traced to the "Release on Commit" checkbox defaulting to 'on', and it has been set to a default condition of 'off'.