XTM Connect – Microsoft SharePoint is based on callbacks. A callback is information feedback from, for example, a system, after a particular task finishes. As soon as you send a request by means of XTM Connect – Microsoft SharePoint, it creates a project and sends the source file to XTM Cloud via the API. After a particular job/project finishes, XTM Cloud sends a callback to XTM Connect – Microsoft SharePoint about the finished task in XTM Cloud. Then, XTM Connect – Microsoft SharePoint will take the generated target file for each individual job, download it, and upload it to SharePoint, for each individual language.

Enabling callbacks

Prerequisite: you need to have callbacks enabled, to be able to use connection profiles in general. To enable them, contact the XTM International Support team by submitting a relevant issue request. They need to set up callback authentication in the database for your XTM Cloud instance.

Displaying callbacks

The Callbacks tab is present in your XTM Cloud instance. Log in to your environment and navigate to Configuration → Callbacks.

You see a table that shows the status of each callback sent from XTM Cloud to a third-party application (in this case, XTM Connect – Microsoft SharePoint). This enables XTM Cloud Administrators to identify communication errors between XTM Cloud and SharePoint and react accordingly.

The table displays the following information:

• Project ID: ID of a particular project in XTM Cloud.

• URL: The URL to which the callback has been sent.

• Type: Possible default callback types for SharePoint are:

  • Project finished.

  • Job finished.

  • Analysis finished.

  • Workflow transition.

• Last attempt date: Click the blue arrow icon to sort in ascending order or descending order.

• Status: Potential callback response statuses are in the following status groups:

  • Informational responses → codes 100–199.

  • Successful responses → codes 200–299.

  • Redirection messages → codes 300–399.

  • Client error responses → codes 400–499.

  • Server error responses → codes 500–599.

• Status icon: If the callback has not been able to reach its endpoint, one of the following icons will be displayed and a tooltip will provide you with information about the callback:

  • Orange warning icon: If the callback has not reached its endpoint, but can still be resent automatically, a warning tooltip will be displayed, informing you about the number of automatic resend attempts remaining.

  • Red error icon: If the callback has not reached its endpoint and cannot be resent automatically, because the maximum number of resend attempts has been reached, an error tooltip will be displayed, informing you that the maximum number of attempts has been reached.

Open

By default, if a callback does not reach its endpoint, it will be resent three times with a 5000-millisecond timeout for responses and a 60000-millisecond timeout between each failed attempt. To customize the timeout, the number of resend attempts, or the intervals between consecutive resend attempts, contact the XTM International Support team and provide the details for your request.