...
Create a request asking for particular documents to be uploaded
Send the request link to a user outside of Salesforce, which will provide an upload button for each requested document
Allow the user to upload one or more documents, including documents that are pre-filled in via merge fields and documents that have been signed via e-signature by the user
Approve or reject the received documents, and request another document if one is rejected
Store the user-uploaded documents in S-Drive
Create document request templates to be used over and over again
Requirements
S-Drive 2.25 or later
Formstack (for filled in documents and e-signature capability. Document upload will work without Formstack.) https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3000000B53bmEAB&tab=e
Overview
Use Case: Requesting Documents
Let’s say you run a company that provides temporary workers for other companies. You need applicants to submit several different documents to your program:
Application
Driver’s license or other ID
List of references
Resume
Sign a pre-filled background check formform with some information
With DocuFetch, you can create a Request template that has each of those items in it. You can then use the template to create a Request, and send the Request link to an applicant, asking them to upload the required documents and sign the document that needs a signature. When you receive the documents, you can take a look at them and either accept them or reject them. If rejected, you can send the request back to the applicant and ask them to try again.
When the documents are uploaded, they are stored in S-Drive for easy, organized access.
Providing Documents Requested
When the requestee receives a DocuFetch request link, they can click the link and see a page with each item that is requested. For each item they can click the corresponding button to complete the request--upload, fill in form, or e-sign.
...
| Info |
|---|
For information on how to use DocuFetch after it is configured, see DocuFetch User Guide |
Configuring DocuFetch on Salesforce
1. Add a lookup field if using a custom object
| Info |
|---|
Skip this step if you are using DocuFetch on Accounts, Cases, Contacts, or Opportunities. |
You must define a relationship between your object and DocuFetch with a lookup field on SDrive Document Intake Request:
Go to Setup
In Object Manager, find SDrive Document Intake Request object
Go to Fields and Relationships and click New
Add a Lookup field to your custom object
2. Add DocuFetch to your object Lightning page
Edit the Lightning Record Page of an object you want to use DocuFetch with. In the example, we’ll use Account.
...
Title: The heading that will show on the component. If blank, the heading will be DocuFetch Requests
File Object Prefix: For S-Drive out-of-the-box objects (Account File, Case File, Contact File, Lead File, Opportunity File) this will be cg__. For Custom object files, it will be blank
File Object Name: the S-Drive File object where DocuFetch files will be stored, such as AccountFile__c.
Parent Object Relationship Name: The API name of the lookup field from Document Request object to the object you’re relating it to. In this example, we’re using DocuFetch on Account, so the lookup field is cg__Account__r. For a custom object, it’s the name of the field you set up in step 1.
Save the settings and Go Back to the Account Page. Now you’re ready to create a Request Item.
Permissions
DocuFetch users (those who create requests) need profile permission on all DocuFetch objects as well as the S-Drive object they’re using S-Drive on.
SDrive Document Intake Requests
SDrive Document Intake Request Items
SDrive Intake Request Item Templates
SDrive Intake Request Templates
DocuFetch requests links are accessed via S-Drive Public Share. Therefore the Public Share user needs profile permission on all the above objects also.