INC-211599 · Issue 708543
Data page definition reload made more robust
Resolved in Pega Version 8.7.2
The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.
SR-A102503 · Issue 271030
Restriction facet set corrected for max and minExclusive
Resolved in Pega Version 7.2.2
Using a service where WSDL defined a single method and used a datatype definition from an XSD import generated the error "Unsupported XML 1.0 Restriction "minExclusive" minExclusive restriction is not recognized". This error occurred because minExclusive was not added to recognized facet names but maxExclusive is added twice. To fix this, the duplicate occurrence of maxExclusive was removed and minExclusive was added to the recognized restriction facet set in XSDConstants.
SR-A22547 · Issue 252633
Cookie handling added to CMIS
Resolved in Pega Version 7.2.2
Support has been added to use cookies with CMIS to allow connecting to FileNet via connect-cmis.
INC-171753 · Issue 649441
Checks for Apache Tomcat 6 with MSSQL removed
Resolved in Pega Version 8.7
After implementing a specific local Tomcat configuration that removed the Tomcat version number from displaying on Tomcat standard error screens, the error "Tomcat 6 not supported or unable to detect version for custom Tomcat: Apache Tomcat. Contact Pega Customer Support!" appeared and Tomcat failed to start. Because Tomcat 6 was not supported for use with Microsoft SQL Server Systems, Pega used the ServletContext.getServerInfo() method to determine the Tomcat version; if the system used Tomcat 6 or an undetermined version in combination with MSSQL then the system would purposefully not start. As Tomcat 6 is no longer supported in Pega 8.5.2 and above, this check is unnecessary in those versions and the Tomcat version 6 checks in ClassMapImpl have been removed to allow serverAllowsMerge to return as true.
SR-A92260 · Issue 259866
GRS supported for JMS Listener ID
Resolved in Pega Version 7.2.2
Support has been added to use a global resource reference setting for the JMS listener Requestor ID field.
INC-177470 · Issue 657142
Optimization prconfig check added for TableInformationMap
Resolved in Pega Version 8.7
A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.
INC-170551 · Issue 656559
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.7
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-182986 · Issue 668829
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
SR-A76100 · Issue 254315
GRS supported for JNDI settings in JMS Listener
Resolved in Pega Version 7.2.2
Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.
SR-A88782 · Issue 263961
GRS supported for JNDI settings in JMS Listener
Resolved in Pega Version 7.2.2
Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.