You are here:
Required Input and Output Parameters
Understand the input and output contract for the Context Service transform plug-in.

使用較常見的搜尋字詞。
選取較少篩選條件以擴大您的搜尋。
You are here:
Understand the input and output contract for the Context Service transform plug-in.
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, Unlimited, and Developer Editions |
Document generation passes token data automatically by using a contract.
| Input Key | Description | Required | Notes |
|---|---|---|---|
| TokenData | Context Service returns token data as a JSON string. | Yes | You can’t pass parameters, such as startTime, endTime, flags, or IDs. All logic derives from values present in the token data. |
Document generation expects the transform plug-in to return token data in a specific structure.
| Output Key | Description | Required | Notes |
|---|---|---|---|
| TokenData | Transformed token data returns as a JSON string. | Yes | If the plug-in doesn’t return a valid JSON string under the TokenData key, document generation fails. |

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.