Actions available for custom controls
Valid from Pega Version 7.3
All standard actions that are available for autogenerated controls are available on non-autogenerated custom controls as well. You can configure actions on custom controls by using the legacy actions options or the standard options that are available to custom and autogenerated controls. By using the standard options, developers can now configure multiple action sets for different types of events on a single custom control.
For more information, see Actions tab.
Relevant records now support class inheritance
Valid from Pega Version 7.3
Relevant records can now be inherited through your class hierarchy. For example, a property that is marked as a relevant record at the Work- class can also be inherited by the child classes of the Work- class.
For more information, see Adding relevant records.
Support for conversational user channels
Valid from Pega Version 7.3
You can now communicate with users and customers of a Pega® Platform application by using Pega Intelligent Virtual Assistant acting as a conversational user channel. You can now use Facebook Messenger, Alexa voice commands, standard email, or mobile texting (SMS) to interact with Pega Platform, for example, to open a case or display a menu of available options. In addition, in the Facebook channel configuration, you define text analyzer rules for advanced text analysis, based on artificial intelligence, so that the system provides the best response to users.
For more information, see Intelligent Virtual Assistant.
New Pega0086 alert and enhanced Pega0019 alert
Valid from Pega Version 7.3
The PEGA0086 alert is generated when the maximum number of attempts to acquire a lock on a requestor has been exceeded and a thread fails to obtain a lock on the requestor, and as a result, displays the RequestorLockException message. The Pega0019 alert has been enhanced and now contains additional information such as a user name, an application name, and a thread stack trace, which are associated with the long-running requestor.
For more information, see PEGA0086: Requestor locked by a busy thread and PEGA0019 alert: Long-running requestor detected.
Create resilient data flow runs
Valid from Pega Version 7.3
The resilience of data flow runs has been improved. If Data Flow service nodes fail, active data flow runs continue on the remaining functional nodes. Depending on the type of primary data source and the selected run failure policy, data partitions on the failed nodes can be reprocessed on another functional node or the data flow run is marked as failed for further investigation. You can also add or remove nodes from the Data Flow service while data flow runs are in progress. The runs are automatically rescaled.
For more information, see Data flow run updates.
Capture real-time feedback with Agile Workbench
Valid from Pega Version 7.3
Project stakeholders can use the new Agile Workbench tool to capture real-time feedback directly in an application, which can increase the efficiency of application development. You capture feedback by creating a user story, bug, or feedback item, and these work items can include video recordings of screens, annotated screen captures, file attachments, or URLs. In Designer Studio, you can configure Agile Workbench to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems.
For more information, see:
- Pega Express 7.3 – Agile Workbench
- Pega Platform 7.3 – Agile Workbench
Performance enhancements to the Strategy rule
Valid from Pega Version 7.3
Strategy designers can create globally optimized strategies to increase the performance of existing strategies. Globally optimized strategies reduce computation time and memory consumption when you run large-scale batch data flows and simulations. Improvements to the Strategy rule performance are the result of decreased run time and quality changes to the code generation model.
For more information, see Introduction of globally optimized strategies.
Create application guides that direct users through tasks
Valid from Pega Version 7.3
Use the new Application Guide rule to create a guide that directs users through a set of tasks. A task can provide instructions to the user and include links to a landing page, wizard, URL, rule, or data record. After you add an application guide to a portal, users can open the guide from the Resources menu.
For more information, see Creating an application guide.
No support for Android versions earlier than 4.4 on mobile devices
Valid from Pega Version 7.3
Pega® Platform dynamic layouts by default now use Flexbox-based rendering. As a result, mobile devices running on Android versions earlier than 4.4 are not supported in Pega Platform. Such devices cannot render correctly with Flexbox because the Pega Mobile Client includes the default stock browser on the Android operating system.
Edit sections across Pega Express and Designer Studio
Valid from Pega Version 7.3
Sections created in Pega® Express can be edited in Designer Studio, saved, and then reopened in Pega Express. This allows developers to create more complex, feature-rich sections and make them accessible to Pega Express users. In the section rule, you can convert template-based sections to full sections that no longer use a template.
For more information, see Harness and Section forms - Adding a section.