Forms
HomeIntegrityControlSolutionsManagement Center
3.1.1 Forms
3.1.1 Forms
  • The service
    • Overview
      • Forms and IAM
      • Related products to Forms
    • About this release
      • Release notes
      • Breaking changes
    • Key components
      • Flow
        • Authenication & authorisation
      • Step
        • Layout
      • Control
        • Basic controls
          • Input
            • Properties
          • Markdown
            • Properties
          • ValuePicker
            • Properties
        • Advanced controls
          • ActiveDirectoryGroupEditGroupMember
            • Properties
          • ActiveDirectoryUserEditGroupMember
            • Properties
          • ActiveDirectorySingleSelect
            • Properties
          • Attestor
            • Properties
          • EntraGroupEditGroupMember
            • Properties
          • EntraGroupSelect
            • Properties
          • EntraUserEditGroupMember
            • Properties
          • EntraUserSelect
            • Properties
          • Selector
            • Properties
          • TextArea
            • Properties
    • Installation
      • Container
      • Linux
      • Windows
  • Modules
    • Forms
      • Properties
    • Pipes
      • Properties
      • Form valves
        • WorkOrderCreate
    • Other modules
  • ATTESTATION
    • Setup
  • User interface (UI)
    • Overview
Powered by GitBook
On this page
  • Prerequisites
  • Flow description
  • Sending data to work order
  • Accepting a work order
  • Rejecting a work order
Export as PDF
  1. ATTESTATION

Setup

This will describe how to configure a flow using attestation

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.

PreviousATTESTATIONNextOverview