Basic information on the use of system parameters can be found in the System Parameters chapter in the manual for the "Portal & Organization" module.
Most parameters of the bean WfOptions are only the system-wide default value: if a value is set in the client's workflow settings (tab "Workflow"), it takes precedence (noted in the table).
The SwitchUser functions are defined in the system parameters - module wf, bean WfOptions:
WfOptions.switchUserMayApprove
WfOptions.switchUserActsAsNominalUser
|
Module |
Bean |
Property |
Explanation |
Possible value(s) |
|---|---|---|---|---|
|
wf |
SharkProperties |
additionalProperties |
Additional configuration parameters for the Shark WF engine (key=value per entry). They are read when the workflow engine starts and therefore only take effect after a restart. |
Default: Cache.OmitXPDLCacheOnStartup=true LimitAgentManagerClassName= |
|
wf |
WfOptions |
alwaysHideActionLogs |
Always hide the History column in the WF list. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
hideSubProcesses |
If a process starts other requests/processes > should these subprocesses be hidden (special case, currently not used in the Webdesk HR modules). The client setting takes precedence. |
true/false (default: true) |
|
wf |
WfOptions |
showEmployeeIdWithinWorkList |
Display of the personnel no. in the workflow lists. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showFormDetailsFirst |
Display of the form tab in the process details in first position. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showProcessVariables |
Display of the process variables in the detail view. The client setting takes precedence. |
true/false (default: true) |
|
wf |
WfOptions |
switchUserMayApprove |
allows users to approve requests in switched views. The client setting takes precedence. |
true/false (default: true) |
|
wf |
WfOptions |
switchUserActsAsNominalUser |
the switched user is treated exactly like the user who was switched to. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showGraphicalProcessRepresentation |
Display of the graphical process flow in the process details. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showOrgUnitWithinWorkList |
Display of the associated department in the workflow lists. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showRoleInsteadNextPerformer |
Display of the role, rather than the person, who is next in the process. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
useWfListBatchModeOnly |
If the parameter is set to true, direct approval of a request is no longer possible (only by checking the corresponding action). The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showConfirmationDialogInWfListOnRedirectAndDelete |
If true, the user must confirm in the workflow list before a delete-and-forward action is executed (e.g. "Start request" for a system notice that is deleted in the process). The client setting takes precedence. |
true/false (default: true) |
|
wf |
WfOptions |
showPrintButtonWithinWorkList |
Display of a Print button in the workflow list. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
showDeputyHintInMyToDos |
If true, a deputy notice is shown in the "My tasks" list for tasks received as a deputy. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
hideDeputyFeatures |
If true, the deputy settings in the user settings ("I also want to receive an email notification as a deputy", "My deputy may approve for me") are hidden. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
userSettingsMailNotificationOnAssignment |
Status of the user setting "In case of new tasks, I want to receive an email notification": ACTIVE = editable, OUTPUT = display only, INVISIBLE = hidden. The client setting takes precedence. |
ACTIVE (default), OUTPUT, INVISIBLE |
|
wf |
WfOptions |
userSettingsMailNotificationOnAssignmentAsDeputy |
Status of the user setting "I also want to receive an email notification as a deputy" (values as above). The client setting takes precedence. |
ACTIVE (default), OUTPUT, INVISIBLE |
|
wf |
WfOptions |
userSettingsDeputyMayApprove |
Status of the user setting "My deputy may approve for me" (values as above). The client setting takes precedence. |
ACTIVE (default), OUTPUT, INVISIBLE |
|
wf |
WfOptions |
commentTemplateKeyValueType |
Name of a key/value type whose entries are offered for selection as comment templates when commenting in the workflow list. Empty: no comment templates. The client setting takes precedence. |
Text (default: empty) |
|
wf |
WfOptions |
deputyMayApproveIfPerformerAbsent |
If true, when an activity is assigned it is checked whether the main performer is absent (see absenceCodesActivatingDeputy), so that the activity can be assigned to the deputy. If false, absences are ignored. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfOptions |
absenceCodesActivatingDeputy |
Absence reason codes (comma-separated): if the main performer has a booking with one of these codes at the time of assignment (and no productive booking), they count as absent. Only takes effect if deputyMayApproveIfPerformerAbsent is active. The client setting takes precedence. |
List of absence reason codes (default: empty) |
|
wf |
WfOptions |
asyncProcessingOfToDos |
If true, individual processing of tasks (approve, reject, complete, acknowledge) in the workflow list is carried out asynchronously in the background: the list is updated immediately, and the processing progress is displayed in the header area of the application. The client setting takes precedence. |
true/false (default: false) |
|
wf |
WfProcessDefinitionDAOTarget |
extendedAttributesToInject |
Extended attribute - only in the xpdl: with this functionality, extended attributes can be injected into the process definitions after the fact. Useful for influencing existing running processes (takes effect only after a server restart) |
procDefNameWithOrWithOutVersion;eaKey=eaValue |
|
wf |
WfProcessDefinitionDAOTarget |
defaultMailSubject |
Default email notification subject (used if the process definition does not specify its own mail subject) |
Webdesk TO-DO |
|
wf |
WfProcessDefinitionDAOTarget |
defaultMailBody |
Default email notification text (used if the process definition does not specify its own mail text) |
You have some To-DOs inside your Webdesk Worklist! |
|
wf |
WfProcessInstanceDAO |
allowSwitchUserAutomaticApprove |
enables automatic approval for a switched user |
true/false (default: true) |
|
wf |
WfTarget |
useCaches |
Use of caches of the workflow engine (takes effect only after a restart) |
true/false (default: true) |
|
wf |
WfTarget |
useDatabaseBasedLockMaster |
Implementation of the lock - process instances; if the parameter is set to true, the locking of process instances is managed via the database, otherwise within main memory. In cluster operation, a cluster-capable lock is used automatically if false. Takes effect only after a restart. |
true/false (default: false) |