Communication Interfaces: Unterschied zwischen den Versionen
| Zeile 26: | Zeile 26: | ||
*[[HVS32_File_Interface_Addressdata_(Interactive)|File (Addressdata)]] | *[[HVS32_File_Interface_Addressdata_(Interactive)|File (Addressdata)]] | ||
*[[HVS32_SOAP_Interface_(Interactive)|SOAP]] | *[[HVS32_SOAP_Interface_(Interactive)|SOAP]] | ||
| + | *[[HVS32_REST_Interface_(Interactive)|REST]] | ||
*[[HVS32_JDBC_Interface_(Interactive)|JDBC]] | *[[HVS32_JDBC_Interface_(Interactive)|JDBC]] | ||
*[[HVS32_SAP_RFC_Interface_(Interactive)|SAP RFC]] | *[[HVS32_SAP_RFC_Interface_(Interactive)|SAP RFC]] | ||
Version vom 1. Februar 2022, 09:12 Uhr
HVS32 Processing-Interfaces
Please note: all descriptions are just examples. Field names, -length, format are open to customization. Due to a data evaluator, we are able to map your fields to our database structure. Except Automatic-Polling SOAP/REST - these interfaces are fixed and can not easily be customized!
Automatic-Polling
In automatic polling mode, the HVS32 dispatch system works completely in the background and is addressed by the upstream system via interface. Functions such as dispatch label printing, package cancellation, daily closing, etc. can be triggered. No user input of data is required.
The data can be transferred from the upstream system to the HVS32 via the following interfaces:
Interactive
In interactive processing, the dispatch data is entered in an entry mask of the HVS32. The dispatch data can be requested from or reported back to the previous system by various interactive Actions in the previous system.
This gives you the possibility, for example, to make a data request after scanning a delivery note, feedback after printing a label, feedback after daily closing, feedback after cancellation/release.
The following interfaces can be used to access the dispatch data of the previous system during interactive processing: