Both Transfer and Transfer Assignment flow actions are displayed in the Bulk Actions tool
Valid from Pega Version 7.1.7
Both the deprecated Transfer flow action and its Pega 7.1.7 replacement Transfer Assignment (pyTransferAssignment) might appear in the menu on the Bulk Actions tool.
Either of the following situations can cause this behavior:
- The original application did not contain the UI-Kit-7 ruleset, for example, the application was built on Pega 7.1.5.
- The default flow actions are based on BulkProcessTransferFlowAction system settings.
- If you add pyTransferAssignment as a local action in a case type rule, users will see both old and new actions.
- The flow actions are still available unless you override the settings.
- The upgraded application uses the UI Kit ruleset, but the Transfer local action was defined in the original case type rule and copied to the application.
- The original is explicitly defined in the application.
- pyTransferAssignment is available through the system settings in the UI Kit.
As a best practice, upgrade Transfer flow actions to Transfer Assignment in your flows and local actions. The UI Kit ruleset ensures that the new flow actions are optimized for mobile interfaces. In addition, Transfer Assignment provides multiple transfer functions (to manager, workbasket, advanced options) in a single form.
Alternatively, keep the original system settings so that the existing flow actions are still available.
Flow import functionality is limited to Microsoft Internet Explorer Version 9 and Version 10 in Pegasystems Public Format
Valid from Pega Version 7.1.7
Importing a flow in the Rule-from-File wizard is limited to Microsoft Internet Explorer 9 and Internet Explorer 10 in the Pegasystems Public Format .
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
| Label in previous versions | Label in Pega 7.2 |
|---|---|
| Text | Text (single line) |
| Text (multiple lines) | Text (paragraph) |
| Check box | Boolean |
| Date and time | Date & time |
| Date | Date only |
| Drop down | Picklist |
| Number (integer) | Integer |
| Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
Process Outline view is unavailable
Valid from Pega Version 7.2
Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.
For more information, see Designing a case type and Diagram tab on the Flow form.
New location for case-type settings
Valid from Pega Version 7.2
The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.
For more information, see Configuring case-type behavior.
No private posts in new Pulse gadget
Valid from Pega Version 7.2
The new Pulse gadget does not support private posts. When you upgrade to the new gadget, any private posts of the following types that you created by using the previous version of the gadget become public.
- Operator posts
- Case posts
- Posts that used the generic pxPostMessage API with private posts enabled
- Posts that used the Pulse smart shape in PRPC 6.3 or earlier with private posts enabled
For more information about the new Pulse gadgets for developers, Pulse gadgets and custom APIs.
For more information about the using the new Pulse gadget, see Communicating with Pulse.
Cannot view all custom context posts in Pulse
Valid from Pega Version 7.2
When you use Pulse in a custom context, the custom context label is displayed as plain text instead of as a link that you can click to view all posts that are associated with the custom context.
For more information about Pulse, see the help topic Pulse.
Processes run by default when a stage is restarted
Valid from Pega Version 7.2
The Run on re-entry check box in Case Designer has been removed. As a result of this change, processes run by default each time that a stage is restarted. Users who previously had this check box cleared can use the Start when option in Case Designer instead to define the criteria for skipping a process.
For more information, see Adding a process to a stage.
Conversion of single-step assignments is no longer required
Valid from Pega Version 7.2
You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
The following table lists the step labels in Case Designer that were updated to support this change.
Step label in previous versions | Step label in Pega 7.2 |
|---|---|
| Single-step assignment | Collect information |
| Approval | Approve/Reject |
| Attachment | Attach Content |
| Case | Create Cases |
For more information, see Adding a step to a process in a stage.
Email approval and instantiation not supported on multitenant systems
Valid from Pega Version 7.2.1
The Enable email approval check box appears on the General tab of an approval step in Case Designer in multitenant systems. It also appears on the Approval shape in Designer Studio. In addition, in Designer Studio, the Settings tab in Case Designer displays the option to configure email instantiation. However, because configuring email listeners is not supported on multitenant systems, you cannot enable email approval or email instantiation.