WorkOrderCreate
Creates a work order for later acceptance or dismissal. To each work order there is a pdf file containing details about the order.
Configuration
namespace
Namspace of Workorders module
default
order_type
Arbitrary type of the order. Use a-z and "_". This is used for selection later on.
N/A
display_name
Used in UI for presentation.
N/A
description
Used in UI for presentation.
N/A
body
Any data one might need for later when processing the work order. It can use both static and expanded data. See example below
N/A
properties
Meta data about the order. Example is name & description.
N/A
order_file_name
Just the name of the PDF file describing the order. Location of the order file is handled by the work orders module
N/A
attestors
Json array of identifiers that can accept or dismiss the order.
N/A
originator
Identifier who created the order.
N/A
approval_policy
Allowed value is one of: ATTESTED_ANY or ATTESTED_ALL
ATTESTED_ALL
accept_pipe
Pipe to execute on accept
N/A
reject_pipe
Pipe to execute on reject
N/A
Operational data to work order - body
Data used for the accept/reject pipe is stored in the body property. It is stored as a Json object and will be available att process time for the order.
Default data in the body is everything available in the request when calling pipes for work order creation.
Excluded data are properties starting with "__".
When creating an order the body is logged and visible if set in debug.
Custom pattern for just work order valves is fortified.flow.api.pipes
this can be used only to enable debug for work order.
Order file - order_file_name
Contains details of the order and is mandatory. Location of the file should not be a part of order_file_name. It must be located in pre configured location.
Work orders module must be enabled for valve to function:
Last updated