Published Release Notes

Attachment support for requirements

Requirements now support attachments. You can add attachments from the Designer Studio > Application > Profile > Requirements landing page, the Add/Edit Requirement modal, or the requirement rule form.

Enhanced document generation

The following usability improvements have been made to documents generated by the Application Document Wizard:

• Stages and Processes now appear for case types that use Case Lifecycle Management. This diagram includes hyperlinks to corresponding sections in the document and is scoped to top-level processes only.
  
• All flows (excluding pyStartCase) referenced by a case type now appear in documents. This removes previous constraints on non-starting, draft, and checked out flows.
• Entity Relationship Diagrams (ERDs) are now embedded in documents as Visio objects.
• Sections without content are omitted from the generated document.
• Screenshots are labeled.
• Requirement text (Long Description) is included in the Requirements Matrix section.
• Linked requirements appear in context beneath their associated specification.
• Acceptance Criteria appears in context beneath the associated specification, report, or correspondence item.

Generate documents in the background

When you generate system documentation by using the Document Application wizard (Designer Studio > Application > Tools > Document), the process now runs on a server and not on your local client system. This change not only generates your document more quickly, but also allows you to multi-task within Pega 7 while your document is generating in the background. When the generation is completed, download the document to your computer.

For more information, see:

Updating customized Application Document templates with server-side document generation

Screenshot generation still runs on local client

Warning message when opening server-generated documents

Screenshot generation runs on local client

If you generate screenshots to include in your application document, this process still runs on your local client. Additionally, you are still required to use Internet Explorer to use this feature.

Warning message when opening server-generated documents

Depending on your system configuration, the following warning message might be displayed when you open a document that was generated on the server.

If you click No, certain content (for example, Table of Contents) is not populated in the document. Instead, click Yes and save the document.

The warning message that displays

Link URLs to applications, requirements, and specifications

In addition to files, you can now attach URLs to applications, requirements, and specifications by using the Add/Edit Attachment modal dialog box in Pega 7. This change allows you to link directly to dynamic content in other URL-based systems rather than link to a static file of that content.

Chrome support for editing specification descriptions in Word

If you use Google Chrome 42 and later, you can now create, save, and update specification descriptions even if you are not using the Microsoft Silverlight NPAPI plug-in.

The new Upload Word document as description option provides you with the functionality to upload a Word document that contains the specification description. In addition, you can use the Export to Word option to export the description that you entered in the rich text editor to a Word document.

Redesigned tool for documenting your applications

Use the newly designed Document Application tool to generate application profile documents, application documents, and specification documents. The Document Application tool provides a streamlined landing page for all document types, including custom templates, and replaces the Application Document wizard.

For more information, see Document Application tool and Enhancements to the Direct Capture of Objectives.

Improvements to the Document Application tool

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.

Associate specifications on implementation rule forms

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.