WSDL generation error prevents invocation of SOAP services
Valid from Pega Version 8.4.2
A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.
Due to changes introduced in the SOAP functionality for the case-mismatch error in SR-D98509/INC-119725, the WSDL is being generated for SOAP services with an incorrectly-capitalized element, which prevents the service from being invoked. The element should be “name” instead of “Name”.
Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:
- To download the WSDL from Pega Platform:
- After using the SOAP Wizard (Dev Studio > Configure > Integration > Services > Service Wizard) the WSDL URL is shown at the bottom right of the Dev Studio screen.
- Click the URL to display the XML.
- Save the WSDL file to your local system.
- In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
- Save your changes to the local file.
- To reload the WSDL into Pega Platform:
- In Dev Studio, open the Configure menu.
- Select Integration > Connectors > Create SOAP Integration.
- In the New SOAP integration wizard, select Upload WSDL from File.
- Complete the upload using the wizard prompts.
This is a design-time issue, not a run-time issue; therefore, clients only have to perform this workaround process once. Existing SOAP services should not be impacted; however, if clients modify an existing SOAP service definition by re-running the wizard, clients must reapply the workaround for Pega Platform to recognize the SOAP definition changes.
This issue will be addressed in the Pega Platform Patch Release 8.4.3. Clients who upgrade to that version or later should not see this issue.
Valid from Pega Version 7.1.4
Improvements to data handling were made for search indexing, agent processing, and filtering. Scripts were provided for proper population of the database tables.
- Importing data from shared obj-external tables is now supported.
- A validation warning will now display when an unexposed property is used in filter or join conditions.
- A Global Search index may now be created across two databases.
- Agent processing on multiple nodes has been improved.
- Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
- Filtering functionality involving special characters has been enhanced.
- Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.
Valid from Pega Version 7.1.4
Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.
- A script was created to run the data schema upgrade for z/OS systems.
- In a split-schema configuration, indexing has been enhanced.
- The product installer has been enhanced.
- The stand-alone Static Assembly Utility does not require a password for its process.
- The UpdateManager tool has been improved.
Primary key constraint error when using JBoss
Valid from Pega Version 7.1.9
A primary key constraint violation exception might occur in the following situation: you use JBoss EAP 6.4 and SQL Server 2012 with a JDBC 4 driver, and you use two or more file listeners or JMS MDB listeners with concurrent threads that create work objects that use multiple files. If a primary key constraint violation exception occurs in this situation, update the data source configuration file to set the jta parameter to true. For example, set <datasource jta="true" jndi-name-"java:/jdbc/PegaRULES>.