Digital Signature

Article last updated on the 11th of November 2020.


1. Introduction

WorkPoint integrates with a range of digital signature providers; DocuSign, Adobe Sign, Visma, and Penneo.

The integration with the providers of digital signature is facilitated through Microsoft Power Automate and PowerApps. Microsoft PowerApps can be used as a fore-step before sending documents through a Power Automate Flow to the digital signature provider in order to specify the signee of the documents and provide comments for the package. This can be useful in some circumstances, however sometimes you have a certain person who always signs off on documents, in which case the PowerApp step can generally be circumvented.

Please be aware that all PowerApps and Power Automate Flows shown in this article are examples of how these can be set up. There is, as such, no one correct answer for how a PowerApp or Flow for digital signature should be set up.

2. Requirements

The use of Digital Signature integration in WorkPoint requires a specific feature license for that feature. For more information about acquiring a license for Digital Signature, please contact WorkPoint Sales at

Digital Signature utilizes an Action from the Action Management feature, but this specific action is included in the Digital Signature price, and therefore, the full Action Management feature is not necessary for Digital Signature to work.

Furthermore, Digital Signature is performed through the use of Power Apps and Power Automate, a license for these services is required. Generally, each end user which should be able to execute digital signature needs a license for the Microsoft Power platform. WorkPoint offers a solution where the Digital Signature is set up in such a way that only a single Power platform license is required, which is used for a service account. If this solution is desired, WorkPoint recommends that the configuration is set up my WorkPoint consultants, and support for the configuration is only provided by WorkPoint if set up by WorkPoint consultants.

3. Configuration

For general information about how to set up a Power Automate Flow or a PowerApp, please see this article.

   3.1. Setting up necessary columns for Digital Signature

Using Digital Signature requires that certain columns are added to the library from where the Digital Signature process is run. These are provided by WorkPoint, and can be added from existing site columns. These are:

  • Signing Status
  • Signing Type
  • Source Item Last Modified
  • Source Item URL
  • Source Item Version

Go to the library settings and add these site columns. They can be found in the "WorkPoint Site Columns" group. Note that it may be a good idea to add these site columns to the Master Site of the business module which uses Digital Signature, and the run a Master Site Synchronization to roll out the site columns to all existing and future entities. You can read more about Master site Synchronization in this article.

   3.2. Setting up an example PowerApp

In this example, we have set up a PowerApp with the following configuration:

  1. The App ID corresponds to the PowerApp created for this example. The PowerApp is shown below.
  2. The "Multiple document selection support" must be checked when using this app for digital signature.

Inside the PowerApp, in order to use WorkPoint parameters, we first need to add WorkPoint as a data source for the PowerApp:

  1. When editing the PowerApp, navigate to the "View" ribbon.
  2. Click the "Data sources" tab.

This opens a side panel which allows the user to add WorkPoint as a data source for the PowerApp. This makes it possible to use WorkPoint data in the PowerApp:

  1. In the side panel, click "Add data source".
  1. Search for "WorkPoint".
  2. Click the "WorkPoint" item from the list

WorkPoint is now added to the list of data sources:

The example app we have set up contains the following:

  1. A gallery shows the documents selected when opening the PowerApp. The following code is used to show these documents:
WorkPoint.ParameterGetPowerAppAndFlowParameter(Param("WorkPointParameterId"), "").Documents


  1. The "Needs signature" check box can be used to assert which of the documents in the list which are to be signed, and which documents are supporting documents.
  2. The "Select all" checker can be used to check or uncheck all documents for signing at once.
  3. The "Signing template" drop down menu allows the user of the PowerApp to select which signing template to use for the digital signature process. Available choices are:
  • Transaction with E-mail/NemId
  • Transaction with E-mail/websignature
  • Transaction with SMS/websignature
  • Transaction with E-mail/NemId MOCES
  1. Type in a name and an e-mail address for a signee to be added to the list of personnel who are to sign the documents.
  2. Clicking the "Add" button adds the input from the "Signee name" and "Signee e-mail address" inputs to the list of signees for the transaction. This button also clears the "Signee name" and "Signee e-mail address" text input fields, so a new signee can be entered.
  3. The "Signees" list displays all signees for the transaction. Signees are added to the list by the process outlined in pt. 13-14.
  4. The "Remove selected" button allows users of the PowerApp to select a signee from the list of signees and remove that signee from the list.
  5. The "Sign in sequence" checker can be checked if the documents should be signed in sequence by the personnel in the signees list. If this is checked, the documents will first be sent to be signed by the first signee in the signees list. Once he/she has signed the documents, they are sent to the next signee in the list, and so on.
  6. Clicking the "Send to Digital Signature" starts the digital signature process. In technical terms, the buttons starts a flow which uses the data from the PowerApp to connect to the digital signature provider, which facilitates the signing of the documents.

Using the app may in practice look something like the following:

When the "Send to Digital Signature" button is clicked, the controls of the PowerApp are disabled, as to not allow further input. This is done so that users cannot accidentally send multiple requests by clicking the "Send to Digital Signature" button multiple times. The PowerApp changes to the following look after the documents are sent:

   3.3. Setting up an example flow for Visma

The following is an example of how a flow for digital signature with Visma could look like. The entry point is a PowerApp, which could be the example PowerApp from this article.

  1. This block is used to Initialize values used in relation to the transaction (these values are hard coded)
  2. This block is used to initialize the list of signees for the transaction and set sequence number (the sequence for the signees)
  3. This step holds the signing template ID which was provided by the user in the PowerApp.
  4. This block Initializes variables and values used in relation to the documents in the transaction.
  5. This step collects information about the WorkPoint transaction including Entity and Documents.
  6. This step creates a log entry in the Signature Log in WorkPoint. It logs which signature provider is used, as well as list ID, Item ID, number of documents in transaction.
  7. This step loops through the documents selected for signing in WorkPoint. See pt. 28 for elaboration on this loop.
  8. This step calls Visma with the e-mail and password from Step 19 to get an authentication token.
  9. See pt. 32 for a description of this point.
  1. This step creates a PDF copy of the document(s). It also declares the file(s) as record. Lastly it adds the document(s) to the Signature Log. PLEASE NOTE: If declaring items as record via the flow, In-place Record Management MUST be enabled in WorkPoint. You can read more about how to do this in this article.
  2. This step collects the data contents of the newly generated PDF file
  3. This step adds the collected into a Visma document object
  4. This step adds that object to a list of Visma documents
  1. Here we send the transaction to Visma based on all previously created variables and data. It can be sent with or without a signing sequence, depending on a choice made in the PowerApp.

As part of the meta data, the transaction ID is sent along to Visma

  1. The URL address from the Callback URL from the previous flow triggers the following flow.
  2. This step gets the transaction in WorkPoint via the transaction ID that we get back from Visma.
  3. This step collects all signed documents and file contents from Visma
  4. This step completes the document transaction by collecting the new file contents from Visma and overwrite the files in WorkPoint with the signed documents. It also sets signing status as "Signed" and undeclares items as record.

   3.4. Connecting a Digital Signature flow to a PowerApp

Once a PowerApp has been set up, it can be combined with a Power Automate Flow. In this way, a button in the PowerApp can be used to start the flow which communicates with the digital signature provider.

This can be done in the following way:

  1. When editing the PowerApp, navigate to the "Action" ribbon.
  2. Click the "Flows" icon.

This opens a side panel from which connected Flows can be added to the PowerApp:

  1. Select one of the Power Automate Flows. Flows that the current user is owner of, or flows which are shared to the current user are available. In this case we select the "Start Visma Digital Signature" flow.
  2. If no flows are available, a new one can be created by clicking the "Create a new flow" button. This will take the user to the start page for Microsoft Power Automate Flow.

In the PowerApp, we can set a button to execute the flow by adding the following code to the button's OnSelect action:


The "StartVismaDigitalSignature.Run command executes the flow with the provided parameters encompassed in the parentheses.

The Switch statement in the command refers to the different signing templates which are selectable in the PowerApp. Depending on the signing template selected, one of the strings are sent along to the flow, along with a set of other parameters.

4. End User Guide

In this example, we will send three documents from the project "Design of Bike0075" for digital signature by two people; Chris Butler and Edward Dean of the company "Anderson's Custom Bikes".

We start in the documents library of the project:

  1. We select the three documents we want to send for signing.
  2. Clicking the "Send to..." button in the Command bar of the library allows us to run the PowerApp to send the documents for signing:
  1. From the selection of PowerApps we click the "Send to Visma Digital Signature" item. WorkPoint provides support for several providers of digital signature; Visma, Penneo, DocuSign, and Adobe Sign.

This opens the following PowerApp:

  1. We check the "Signature required" check boxes for the documents which must be signed by Chris Butler and Edward Dean. Whichever documents are not checked are considered supporting documents, which may be important for the signees in addition to the documents to be signed.
  2. We need the documents to be signed using NemID, so we select it from the "Signing template" drop down menu.
  3. Chris Butler is already added to the list of signees, so we input the information for Edward Dean in the "Signee name" and "Signee e-mail address" input fields.
  4. To add Edward Dean to the list of signees, we click the "Add" button.
  5. Now that the documents to be signed have been specified, and the required personnel have been added to the list of signees, we proceed by clicking the "Send to Digital Signature" button.

E-mails are now sent to Chris Butler and Edward Dean, with links to a page in Visma where they can log in and sign the documents. the content of the e-mails looks something like the following:

  1. The link can be used to go to Visma. From here, the documents can be signed.

Once all documents have been signed, an e-mail is sent to the signees:

5. Video example

The following video exemplifies how the digital signature process in WorkPoint with Visma works.

Have more questions? Submit a request