Quickly add an attachment step to your processes
Valid from Pega Version 7.1.6
The Attachment step allows you to quickly add an Attach Content subprocess to your flow. Once added, choose the attachment type and instructions to present to users:
View a record of Case Designer updates on the case type rule History tab
Valid from Pega Version 7.1.7
The History tab on case type rules now automatically records a history of rules edited or created from the Case Designer Stages & Processes tab. This feature allows system architects to review updates made by business analysts and other developers. It also allows business analysts to easily convey to fellow team members a record of configuration changes.
See More about Case Type rules.
Edit process-based case type flows in Case Designer Process Outline view
Valid from Pega Version 7.1.7
If your case type does not employ a stage-based design, you can now employ the Step Tree and other features available in Process Outline view to facilitate your design.
Click a process tile in the Stages & Processes tab to open the flow in Process Outline. In this example, the Graffitti report is selected.
Processes in Stages & Processes tab
The process opens in Process Outline view. Note that the tree view allows you to easily see and update the underlying shapes and subprocess that compose the Single Approval process.
Process in Process Outline view
Flow action and attachment category rule types moved to Process category
Valid from Pega Version 7.1.7
The flow action and attachment category rule types now appear in the Process category within the Record and Application Explorers. Previously, they were in the User Interface and Security categories, respectively.
A single starting flow creates all ad hoc cases
Valid from Pega Version 7.1.6
An operator can uniformly create ad hoc cases in the My Cases area on the Case Manager portal, on user forms, and in Pega Pulse by way of the standard starting flow pySimpleCaseWorkFlow. Operators can define the routing of the case and an overall SLA when creating the case.
The default action created by the ad hoc flow contains a dashboard that also enables operators to quickly define tasks and add attachments.
Previously, the standard flows pyManualTaskStandardAssignment and pyManualTaskStandardApproval were employed. These are deprecated, but are still supported in existing configurations.
Certain flow actions deprecated and replaced
Valid from Pega Version 7.1.7
To ensure compatibility with supported browsers and mobile devices and to enhance ease of design, the following flow actions are deprecated and replaced. As a best practice, use the replacement actions for new development. The deprecated rules are still supported and do not have to be updated.
Deprecated | Replacement |
---|---|
Transfer | Transfer Assignment |
TransferAdvanced | " |
TransferToManager | " |
TransferToWorkbasket | " |
Approve | Approval |
Reject | " |
AttachAFile | Attach Content |
pyAdjustSLA | Adjust Assignment SLA |
pyAdjustSLATimes | " |
pyChangeAssignmentSLA | " |
pyUpdate | Update Case |
For example, the new Transfer Assignment action supports the most common routing options such as operator, workbasket, and reporting manager. Advanced options allow users to escalate, set due dates, update status, and provide instructions.
Transform Assignment form
See Atlas - Standard Flow Actions (Local).