Actions208
- Activity Feed Actions
- Availability Actions
- Call Actions
- Call User Actions
- Callback Actions
- Chat Actions
- Checklist Actions
- Company Actions
- Company Category Actions
- Component Actions
- CPU Actions
- Domain Actions
- Employee Actions
- HDD Type Actions
- IP Actions
- Mail Actions
- Manufacturer Actions
- Operating System Actions
- PC Actions
- Periphery Actions
- Project Actions
- Remote Support Actions
- Search Actions
- Service Actions
- Software License Actions
- Get Software Licenses
- Create Software License
- Get Software License by ID
- Update Software License
- Delete Software License
- Get Software License Types
- Create Software License Type
- Get Software License Type
- Update Software License Type
- Delete Software License Type
- Get Expiring Licenses
- Get Software License Assignments
- Get Software License Contracts
- Copy Software License
- Get Software License Properties
- Get Software License Types Treeview
- Ticket Actions
- Ticket Content Actions
- Ticket List Actions
- Ticket State Actions
- Timestamp Actions
Remote Support → Create Device Assignment
AI-generatedSummary
The operation-scoped properties declare an apiToken (required, password-type) and a assignDeviceObject collection with optional fields deviceId (string), companyId (number), linkTypeId (number), linkId (number). The source.xml shows the node structure but the module bodies are mostly truncated with ⋮---- markers. The RemoteSupports.js file has async function handleRemoteSupports(i) but its body is not fully displayed.
Inputs
- apiToken (required) — API token obtained from the TANSS web interface (must be generated in TANSS)
- assignDeviceObject — Collection with optional fields: deviceId (string), companyId (number), linkTypeId (number), linkId (number)
Output shape
not explicitly defined in the truncated source
The source.xml provides structural overview of the TANSS node package but the actual execute/run implementation bodies are largely obscured by the
⋮----truncation pattern.