The Junction vendor portal is the vendor portal for Welocalize (https://www.welocalize.com). There is only one instance of this system running.
Use cases:
BeLazy supports integration with Junction through a comprehensive connector that enables seamless vendor workflow management. The main use cases where the Junction integration is valuable:
- You receive job offers from Welocalize through Junction and want these managed in your business management system or a tracker
- You want automatic job acceptance and delivery workflows
- You need to map your vendors to Junction workers for subcontracting
- You need to deliver projects back automatically when they are completed in your business management system or tracker, or you want to update your business management system or tracker based on manual completion of these projects in Junction
Integration type:
The Junction integration impersonates users through the Junction web interface using internal APIs. The integration supports both OKTA and Welocalize login authentication systems.
Requirements:
There are no requirements to use the Junction vendor portal other than having a valid username and password.
Expected URL format:
The URL is always https://junction.welocalize.com
Junction-specific configuration:
The Junction integration has one connector-specific configuration option:
- Automatically merge translation and copy-edit tasks into a two-step workflow: When enabled, related translation and copy-edit projects are automatically merged into cohesive workflows in your business management system.
Functionalities and connector-specific information:
- Unit of acceptance: Offer (become task after accept)
- Multiple target languages: Not supported, only through bundling
- End Client, Workflow: End client and workflow extracted from job details
- Pricing: Extracted from Junction job information, minimum fees handled
- Project exclusion: Supported
- Download files: Supported
- Delivery: Supported, if a file delivery is required in order to close the job, BeLazy uploads a one-byte file
- Manual delivery detection: Supported, delivery date is the date of the first check for delivery detection after delivery
- Linguist assignment: Supported (cannot create new workers - only mapping to existing Junction workers)
- Project bundling: Supported, also through automatically merging translation and copy-edit tasks (convenient)
- 2-factor authentication: Not required
Typical issues and how to resolve them:
- Currency and office mapping: Junction provides jobs in multiple currencies from different Welocalize offices. You need to map these offices to customers in your business management system. Since different offices can send jobs in different currencies, handle this appropriately: in XTRF select multiple price profiles for the same customer (one per currency), in Plunet and Protemos create different customers (one per currency). For Plunet, check currency settings in Contacts / Customers under the Currencies selector in Payment.
- Project bundling and workflow structure: Each workflow in Junction is single-step, except for the bundled translation and copy-edit workflow which becomes a two-step process when the automatic merging option is enabled. For tasks like LQA or LSO for the same project, we recommend using task bundling, meaning they are added under the same project in Plunet, XTRF Classic and any custom integration under a new task or item. Daily and monthly project bundling and project bundling creating one project with different language pairs are supported. Different steps such as machine translation post editing and copy-edit can be merged into one job chain in every business management system.
- Instruction mapping: All instructions are extracted from the various instruction fields in Junction, 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.