# Attaching a script task in a process
## Attaching the ScriptCode Handler in the process
For the process to be able to call the handler, the process definition must set ***ServiceTask*** to:
* section ***Implementation***: **Topic = eximeeScriptCodeTask**
Figure 1. The 'Implementation' section in ServiceTask
* section ***Extension properties***: add a variable named **script** of **with the name of the script** as the value, which we want to invoke:
Figure 2. The 'Extension properties' section in ServiceTask
In the section ***Inputs*** we can define arguments for the handler, for an example script:
Figure 3. The 'Inputs' section in ServiceTask
In the above example, we added the variable to the handler's **testVariable** with the value **10**.
It is worth remembering that in the handler's script we have access to all global process variables using the getVariable() and getAllVariables() methods.
## Cache handling in process-handler-executor
process-handler-executor is an application that is part of the Eximee platform. It is responsible for executing script tasks. This application has a cache that helps reduce the number of requests for the content of script task artifacts, resulting in better performance.
The cache can be configured via the PROCESS\_HANDLER\_SCRIPT\_CODE\_CACHE\_TTL parameter. Its value should be set depending on how frequently artifacts are updated in a given environment. In development environments, where artifacts are frequently updated, a low value is recommended, for example '1s'; for production environments, a much higher value can be used, for example '10m'.
The cache can also be cleared on demand by making a request:
```
curl --location --request POST '
http://DOCKER_HOST/process-handler-executor/cache/invalidate'
```
