You are here:
Client-Side and Server-Side Omnistudio Document Generation Compared
Omnistudio Document Generation provides both client-side and server-side document generation. To help you decide when to use each method, learn about their common use cases and limitations.
Comparison
Client-Side |
Server-Side |
|---|---|
Document generation is initatied by sales reps on demand in the user interface. |
Document generation occurs on a schedule or is triggered by automation. |
Best for documents with less than 200 quote lines, contract lines, rate sheet lines, and so on. |
Best for documents with lots of token processing, heavy tabulation, or more than 200 line items. |
Best for lightweight documents that don't overload web browser resources. |
Best for generating large batches of documents. |
Best for on-demand generation and point solutions. |
Best for trigger-based document generation (for example, generating documents based on a Case status change). |
Supports only specific default fonts. For more information, see Fonts for Server-Side Document Generation. |
|
Supports Customer Community Plus, Customer Community, and Partner Community users to generate documents using client-side Omniscripts. The client-side Omniscripts are: |
Supports Customer Community Plus, Customer Community, and Partner Community users to generate documents using server-side Omniscripts. The server-side Omniscript is Omnistudio Server-Side Document Generation Omniscript . |
Limitations
These limits apply for Client-Side and Server-Side document generation:
Client-Side |
Server-Side |
|---|---|
Content Version daily limit: The generated documents are stored in Salesforce Content. Each org type has a daily limit (per 24 hours) on how many .docx and .pdf documents can be generated and stored. For more information, see Content Version Limit. |
Content Version daily limit: The generated documents are stored in Salesforce Content. Each org type has a daily limit (per 24 hours) on how many .docx and .pdf documents can be generated and stored. For more information, see Content Version Limit. |
File Storage limit: The org’s file storage limit is calculated by a base allocation. It's based on your Salesforce org edition plus a per-user allocation multiplied by the number of standard licensed users in the organization. For more information, see File Storage Limit. |
File Storage limit: The org’s file storage limit is calculated by a base allocation. It's based on your Salesforce org edition plus a per-user allocation multiplied by the number of standard licensed users in the organization. For more information, see File Storage Limit. |

