Customized data imports
Valid from Pega Version 7.2.2
You can now further customize the data import process in Data Designer by:
- Setting a default import purpose and preventing the selection of an import purpose to speed up frequent imports of the same kind
- Removing the import purposes that you do not need for your data type
- Defining a default field mapping between the fields in the .csv file and the fields in your data type that act as a unique identifier (key), to save time during the import process
- Skipping the import progress screen and showing progress contextually within your application
- Including the link for data import anywhere in your application or calling it in the background from a service or agent
For more information, see Data import customization.
Enhanced data imports
Valid from Pega Version 7.2.2
The data import process in Data Designer has been enhanced to give you more options. You can now import case types, save and use templates for field mapping, add data without updating existing data, specify date and time formats, and reprocess erroneous records by downloading a .csv file that lists the errors in your data import. You can also adjust the data import wizard to the context where it is included.
For more information, see Data import enhancements.
Robotic Process Automation (RPA) support for Pega 7 applications
Valid from Pega Version 7.2.2
You can now use Robotic Process Automation (RPA) to automate repetitive and unattended back-office activities directly from your Pega 7 application. By using RPA with your application, you can batch process large volumes of cases faster and with fewer errors compared with manual case processing. You configure the automations in Pega Robotics Automation Studio.
For example, when an automobile insurance claim is submitted, an automation can analyze the submitted information, look up and verify policy holder information, and update web and desktop applications with case information.
For more information, see:
Improvements to guided tour creation
Valid from Pega Version 7.2.2
Usability improvements to creating and managing guided tours enable you to more efficiently create tours that introduce the key features of your application. Now, you configure the Manage guided tour action on a control to start, continue, or dismiss a tour, instead of specifying an API script.
For more information, see Managing a guided tour.
Upgrade utility for Get Next Work performance
Valid from Pega Version 7.2.2
You can run a utility to upgrade Get Next Work processing to more quickly process assignments that were created in versions of the Pega 7 Platform earlier than 7.2.2. Performance is automatically improved on new installations.
For more information, see Upgrading Get Next Work performance.
Create case and Wait smart shapes available in Case Designer
Valid from Pega Version 7.2.2
Two smart shapes have been added in Case Designer. Use the Create case smart shape in a case step to create another case, a child case, or multiple child cases. Use the Wait smart shape to pause the process of a case under specified conditions.
For more information, see Adding a preconfigured step to a process.
Pega File Listener process changes
Valid from Pega Version 7.2.2
Beginning with Pega 7.2.2, File Listener processes files in a different way:
- File movement in directories – Previously, files were processed from the Work directory. In Pega 7.2.2, files are processed from the source location. Files move to the Work directory only if the initial processing fails and Recovery is disabled.
- New file processing – Previously, File Listener would process all files in the source location, even if the files were added during the processing. In Pega 7.2.2, files added to the source location during processing are read the next time the File Listener starts.
For more information, see File Listener data instances.
Automatically process cases with Box
Valid from Pega Version 7.2.2
You can now use Box to store attachments during automated case processing without requiring user input at run time for authentication or authorization with Box. The authentication profile must be OAuth 2.0 with a grant type of authorization code. You can view which apps are connected, connect apps, and disconnect apps on the Connected apps landing page.
For more information, see Connected apps landing page.
Single sign-on (SSO) support for Box
Valid from Pega Version 7.2.2
You can now use SSO integration with Box so that users who have already been authenticated are not asked to reauthenticate when accessing Box from their Pega application. The Pega application and the Box application must use the same identity provider federation. This capability provides an integrated user experience and supports automated case processing of attachments.
For more information, see Authentication Profile data instances - Completing the OAuth 2.0 tab.
Send and receive queued messages securely with IBM MQ servers
Valid from Pega Version 7.2.2
You can now configure applications developed on the Pega 7 Platform for secure message queuing with IBM MQ servers by using the MQ server rule form. You secure the connection by specifying the cipher suites with encryption standards that meet your requirements and the SSL/TLS X.509 certificates that you use for authentication.
For more information, see Configure secure message queuing with IBM MQ servers.