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 process, 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.
Before you begin
Important: The following information applies to both
Heritage Process Portal
(deprecated) and Process Portal.
About this task
| Property | Default | Description |
|---|---|---|
| calc-all-paths-processing-time-limit | 20 |
Limits the amount of time (in seconds) that Process Portal spends trying to calculate the critical path.
If a projected path cannot be determined during this time, the Gantt chart does not display any future tasks. For all future instances of the process, the Gantt chart does not include any future tasks either. If the value is updated and the server is restarted, the projected path will be reevaluated for the next instance that is started. |
Attention: The way in which a process is modeled affects the projected path discovery
time. Certain modeling constructs cause longer discovery times and can result in a process timeout,
stack overflow, or out-of-memory condition. For more information about these constructs, see Enabling process instance management.
Use the following XML snippet to make the configuration change in the
100Custom.xml
file:
<common>
<critical-path>
<calc-all-paths-processing-time-limit merge="replace">20</calc-all-paths-processing-time-limit>
</critical-path>
</common>
For information about making and deploying 100Custom.xml configuration changes, see Creating a 100Custom.xml configuration file.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15