Customized application overview documents in App Studio
Valid from Pega Version 8.3
Keep stakeholders notified of the status of an application by customizing and generating an application overview document in App Studio. The overview may include information such as case types, roles, features in your application, and more. Select the chapters that you want to include in the overview, and then highlight the most relevant information by ordering the chapters. In addition to the application overview document, you can generate a detailed data model, either in Microsoft Word or Excel format.
For more information, see Creating project documents for stakeholders in App Studio, Exporting a data model into a document.
New send email automations and enhancements
Valid from Pega Version 8.3
You can now configure cases, flows, and activities to compose and send guardrail-compliant emails that conform to the MIME standard by using email automations. Use the new Call-Automation method to call an automation from an activity without writing Java.
You can also now categorize error messages in automations to quickly understand the type of error that occurred. In addition, page list data types are now supported for inputs and outputs in automations.
For more information, see Calling an automation from an activity and Viewing automations.
Simple associations for quickly joining classes
Valid from Pega Version 8.3
Associations now have a simple mode. Use a simple association to quickly and easily join a class to another class. The simple association defines a left join, using a foreign key in the source class and the class key in the target class. Use an advanced association for all other conditions. In addition, simple associations are drawn in the Visual data model reporting mode to visualize the relationships that are available for reporting.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Exploring the data model.
Association changes after upgrade
Valid from Pega Version 8.3
Associations now have a simple mode. Simple associations are those that join to only one class, use a left join, and have one filter condition to a class key in the target class. Existing associations that define a simple foreign key relationship are upgraded to simple associations when opened; all others are treated as advanced associations. All associations continue to work in reporting.
Making an association simple changes only one piece of metadata; all other data on the association rule is not affected.
Upgrade impact
The new simple mode draws a map of where all the classes defined in the application rule are drawn as nodes. Relationships between the nodes that are defined by relevant properties are drawn as lines linking the two classes. This feature only includes Case and Data classes that are defined on the Application rule form's Cases and Data tab. It also only includes relevant fields for those classes in order to define the relationships from one class to another.
What steps are required to update the application to be compatible with this change?
After a successful upgrade, add the data and case type classes to the application rule in Dev Studio to have the selected classes appear as a node. In addition, if you want a relationship to display as relevant, set the properties (of the class that defines that relationship) as relevant.
For more information, see Associations.
More efficient navigation between applications in App Studio
Valid from Pega Version 8.3
The new My Applications gadget helps you switch applications in App Studio more conveniently. You can also search applications by name instead of choosing an application from the list, and then select the access role that you want to use. In addition, you can see descriptions of your applications and create an application by going to the My Applications landing page. To use the My Applications gadget, ensure that you update the UI Kit to version 14.
For more information, see Adding the My Applications gadget, Switching between applications in App Studio.
BIX ruleset is now included with Pega Platform
Valid from Pega Version 8.3
The Pega Business Intelligence Exchange™ (BIX) ruleset is now included with Pega Platform™, which eliminates the need for additional provisioning for Pega Cloud customers and for a separate BIX installation for on-premises customers. To add BIX to your application, add the Pega-BIX:<version>
ruleset to your application rulesets.
For more information, see Data extraction.
Upgrade impact
After a successful upgrade, the BIX ruleset is available within Pega Platform. You should synchronize the BIX ruleset and Pega rules to avoid extraction errors.
What steps are required to update the application to be compatible with this change?
After the upgrade is complete, change the ruleset version for Pega Platform and BIX to use the same, latest version.
Facilitated application development with saving changes in branches in App Studio
Valid from Pega Version 8.3
For improved development of your application, you can now define branches in which you save changes that you make to your application in App Studio. Create features in branches so that you can review and merge them without affecting other features in the application. You can quickly identify and review any changes to rules because you know in which application layer they were saved.
For more information, see Setting branch preferences in Dev Studio, Setting branch preferences in App Studio.
Support for controlling simulations in Integration Designer
Valid from Pega Version 8.3
Integration Designer now supports toggling an existing simulation for a data source on and off, and supports creating a simulation when a data source does not have a simulation configured. By simulating a data source, you can continue developing an application when your integration is not available, and test an application independently from the integration.
For more information, see Managing data and integrations with the Integration Designer.