New field types in Form Builder
Valid from Pega Version 7.1.9
You can create forms in Form Builder that include the following field types:
- Data reference – Prompts users with a list of data records or instances of a specific data type.
- User reference – Prompts users to select or search for an existing user in the application.
For more information, see Data references in Form Builder and User references in Form Builder.
Reusable components in Form Builder
Valid from Pega Version 7.1.9
You can reuse an existing form or data reference when creating a form. By referencing the existing fields in your application, you save time and build forms that are easier to maintain. Refer to the Reuse fields panel in Form Builder to view all of the fields, forms, and data references in your application.
For more information, see Reuse fields panel in Form Builder.
Search field type is deprecated
Valid from Pega Version 7.1.9
The search field type in Form Builder is deprecated. Use a data reference or user reference instead, both of which prompt users with an autocomplete field at run time.
For the full list of supported field types in Form Builder, see Supported display modes by field type.
Support for enterprise and express applications
Valid from Pega Version 7.1.9
When you run the New Application wizard, you can create two types of applications:
- Enterprise – A full-scale application that has access to all the capabilities in the Pega 7 Platform.
By default, enterprise applications are developed in Designer Studio, but users have access to express mode. - Express – A small-scale application that has access to a subset of the capabilities in the Pega 7 Platform.
Express applications are developed in express mode, and are ideal for new users or for quickly testing functionality.
For more information, see Express applications.
Support for advanced validation of embedded and referenced data
Valid from Pega Version 8.5
To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.
For more information, see Validating field values for stage entry.
Complete email and notification approval in App Studio
Valid from Pega Version 8.5
App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way.
For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.
Business logic routing of approval steps
Valid from Pega Version 8.5
Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.
For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.
Default Create stage in a case life cycle
Valid from Pega Version 8.5
Pega Platform™ now adds a default Create stage to a case life cycle every time you create a new case type, both in App Studio and Dev Studio. The default Create stage includes a view that users interact with to provide initial data before case processing begins. Consequently, you can now easily locate the view to make any necessary changes. In the background, the Create stage makes a case type independent from the starting process, which removes relevant advanced configurations and makes application development faster.
For more information, see Capture initial data faster with the default Create stage (8.5), The Create stage.