Formally deprecated rule types
Valid from Pega Version 7.1.6
The following rule types have been deprecated. Migrate to alternatives as appropriate:
| Rule type (class) | Replacement |
|---|---|
Rule-Connect-BPEL | Service SOAP rules |
Rule-Define-Hierarchy | Navigation rules |
Rule-File-Form | Harnesses and Sections |
Rule-Parse-Infer | @pxReplaceAllViaRegex function |
Rule-Parse-Transform | @pxReplaceAllViaRegex function |
Rule-Parse-TransformCollection | @pxReplaceAllViaRegex function |
Rule-Service-BPEL | Service SOAP rules |
Rule-Service-COM | Service dotNet rules |
Retired Six R's
Valid from Pega Version 7.1.6
The Designer Studio > Application > Inventory > Six R's landing page has been retired.
Integration landing page updates
Valid from Pega Version 7.1.6
The following features and wizards now launch as landing pages in the Designer Studio:
Designer Studio > Integration > Tools > Wizard cleanup
Designer Studio > Integration > Email > Email Accounts
Designer Studio > Integration > Email > Email Listeners
Restructured Process & Rules landing pages
Valid from Pega Version 7.1.6
The Designer Studio > Process & Rules > Tools landing page menu has been restructured for better navigation and access:
- The Find Rules by Custom Field wizard now launches as a tab in Designer Studio.
- A new Find Rules menu item consolidates previous wizards. It launches a single landing page with different search criteria options:
Check out rules with errors
Valid from Pega Version 7.1.6
You can now check out rules with validation errors. This is helpful when a checked-in version becomes invalidated by changes elsewhere in the application, such as a modified ruleset pre-requisite or a deleted referencing rule.
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.
Stage-related audit notes
Valid from Pega Version 7.1.6
History notes for the following stage-related process steps appear on the user form's Audit tab:
- Automatic Stage Transition
- Manual Stage Transition
- Process Stage Transition
- Stage Skipped
- Stage Started
You can select the ones you want to turn off for a given case type by copying the standard decision tree Work-.FilterHistory to your application ruleset and updating the above parameter entries.
Redesigned Process Modeler property panels
Valid from Pega Version 7.1.6
Process Modeler property panels have been reorganized so that it's easier to find the properties and fields you're likely to want, and quickly create the configuration you need. To enhance ease of use:
- Tabs were eliminated.
- All fields are located on a single panel and are grouped by their function.
- The most commonly used fields appear at the top of the panel and are clearly visible.
- Field and functionality of interest to advanced users are organized into an expandable Advanced section positioned at the bottom of the panel.
- Business-friendly labels and headings, and instructional text make it easier for non-technical users to quickly understand the meaning and purpose of each field.
Dynamic layout improvements
Valid from Pega Version 7.1.6
The following usability improvements have been made to dynamic layouts:
- Refresh conditions can be specified on a dynamic layout. You no longer need to create sections to create refresh boundaries.
- Labels on an included section or nested dynamic layout can be specified with label-positioning specified in the skin.
- Validation errors in a dynamic layout now display below the field.
- Use natural label width for inline dynamic layouts so only necessary space is used.
