Pega Mobile Preview app
Valid from Pega Version 8.2
You can now use Pega Mobile Preview to access multiple mobile channels and preview your Pega Platform™ application, for example, to verify that it is displayed correctly and operates as intended. Pega Mobile Preview is a native application that runs on Android and iOS devices. Compared with Pega Mobile Express, it enables switching between mobile channels and supports enhanced layout configuration options.
You can download Pega Mobile Preview from the Apple App Store or from Google Play.
For more information, see Pega Mobile Express and Pega Mobile Preview.
Changes in JSON results when checking the health of your system
Valid from Pega Version 8.2
Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.
JSON results for pre-Pega Platform 8.2:
{ "duration":"3954.448601", "count":"0" }
JSON results for Pega Platform 8.2 and later:
{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.
Add the security checklist to applications created before 7.3.1
Valid from Pega Version 7.3.1
The security checklist is now automatically added to applications. You can manually add the security checklist to applications that were created in earlier versions.
You can improve the security of your application by completing the tasks on the checklist.
The following task reflects the procedure on how to manually add the security checklists to Designer Studio prior to 7.3.1:
- In the header of Designer Studio, click the name of the application, and then click Definition.
- Click the Documentation tab.
- In the Application guides section, click Add guide.
- In the Application guide& field, enter pxApplicationSecurityChecklist.
- Click the Configure icon in the Available in column and select the portals (App Studio and Dev Studio) that you want to add the security checklist to.
- Click Save.
Default value of the threadpoolsize agent affects batch indexing
Valid from Pega Version 8.5.2
After you patch Pega Platform to version 8.5.2 or higher, the system changes the default value of the threadpoolsize agent, which controls the number of concurrent activities (threads) in the system, from 5 to 15. Batch indexing in Pega Platform™ does not require all 15 threads, so you can change the agent value to increase system performance by managing the indexing/distributed/batch/numworkers dynamic system setting.
If your deployment does not support that setting, and batch indexing does not use Queue Processors, the system uses the threadpoolsize value for batch indexing instead.
For more information, see Editing a dynamic system setting.
New dynamic setting to manage validation of hidden fields
Valid from Pega Version 8.6.4
Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false.
For more information, see Managing field validation in hidden sections.