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.
Generate documents in the background
Valid from Pega Version 7.1.8
When you generate system documentation by using the Document Application wizard ( > > > ), the process now runs on a server and not on your local client system. This change not only generates your document more quickly, but also allows you to multi-task within Pega 7 while your document is generating in the background. When the generation is completed, download the document to your computer.
For more information, see:
Updating customized Application Document templates with server-side document generation
Screenshot generation still runs on local client
Warning message when opening server-generated documents
Screenshot generation runs on local client
Valid from Pega Version 7.1.8
If you generate screenshots to include in your application document, this process still runs on your local client. Additionally, you are still required to use Internet Explorer to use this feature.
Warning message when opening server-generated documents
Valid from Pega Version 7.1.8
Depending on your system configuration, the following warning message might be displayed when you open a document that was generated on the server.
If you click , certain content (for example, Table of Contents) is not populated in the document. Instead, click and save the document.
The warning message that displays
Link URLs to applications, requirements, and specifications
Valid from Pega Version 7.1.8
In addition to files, you can now attach URLs to applications, requirements, and specifications by using the Add/Edit Attachment modal dialog box in Pega 7. This change allows you to link directly to dynamic content in other URL-based systems rather than link to a static file of that content.
New property pxCommitDateTime
Valid from Pega Version 7.1.8
A new property, pxCommitDateTime, records the time when a record or updated rule was committed to the database. This property also allows for incremental extracts when running BIX.
Report Browser removed from Designer Studio
Valid from Pega Version 7.1.9
The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.
The Report Browser is still available in the Case Manager portal.
Enabling historical compliance score data
Valid from Pega Version 7.1.9
Project stakeholders can now track the compliance score for an application over time to better understand and manage ongoing development adherence to Pega 7 Platform guardrails. The compliance score history can be displayed on a line graph on the Compliance Score tab of the Application Guardrails landing page. The data is collected daily and displayed in weekly increments, up to four weeks prior to the current date.
For more information, see Guardrails compliance score, Enabling compliance score history, and Compliance score trend reporting.
Application Sizing Wizard worksheet template now includes business impact
Valid from Pega Version 7.1.9
A column for business impact has been added to the project sizing template used by the Application Sizing Wizard. Project owners can now incorporate this assessment into their project sizing.