SALECOLL: Collateral
The SALECOLL entity: A sales collateral document (datasheet, app note, battle card, etc.) attached to a product.
Default definition. This article describes the default
SALECOLL definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches SALECOLL.Entity properties
| Property | Value |
|---|---|
| Entity code | SALECOLL |
| Display name | Collateral |
| Plural | Collateral |
| Level | 30000 |
Use cases
Child entity of PROD via comboKey (SUB|PROD). Each collateral item has a name, description, type classification, audience (external/internal), and a file attachment. Shown on the PROD editor as a relatedlist in the Collateral panel.
Fields
Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
description | text (multi-line) | Description | |
collateralType | enum | Type Valid ids: datasheet (Datasheet), appNote (Application note), techSpec (Technical specification), battleCard (Battle card), priceList (Price list), caseStudy (Case study), whitepaper (Whitepaper), brochure (Brochure), other (Other). | |
audience | enum | Audience Valid ids: external (External (customer-facing)), internal (Internal only). |
Attachments
attachments: file attachment field.
Relationships
- No declared relationships in the default definition.
Creating a Collateral via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SALECOLL",
"level": 30000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description",
"collateralType": "datasheet",
"audience": "external"
} Listing Collateral records
GET /v1/entities/SALECOLL/SUB