SR-113506 · Issue 163412
Localization added for previously hard-coded popup
Resolved in Pega Version 7.1.7
The popup message generated by opening a resolved assignment was previously hard-coded to appear only in English. The message will now reflect the proper localization.
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-113597 · Issue 163512
Fixed ability to use 'disable work processing' in the dashboard
Resolved in Pega Version 7.1.7
Setting 'disable work processing' to true caused an NPE when opening a modal window via a Local action from dashboard (assign page class). This was caused by the process attempting to assign properties from a null page, and has been corrected.
SR-113624 · Issue 167070
Enabling out-of-the-box Security Policies now redirects immediately
Resolved in Pega Version 7.1.7
When enabling out-of-the-box Security Policies, it was not immediately redirecting to the change password screen but instead requiring the timeout interval to expire before redirect happened. This has been corrected.
SR-113703 · Issue 163067
Custom root certificate support added to Connect-REST
Resolved in Pega Version 7.1.7
Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.
SR-115779 · Issue 167907
Custom root certificate support added to Connect-REST
Resolved in Pega Version 7.1.7
Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.
SR-113714 · Issue 173122
Added tenantID checking for multi-tenant import of access groups
Resolved in Pega Version 7.1.7
When attempting to overwrite an existing access group by importing the Client Access groups in the tenant layer, an error was generated and the access groups were not overwritten. This occurred when the SQLs were not Tenant-qualifying for operator records but were being imported into a tenant; as a result, operator record updates were marked as inserts. To correct this, the behavior has been updated to query for current tenantId and always tenant-qualify the query if it's an overridable instance and not in a shared context.
SR-113720 · Issue 167454
Page names for specialty components correctly generated as JSON
Resolved in Pega Version 7.1.7
When using a specialty component that accepts input parameters of type page list, the necessary page list parameter names were not being passed as a JSON object due to the system's inability to reference each of them. To correct this, logic has been added to create page name in cases of page list.
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.