Business logic-based routing cards enhancements
Valid from Pega Version 8.5
To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.
For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.
Automated Unit Testing is unavailable
Valid from Pega Version 7.1.1
Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.
Starting in 7.1.6, users can access AUT features from supported browser versions of IE.
IE8 limits expansion features
Valid from Pega Version 7.1.1
Internet Explorer 8 (IE8) does not support CSS media queries, which are used by re-expansion features in the Designer Studio. IE8 users with low screen resolution (800 x 600) and a small window size may find that the explorer area in the Designer Studio collapses but cannot re-expand.
As a work around, access the Designer Studio from another supported browser version and use the recommended, minimum screen resolution width of 1280 pixels.
Unicode-enabled database for international language support
Valid from Pega Version 7.2.1
The Pega 7 Platform database has been enhanced to natively support Unicode multibyte character set encoding when using Postgres on Pega Cloud. This enhancement allows you to store data in languages such as Japanese, Chinese, and Korean.
Change the type of an existing field
Valid from Pega Version 7.2.1
You can now change the type of an existing field on the Data model tab of a case type or data type, resulting in a more efficient development process at design time. If there are any validation issues when changing a type, an error message is displayed, and the type cannot be modified by using this method.
For more information, see:
- Modifying the type of a field
- Troubleshooting validation errors when changing the type of an existing field
Open authoring for rule forms has been removed
Valid from Pega Version 7.2.1
Open authoring for rule forms has been removed. You can now edit decision tables and map values by using the application and supported browser of your choice; Microsoft ActiveX controls are no longer required. In addition, support for external XML, HTML, and Java IDE editors has been removed.
Pega Express application views simplify portal creation
Valid from Pega Version 7.2.1
Pega Express application views offer a simple, intuitive authoring experience for portals. Application view templates support responsive application development and offer mobile-specific templates. You can create portals by selecting from a predefined set of application view templates.
For more information, see Application views.
Rule form search
Valid from Pega Version 7.2.1
You can now search for content within some rule forms by clicking Search rule on the menu. The search results and the tabs of the rule form that contain the search results are highlighted.
For example, you can find the properties that are used in a when condition inside an activity without navigating to each tab, when condition, transition, and method in the activity.
Delegate service-level agreements
Valid from Pega Version 7.2.1
You can now delegate service-level agreements (SLAs) to your business line by clicking
. You can also delegate circumstanced versions of SLAs.For more information about delegations, see Delegating a rule or data type.
Circumstance a rule by different properties
Valid from Pega Version 7.2.1
You can specialize or circumstance a rule by a different property even if the base rule is circumstanced by another property. This flexibility can help address cases where the same rule needs to be circumstanced by different properties. When you circumstance a rule by different properties, the circumstanced versions of the rule must be in different rulesets or Applies To classes.
You can circumstance a rule by a different property in the same ruleset, but in a higher version, by withdrawing the existing circumstanced versions.
For more information, see Circumstance a rule with different properties or templates.