Translation files often carry more than the text itself: a game script may have a column saying who is speaking, a product sheet a column with a character limit per string. Wordbee stores these as segment custom fields, and your AI post-editing and quality assurance workflows can read them. Enable one option, and every segment travels to the AI together with its custom field values, so your instructions can use them: "keep the translation within the character limit in CustomStr2".
Enabling It
In the workflow configuration (the AI Agent tab for post-editing, the AI Analysis rule for quality assurance), tick Include segment custom fields. It is off by default, and with it off, nothing changes. Machine translation workflows are not covered by this option.
Custom field values reach the AI from any source that populates them: Excel columns, XML or JSON attributes, the API, or manual entry in the Editor.
Referencing a Field in Your Instructions
The AI receives each field by its technical id: the field configured as CustomStr2 arrives as field 2. Write instructions that name the field and say what to do with its value:
-
"Field 2 contains the maximum character length. Keep the translation within it."
-
"Field 12 names the speaker. Match the register to that character."
-
"If field 5 contains |Legal|, use formal register and do not rephrase."
You can find each field's technical id in the custom fields administration (see Creating and updating Custom Fields).
What the AI Receives per Field Type
Every value arrives exactly as stored, as text. Write your instructions with the stored form in mind:
|
Field type |
What the AI receives |
|---|---|
|
Text |
The text as entered |
|
Pick list (single choice) |
The option text |
|
Pick list (multiple choice) |
The options wrapped in pipes, for example |
|
Check box |
The text "1" when ticked; nothing at all when not ticked |
|
Hyperlink |
The URL |
|
Date / date-time |
The date as stored |
|
Image |
The image's internal identifier, not the image |
Two consequences worth knowing: a check box is never "true" or "false", so write "if field 7 is present" rather than "if field 7 is true"; and a multiple-choice value keeps its pipes, so quote them when matching ("contains |Legal|").
An empty field is simply absent. An instruction referencing a field that is empty or does not exist does no harm; the run completes normally.
Who Sees What
The AI receives the custom fields that the person the workflow runs as is allowed to see: post-editing runs as the assigned worker, quality assurance as the user who launched it. A field hidden from external users is not sent when the job is assigned to an external linguist. Nothing hidden is ever sent; the only effect of restrictions is that the AI has less context, which can mean more generic output for that run.
Learn More
-
Custom Fields: What segment custom fields are and where they appear.
-
Configuring AI Workflow Parameters: All other workflow settings.