Connecting Third-party Systems
Solutions and Use Cases
With the solutions that Across offers, so-called cold and hot integrations are possible. They differ in the way how files are transferred from your source system to Across and how (if at all) the systems interact.
Type | Details |
Cold integration | Cold integrations are services that watch a so-called "hot folder" and trigger actions such as project creation, check-in, etc. when a new file is added by a third-party system to this hot folder. |
Hot integration | With a hot integration, the third-party system communicates directly with Across through crossAPI SI functions. |
Across offers the following solutions:
Solution | Type | Use cases |
crossConnect | Cold integration | Standard solution of Across for cold integrations. |
crossConnect for External Editing | Cold integration | For implementations where an external editing step outside of Across has to take place (e.g. QA or MT). |
crossAPI SI | Cold integration | Used to implement your own connector service that uses crossAPI SI for the interaction with the Across Language Server. |
crossAPI SI | Hot integration | Used for a third-party system to communicate directly with Across. |
