Unit testing support for more rule types
Valid from Pega Version 8.3
You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.
- Collection
- Declare expression
- Map value
- Report definition
For more information about unit testing rules, see Pega unit test cases.
Upgrade impact
With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.
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.
Test coverage support for more rule types
Valid from Pega Version 8.3
Test coverage has been expanded to include the following rule types. Test coverage support for these rule types enables developers to more accurately measure the effectiveness of their tests.
- Collection
- Declare trigger
- Map value
- Navigation
- Report definition
- Scorecard
For more information about test coverage, see Test coverage.
Upgrade impact
The new rule types may impact the test coverage metrics for your applications. Due to the increased number of supported rules, the reported test coverage percentage will decrease.
What steps are required to update the application to be compatible with this change?
Run your coverage reports after upgrading to see the latest metrics.