Sharepoint

Revamp Your Workflow with the memoQ Ecosystem

Discover memoQ’s extensions such as memoQWeb and Customer Portal, and enjoy seamless integration with a large number of third-party applications.

SharePoint connector  

SharePoint Connector is an add-on to memoQ TMS, provided by memoQ Business Services. SharePoint is a collaborative platform used by enterprises to create intranet pages and manage collections of documents. It is typically integrated with Microsoft 365 and Microsoft Windows. 

The memoQ-SharePoint connector can support both enterprises and language service providers: 

  • The integration can be used by enterprises to translate both their SharePoint pages and documents using their own memoQ TMS. 
  • The integration can be used by enterprises to translate both their SharePoint pages and documents using their own memoQ TMS. 

Functionalities

Translating SharePoint sites and pages (.aspx) using SharePoint’s multilingual framework.  

  • This can be done by using a dedicated web application where pages can be selected and sent for translation. 
  • It can also be done by selecting pages in SharePoint and sending them to memoQ using Power Automate. 

Translating files saved on SharePoint (documents/assets) with memoQ. All document formats supported by memoQ can be used.  

  • This can be done by configuring the connector to watch a certain folder tree for changes and automatically pick up content from that folder for translation. 
  •  It can also be done by selecting content in SharePoint and sending it to memoQ using Power Automate. 

Technical Requirements

From a technical perspective, it requires memoQ CMS API, the connector service, and the web application, which requires hosting. If you want to use Power Automate, you will need a premium account, which supports custom HTTP API calls. 

How It Works 

Sites/Pages

The connector takes advantage of the multilingual framework of SharePoint to translate pages. The framework has one default language per site, which is also the default source language. The connector creates target language folders for every page to be translated and generates a copy of the source page within. This page (so-called language copy) is later automatically overwritten by the translation. When the SharePoint user changes the language of the original page, SharePoint seamlessly switches to the newly chosen language copy. Sending the copies for translation is managed in the connector application. The connector web application lists both the available pages and their available languages. It also includes information on the status of the translation for tracking purposes, and it shows the available languages and the existing copies. 

Assets/documents 

Documents saved on SharePoint can be sent to memoQ in two ways: 

  • By watching a particular folder on SharePoint, new content will be picked up and sent to memoQ automatically. 
  • By sending individual files to memoQ using Power Automate (Premium). 

Automation 

Automation can be achieved in the connector and memoQ on several levels: 

  • A memoQ project can be created automatically if workflow automation is set up in the memoQ CMS Dashboard. As soon as new content is sent to memoQ TMS from the connector, a pre-defined memoQ project template is used to create the project. 
  • Automated actions in the memoQ project can be configured to perform certain predefined tasks in the project based on selected project events. 
  • The translated page can automatically be delivered to SharePoint as a draft. 
  • If Premium Power Automate is available in the customer’s Microsoft subscription, it is possible to set up Power Automate Flows to send content to memoQ via the connector, e.g., by selecting an item in the context menu of SharePoint. The information about the translation job will also be displayed in the user interface of the connector. 

Additional Notes 

SharePoint sites have a generic source language defined when the site is created. A newly created page is found by SharePoint as being in that generic language of the site, regardless of the actual language in which it is written. For example, a SharePoint site may have English as its default language. Even if a new page is created in French, SharePoint will identify it as English. This can be confusing, and it forces customers to create original content in the default site language. But customers sometimes prefer to create original content in a language different from the default and then translate it back into the default site source language. The connector aids this workflow by automatically organizing the pages in the right language folders. It creates a language copy to house the original non-default language content and overwrites the default site language page with the relevant back translation into the generic site language.