Transform Token Data with Context Service for Document Generation

When to Use the Transform Plug-In

Use the context service transform plug-in when you want to:

• Group related records based on business rules.
• Build parent-child hierarchies, such as bundles.
• Perform custom calculations on token data.
• Reshape token data for template consumption.

Use context filters instead when you only want to filter, sort, or limit records. See Context Filters for Document Generation.

How the Transform Plug-In Works with Document Generation

When you generate a document by using context service, it evaluates the context definition and mapping. If configured, applies the selected context filter, and fetches the token data. Document generation then calls the transform plug-in, which returns transformed token data that document generation uses to populate the template. Filters always apply before transformation. The transform plug-in runs only when the context service is the token mapping method, and document generation uses the transformed output to populate the template.

Scope, Support, and Consideration

• Use a transform plug-in only when the context service is the token mapping method.
• Associate only one transform plug-in with a document template.
• Run transform logic in Apex without modifying Salesforce data.
• Configure advanced transformations in code because the template designer UI doesn’t expose transform plug-ins.
• Account for Apex governor limits because the transform logic runs in Apex.
• Limit token payload size because large payloads can degrade performance or cause document generation to fail.
• Build all transformation logic by using token data returned by the context service because transform plug-ins don’t accept custom input parameters.
• Control document output through the template and include repeater tokens for each hierarchy level you want to render.
  

  Note Omnistudio document generation doesn’t support context service transform plug-ins.