Skip to main content
WEBCON BPS
Documentation
2025 R2
  • 2025 R2
  • 2025 R1
  • 2024 R1
  • 2023 R3
  • 2023 R2
English
  • English
  • Polski
ctrlK
  • Introduction
  • Getting started
  • Designer Studio
    • Licenses
    • Main menu
    • Designer Studio Toolbar
    • Applications
    • Processes
    • Workflows
    • Actions
      • Sequence of action execution
      • OCR and scanning
      • Notifications
      • Form
      • Task assignment
      • Privileges and public access
      • Workflow control
      • Substitutions
      • Reports and printouts
      • Digital signatures and certificates
        • Sign an attachment
        • Verify attachment’s signature
      • Barcodes
      • BPS users and groups
      • Exchange
      • Active Directory
      • SharePoint content
      • SharePoint users and privileges
      • Integration
      • Attachments
      • Database retention
      • OneDrive
      • Performance indicators
      • AI
    • Automations
    • Importing and exporting applications
    • Variables
    • Business rules
    • Form rules
    • Administration tools
    • Data sources
    • System settings
    • Reports
    • SDK plugin packages
  • Portal
  • Mobile application
  • MS Office Add-Ins
  • Guides
  • Designer Studio
  • Actions
  • Digital signatures and certificates
  • Verify attachment’s signature
Version: 2025 R2

Verify attachment’s signature

The action is complementary to the Sign an attachment action.
It is used to validate digital signatures applied to the attachments of the workflow instance.
The action also verifies the certificate’s source and issuer, returns the validation results according to the configuration, and determines the behavior of the system in the event of a failed validation.

Verify attachment's signature

In the simplest scenario, when defined on the Attachments menu trigger, the action will display the result of the verification to the user.

Notification

For other triggers (those that force the instance to save, e.g. On path, Upon instance saving), there are additional configuration options that allow the verification results to be saved in specified form fields.

Config

These can be technical fields in read-only mode. The result can be saved in a Yes/No choice field, while the details and log can be placed in a Multiple lines of text field.

Fields

Once saved in appropriate fields, the result can then be used in comparisons that control the business logic.

1. Attachments to be processed​

Specify how source files are selected for the validation process, either by defining a Category, Regular expression or an SQL query.

2. Verification parameters​

The section allows you to determine the following:

  • Validation level – verification may cover the validity of the signature itself or both the signature and the trusted certificate.
  • Certificate issuer filter – limits the usable digital signatures to those issued by approved sources. The value entered here is then checked against the value in the Issuer field from the certificate’s (signature’s) properties.
  • Behavior – indicate how the system will behave after verification of the signature.
    If the Information checkbox is selected, the system will allow the workflow to progress down the path regardless of the verification result, and the verification outcome will be logged in the system. On the other hand, if the Block transition box is checked and the signature verification fails, the system will not only log the verification outcome, but also block the path and deny entry to the next step.

3. Verification results​

Form fields in which information about the outcome of the verification process is contained (the information logged in these form fields can then be used further in the workflow).

4. Variables editor​

Dynamically generated tree containing all variables that may be used in the current location of Designer Studio. Information on how to use variables in WEBCON BPS, as well as a list of variables can be found here.

Other signatures

In addition to signatures made with server certificates, it is possible for the user to apply a personal signature, or use one of the many available external tools. These methods are described in a series of community articles.

  • Personal signatures applied by the user directly on the form
  • AdobeSign
  • Autenti
  • Docusign
Previous
Sign an attachment
Next
Barcodes
  • 1. Attachments to be processed
  • 2. Verification parameters
  • 3. Verification results
  • 4. Variables editor
WEBCON is the leading European-based provider of a complete Low-code Application Platform for mass delivering business solutions. Companies choose WEBCON to dramatically reduce time and cost of app development. The platform allows them to automate and manage business processes across the entire organization – using a single, unified platform. Thanks to its unique InstantChange™ technology, WEBCON embraces change like no other platform on the market.
  • Copyright © 2025 WEBCON
Platform
  • The latest version
  • InstantChange™ Technology
  • WEBCON BPS overview
Community
  • WEBCON Community
  • Developer portal
Meet us
  • About WEBCON
  • News
  • Contact
Copyright © 2023 WEBCON

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪.

Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.