HUB
Sign inSign up
workflowgen logo

advantys/workflowgen

By advantys

•Updated 3 days ago

WorkflowGen workflow automation. Windows containers only. PostgreSQL or SQL Server 2025.

Image
0

50K+

advantys/workflowgen repository overview

⁠WorkflowGen - Business Process Automation Platform

This image contains a WorkflowGen Server using IIS and WorkflowGen's Windows Services. Use this image to run WorkflowGen's web application, Windows services, or both.

⁠WorkflowGen 10.6.0 Beta — MCP process design

WorkflowGen 10.6.0 Beta adds AI-assisted process design through MCP 1.1.0, subject to native rights and process-state rules.

Beta: evaluation only, not recommended for production. Examples below use stable 10.5.0. Select the beta tag from its release notes⁠, not latest. See the plugin setup guide⁠ for client configuration.

Back up before upgrading. latest follows the newest stable v10 LTSC 2019 release; Beta publication keeps it on the stable release. Pin a version tag for reproducibility. Application images remain Windows containers; this feature requires no database-major upgrade.

⁠⚠️ Platform & Database Support

WorkflowGen application: Windows containers only (all versions)

Database options for production:

WorkflowGen VersionProduction DatabaseContainer Type
v10.5.0PostgreSQL 17.6–17.11Windows or Linux
v10.5.0PostgreSQL 18.0–18.6Linux or Windows LTSC2022
v10SQL Server 2025Linux only
v9.3.1+SQL Server 2022Linux only
v9.3.0 and earlierSQL Server 2019Linux only
v8SQL Server 2019Linux only

Development/Testing database options:

WorkflowGen VersionDev/Test DatabaseNotes
All versionsSQL Server Express 2017 (Windows)10GB limit, not for production
v10 onlySQL Server 2025 Express (Windows)50GB limit, not for production

Hybrid deployments pair the WorkflowGen Windows container with a Linux database container using the production combinations listed above. Windows SQL Server images are for development/testing only.

See the SQL Server overview⁠ and PostgreSQL overview⁠ for database deployment details.

⁠PostgreSQL images for WorkflowGen 10.5.0

WorkflowGen 10.5.0 provides PostgreSQL 17 and 18 images with pgvector. Use the latest corrective release in the supported range. On customer-managed servers, select pgvector for your PostgreSQL major, OS and architecture; image versions are listed in the PostgreSQL overview.

Database container platformPostgreSQL 17 tagPostgreSQL 18 tag
Linux Debian Bookworm10.5.0-postgres17-debian-bookworm10.5.0-postgres18-debian-bookworm
Windows Server 2022 LTSC10.5.0-postgres17-win-ltsc202210.5.0-postgres18-win-ltsc2022
Windows Server 2019 LTSC10.5.0-postgres17-win-ltsc2019No PostgreSQL 18 variant

Pin the WorkflowGen version, PostgreSQL major and platform. Legacy versioned tags without a major remain PG17 aliases. See the PostgreSQL overview⁠ for moving aliases and volume examples.

To update within the same PostgreSQL major, back up the database, pull the new image, stop the old container cleanly and create its replacement with the existing compatible volume. Pulling an image alone does not update a running container or its database.

Changing images does not migrate PostgreSQL majors: never reuse a PG17 data directory with PG18, or vice versa. Linux PG18 mounts /var/lib/postgresql with PGDATA=/var/lib/postgresql/18/docker; PG17 mounts /var/lib/postgresql/data. Updating pgvector binaries does not update an existing database extension.


⁠Available Tags

Dockerfile sources:

Each directory contains Windows Server 2019 and 2022 Dockerfiles and their customizable onbuild variants.

Example tags:

  • 10.5.0-win-ltsc2022 - WorkflowGen v10.5.0 for Windows Server 2022
  • 10.5.0-win-ltsc2019 - WorkflowGen v10.5.0 for Windows Server 2019
  • 9.7.0-win-ltsc2022 - WorkflowGen v9.7.0 for Windows Server 2022
  • 9.7.0-win-ltsc2019 - WorkflowGen v9.7.0 for Windows Server 2019
  • 8.3.5-win-ltsc2019 - WorkflowGen v8.3.5
  • latest - Latest published v10 release; points to the primary Windows Server 2019 image
  • -onbuild suffix - Customizable variant

⁠Requirements

  1. On Windows 10 Pro or Enterprise, install Hyper-V and Docker Desktop⁠, switch to Windows containers, and use an ltsc2019 image. Windows 10 does not support Windows Server 2022 container images.
  2. Use Windows 11 or Windows Server 2022 or later for ltsc2022 images. Consult Microsoft's Windows container version compatibility⁠ matrix when the host and container versions differ.
  3. On Windows Server, use the image tag matching the host version for process isolation. A newer compatible host can run an older image with Hyper-V isolation.
  4. A WorkflowGen license to copy into the C:\wfgen\licenses volume.
  5. A serial number to set via WFGEN_APP_SETTING_ApplicationSerialNumber.
  6. A database: v10 uses PostgreSQL or SQL Server 2025; v9/v8 use SQL Server.

⁠Run the Container

Before running, ensure the database is initialized with provided SQL scripts.

docker run -it --env-file .\workflowgen.env -v C:\path\to\licenses:C:\wfgen\licenses --name wfgen advantys/workflowgen:{version}-win-{windows-version}

Replace {version} with your WorkflowGen version and {windows-version} with the matching Windows container version, such as ltsc2022 or ltsc2019.


⁠Quick Setup with Docker Compose

Examples use WorkflowGen 10.5.0 and LTSC2022, with PostgreSQL 17 where applicable. For Server 2019, replace every ltsc2022 tag with ltsc2019. Do not mix Windows container versions in one stack.

⁠v10 with PostgreSQL on Windows

Prerequisites:

# Create volumes
docker volume create licenses
docker volume create wfgdata
docker volume create pgdata

# Copy license
$licensesPath = docker volume inspect --format "{{.Mountpoint}}" licenses
Copy-Item ~\Desktop\license.lic $licensesPath

# Generate symmetric encryption key (32 characters)
[guid]::NewGuid().ToString("N")
# Example: ca8e4e2b04254aeeadbcfc0724e3b62a

docker-compose.yml:

services:
  workflowgen:
    image: advantys/workflowgen:10.5.0-win-ltsc2022
    depends_on:
      - database
    environment:
      - WFGEN_DATABASE_CONNECTION_STRING=Host=database;Port=5432;Database=wfgen;Username=wfgen_user;Password=yourStrong(!)Password;
      - WFGEN_DATABASE_CONNECTION_STRING_PROVIDER_NAME=Npgsql
      - WFGEN_APP_SETTING_ApplicationUrl=http://localhost:8888/wfgen
      - WFGEN_APP_SETTING_ApplicationSerialNumber=YOUR_WORKFLOWGEN_SERIAL_NUMBER
      - WFGEN_APP_SETTING_ApplicationSecurityPasswordSymmetricEncryptionKey=ca8e4e2b04254aeeadbcfc0724e3b62a
    ports:
      - 8888:80
    volumes:
      - licenses:C:\wfgen\licenses:RO
      - wfgdata:C:\wfgen\data
  database:
    image: advantys/workflowgen-postgres:10.5.0-postgres17-win-ltsc2022
    container_name: database
    environment:
      - PGDATA=C:\pgsql\data
      - POSTGRES_INITDB_ARGS=--username=postgres
      - POSTGRES_PASSWORD=yourStrong(!)Password
      - WFGEN_DATABASE_USER_PASSWORD=yourStrong(!)Password
      - WFGEN_ADMIN_PASSWORD=yourStrong(!)Password
    volumes:
      - pgdata:C:\pgsql\data
    ports:
      - 5432:5432

volumes:
  licenses:
    external: true
  wfgdata:
  pgdata:

For a new PostgreSQL 18 deployment on LTSC2022, select 10.5.0-postgres18-win-ltsc2022 and a fresh database volume. Do not reuse an existing PostgreSQL 17 data volume directly.

Run:

docker compose up -d

Access: http://localhost:8888/wfgen⁠ (username: wfgen_admin, password: yourStrong(!)Password)


⁠v10 with SQL Server 2025 Express on Windows

Prerequisites:

# Create volumes
docker volume create licenses
docker volume create wfgdata
docker volume create sqldata

# Copy license
$licensesPath = docker volume inspect --format "{{.Mountpoint}}" licenses
Copy-Item ~\Desktop\license.lic $licensesPath

# Generate symmetric encryption key
[guid]::NewGuid().ToString("N")
# Example: ca8e4e2b04254aeeadbcfc0724e3b62a

docker-compose.yml:

services:
  workflowgen:
    image: advantys/workflowgen:10.5.0-win-ltsc2022
    depends_on:
      - database
    environment:
      - WFGEN_DATABASE_CONNECTION_STRING=Data Source=database;Network Library=DBMSSOCN;Initial Catalog=WFGEN;User ID=WFGEN_USER;Password=yourStrong(!)Password;TrustServerCertificate=True;
      - WFGEN_APP_SETTING_ApplicationUrl=http://localhost:8888/wfgen
      - WFGEN_APP_SETTING_ApplicationSerialNumber=YOUR_WORKFLOWGEN_SERIAL_NUMBER
      - WFGEN_APP_SETTING_ApplicationSecurityPasswordSymmetricEncryptionKey=ca8e4e2b04254aeeadbcfc0724e3b62a
    ports:
      - 8888:80
    volumes:
      - licenses:C:\wfgen\licenses:RO
      - wfgdata:C:\wfgen\data
  database:
    image: advantys/workflowgen-sql:10.5.0-express-win-ltsc2022
    container_name: database
    environment:
      - SA_PASSWORD=yourStrong(!)Password
      - WFGEN_DATABASE_USER_PASSWORD=yourStrong(!)Password
      - WFGEN_ADMIN_PASSWORD=yourStrong(!)Password
    volumes:
      - sqldata:C:\wfgen\sql
    ports:
      - 1433:1433

volumes:
  licenses:
    external: true
  wfgdata:
  sqldata:

Run:

docker compose up -d

Access: http://localhost:8888/wfgen⁠ (username: wfgen_admin, password: yourStrong(!)Password)


⁠Linux Database Containers

WorkflowGen application images run on Windows, but v10 can connect to a Linux database container. See the dedicated repositories for complete examples:


⁠Configuration

⁠Database Connection Strings
⁠v10: PostgreSQL
WFGEN_DATABASE_CONNECTION_STRING=Host=database;Port=5432;Database=wfgen;Username=wfgen_user;Password=<password>;
WFGEN_DATABASE_CONNECTION_STRING_PROVIDER_NAME=Npgsql
⁠v10: SQL Server 2025
WFGEN_DATABASE_CONNECTION_STRING=Data Source=database;Initial Catalog=WFGEN;User ID=WFGEN_USER;Password=<password>;TrustServerCertificate=True

Note:

  • TrustServerCertificate=True bypasses certificate validation for the example's self-signed certificate. In production, use a trusted certificate and keep validation enabled.
  • SQL Server provider is System.Data.SqlClient (default, no need to specify)

For v8 and v9 connection-string examples, see the documentation for the corresponding image tag.

⁠web.config File

Configure settings via environment variables: WFGEN_APP_SETTING_<name>

Example:

WFGEN_APP_SETTING_ApplicationUrl=https://example.com/wfgen
⁠iisnode Configuration for Node Applications

Configure IISNode: WFGEN_IISNODE_<app name>_<setting name>

Replace <app name> with the node child application name, such as AUTH, HOOKS, GRAPHQL, MCP, or SCIM.

Example:

WFGEN_IISNODE_AUTH_loggingEnabled=true
⁠iisnode Special Options

WFGEN_ENABLE_IISNODE_OPTION_<app name> - exposelogs value exposes logs via HTTP (debugging only)

⁠MCP OAuth Environment Variables (v10.3.0+)

From v10.3.0, startup writes direct OAuthServer* and Mcp* environment variables into the root wfgen\web.config appSettings, shared by /wfgen/mcp under IIS/iisnode.

MCP Server 1.0.0 requires WorkflowGen 10.4.0+. MCP OAuth browser login requires OIDC or SAML; otherwise keep OAuthServerEnabled=false.

The standard image uses /wfgen and MCP endpoint /wfgen/mcp. Do not set McpResourceUri to root /mcp; that path requires a separate no-virtual-directory deployment configuration.

Minimum MCP OAuth configuration:

OAuthServerEnabled=true
OAuthServerKeyEncryptionKey=<base64-or-base64url-32-byte-key>
OAuthServerBridgeTokenSigningSecret=<strong-random-secret>

Optional overrides:

OAuthServerAccessTokenLifetimeSeconds=3600
OAuthServerAuthorizationCodeLifetimeSeconds=600
OAuthServerRefreshTokenLifetimeSeconds=7776000
OAuthServerAllowLocalhostRedirects=true
McpResourceUri=https://<public-host>/wfgen/mcp
McpAllowedScopes=mcp:read mcp:write mcp:process_admin mcp:admin
McpDiagnosticLogLevel=INFO

Use ApplicationUrl + "/mcp" for McpResourceUri. Overrides must be absolute HTTPS URLs ending in /mcp, without query or fragment. Expose the container through HTTPS and set WFGEN_APP_SETTING_ApplicationUrl to its public HTTPS WorkflowGen URL.

The image includes the durable OAuth store and production IIS profile; no extra store or child-application setting is normally needed.

Set OAuthServerAllowLocalhostRedirects=true only when an authorized desktop or command-line client uses a loopback callback such as http://localhost, http://127.0.0.1, or http://[::1]. This setting does not allow arbitrary HTTP redirect URIs.

⁠MCP and Administration request sizes

Default limits (information only): The official 10.6.0 Beta image includes 32 MiB request limits for MCP and Administration. No size setting needs to be added. To update a standard deployment, pull the image and recreate the container with the existing volumes and environment settings; pulling alone does not update a running container.

If you previously supplied WFGEN_APP_SETTING_McpMaxInputFileSize at startup, remove it from your environment or Compose configuration: it is no longer used. If you supply custom web.config files, review their limits and MCP inheritance, and remove that retired setting there too. Valid custom limits can be retained. Encoded requests must fit the limit. Portal, GraphQL and Webhooks keep their separate size settings.

⁠Custom Connection Strings

Add custom connection strings: WFGEN_CUSTOM_CONNECTION_STRING_<name>=<connection_string>

This adds the connection string with default provider System.Data.SqlClient.

Specify custom provider:

WFGEN_CUSTOM_CONNECTION_STRING_<name>_PROVIDER_NAME=<provider_name>

Example (PostgreSQL):

WFGEN_CUSTOM_CONNECTION_STRING_MyCustomDB=Host=myserver;Port=5432;Database=mydb;Username=user;Password=pass;
WFGEN_CUSTOM_CONNECTION_STRING_MyCustomDB_PROVIDER_NAME=Npgsql
⁠Secrets Management

For Docker Secrets and Kubernetes Secrets, any environment variable can be suffixed with _FILE. Its value is a path to a file containing the real value.

Note: Variables with and without _FILE suffix are mutually exclusive.

Docker Swarm example:

# Create secrets
"84c953d4eac14da2ba93c010e85c76e0" | docker secret create ApplicationSecurityPasswordSymmetricEncryptionKey -
"Host=database;Port=5432;Database=wfgen;Username=wfgen_user;Password=secretPassword;" | docker secret create WFGEN_DATABASE_CONNECTION_STRING -
"YOUR_SERIAL_NUMBER" | docker secret create ApplicationSerialNumber -

# Create WorkflowGen service (v10 with PostgreSQL)
docker service create `
    --env WFGEN_APP_SETTING_ApplicationSecurityPasswordSymmetricEncryptionKey_FILE=C:\ProgramData\Docker\secrets\ApplicationSecurityPasswordSymmetricEncryptionKey `
    --env WFGEN_DATABASE_CONNECTION_STRING_FILE=C:\ProgramData\Docker\secrets\WFGEN_DATABASE_CONNECTION_STRING `
    --env WFGEN_DATABASE_CONNECTION_STRING_PROVIDER_NAME=Npgsql `
    --env WFGEN_APP_SETTING_ApplicationSerialNumber_FILE=C:\ProgramData\Docker\secrets\ApplicationSerialNumber `
    --secret ApplicationSecurityPasswordSymmetricEncryptionKey `
    --secret WFGEN_DATABASE_CONNECTION_STRING `
    --secret ApplicationSerialNumber `
    --mount "type=volume,src=licenses,dst=C:\wfgen\licenses,readonly" `
    advantys/workflowgen:10.5.0-win-ltsc2022

⁠Special Environment Variables

NameDescription
WFGEN_ADMIN_USERNAMEThe username for the WorkflowGen administrator account. Useful when configuring with an OpenID provider. Set to a username that exists on the provider to authenticate with administrative access. Note: If you change this, update the database as well. Default: wfgen_admin
WFGEN_DATABASE_CONNECTION_STRINGRequired. The connection string of the main database source. Container will exit with error if not present.
WFGEN_DATABASE_CONNECTION_STRING_PROVIDER_NAMERequired for PostgreSQL (v10). Database provider name. Set to Npgsql for PostgreSQL or System.Data.SqlClient for SQL Server. Default: System.Data.SqlClient
WFGEN_DATABASE_READONLY_CONNECTION_STRINGThe connection string of the readonly database source for database setups with replicas.
WFGEN_AUTH_MODEAuthentication method to be used by WorkflowGen. Possible Values: application, basic, windows, adfs, azure-v1, auth0, okta. Default: application
WFGEN_GEN_APP_SYM_ENCRYPT_KEYWhen Y, generates ApplicationSecurityPasswordSymmetricEncryptionKey only when neither an explicit key nor an existing web.config value is available. A restart preserves that value; container recreation can generate a different key. Supply a fixed key for production. Possible Values: Y, N. Default: Y
WFGEN_LICENSE_FILE_NAMELicense file name (including extension) in C:\wfgen\licenses volume. If not specified, first file found is used.
WFGEN_START_SERVICEWhat the container should run. For clusters, run multiple containers in different modes. Possible Values: win_services, web_apps, engine, dir_sync, all. Default: all
WFGEN_MACHINE_KEY_VALIDATION_KEYvalidationKey property of machineKey element in web.config. Recommended to share machine key between instances (e.g., web farm). See Microsoft docs⁠.
WFGEN_MACHINE_KEY_DECRYPTION_KEYdecryptionKey property of machineKey element in web.config. Recommended for web farms. See Microsoft docs⁠.
WFGEN_MACHINE_KEY_VALIDATION_ALGValidation algorithm for machine key. Default: HMACSHA256
WFGEN_MACHINE_KEY_DECRYPTION_ALGDecryption algorithm for machine key. Default: AES
WFGEN_DEPENDENCY_CHECK_INTERVALTime between dependency check retries in milliseconds. Default: 1000
WFGEN_DEPENDENCY_CHECK_RETRIESNumber of retries for each dependency check. Default: 10
WFGEN_DEPENDENCY_CHECK_ENABLEDEnable/disable dependency checks. Default: Y

⁠Example Configuration Using Environment File

When you have multiple environment variables, use --env-file with docker run.

Example with Azure AD authentication (v10 with PostgreSQL):

WFGEN_AUTH_MODE=azure-v1
WFGEN_APP_SETTING_ApplicationUrl=https://example.com/wfgen
WFGEN_APP_SETTING_ApplicationSecurityAuthProvider=azure-v1
WFGEN_APP_SETTING_ApplicationSecurityAuthMetadataUrl=https://login.microsoftonline.com/<Directory ID>/.well-known/openid-configuration
WFGEN_APP_SETTING_ApplicationSecurityAuthClientId=SomeClientId
WFGEN_APP_SETTING_ApplicationSecurityAuthClientSecret=SomeClientSecret
WFGEN_APP_SETTING_ApplicationSecurityAuthUsernameClaim=upn
WFGEN_APP_SETTING_ApplicationSecurityAuthAppIdClaim=appid
WFGEN_APP_SETTING_ApplicationSecurityAuthSessionTokenSigningSecret=SomethingVerySecret
WFGEN_APP_SETTING_ApplicationSecurityPasswordSymmetricEncryptionKey=84c953d4eac14da2ba93c010e85c76e0
WFGEN_DATABASE_CONNECTION_STRING=Host=database;Port=5432;Database=wfgen;Username=wfgen_user;Password=secretPassword;
WFGEN_DATABASE_CONNECTION_STRING_PROVIDER_NAME=Npgsql

For v8 and v9 environment-file examples, see the documentation for the corresponding image tag.


⁠Authentication Methods

⁠OpenID Connect Providers

Supports Azure Active Directory, Auth0, ADFS, and Okta. See WorkflowGen docs⁠ for provider configuration.

For Docker deployments:

  1. Set authentication method: WFGEN_AUTH_MODE (e.g., azure-v1, auth0, okta)
  2. Set provider: WFGEN_APP_SETTING_ApplicationSecurityAuthProvider
  3. Pass provider information via corresponding WFGEN_APP_SETTING_* environment variables
⁠Application Authentication

No special setup required. WFGEN_AUTH_MODE=application (default).

⁠Windows Integrated / Basic

Set WFGEN_AUTH_MODE=windows or basic. Requires Active Directory environment (container host must be domain joined).


⁠Volumes

Container PathDescription
C:\wfgen\dataAll WorkflowGen data including App_Data and workflow applications
C:\wfgen\licensesLicense files. Container uses first file found.

Example:

docker run ... -v C:\Path\To\Licenses:C:\wfgen\licenses ... advantys/workflowgen:10.5.0-win-ltsc2019

Note: Map all volumes to persist data. Unmapped volumes lose data when container is removed.


⁠Site Offline/Online

# Set offline
docker container exec -i wfgen powershell C:\set-state.ps1 Offline

# Set online
docker container exec -i wfgen powershell C:\set-state.ps1 Online

Customize offline page:

Place your HTML at appdata\Templates\server\offline.htm in the actual C:\wfgen\data mount. Compose prefixes volume names; do not assume a separately created wfgdata volume is used. Run from the Compose directory on the Docker host with mount access:

$offlinePath = ".\offline.htm"
$containerId = @(docker compose ps -q workflowgen)
if ($LASTEXITCODE -ne 0 -or $containerId.Count -ne 1) { throw 'Select one running WorkflowGen container.' }
$mounts = docker inspect --format '{{json .Mounts}}' $containerId[0] | ConvertFrom-Json
if ($LASTEXITCODE -ne 0) { throw 'Container inspection failed.' }
$dataMount = @($mounts | Where-Object { $_.Destination -ieq 'C:\wfgen\data' })
if ($dataMount.Count -ne 1 -or -not (Test-Path -LiteralPath $dataMount[0].Source)) { throw 'Data mount is unavailable on this host.' }
$serverTemplatePath = Join-Path $dataMount[0].Source 'appdata\Templates\server'
if (-not (Test-Path $serverTemplatePath)) {
    New-Item $serverTemplatePath -ItemType Directory -Force
}
Copy-Item $offlinePath $serverTemplatePath

⁠Default Container State

When no environment variables are supplied:

  • ApplicationUrl defaults to localhost/wfgen
  • Authentication method is applicative (handled by WorkflowGen)
  • No SSL certificate (HTTP by default)
  • Password symmetric encryption key is generated randomly
    • For production: use a fixed 32-character key via WFGEN_APP_SETTING_ApplicationSecurityPasswordSymmetricEncryptionKey

⁠Customize Files and Libraries

Use the onbuild variant to customize files in C:\inetpub\wwwroot or C:\Program Files\Advantys\WorkflowGen.

Example: Customize web.config, banner, and add custom library

File structure:

context-dir\
    inetpub\
        wwwroot\
            wfgen\
                web.config
                bin\MyCustomLib.dll
                App_Themes\Default\portal\banner\banner.htm
    Program Files\
        Advantys\WorkflowGen\Services\Bin\MyCustomLib.dll

Dockerfile:

#escape=`
FROM advantys/workflowgen:10.5.0-win-ltsc2019-onbuild

Build:

docker build -t mycorporation/workflowgen:10.5.0-win-ltsc2019 .

⁠Updates

Update by changing the version in your Dockerfile and rebuilding:

- FROM advantys/workflowgen:10.4.0-win-ltsc2019-onbuild
+ FROM advantys/workflowgen:10.5.0-win-ltsc2019-onbuild
docker build -t mycorporation/workflowgen:10.5.0-win-ltsc2019 .

⁠Support and Documentation


⁠License

By using this image, you agree to the WorkflowGen End User License Agreement. Visit workflowgen.com⁠ for details.

Tag summary

Content type

Image

Digest

sha256:2090d23d2…

Size

3.5 GB

Last updated

22 days ago

docker pull advantys/workflowgen