> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/integration-toolkits/lltk.md).

# Lab Logic Toolkit

Lab Logic Toolkit (LLTK) provides the *evaluateDynamicExpression* script, which allows for the evaluation of simple dynamic expressions — Excel-like formulas that can be used to perform calculations. The expressions may include full Java or Groovy syntax.

Each Clarity LIMS step comprises a series of mappings that relate a single input to a single output. The script applies and evaluates the expression for each input-output-mapping in the step.

For example, the following expression sets the next step for each output sample, depending on whether the input sample has passed or failed QC:

{% code overflow="wrap" %}

```markup
-exp 'if (input.QC == true) { nextStep = ::ADVANCE:: } else { nextStep = ::ESCALATE:: }'
```

{% endcode %}

Often, the formulas are used to set the values of one or more custom fields. However, LLTK can do a great deal more than simply manipulate field values.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/clarity-lims/integration-toolkits/lltk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.