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.

Cause

By default, Pega Platform ships a Xalan JAR file that conflicts with a Xalan JAR file that is packaged in the JBoss EAP container.

Workaround

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.xml deployment 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 pattern.

For more information about including data instances in the export package, see Specifying the content of a product rule.

Section appears in the wrong harness

In existing Theme Cosmos applications, when the user completes the Create stage, the new step opens in the Create stage dialog box, and not in the main action area in the portal.

Cause

The issue occurs when Pega Platform version 8.7.1 is paired with the Theme Cosmos ruleset 02-01.

Workaround

Update the Theme Cosmos ruleset to version 03-01 or 04-01. However, the ruleset change might require additional development effort. For more information, see Updating Theme Cosmos in your application.

Alternatively, you can use hotfix HFIX-83337 and keep your current Theme Cosmos ruleset version.

Tags disappear from Rich Text Editor source mode

When you use Rich Text Editor in HTML source mode, some tags disappear from the markup, which causes backward compatibility issues and data loss.

Cause

Pega Platform version 8.5.5 introduced the DOM Purifier security plugin. The plugin removes potentially vulnerable tags, including custom tags, from the raw HTML code in the Rich Text Editor source mode.

Workaround

You can disable the DOM Purifier plugin by adding the window.disableDomPurifier = true markup to the userWorkForm HTML fragment rules.

Alternatively, as of Pega Platform version 8.5.6, you can add a tag to the allow list by including the window.rteCustomAllowedTags =['myCustomTag'] snippet in the userWorkForm HTML fragment rule.

Duplicate columns in tables produce run-time issues

In Pega Platform versions 8.6 and newer, when using optimized tables in traditional, section-based architecture, sourcing two columns from the same property can produce run-time issues in personal views.

For example, if a user adds a second column sourced from the same property as an existing column in the view, the column might appear in the wrong place in the selector menu, or might not hide when toggled in the column selector.

Customer search fails after updating from Pega Platform version 8.4.6 or earlier

In some cases, customer search fails to work after updating from Pega Platform version 8.4.6 or earlier to version 8.7.2 or higher.

Cause

In Pega Platform version 8.7.2 or higher, Rest Connect causes this issue when the lowest allowable SSL/TLS version is set to TLS version 1.0.

Workaround

Edit your rule form for outbound connections to use the appropriate protocol supported by your Pega application's underlying Java version, preferably TLS 1.2 if the server supports that version.

Decision Data Store data set failures after modifying the Decision Data Store table consistency level

There is an issue with Decision Data Store data set ingestion failing if the Decision Data Store tables consistency level is set to Strong. If you are experiencing any issues when you want to modify the consistency level for read operations and write operations, you need to contact customer support to acquire a hotfix. To learn more about setting the consistency level for read operations and write operations in Decision Data Store tables, see Managing Decision Data Store tables.