DemandFlow Support Centre

SUPPORTASSET: Support Asset

Customer-purchased product or asset tracked for support purposes, including hardware, software, services, and subscriptions.

Default definition. This article describes the default SUPPORTASSET 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 SUPPORTASSET.

Entity properties

Property	Value
Entity code	`SUPPORTASSET`
Display name	Support Asset
Plural	Support Assets
Level	52200

Use cases

Customer-purchased product or asset tracked for support purposes, including hardware, software, services, and subscriptions.

SUPPORTASSET represents a product or service that a customer has purchased and may raise support tickets against. Distinct from ITASSET which tracks internal IT equipment. The General panel uses a 3-column layout: left column for product identification (name, description, product type as Hardware/Software/Service/Subscription, status as Active/Inactive/Retired/Replaced with grid colours), middle column for detailed identification (serial or license number, manufacturer, model, version, quantity, unit cost), right column for customer and contract linkage via CLIENT and SUPPORTCONTRACT objectLookups plus date tracking (purchase date, warranty end with pastCheck, install date, end of life with pastCheck). The Tickets relatedlist uses stockRecord on the supportAsset field to show all SUPPORTTICKET records raised against this asset. Activity and Files panels provide standard notes timeline and document attachments.

Fields

Product Information

Field	Type	Required	Notes
`ref`	text		Asset ref.. Read only.
`name`	text	Yes	Product Name.
`description`	text (multi-line)		Description.
`productType`	enum	Yes	Valid ids: `1` (Hardware), `2` (Software), `3` (Service), `4` (Subscription).
`status`	enum	Yes	Valid ids: `1` (Active), `2` (Inactive), `3` (Retired), `4` (Replaced).

Identification

Field	Type	Notes
`serialNumber`	text	Serial / License Number.
`manufacturer`	text	Manufacturer.
`model`	text	Model.
`version`	text	Version.
`quantity`	number	Quantity.
`unitCost`	number	Unit Cost.

Customer & Contract

Field	Type	Notes
`client`	reference → `CLIENT`	Client.
`supportContract`	reference → `SUPPORTCONTRACT`	Support Contract.
`purchaseDate`	date	Purchase Date.
`warrantyEndDate`	date	Warranty End Date.
`installDate`	date	Install Date.
`endOfLifeDate`	date	End of Life Date.

Attachments and additional panels

Activity timeline panel attached.
File attachment on file. Allowed types: *.

Relationships

Lookups: client points at a CLIENT record; supportContract points at a SUPPORTCONTRACT record.
Related lists: SUPPORTTICKET via stockRecord.

Creating a Support Asset via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "SUPPORTASSET",
  "level":    52200,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "productType": 1,
  "status": 1
}

Listing Support Assets

GET /v1/entities/SUPPORTASSET/SUB

DemandFlow Support Centre

SUPPORTASSET: Support Asset

SUPPORTASSET: Support Asset

Entity properties

Use cases

Fields

Attachments and additional panels

Relationships

Creating a Support Asset via the API

Listing Support Assets

See also

Was this article helpful?