Skip to main content

Simple Case Template

This article describes the "Simple Case" setup and its associated template ("Case Summey"). It's written for admins who want a quick, non-technical reference to adapt the template for their org.

Overview​

This page helps you understand what the template does and how to use it. The template produces a simple Case summary PDF by merging fields from the Case record and a few related records (contact, account, organization). Use this guide to change which fields appear on the PDF and to test the template quickly.

Quick reference​

  • Setup name: Simple Case
  • Template name: Case Summey
  • Output file type: pdf

Download Template​

📥 Download Simple Case Template

What this template does​

The Simple Case template generates a PDF document for a Case record. It collects related data from several Data Items (Contact, Account, Case, Organization) and merges those fields into the PDF template.

Adapting this template

This is a simple example template. Update the fields shown on the PDF to match the data you have in your org — no coding required. Test with one Case record first to confirm the layout.

Data items​

The template uses a small set of related records to build the document. These are listed below with a short, non-technical description you can use when adapting the template:

  • Contact — the Case contact (name, phone, email)
  • Account — the account related to the Case (name, phone, website)
  • Case — the primary record providing fields like Case Number, Status, Subject, and Description
  • Organization — basic org information (used for header/footer details)

When adapting the template for your org, update the fields shown on the PDF to match your schema or the data available in your flows or quick actions.

Practical example (how to use)​

  1. Import the template bundle into Viewer.
  2. Make sure the Simple Case setup is active for the Case object.
  3. Check the fields you want to show on the PDF and update the template if needed.
  4. Generate a document for a Case record from the Viewer UI or an automation flow.

Example: generate a PDF for Case 5003... and check that Case details, contact info, and account name appear as expected.

Best practices​

  • Start with a single Case record for your first test to confirm layout and field mapping.
  • Only add fields to the PDF that your users need to see — simpler layouts are easier to review.
  • If a field is missing, update the template to use a different field or add the data to your record before generating.