> For the complete documentation index, see [llms.txt](https://docs.flightwatching.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flightwatching.com/user-manual/designer-user-manual/edit-fault-codes/ift-at-fault-code.md).

# IFT at Fault Code

create/edit the IFTs on reception of the fault code!

{% hint style="info" %}
***NOTE**: **a pre-requisite is to know javascript.***

***NOTE:  help on*** [***IFT V2.0***](/user-manual/designer-user-manual/edit-ifts/ift-v2.md)***.***
{% endhint %}

Click on *EDIT* button to change/create specific code ([IFT](/user-manual/designer-user-manual/edit-ifts/ift-v2.md)) when this fault code is received:

<figure><img src="https://4203901285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LucrvGdSn3RONbIcfqh%2Fuploads%2Fs7RqEHM3sAH0oMYHjgeP%2FScreenshot%202023-11-09%20at%2009.16.33.png?alt=media&amp;token=6e2b0ea3-7020-45aa-8ccd-37ac6877c9ba" alt="" width="563"><figcaption></figcaption></figure>

Each Fault Code could be described and it's severity could be set (it could be  different than the aircraft setting!). You can even choose to auto-dismiss fault code, so that you do not need to see it on the timeline (this is particularly useful to manage the spurious fault codes from the aircraft):

<figure><img src="https://4203901285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LucrvGdSn3RONbIcfqh%2Fuploads%2FAk8hA2WomYIq9ocdPzmy%2FScreenshot%202023-11-09%20at%2009.15.38.png?alt=media&amp;token=51b9e299-9533-40ea-8a4d-3cc3ef5df61f" alt="" width="563"><figcaption></figcaption></figure>

## write your IFT

<figure><img src="https://4203901285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LucrvGdSn3RONbIcfqh%2Fuploads%2FGyhqGe07xqJSOzqoJU7h%2FScreenshot%202023-11-09%20at%2009.20.04.png?alt=media&amp;token=1fbe18f3-0d3c-4fe4-a9ef-873af6968159" alt=""><figcaption></figcaption></figure>

The place to write your IFT is shown in the orange box at the picture above. Beside it, on the right side you have a link to the [*help V2.0*](/user-manual/designer-user-manual/edit-ifts/ift-v2.md) always available while writing your IFTs. Below the IFT box, you have a testing zone - to test your IFT before creating it. The way it works is described at [Edit IFTs](/user-manual/designer-user-manual/edit-ifts.md) section.

Example of the IFT that could be created at the reception of the Fault Code:

<figure><img src="https://4203901285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LucrvGdSn3RONbIcfqh%2Fuploads%2FBR5mp8rndPAdJFYrXmSY%2FScreenshot%202023-11-09%20at%2009.41.10.png?alt=media&amp;token=3e1f621e-39cb-4933-82ef-03112cee5753" alt="" width="563"><figcaption></figcaption></figure>

That IFT would tag a Fault Code with the OIL\_LEVEL tag and email would be sent at the reception of the fault code to an email address or delivery list (here presented as Constant - MAIL\_DL\_FWSupport). You can even test how the email would look like by clicking on *try with email-->* button situated beside the testing event.&#x20;

If you're happy with the IFT you've created - do not forget to click on *SAVE* button situated below the *TEST* button.