Internal rules in search results and explorers
Valid from Pega Version 7.4
Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.
Applications not working as expected when using fast processing for Connect REST and Service REST integration
Valid from Pega Version 7.4
In Pega® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.
Service Portlet rules are deprecated
Valid from Pega Version 8.2
Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.
For more information about Pega Web Mashup, see About Pega Web Mashup.
Deprecated metadata types in the Connector and Metadata wizard
Valid from Pega Version 8.2
The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.
For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.
Deprecated support for passing symbolic index as strings to value lists and page lists
Valid from Pega Version 8.2
Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:
myPageList("<LAST>")and
param.str = "<LAST>" myPageList(param.str)
The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.
param.str = <LAST> myPageList(param.str)
To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.
For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.