Skip to content

Fortified IDDocs

WorkOrders

Configuration reference for database-backed approvals and order execution with WorkOrders.

The WorkOrders module stores approval orders, their actors, state, and specification files. It deploys the command, query, task, and file-management components used to create, attest, retrieve, and execute orders.

The module uses JDBC for persistence, Liquibase for database migrations, and Pipes for configured accept and reject actions.

NameDescriptionDefaultMandatory
namespaceNamespace shared by the WorkOrders components and their event-bus addresses.""
db_driverFully qualified JDBC driver class name.""
jdbc.urlJDBC connection URL.""
jdbc.usernameDatabase user name.""
jdbc.passwordDatabase password.""
encryption_keySecret used to initialize encryption for protected database values.""
file_source_dirDirectory from which order specification files are read.""
file_storage_dirDirectory in which order specification files are stored.""
copy_filesKeeps the source file after storing a specification. When false, the file is moved.true
order_executionsBatch configurations for executing accepted and rejected orders.[]
order_executions[].order_typesOrder types handled by this batch configuration. An empty list matches all types.[]
order_executions[].accept_pipePipe invoked for accepted orders.""
order_executions[].reject_pipePipe invoked for rejected orders.""
order_executions[].interval_millisInterval between order-execution polls, in milliseconds.1325
order_executions[].batch_sizeMaximum number of orders processed by one configured execution batch.""

The module creates file_source_dir and file_storage_dir when they do not exist. Ensure that the server process can read and write both directories.

Order specification files are copied to storage by default. Set copy_files to false only when the source file should be removed after it has been stored.