wxrks accepts many file formats, and some of them, such as HTML, JSON and XML, contain markup or metadata that isn't meant for translation. Instead of adjusting the parsing options by hand on every project, save them once as a named filter and let new projects use it automatically. Filters can live on the account, shared by every Organizational Unit, or on a single Organizational Unit.
💡 Who is this for? Account Admins who set up how files are parsed for the whole account or for one Organizational Unit, and Project Managers who pick a filter when creating a project.
How filters work
A filter is a saved set of parsing options for one file type, for example .json or .xml. Every filter has a Filter Name, Apply segmentation to text and a RegEx for tags; the other fields depend on the file type. See How to configure your files when creating projects for what each field does.
Filters exist at two levels:
Level | Where | Who uses it |
Account | Settings > Translation > Filter settings | Every Organizational Unit that has no default of its own for that file type, including projects created by the API and connectors. |
Organizational Unit | The same page with the unit selected in Editing, or the unit's Project section | Only that unit's projects. |
Each level has at most one default filter per file type, and wxrks picks the default like this:
If the Organizational Unit has its own default for the file type, that one is used. The unit's default always wins.
Otherwise, the account default for the file type is used.
The inheritance is live: when you edit an account filter, the next projects of every unit that uses it follow the change. Projects already created keep the parameters they were created with.
Create an account filter
Go to Settings > Translation > Filter settings. Editing shows Account default.
Click Add filter, choose the file type, fill in the filter's fields and save.
In the Account filters list, select Default on the filter to make it the account default for its file type. Used by shows how many Organizational Units use it.
Set an Organizational Unit's filters
Select the unit in Editing (or open the unit and go to Project > Filter settings). Its list shows its own filters and the account's, marked Account. The Status column tells you which one each project of the unit uses: In use · unit default, In use · account default, Overridden by unit or Available in projects.
From there you can:
Use an account filter as the unit's default. Select Default on it. The filter stays in the account, so later edits made there reach this unit too.
Change an account filter for this unit only. Account filters are read-only on a unit. Click Duplicate to this unit to get an editable copy, then edit and set the copy as the unit's default.
Create a filter just for this unit. Click Add filter.
ℹ️ Note: A unit without a default for a file type follows the account default. Units that already had their own default before account filters existed keep it.
Delete a filter
Deleting a filter doesn't change files that already used it, only future uploads. When you delete an account filter that units use, the confirmation tells you how many use it and what happens next: they switch to the account default for that file type, or, if the deleted filter was the account default, they are left without a filter for it.
Use filters when creating a project
When you upload files during project creation, wxrks applies the default filter for each file type automatically. In the files step, the filter list groups the options by origin, Organizational Unit and Account, so you can pick another filter for one project.
Related articles