TANSS
Connect NetLock RMM to TANSS: alerts become tickets of the mapped company, the all-clear adds an internal comment and sets the closing status, devices can be synced as PCs or peripherals, companies can be imported.
TANSS
Requirements
The connection uses two credentials, because the TANSS API requires different credentials for different functions:
- A login of a technician, for tickets, comments and devices. Use a dedicated technician for this connection, with access to the mapped companies and without two-factor authentication: a connection cannot enter a code. A login of a customer is refused by the test.
- An API token of the external role
ERP, created in TANSS, for the list of all companies. The test checks it as well.
For the device sync, the technician also needs the rights for PCs and peripherals.
Setup
- In
Settings → Integrations, open the TANSS tile and chooseConnect. - Enter the
Instance address, theLogin name, thePasswordand theAPI token (role ERP).Allow unencrypted httpis for an instance on an internal network only. - Under options, choose the
Status when closing. TANSS does not mark a status as closing, so choose the status your tickets end in.Status of new tickets,Ticket typeandDepartmentare optional. - Map each tenant to a company, or import the companies as tenants. Tenants without a mapping are not included. Inactive companies are not offered.
- Optionally map the severities to ticket types: a TANSS ticket has no priority field.
- Activate the connection.
What goes to the vendor
For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.
With the asset sync on, also: device name, operating system, manufacturer, model, serial number, IP address and MAC address.
What happens to a ticket
- An alert becomes a ticket of the mapped company, without a remitter, assigned to the PC of the device if the asset sync linked one. The reference
NetLock-Alert-<id>is stored in the external ticket id. - When the alert ends, the ticket gets an internal comment and the closing status, if no technician is assigned. A department alone does not count as assigned.
- If TANSS refuses the status, the ticket keeps its comment and stays open, and the history says
close_refused. A missing permission still fails the job.
The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.
Asset sync
The sync is off by default. Switch on Sync devices as assets. Devices are created as PCs; a device with Server in the name of its operating system is marked as a server. To send a device class to the peripherals instead, map it to a periphery type.
Every hour NetLock sends the authorized devices of the mapped tenants that changed since the last run, at most 200 per run; if more devices changed, the next run starts right after. Synchronize now starts a run immediately.
- A device carries
NetLock-Device-<id>as inventory number, which NetLock uses to find it again. - A device with the name of an existing device of the company is linked to that device, provided that exactly one such active device exists, it has no inventory number yet and no other device holds it.
- Operating system and manufacturer are set when TANSS knows a value of exactly that name. NetLock creates no entries in these lists. All values are also written to a marked block of the remark. Text outside that block is kept.
- An update sends only name, company, inventory number, model or type, serial number, operating system, manufacturer and remark.
- An object that carries another inventory number is left alone and the device is named in the history.
- If the class of a device maps to the other kind of object later, the existing object stays and the device is named in the history. Set the mapping back, or delete the old object in TANSS to create the new one.
- A device that moved to another tenant moves to the new company.
- A device that fails is named in the history and waits for the next hourly run; the other devices are still processed.
Nothing is deleted in TANSS.
Known limits
- Components such as CPU, memory and disks are not sent, only the device itself.
- IP and MAC address go into the address list of a device only when it is created. Later changes are written only to the remark.
- A periphery is not assigned to tickets. Its model goes into
type, and it has no operating system. - TANSS has no search for the external ticket id. When a job has to be repeated, NetLock reads the tickets of the company to find out whether the ticket already exists. If it cannot read all of them, the job ends as failed without a new ticket, and you decide whether to use
Send again.
Related
DocBee
Connect NetLock RMM to DocBee: alerts become tickets of the mapped customer, the all-clear adds an internal message and sets the closing status, devices can be synced as customer objects, customers can be imported.
NEXOWARE / c-entron
Connect NetLock RMM to NEXOWARE / c-entron ERP: alerts become helpdesk tickets of the mapped customer, the all-clear adds a comment and closes the ticket, devices can be kept as customer devices, device counts go to contract items.