For the complete documentation index, see llms.txt. This page is also available as Markdown.

Attaching a script task in the process

Attaching the ScriptCode Handler in a process

For the process to be able to invoke the handler, you need to set in the process definition ServiceTask to:

  • section Implementation: Topic = eximeeScriptCodeTask

Figure 1. The 'Implementation' section in ServiceTask
  • section Extension properties: add a variable named script of the name of the script as the value of the script we want to invoke:

Figure 2. The 'Extension properties' section in ServiceTask

In the section Inputs we can define arguments for the handler, for the example script:

Figure 3. The 'Inputs' section in ServiceTask

In the above example, we added the variable to the handler testVariable with the value 10.

Remember that in the handler 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 reduces the number of requests for script task artifact content, resulting in better performance.

The cache is configurable 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 updated frequently, 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:

Last updated

Was this helpful?