Changing configuration properties for Process Portal in the 100Custom.xml file
You can add configuration properties to the 100Custom.xml file to change the runtime behavior of Process Portal. For example, you can change the default duration for projected path discovery or specify the default snapshot for when Process Portal runs on a Process Center server.
Important: The following
subtopics apply to Heritage Process Portal, Process Portal, or
both. To determine the applicability of the information to your environment,
see the individual subtopics.
- Configuring Process Portal notification and refresh behavior
In non-federated environments, Process Portal uses CometD web messaging to push notifications and data refreshes to users when relevant events happen in the system. You can configure notification and refresh behavior by updating settings in the 100Custom.xml configuration file. - Tuning authorization performance for Process Portal
Authorization for many actions in REST API based clients, such as Process Portal, is determined by the security groups and teams that a user belongs to. If users belong to many (thousands of) security groups and teams, they might experience performance issues because of frequent authorization lookups. You can improve performance in these situations to restrict authorization lookups to the groups and teams that are relevant in a specific context. - Configuring the default duration for projected path discovery in Process Portal
There are several routes, or paths, that can be followed to complete a process instance. If projected path management is enabled for a BPD, the Gantt chart in Process Portal can display the projected path for an instance if distinct paths from the start to end nodes are found. You can configure the default time that Process Portal can take to discover the projected path. - Disabling the display of time tracking information in Process Portal
You can disable the display of time tracking information for Process Portal users by setting the display-time-tracking property in the 100custom.xml configuration file. - Configuring the default snapshot for Process Portal running on a Process Center server
In production environments that run on a process server, each process application has a nominated default snapshot. This snapshot is used to start instances of a process in Process Portal. However, in test environments where Process Portal runs on a Process Center server, Process Portal uses the current snapshot (tip) instead. If you want to specify a specific snapshot as the default for the test environment, you can configure the Process Center snapshot behavior by using a setting in the 100Custom.xml file. - Opening services in Heritage Process Portal in a new browser window
By default, services, such as tasks and startable services, are opened in the Heritage Process Portal browser window. You can change the browser behavior by setting the launch-in-new-window-enabled property in the 100custom.xml configuration file. - Configuring the My Team Performance dashboard for Process Portal (deprecated)
You can configure certain aspects of the My Team Performance dashboard, for example, which tasks are visible to team managers and the maximum number of tasks that is displayed in the task list. 
Optimizing the login time for web applications
To help improve performance, you can reduce the time that a user spends logging in to web applications, including Process Portal. For this purpose, you set the user-group-membership-sync-cache-expiration configuration property to a number of minutes below which that user's membership to user groups is not recalculated.
Parent topic: Modifying Process Portal runtime behavior