1. Overview

The Hougaard SharePoint Connector lets you move any Business Central document into SharePoint and route it to an e-signature service. This guide walks you through the complete Adobe Sign flow—configuration, sending, tracking, and retrieving the signed PDF—so you can replace manual signing with a seamless, audit-ready process.

Requirements:
• Adobe Sign “Business” plan or higher with API access

2. Prerequisites

3. One-Time Setup

3.1 Create an API key in Adobe Sign

1. Sign in to Adobe Sign as an administrator.

2. Navigate to Account → Integrations → API Applications.

3. Click + Create → “API Application”.

4. Name it BC SharePoint Connector (or similar).

5. Under Authentication, choose User OAuth.

6. Tick User agreement read/write and Library templates.

7. Save and copy the Integration Key—you’ll paste it into Business Central.

3.2 Configure the connector in Business Central

1. Open Business Central → Search → SharePoint Connector Setup.

2. In the E-Signing FastTab, switch Adobe Sign Active to On.

3. Paste the Integration Key into API Key.

4. Press Test Connection. A green check confirms the handshake.

5. (Optional) Define a Default Adobe Sign Account Email if different from your BC user email.

6. Set the callback URL to https://businesscentral.dynamics.com/<tenantid>/<environment>?page=70319484

You’re now ready to request signatures.

4. Sending a Document for Signature

1. Navigate to the record that owns the document (e.g., Customer Card, Sales Order, Purch. Invoice).

2. In the SharePoint Attachments FactBox, select the PDF you want signed.

3. Choose Actions → E-Signing (this button appears once Adobe Sign is active).

4. Recipient window opens:

   • Primary signer pre-fills with your customer’s contact if available.

   • Click + Add Recipient for additional signers (max 10).

5. (Optional) Attach extra files—the connector merges them into a single signing package.

6. Review Email Subject/Message, then hit Send to Adobe Sign.

Tip: Use Business Central’s standard personalization to pin the E-Signing action exactly where your team expects it.

5. Tracking Signature Progress

From the same FactBox, click Check Adobe Sign Status any time to refresh.

6. Retrieving the Signed PDF

Once Adobe Sign marks the agreement Completed, the connector automatically:

1. Downloads the certified PDF.

2. Stores it in the same SharePoint folder, appending “ _signed” to the file name.

3. Creates a new record version in Business Central so you never overwrite the original.

Double-click the new file to verify the applied signature stamp and Adobe’s cryptographic seal.

7. Automating Post-Signature Workflows (Advanced)

Developers can subscribe to the SPC E-SIGNATURE COMPLETED event publisher to trigger follow-up logic, such as:

• Auto-releasing a sales order.

• Generating a posted invoice.

• Sending a confirmation email to internal teams.

8. Best Practices & Tips

• Brand your emails—edit the Adobe Sign email template to add your logo and support links.

• Bulk signing—batch-post multiple documents and trigger one Adobe Sign envelope per customer.

• Audit trail—the PDF includes a tamper-proof log; retain it for compliance.

• Time-outs—Adobe Sign links expire after 30 days by default; adjust in your Adobe admin console.

9. Troubleshooting

10. FAQ

Q: Can I use both Adobe Sign and DocuSign?
Yes—enable either or both in SharePoint Connector Setup. The E-Signing dialog lets you pick the service per transaction.

Q: Where is the data stored?
Original and signed PDFs reside in your chosen SharePoint document library; minimal metadata (agreement ID, status) is stored in Business Central tables.

Q: Does the connector support parallel or sequential signers?
Sequential only (signers receive the document in the order you enter them). Parallel routing will be added in a future release.

Q: Are reminder emails automatic?
Yes—Adobe Sign sends default reminders at day 3 and day 7. Customize intervals in your Adobe Sign account settings.