Work Modes

--run

This mode executes kenaflow in the actual execution mode.

kenaflow launches several subprocesses, that is, other kenaflow.exe instances that perform various tasks.

Multiple Tasks are possible:

  • Receive remote events from SharePoint
  • Processing of remote events from SharePoint 2013
  • Processing of remote events from SharePoint 2016
  • Processing of remote events from SharePoint 2019
  • Processing of remote events from SharePoint Online
  • Workflow processing

In the default setting, 1 process for receiving remote events is started, plus one process each for processing remote events for SharePoint 2013, 2016 and Online. There are also 5 processes for workflow processing.

All workflows that kenaflow finds in the workflow root directory - as specified in the global configuration file - are queued and processed one after the other. A maximum of 5 in parallel (in the standard setting).

Each individual workflow can only be executed once at a time.

Each SharePoint list item can only be processed by 1 workflow at a time.

For example, the remote event processing processes might want to access list items that are currently being processed. The processing is then postponed by remote event and tried again later.

The number of processing processes can be changed via the global kenaflow configuration. See section "multiprocessing".

Together with --run, the --workflowroot switch can be used to ignore the globally configured workflow root directory and use the specified one instead.

If the global configuration changes during execution, all subprocesses and the main process are terminated and restarted.

If a workflow configuration changes, the subprocess for this workflow is restarted.

--workflowroot

will be edited soon

--vscode

This starts Visual Studio code that is integrated into the kenaflow program directory.

The data and user directories of Visual Studio Code are adapted so that all data (including extensions) is stored in the context of the current kenaflow instance.

--onlywf

The --onlywf=<full-path>[%<full-path>[%<full-path>...] option can be used to allow only special workflows in subprocesses. The paths to workflow configuration files must be specified. Several are separated by % if necessary.

Execution delay means that for each workflow or additionally for each workflow step (for state machine workflows) you can specify how much time should elapse between two executions.

--exec

This mode executes a workflow.

Normally, this switch is not called directly by the user. However, it is possible to execute exactly 1 workflow.

For this purpose, kenaflow.exe --exec is started in the workflow directory or the parameter --workflow=<full-path> is used with a complete path to a workflow configuration file, e.g.:

kenaflow.exe --exec --workflow=c:\workflows\wf1\_wfconfig.ps1

The option --teststate=<state-code>[:<state-code>[:<state-code>...]] can be used to allow only certain workflow steps for workflow execution. All steps not included here are ignored.

Execution delay means that for each workflow or additionally for each workflow step (for state machine workflows) you can specify how much time should elapse between two executions.

--teststate

Coming soon!

--notbe

The --notbe option can be used to disable all execution delays.

Discussion