Geolocation tracking for the latest mobile client
Valid from Pega Version 8
The latest version of Pega Mobile Client™ now supports geolocation tracking for offline-enabled mobile apps. You can enable constant tracking when users work on specific cases from their worklists. This enhancement helps audit the trail of the case and increase the efficiency of your mobile users. For example, dispatchers at headquarters can track the routes of field workers and more effectively assign them tasks based on their current location.
For more information, see Tracking mobile users based on geolocation data.
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.