The Symfonie vendor portal is the vendor portal for RWS Moravia (https://www.rws.com/what-we-do/rws-moravia/). There is only one production instance of this system running. RWS Moravia uses multiple systems that provide a vendor portal, but Symfonie is by far their main platform.


Important note: We do not offer trial for Symfonie integration, because it requires the activation of APIs from a third-party. This connector is offered to users only. You can still do a trial of BeLazy with other vendor portals, and add Symfonie later.


Use cases:

BeLazy supports integration with Symfonie through a comprehensive connector that enables seamless vendor workflow management with RWS Moravia. The main use cases where the Symfonie integration is valuable:

  • You receive job offers from RWS Moravia through Symfonie and want these managed in your business management system or tracker
  • You want automatic job acceptance and delivery workflows for RWS projects
  • You need license assignment management for translation management system integration projects
  • You want to close jobs in your business management system or tracker when jobs are delivered by vendors in the translation management systems or Symfonie itself
  • You want to deliver projects back automatically when they are completed in your business management system or tracker

Integration type:

The Symfonie integration uses Symfonie's public API to connect to the RWS vendor portal system. API credentials are to be requested from RWS support.

Requirements:

RWS has moved from the Moravia Login to Microsoft Azure authentication. The Azure authentication only needs a client ID and client secret, while the legacy Moravia Login requires an additional service account. BeLazy supports both authentication methods (there is a selector when configuring the connection), but RWS is moving away from the Moravia Login.

Contact the RWS support team to obtain the necessary credentials. Make sure you refer to BeLazy in your email to speed up approval.

For full project visibility, you need BPP permission enabled for your API user in RWS Workzone. This permission allows the API user to see all projects assigned to your organization. Without BPP permission, it is possible that no projects will arrive in BeLazy.

 

Expected URL format:

The URL is always https://projects.moravia.com/
 

Symfonie-specific configuration:



To use the Symfonie vendor portal, you will need to enter the URL, user name, password that you use on the portal to add the connection. During configuration, you can select between Microsoft Azure authentication (client ID and client secret) or legacy Moravia Login (service account, client ID, and client secret).


For license assignment, you need to manually copy the license names as they appear in your Symfonie portal into BeLazy. Licenses are available for Phrase TMS, memoQ, and possibly other translation management systems. There is no API available for automatic license retrieval, and this is why manual copy-pasting is necessary. When copying license names, ensure they match exactly - avoid copying extra spaces and verify that every character is identical to what appears in the portal. In BeLazy's vendor assignment page, you will be assigning business management system users to Symfonie license names, instead of assigning to different users as in other integrations.


Functionalities and connector-specific information:

  • Unit of acceptance: Task
  • Multiple target languages: Not supported, only through bundling
  • Job types: Offers are supported and automatically displayed
  • Pricing: Extracted from Symfonie with BPP permission - includes word counts and financial information
  • Project exclusion: Not customizable, only shows offers where Symfonie State is `Order` and Lock status is `Unlocked`, and the order date is not older than one month
  • Download source and reference files: Supported
  • Delivery: Files delivery and project completion supported
  • Manual delivery detection: Supported, with delivery time being the exact time of delivery
  • License assignment: Supported for Phrase TMS, memoQ, and other translation management systems with manual license name configuration
  • Project bundling: Supported
  • 2-factor authentication: Supported via API integration
  • Translation management system integration: Licenses available for Phrase TMS, memoQ, and other supported systems
  • BPP permission: Required API permission for full project visibility - set in RWS Workzone
  • Data synchronization: All job information and project details are synchronized


Typical issues and how to resolve them:

  • Authentication setup: Choose between Microsoft Azure authentication (client ID and client secret) or legacy Moravia Login (service account, client ID, client secret). Azure authentication is recommended as RWS is moving away from Moravia Login. If you experience authentication issues, verify credentials and contact RWS support.
  • BPP permission for project visibility: Ensure BPP permission is enabled for your API user in RWS Workzone. This permission allows the API user to see all projects assigned to your organization. Without BPP permission, no projects may appear in BeLazy.
  • License assignment configuration: Manually copy license names exactly as they appear in the Symfonie portal for Phrase TMS, memoQ, and other translation management systems. Create one license per vendor and share login credentials upfront, as user details of assigned vendors cannot be retrieved automatically.
  • License management best practice: Create one license for each vendor that you will assign work to. This ensures that each vendor always knows which username and password to use when logging into their assigned translation management system.
  • API-related issues: Due to using RWS's public API, there may be temporary issues with the integration throwing red flags even when the Symfonie user interface is working normally. These issues are usually quickly resolved by RWS.
  • Project bundling and workflow structure: Each workflow in Symfonie is single-step. You can use the job bundling to turn consecutive steps such as translation, revision into one workflow in your business management system or tracker. Daily and monthly project bundling and project bundling creating one project with different language pairs are supported.
  • Instruction mapping: All instructions are extracted from the various instruction fields in Symfonie, and can be automatically reused in your customizable, client and program-specific instructions to the project managers and the vendors.
  • Synchronization: By default, the connector is synchronized every 30 minutes, but you can also synchronize immediately once an email with a new job offer comes in.



Connector-specific data extracted: See here. 


Outdated information about the partner app settings in case you are still using the Moravia Login:

You need three pieces of information for the integration to work: service account, client ID, and client secret. The RWS support team will generate the client ID and the client secret for you, while the service account should be generated by you.

First you need to create a service account in the RWS Moravia partner app. The service account needs to start with srv_ prefix (underscore included), and use an existing e-mail address (or distribution list) to receive a generated password. If you need help, you can contact the RWS support team and they will send you detailed documentation.

Second, you need to send the service account's username and password to the support team, and they will send you back an email with the client ID and the client secret. Make sure you refer to BeLazy in the email you send, because that will speed up approval. After this, please change the service account's password so that the support team has no longer access to it.


An additional requirement to receive not only the job information but also word counts and financial information about your projects is to give the service account BPP permission. This you need to do yourself in the RWS Moravia partner app. Please note that only the primary contact for an organization can do this - the primary contact is the one that is able to see and manage each and every account under their organization. If you don't know which user is the primary contact, you can contact RWS support team for help. Once you managed to log in with the primary user, select and edit the service account user (the one whose name starts with srv_), and under Profile, enable the checkbox BPP Enabled. After this, you should be able to see prices in BeLazy.