Install & configure
Install the SuiteApp, enable the required NetSuite features, confirm the supporting SuiteApps are in place, and verify the post-deploy steps have run.
Module requirements
Required NetSuite features
- Custom Records
- Server-Side Scripting
- Token-Based Authentication (used by the external upload portal to call back into NetSuite)
- Workflow
- Accounting
- CRM
Optional features supported
- Subsidiaries (OneWorld)
- Mail Merge (the request, reminder, renewal and rejection email templates are mail-merge enabled)
- Multi-Subsidiary Customer
- Jobs
SuiteApp dependencies
Certified Documents requires three other FullClarity SuiteApps:
| Dependency | Why |
|---|---|
| Portal | Provides the external-facing upload pages, storage region/bucket configuration, and the signed-URL generator used in request emails |
| File Storage | Persists the uploaded files in your S3-backed storage. Each upload is recorded as a File Storage record linked to the Docs Submitted record |
| Code Library | Provides the FullClarity entity subtab where Required Docs and Docs Submitted appear on Vendor, Customer and Employee records |
All three install automatically when you install Certified Documents from the SuiteApp Control Centre.
Installing the SuiteApp
- In NetSuite, navigate to Customisation → SuiteApps → SuiteApp Control Centre.
- Find FullClarity Certified Documents and click Install.
- Accept the dependency prompts for Portal, File Storage and Code Library if not already installed.
- Wait for the install to complete — the post-deploy script confirms File Storage integration is wired up, and seeds the Decline Reason list with the bundled defaults.
Post-deploy verification
After install, confirm:
- The Certified Documents centre tab is visible — navigate to FullClarity → Certified Documents. You should see Certifiable Documents, Required Docs, Docs Submitted, and the Decline Reasons reference list.
- Decline Reasons are seeded. Open the Decline Reasons list — expect nine entries (three per entity type: Vendor, Customer, Employee).
- Portal storage region is configured. Certified Documents uses Portal's signed-URL generator to build upload links. If Portal isn't configured, request emails won't have working links. See the Portal section for region setup.
- Email Author is set. Confirm there's a NetSuite user designated to send the automated request, reminder, renewal and rejection emails. The default sender is configured per certifiable document type.
Email templates
Four default email templates ship with the SuiteApp:
| Template | Trigger |
|---|---|
| Default Request Email | First request when a Required Doc is created (Auto Send mode) or actioned (Manual mode) |
| Default Reminder Email | Sent on a 7-day cadence until the document is received |
| Default Renewal Email | Sent N days before expiry (default 30; configurable per document type) |
| Default Rejection Email | Sent when an internal reviewer rejects a received document |
Customise the wording by editing the templates at Documents → Templates → Email Templates and filtering to the FC CD prefix, or by creating your own templates and selecting them on individual certifiable document types.
Walkthrough
Walkthrough coming
A step-by-step Scribe walkthrough for installing and configuring Certified Documents is being recorded. Track its status in the Scribe register (internal).
What success looks like
- The Certified Documents centre tab shows under FullClarity in the top navigation.
- Vendor, Customer and Employee records have a Required Docs sublist visible on the FullClarity entity subtab.
- A test upload of a document via the external portal completes successfully — the uploaded file appears against the Docs Submitted record.
Gotchas
- Portal must be installed and configured. Installing Portal is not enough — the storage region and bucket must be set on Portal's Configuration record before upload links will work. If you install Certified Documents into an account where Portal exists but isn't configured, request emails will fire but the links will return an error.
- Token-Based Authentication is required. The external portal calls back into NetSuite via a RESTlet using token-based auth. Without the feature enabled, the upload step fails silently from the recipient's perspective.
- The default email author needs send-as-someone permissions. If the configured email-author user has been deactivated, automated emails will queue but not send. Check the user is active and has permission to send email.
- Mail Merge is optional but recommended. The bundled email templates are mail-merge enabled — without Mail Merge feature on, the template falls back to static text and won't substitute fields like the contact's name or the document description.