Prerequisites

WorkOrder module deployed.

Create a flow used for attestation (accept/reject) using Attestor control.

Flow description

Configure last PIPE sending data to work order database and possible notifying user.

Configure one accept pipe to be executed once the work order is attested

Configure one reject pipe to be executed if order is rejected

Sending data to work order

Instead of performing updates directly, data used must be send to work-order database. Two thing are required for this:

• A PDF file used to visualise what is about to happen if accepted. Either use Html2Pdf valve for dynamic creation or use a static PDF file.

• In the last PIPE in the flow use

Accepting a work order

Once all attesters accepted the work order, accept pipe will be executed. Any flow data from order creation is present along with additional static data.

Accessing data sent from "work flow accept" is done using pattern {{request.xxx}}

Note that the accept pipe is executed in system context. No session with user data will be present.

Rejecting a work order

It only takes one attester to reject for the order to be rejected. Once rejected the reject pipe is executed. Here you can configure notification if desired.

Overview

Certain operations or flows may be deemed sensitive or require additional oversight before proceeding. This is where attestation might come in handy.

Attestation lets you define manual oversight be one ore persons before any kind of automation is performed.

Attestation is a flow and defined using built in functionality.

Attestors are notified via email, with the relevant data for verification packaged in a PDF file. Each PDF is tailored specifically for its respective flow, making the information clear, accessible, and easy to review. After a flow is successfully attested, the PDF document can be sent to an external archiving system for secure, long-term storage. This process ensures that all documentation is systematically preserved and readily available for future reference or audits.