Integrating WebViewer, SharePoint Online, and PowerApps to create a Digital Signature Workflow
Welcome to Apryse. This guide will help you integrate a free trial of WebViewer into SharePoint Online as a web part. It will help you clone the SharePoint sample repository and show you how to integrate WebViewer as a web part. Your free trial includes unlimited trial usage and support from solution engineers.
Prerequisites
This guide expects you to have completed the SharePoint webpart integration guide found here.
SPFx: v1.21.1
WebViewer:
(Optional but recommended) Node Version Manager
Get your Apryse trial key.
For step-by-step help on setting up a SharePoint development environment, see one of the following:
Keep your license keys confidential.
License keys are uniquely generated. Please make sure that it is not publicly available (e.g. in your public GitHub).
SharePoint Webpart Environment Update
Inside the webpart, inside the environment config, you will need to update this information related to your environment.
Update TENANT_ID (https://xxxx.sharepoint.com/ where the xxxx is the TENANT_ID)
Update the SiteName to the Site of your Webpart location
Update Webviewer Sharepoint library folder location in your SharePoint env.
Update CRM_URL to the base URL of your CRM setup (https://xxxx.crm.dynamics.com)
Dataverse Integrations
We will be using Dataverse to store information regarding the Signature Signing process.
Navigate to PowerApps here
Select Tables (If not found, dropdown for Additional options on the left Navigation bar)
Create a new table and name it Signature Requests
Create the table with the following new Columns:
Column: File to Sign
Data type: File
Required: Business required
Column: Requestor
Data type: Single line of text
Format: Email
Required: Business required
Column: RequestUser
Data type: Lookup
Required: Business required
Related table: AAD User
Rename column ID to SignatureRequestID
PowerApps Integration
We will be creating a Model-driven App in PowerApps to create our Signature Workflow.
Navigate to PowerApps here
Select Create a Model-driven App from existing data
When selecting existing data, select the Dataverse table we just created
Navigate back to Dataverse to the Signature Request table
Select the Forms option to modify the Main form
Adjust the form so the fields are displayed in order:
Title
Owner
File to Sign
Requestor
Request User
PowerAutomate Integration
We will be using PowerAutomate to generate email notifications to notify users when a request is made or updated.
Navigate to PowerAutomate here
Navigate to My Flows
Create a new Cloud Flow
Set the following settings in the new Cloud Flow:
Email Notification
Connections: Microsoft Dataverse, Office 365 Outlook
Flow: When a row is added, modified or deleted
Change type: Added, Table name: Signature Requests, Scope: Organization
Flow: Send an email (V2)
To: Requestor, Subject: A signature request has been sent to you, Body:
Note: replace TenantID, SiteName, and TableID as necessary
Email Notification (Document Modified)
Connections: Microsoft Dataverse, Office 365 Outlook
Flow: When a row is added, modified or deleted
Change type: Modified, Table name: Signature Requests, Scope: Organization
Flow: Send an email (V2)
To: Requestor, Subject: Document was modified
Deployment
The App can be shared from PowerApps with a share-able hyperlink. The hyperlink can be embedded into SharePoint as well if needed.
Addtional Information
Last updated
Was this helpful?