Package caching is not supported in offline-enabled applications built with the UI Kit 7 (09-01-01) portal
Valid from Pega Version 7.3
When you create an offline-enabled application in Pega® Platform, by default, it uses a portal with the UI Kit 7 (09-01-01) ruleset. In such a case, the package caching functionality cannot be used. You must either disable caching on the Advanced tab of the Access Group rule form, in the Offline Configuration section, or use an adaptive design instead of rendering different elements for different devices with the UI Kit 7 (09-01-01) ruleset.
For more information, see Access Group form - Completing the Advanced tab.
Create specialized Decision Data rules for text analytics resources
Valid from Pega Version 7.3
You can store various types of resources for text analytics in Decision Data rules that are based on templates. Each resource type (for example, sentiment analysis models, taxonomies, entity extraction rules, and so on) has its own definition class that defines the appearance of the corresponding Decision Data rule form. With this enhancement, system architects can create and maintain various text analytics-related artifacts without having to edit the default Decision Data form fields first.
For more information, see Definition class of text analytics Decision Data rules.
Pega Agile Studio integration
Valid from Pega Version 7.3
You can configure the new Agile Workbench tool to integrate with Pega® Agile Studio so that bugs and user stories are synchronized between the two systems. In addition, you can improve traceability in your development environment by using the Current work feature to associate a user story or bug with development changes.
For more information, see Integrating Agile Workbench with Pega Agile Studio and Tracing development changes to work items.
Style UI elements based on their state
Valid from Pega Version 7.3
You can style a control or component based on its state to give users a visual indication of an element's current state, without overriding the CSS file. The styles that you specified for each state (hover, focus, or active) are applied at run time.
For more information, see Styling UI elements based on their state.
Style radio buttons as segmented buttons
Valid from Pega Version 7.3
You can configure radio buttons to be displayed as segmented buttons. Segmented buttons display multiple button options in a compact format. Segmented buttons do not support vertical orientation. On the Presentation tab of the properties panel, set Control format to Other and select Segmented.
For more information, see Radio Buttons control properties – Presentation tab.
Text file rules support JavaScript and CSS validation
Valid from Pega Version 7.3
The Rule-File-Text rule form supports validation errors and warnings for JavaScript and CSS files. This support makes JavaScript and CSS code easier to maintain and allows you to follow best practices while editing the rule. Any JavaScript or CSS validation warnings generate a guardrail warning of moderate severity.
For more information, see Text File rules - JavaScript and CSS validation.
Log file description in web.xml incorrect after upgrade to Apache Log4j 2
Valid from Pega Version 7.3
As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, it is recommended that you update the log file description in the web.xml file from location of prlogging.xml file to location of prlog4j2.xml file. The description indicates which log file is in use. Updating the description avoids confusion about which log file is current. Change the description as shown in the following example.
<resource-ref id="ResourceRef_5">
<description>location of prlog4j2.xml file</description>
<res-ref-name>url/pegarules.logging.configuration</res-ref-name>
<res-type>java.net.URL</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Apply logic to data import fields
Valid from Pega Version 7.3.1
When importing data from an external system, you can translate data fields into values that can be read by Pega® Platform. From the Import wizard, you can do the following actions:
- Apply a decision tree or decision table to the data that is imported for a field.
- Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
- Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.
For more information, see Transforming data during import.
X-Forwarded-Host field is optional for HTTP proxy servers
Valid from Pega Version 7.3
Prior to Pega® Platform 7.3, the X-Forwarded-Proto and X-Forwarded-Host fields were both required to deploy Pega Platform instances behind an HTTP proxy server. Some proxy servers or load balancers (for example, Amazon ELB) do not support the X-Forwarded-Hostfield. Starting with Pega 7.3, only the X-Forwarded-Proto field is required. For more information, see Deployment behind a reverse proxy.
Pega Cloud Services support for the AWS Canada (Central) region
Valid from Pega Version Pega Cloud
Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) Canada (Central) region. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.
For more information about regions and availability zones, see Pega Cloud Services capabilities.
This additional region is available as of QIII 2017.