Centerpoint for Salesforce
Introduction
Centerpoint for Salesforce is a managed package that connects Salesforce to Doxis Doc Gen. It is installed in your Salesforce org and puts letters, documents and Smartforms on your Salesforce records, with the look and feel of Salesforce itself. This section describes that package, not SmartForms Studio or Pages.
Doc Gen is the cloud service that holds your templates, creates the documents and keeps the archive. By connecting Salesforce, other business systems and your e-signature service to Doc Gen, you can create personalized letters, messages and forms for both digital and postal distribution, and combine them with workflows into processes such as quotes, on-boarding, contracts and applications.
How it works
The package adds components to your Salesforce record pages. They send the record’s data to Doc Gen, which creates the document or Smartform and reports back to Salesforce.
Salesforce keeps the records that track the work: print orders, editor sessions, and Smartform webhook records that also hold the answers of finished forms. The documents themselves are archived in the cloud archive.
Application overview
- The package integrates Doc Gen into Salesforce as seamlessly as possible. Users find Doc Gen at their fingertips in the Salesforce user interface.
- It is context aware: it offers the right templates and Smartforms for the record the user is looking at.
- It understands the Salesforce data model and uses it through configuration. You decide which records and fields go into a document with data templates, and custom data sources are supported.
- Users interact on demand, and background business processes can send letters on a schedule or trigger with batch sending.
- Documents are stored in the Doc Gen archive. By default nothing is stored as a Salesforce File. If you want a copy of each generated PDF on the record, turn on the Generated PDF setting described in Configuration.
- The package has extensive configuration for data structures, access, document classification, the user interface and your own logic and integrations.
- For advanced cases, three Apex APIs let your own code use Doc Gen: the Editor Apex API, the Smartforms Apex API and the Workflow Apex API.
Letters
Letters can be sent on demand, with or without editing, or from a batch job.
On a record page, the Select Template card shows the templates that fit the record. Select a template and click Preview to see the PDF, Create to create and distribute the document at once, or Edit to open the letter in the editor. Three lists on the record follow the work: Documents Under Construction, Documents in Distribution and Archived Documents.
See Letters and documents and Batch sending.
Smartforms
Smartforms can be sent on demand from a Salesforce record, or started outside Salesforce and reported back.
The Smartforms card lists the forms that fit the record. Click a form, choose the participants from the record’s Contacts or from Users, choose Send SMS, Send Email or both, and click Send. Salesforce keeps each form as a reference and updates its status through webhooks. Open forms appear in Smartforms In Process, finished forms in Archived Smartforms.
See Smartforms and Smartform field mapping.
Workflow
Apex code and Flows can start a Doc Gen workflow by sending a payload to its webhook. See the Workflow Apex API.
Package version
The package available today is the Enterprise variant, which contains both the editor and Smartforms capabilities. Its namespace is mfwe, which is the prefix you use in Apex, for example mfwe.MFAPI_SmartForms. There is no separate package with only Smartforms.
In this section
Where to start
- Install and connect the package in your org.
- Open The Configuration screen and create the default settings.
- Use Letters and documents or Smartforms.