For the complete documentation index, see llms.txt. This page is also available as Markdown.

How To: Reminders and Expirations

Configuration & Use of the New S-Sign Notifications Batch Job (v12.0+)

Efficiently managing the signature lifecycle requires timely communication. S-Sign automates this through a background notification system that handles reminders and document expirations. Follow the steps below to configure and customize these notifications.

Step 1: Enable the Notifications Engine

The first step is to activate the background process that handles all automated outreach.

  1. Navigate to the S-Sign Setup page.

  2. Locate the S-Sign Configurations section.

  3. Toggle on Enable Notifications.

What happens next?

Once enabled, S-Sign schedules the "S-Sign Notifications Job" (an Apex Batch job) to run every hour. During each run, the system will:

  • Audit Active Requests: Scan all pending S-Sign envelopes.

  • Send Reminders: Dispatch emails to the current signer if they haven't signed within your specified timeframe.

  • Process Expirations: Identify requests that have passed their deadline, expire them, and notify relevant parties.

Step 2: Configure Template-Level Settings

After enabling the engine, you must define the "when" for each specific document type.

  1. Open your S-Sign PDF template and navigate to S-Sign Notification Settings.

  2. Enter values for the "Number of days" options.

The Trigger: Only S-Sign Envelope Documents generated from templates with these values populated will be processed by the hourly batch job.

Step 3: Customize Your Notification Emails

While S-Sign provides professional default templates for reminders and expirations, you can create your own to match your brand's voice and formatting requirements.

  • Build Your Own: Use the Custom S-Sign Email Notification Guide to create email templates that pull specific data from the signature process.

  • Assign the Templates: Once your custom email templates are ready, return to the S-Sign Notification Settings within your main PDF template and map them to the appropriate fields.

🏆 Pro Tip for Admins:

When assigning custom templates, use the Template Name (text) rather than the Record ID. This ensures a much smoother deployment process when moving configurations between Sandbox and Production environments.

Last updated

Was this helpful?