The Create Build button appears grayed out when configuring and building a mobile application
Valid from Pega Version 7.1.8
When you attempt to configure and build your Android or iOS mobile application from the Mobile tab, the button might appear dimmed. This issue occurs if any of the access roles in the access group were cloned from the PegaRULES:SysAdm4 access role.
Refer to Troubleshooting Pega Mobile Client to learn how to fix this issue in your application.
Resolved Issues for This Release
Valid from Pega Version 7.1.8
For details on the Resolved Issues for this release, visit the Resolved Issues page.
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.
Data flow destination is resolved at assembly time
Valid from Pega Version 7.1.8
Data flow execution always uses the design-time destination data sets or destination data flows, regardless of the input records at run time.
Example:
You create a data flow and set the destination to a specific data set. In the data flow, you use a strategy that produces some results. Regardless of these results, the execution of your data flow always uses the destination data set that you specified when you designed the data flow.
The same applies when you set the destination to a data flow.
Offline configuration limitation
Valid from Pega Version 7.1.8
When enabling the offline capability for a case type, do not select the Enable offline check box in Case Designer because it incorrectly sets the locking strategy. Instead, select the Enable offline mode check box on the Advanced tab of the Case Type form.
To open the Case Type form from Case Designer, click Open on the menu.
Creating data page unit tests in Internet Explorer 8
Valid from Pega Version 7.1.8
When creating data page unit tests, selecting a parent property does not automatically select the child properties when using Internet Explorer 8.
Page and page list properties to be included in a data page unit test are selected on the Create test screen by selecting a check box next to the property name. Normally, selecting the check box of a parent property automatically selects all subsequent child properties as well. When using Internet Explorer 8, child properties are not automatically selected when the parent property's check box is selected.
The solution requires selecting all of the desired child properties individually. Select the check box next to each child property to include it in the data page unit test.