# Use in the process

In the process definition, we create a task of type **Service task**, which has the following pair entered as an extended property:

* **Name** - script
* **Value** - the name of the artifact containing the script code

and as **Implementation** pair:

* **Type** - External
* **Topic** - eximeeScriptCodeTask

<figure><img src="/files/8d53e1fc5e9f81b95670ae11e97ddd804e7efede" alt="" width="536"><figcaption><p><em><strong>Figure 1.</strong> "Service task" task</em></p></figcaption></figure>

This way, we attach a script task in the process, or more precisely, an artifact named - in the example above - *skarbonkaCalculateFormColor*.

We must create (or have created earlier) a script task with the appropriate name

<figure><img src="/files/31cdc0ad22ae272f65e4025387b6b0cf0afc62d2" alt=""><figcaption><p><em><strong>Figure 2.</strong> Example of a script task</em></p></figcaption></figure>

More information: [Script task](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/zadanie-skryptowe-scripttask.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-automatyczne/uzycie-w-procesie.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.