> 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/lltk-working-with-the-script/lltk-working-with-submitted-samples.md).

# Working with Submitted Samples

For a pooled derived sample consisting of several submitted samples, Lab Logic Toolkit exposes a *submittedSamples* property that is a collection of the submitted samples represented in the well.

* *submittedSamples* returns a list of submitted samples.
* If it is not a pooled sample, it will return a list of 1.
* *submittedSample* returns an error if sample is pooled.

Use this collection to read and/or update all related submitted samples.

For example:

* To set the sample level UDF/custom field for each of the related submitted samples:

  <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">-exp 'submittedSamples.each { sample -> sample.::My Sample-Level UDF:: = 123 }'
  </code></pre>
* To sum the *Volume* UDF/custom field on all the related submitted samples into a single value written to the input analyte / derived sample:

  <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">-exp 'input.::Total Origin Sample Volume:: = submittedSamples.sum { sample -> sample.::Volume:: }'
  </code></pre>

For information on Groovy syntax and closures, see [Groovy Closures](https://groovy-lang.org/closures.html).


---

# 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/lltk-working-with-the-script/lltk-working-with-submitted-samples.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.