Enabling historical compliance score data
Valid from Pega Version 7.1.9
Project stakeholders can now track the compliance score for an application over time to better understand and manage ongoing development adherence to Pega 7 Platform guardrails. The compliance score history can be displayed on a line graph on the Compliance Score tab of the Application Guardrails landing page. The data is collected daily and displayed in weekly increments, up to four weeks prior to the current date.
For more information, see Guardrails compliance score, Enabling compliance score history, and Compliance score trend reporting.
Application Sizing Wizard worksheet template now includes business impact
Valid from Pega Version 7.1.9
A column for business impact has been added to the project sizing template used by the Application Sizing Wizard. Project owners can now incorporate this assessment into their project sizing.
Internet Application Composer (IAC) renamed to Pega Web Mashup
Valid from Pega Version 7.1.9
The name of Internet Application Composer (IAC) has changed to Pega Web Mashup.
For more information, see Pega web mashups for embedding Pega Platform UI in external web pages.
FTP server records enhanced for SSH FTP
Valid from Pega Version 7.1.9
When using SSH FTP (SFTP) in an FTP Server record, you can securely transfer files by using SSH keys. You can enable and configure SFTP by opening the FTP server record and completing the fields in the Protocol section.
For more information, see SSH FTP for FTP server records.
New Business impact optimization dashboard
Valid from Pega Version 7.1.9
On the Analysis tab of the Application Profile landing page, you can now enable historical specification count and implementation progress by complexity and business impact. On the Business impact optimization dashboard, you can view counts of specifications by complexity and business impact. You can also view counts, by business objective, of specifications that have been implemented and for those not yet implemented. You can filter specifications by release and iteration.
For more information, see Viewing specifications by complexity, impact, and business objective, and Associating project specifications with business impact and complexity.
Data page unit test case setup and cleanup
Valid from Pega Version 7.2.1
You can now use one or more data pages, data transforms, or activities to set up a clipboard page with the appropriate properties before you run a data page unit test case. You can also use activities to create any required test data, such as work or data objects.
After you run a data page unit test case, the data pages that were used to set up the test environment are automatically removed. You can now also apply additional data transforms or activities to clean up the clipboard.
For more information, see Setup and cleanup of data page unit test cases.
New assertions for data page unit test cases
Valid from Pega Version 7.2.1
You can now configure the following assertions for data page unit test cases:
- Result count assertions for page lists, page groups, value lists, and value groups
- Unordered list and ordered list assertions for page lists
The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.
For more information, see Data page unit test case assertions.
Improvements to the Document Application tool
Valid from Pega Version 7.2.1
Application profile documents and application documents generated by the Document Application tool have been improved to present information in a more logical order based on how the application was built (for example, by case life-cycle management). Also, these types of documents now include all specifications linked with an implementation rule, presented in logical order under the implementation rule.
In addition, to help you more efficiently drive decisions by stakeholders, you can specify whether to include related built-on application layer assets in application profile documents and application documents. For specification documents, you can specify whether to include specifications from the built-on application layer.
For more information, see Document Application tool.
Execute Tests service to run all data page unit test cases
Valid from Pega Version 7.2.1
You can now use the Execute Tests service to run a set of tests at the end of build runs. An external validation engine, such as Jenkins, calls the service, which runs all data page unit test cases in your application, and returns the results in XUnit format. Use this service to validate the data in your application and to correct any issues before you deploy your application.
For more information, see Running all data page unit test cases with the Execute Tests service.
Associate specifications on implementation rule forms
Valid from Pega Version 7.2.1
You can now view, add, and delete the specifications that are associated with a rule on the new Specifications tab of most rule forms. The Specifications tab is available for almost all implementation rules, except for administrative and deprecated rule types. By associating specifications with the rules that implement them, you improve the end-to-end traceability of your specifications.
For more information, see Associating specifications on implementation rule forms.