CommunicatorV2

The Communicator API makes it possible to communicate to the back office using the Tensing Communicator. This API makes it possible to retrieve data which has been prepared by the Tensing Communicator. Also messages can be send to the Tensing Communicator so that it can be processed into the back office database.

APIDescription
GET api/Communicator/{id}

No documentation available.
POST api/Communicator/{id}

No documentation available.

ClientRegistration

APIDescription
POST api/RegisterClient/{id}

WebService

The WebService API makes it possible for the mobile client app to communicate with WebServices via the WebService DataSource. The WebService DataSource connects with this controller using the GET, POST, PUT and DELETE verbs, provides namespace(s) in the HTTP Headers and the controller will send the messages through and wait for the answer. This all will be done Async.

APIDescription
POST api/WebService/{id}

Send a message to a webservice and get some response back.

CommunicatorAckNack

The Communicator Ack Nack API receives acks or nacks from the client when it has processed the messages and put them in the client queue. When a Ack arrives it will contains filenames that can be deleted by the CCS. When a Nack arrives or a CancellationToken then no delete is done.

APIDescription
GET api/CommunicatorAckNack/{id}

Get prepared messaged for the engineer. It also sends a message to notify the system the engineer is still online.
POST api/CommunicatorAckNack/{id}

Submits a TensingSyncAckMessage for an engineer so the files can be deleted.

File

The FileController is used to upload files from the Mobile Client to the FMP360 Communicator.

APIDescription
POST api/File/{id}?ActivityId={ActivityId}&QuoteId={QuoteId}&AssetId={AssetId}&AssetDebriefId={AssetDebriefId}

Read all contents of multipart message and saves files on TransformInputPath folder so that communicator can pick it up.
GET api/File/{id}?FileName={FileName}