Cannot copy final section rules in UI Kit ruleset
Valid from Pega Version 7.1.6
You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).
Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at
, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.User interface distortions in the Decision Manager portal
Valid from Pega Version 7.1.6
By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.
Workaround:
- Open the application record.
- In Application Rulesets, remove UI-Kit-7.
- Save the application record.
User interface distortions in the Predictive Analytics Director portal
Valid from Pega Version 7.1.6
By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.
Workaround:
- Open the application record.
- In , remove UI-Kit-7.
- Save the application record.
Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button
Valid from Pega Version 7.1.6
A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.
Number and text input controls on Android devices may not display the correct keyboard
Valid from Pega Version 7.1.8
When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number
.
At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.
To resolve this issue, use the Phone
type when numbers with decimal values may be required. Using the Phone
type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.
The Phone type selected in the Presentation tab of a Number control
Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.
Decision Data Store data sets can be used only on DNodes
Valid from Pega Version 7.1.8
Data flows that contain Decision Data Store data sets as the primary or secondary source must be created and executed only on DNodes.
Data flows are not restarted automatically after application server restart
Valid from Pega Version 7.1.8
When you restart the application server or the Pega 7 server, you stop the execution of your data flows. The interrupted batch and real-time runs are marked as Failed.
Recommendation:
- Go to the > > > > tab and start the failed batch runs.
-
Go to the
> > > > tab and activate the failed real-time runs.
Value list and value group properties are not supported inside data flows
Valid from Pega Version 7.1.8
Value list and value group properties are not supported inside data flows, and you need to instead use other property types.
See the Pega 7 developer help to check all available property types.
Data flow preview size is fixed to 10
Valid from Pega Version 7.1.8
The Preview option for each shape in data flows returns the first 10 records. This value is fixed and currently cannot be changed.
Data Flow transformation shapes cannot be used in combination with the Compose or Merge shapes
Valid from Pega Version 7.1.8
When you reference another data flow from a data flow that contains the Compose or shape, the referenced data flow cannot contain transformation shapes ( , , ).
Data flow validation does not currently prevent you from designing a data flow that goes against this design pattern. Make sure that your data flows follow this design pattern by checking the referenced and referencing data flows.