# Okapi Framework - Steps ## Leveraging Step
- Overview - Parameters |
Steps | Developer's Guide | Okapi Framework

If you are using an Okapi Tool after the M9 release, you should be using the wiki online help:
http://www.opentag.com/okapi/wiki/index.php?title=Leveraging_Step

## Overview

This step leverages existing translations into extracted text units.

Takes: Filter events
Sends: Filter events

This step allows you to send the text units (or the segments if the text units are segmented) to a given translation resource and get a corresponding translation, if one is available. The translation resource can be a TM engine or an MT system.

The text units that are flagged as non-translatable are skipped.

The text units that are flagged as approved (i.e. the Approved property is set to yes) are skipped.

Question: How can I use several translation resources? For example, a TM as the first resource, them an MT system for the cases where no TM match has been found.

Answer: Use several Leveraging steps on after the other in your pipeline.

## Parameters

Leverage the text units with existing translations -- Set this option to enable the step. This option allows you to keep the step in your pipeline and to set it on and off.

Translation resource -- Select a translation resource. It can be a TM or an MT engine, the list may vary based on your installation. Note that Internet-based resources may be slow and result in lengthy processing time.

Settings -- Click this button to edit the settings associated to the translation resource you have selected. Note that some translation resources have no user settings.

Leverage only if the match is equal or above this score -- Select the threshold value under which a match is not taken into account.

Fill the target with the leveraged translation -- Set this option to fill the target with the leveraged translation if a match above or equal to the specified threshold has been found.

Generate a TMX document -- Set this option to create a TMX document with all the entries for which a match has been found. A single document is created for all the input files.

Add a prefix to the source text -- Set this option to add a MT-spacific prefix to the source text. this ensure the entry will be only used as fuzzy match in tools that cannot identify the origin of the entry as MT using the `creationid` attribute..