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.
Noticeable differences between work objects created in the Decision Manager portal when compared to Designer Studio
Valid from Pega Version 7.1.7
In the Decision Manager portal, you create work objects by running flows in the enterprise application that serves as the base application for the application overlay. If the enterprise application does not include the UI-Kit-7 in its application rulesets, work objects can display differently in the Decision Manager portal when compared to Designer Studio because an application overlay is always configured to include the UI-Kit-7 ruleset.
Recommendation:
- Add the UI-Kit-7 ruleset dependency to the enterprise application.
- Redesign the user interface to comply with the UI-Kit-7 ruleset.
Rollback functionality is limited to latest revision
Valid from Pega Version 7.1.7
The rollback functionality in DSM Revision Manager allows customers to roll back the import of the latest revision to their DSM application. Only one rollback is allowed; after a rollback, the rollback option is disabled until the next revision is imported. If importing two (or more) revisions at once then attempting a rollback, the system only rolls back one revision.
Example: a user has a base DSM application. They import Revision 1, and then import Revision 2. Next, they try to roll back both revisions. The system reverts to the Revision 1 version of the application, and the customer cannot revert all the way back to the base application.
System Management Application displaying listeners that do not require any action
Valid from Pega Version 7.1.7
After installing or upgrading to Pega 7.1.7, there is an additional available listener (Data-Decision-DNode-Service:Default) that does not require any action. This listener can be safely ignored and you should not use the System Management Application to manage any of its operations or state.
- The Data-Decision-DNode-Service:Default listener is always running on every PRPC node.
- The state of this listener is internally managed by PRPC. Starting or stopping it through SMA does not have any effect on its state.
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.