General Information on POST/PUT/DELETE actions in CubeConnect

All reading processes in CubeConnect are handeled synchronous.

All writing processes in CubeConnect are handeled asynchronous. The processing of the data is not handled within the request. For any PUT/POST/DELETE-action a transaction with transaction status is created. This transaction status can be requested at any time.

In detail:

  1. CubeConnect receives data by PUT/POST/DELETE

  2. CubeConnect checks the data for technically correctness

  3. If the data is correct, CubeConnect creates a transaction with transaction status = 2 (processing) and returns the transaction id

  4. CubeConnect answers the request with status code 202 (accepted) or 405 (invalid input)

  5. The PUT/POST/DELETE-request now is finished - but the data has not been processed yet

  6. CubeConnect now sends data to Cube ERP

  7. Cube ERP processes the data and sends the result to CubeConnect

  8. CubeConnect inserts/updates/deletes processed data 

  9. CubeConnect finishes the transaction and updates the transaction status

Transaction Status

List of transaction statuses: GET /transaction/statuses (optional parameter languageId (string(2))

Transaction statuses:

1 = pending

2 = processing (transaction just had been created, data is processing)

3 = successful

4 = partially successful

5 = error

Transaction status is part of Cube response (cubeResponseId, cubeResponseDescription). Cube response additionally provides information on failed requests as ResponseInformationText.

For every writing request CubeConnect supplies a status-controller with transaction id as parameter.