Data synchronization does not resume after mobile app restart
Valid from Pega Version 8.3
If an offline-enabled mobile app that you build with Pega Infinity Mobile Client™ is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.
Following the introduction of new functionalities for mobile apps, some features are reaching end of life. To avoid additional effort during updates to future releases, do not use deprecated features.
In the 8.4 release, the following features are no longer recommended:
Mobile Client 7 is now deprecated and planned for removal in 8.5. Use Pega Infinity Mobile Client to meet the mobile needs of your business.
The Reuse existing web portal functionality is deprecated and planned for removal in 8.5. For improved app performance and more efficient development, use the mobile app builder in the mobile channel. Also, you must convert existing projects to use separate channels for mobile and web portals before upgrading to 8.5.
In addition, the Pega Mobile Express app has been removed from app stores and replaced with the Pega Mobile Preview app.
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.
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.
Search and Reporting does not index large items
Valid from Pega Version 8.5
When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.
Change logic does not work in Report Editor
Valid from Pega Version 7.1.2
The Report Editor change logic button does not work. As a workaround, use the rule form to change the logic.
Source field not displaying in data transform
Valid from Pega Version 7.1.4
On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.
(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)
Below is a data transform that has been configured to use Update Page.
If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
Required Oracle optimization parameter
Valid from Pega Version 7.1.3
To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.
Slow WebSphere performance on Mac platforms
Valid from Pega Version 7.1.2
Use the following JVM setting to improve WebSphere performance on Mac platforms:
Turn off saved connections in WebLogic
Valid from Pega Version 7.1.1
PRPC caches connections in thread-local storage. When using a WebLogic application server, set database/savedconnections to FALSE to avoid incorrectly saved, container-managed transactions. You can make this update through JNDI settings or by adding an entry to the prconfig.xml, for example: