Documentation Center

Configuring business units (invoicing)

The <BusinessUnits> element in the TranslationManager.xml file allows the initiator of a Translation Job to specify the organizational unit of your business that is billed for the translation. The value of a business unit is passed to SDL TMS as metadata where you need to create a Broker Script to handle it. Note that this feature is deprecated as of SDL Web 8.

About this task

The <BusinessUnits> element can contain one or more <BusinessUnit> elements. Each <BusinessUnit> element contains a String defining the name of the business unit as it appears in the Translation Job dialog.

Attributes

The <BusinessUnits> element is an optional element and has the following attributes:

AttributeMandatoryDescription
idYesthe ID of the business unit
labelNothe label name for business units in the Translation Dialog window
metadataKeyNothe metadata key that is sent to SDL TMS
mandatoryNoBoolean specifying whether entering a business unit is mandatory or optional

Procedure

  1. Open the TranslationManager.xml file in a text editor.
    By default, the file is located in your %TRIDION_HOME%\config directory.
  2. In the <BusinessUnits> section, enter for example:
    <BusinessUnits label="Business unit" metadataKey="BusinessUnit" mandatory="false">
    	<BusinessUnit id="exampleID1">Tridion France</BusinessUnit>
    	<BusinessUnit id="exampleID2">Tridion Germany</BusinessUnit>
    	<BusinessUnit id="exampleID3">Tridion France</BusinessUnit>
    	<BusinessUnit id="exampleID4">Tridion US</BusinessUnit>
    </BusinessUnits>
  3. Save and close the file.
    The Business Unit appears as a drop-down list in the General tab in the Translation Job dialog.
  4. Open SDL Translation Management System (SDL TMS).
  5. Do one of the following:
    • If you use SDL TMS 11 or newer, add an Attribute to hold the value of the business unit—in your Organization > Attributes folder, click Add Attributes.
    • If you use SDL TMS 2011 or older, add a Metadata Definition to hold the value of the business unit—in your Organization > Metadata Definitions folder, click Add Metadata Definition.
    These are ad-hoc database fields created to store organization specific data. They can be displayed on screen for completion by users or they can be hidden fields used by Broker scripts.
  6. Create a Broker Script file—a Broker stage is a System stage which runs a locally prepared script. Before you can create a Broker Stage you must have uploaded a Broker script to the Resource library.
  7. Add a Workflow Stage and create a new system stage to run a Broker script—in your Organization > Workflows > Workflow Stages folder, click Add Workflow Stage, and in the dialog that opens, do the following:
    1. Select System.
    2. Set Interface to CUSTOM.
    3. Select the Broker Script file you uploaded.
  8. Add the Workflow stage to the Workflow used in translations where invoicing requires a Business Unit to be specified.