DCO
Valid from Pega Version 7.1.4
This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer. The layout of the New and Save As forms were made more intuitive and intelligent. Specification actions were made to be more consistent across various aspects of the Case Designer.
- After removing specification references, users can create and save a new specification.
- Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
- If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
- In the outline view, specification changes will be preserved when switching from tab to tab.
- The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.
Attachment support for requirements
Valid from Pega Version 7.1.6
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
Valid from Pega Version 7.1.6
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.