INC-162262 · Issue 654966
Query added to find time zone for MSSQL database
Resolved in Pega Version 8.7
The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server.
INC-172849 · Issue 665983
SortPageList method updated for Obj-Sort
Resolved in Pega Version 8.7
Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.
SR-124027 · Issue 190234
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL+D249 Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124028 · Issue 189200
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124029 · Issue 189201
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124036 · Issue 190234
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
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.
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.
SR-127549 · Issue 190837
Improved processing of WSDL for the Create SOAP Integration wizard
Resolved in Pega Version 7.1.8
When running the Create Soap Integration wizard for a selected operation from the WSDL, the wizard was not only generating the necessary rules for the selected operation, but for all operations in the WSDL. To address this, when processTypeContentsAndRelatives is processing a parent type, it now skips type substitutions of the parent.
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.