Learn about known issues in Pega Platform version 8.7.
SOAP connector wizard fails for JBoss EAP deployments
If you create a SOAP integration connector for a JBoss EAP deployment, the integration wizard fails to generate the SOAP rules and returns critical errors on the final step. This issue affects applications that you use on Pega Platform version 8.6 and later, with JBoss EAP version 7.3.
- By default, Pega Platform ships a Xalan JAR file that conflicts with a Xalan JAR file that is packaged in the JBoss EAP container.
- Exclude or remove the conflicting Xalan JAR file from your JBoss EAP
deployment, and then run the SOAP integration wizard again.
You can prevent the Xalan module from being loaded in JBoss EAP by creating the
jboss-deployment-structure.xmldeployment descriptor file, adding the file to the appropriate project directory, and then including the following code in that file:
<jboss-deployment-structure> <deployment> <exclusions> <module name="org.apache.xalan" /> </exclusions> </deployment> </jboss-deployment-structure>
For more information about excluding a module from a JBoss EAP deployment, see the official Development Guide for Red Hat JBoss EAP 7.3.
Hybrid Theme Cosmos and Cosmos React applications require a URL alias
As of Pega Platform version 8.7, all hybrid Theme Cosmos and Cosmos React applications require an application URL alias.
While earlier Pega Platform versions recommended a URL alias, the system now enforces the choice more strictly by displaying an error screen when the user accesses the application differently, for example through a /prweb format. The error might cause integrations, web embeds, mashups or test automations to fail. You can prevent the issue by defining a URL alias for your application. For more information, see Adding an application URL alias.
OAuth artifacts need to be exported to other systems
Hybrid Theme Cosmos and Cosmos React applications generate OAuth artifacts automatically. However, the OAuth registration records are not automatically included in the application rule that the system generates when you export the application. To ensure correct operation of an application that uses the Constellation engine, you need to manually add the OAuth data instance to the product rule.
You can find the OAuth2Client Registration data instance in the
Security node of the Records
explorer. The OAuth record for the application follows the
PegaApp_<application name> naming
For more information about including data instances in the export package, see Specifying the content of a product rule.