> For the complete documentation index, see [llms.txt](https://documentation.efalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.efalia.com/produit/efalia-process/developpeurs/ressources-developpeurs.md).

# Ressources Développeurs

Références, outils et liens utiles pour développer avec Efalia Process.

## Documentation

| Ressource                                                                                                                | Description                                  |
| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------- |
| [Vue d'Ensemble](https://documentation.efalia.com/produit/efalia-process/developpeurs.md)                                | Point de départ pour les développeurs        |
| [Documentation API REST](https://documentation.efalia.com/produit/efalia-process/developpeurs/documentation-api-rest.md) | API exposée par Efalia Process               |
| [Connecteur API REST](https://documentation.efalia.com/produit/efalia-process/developpeurs/connecteur-api-rest.md)       | Appeler des services externes depuis Process |
| [Référence STalk](https://documentation.efalia.com/produit/efalia-process/developpeurs/reference-stalk.md)               | Langage d'expression côté serveur            |
| [Référence WKYJS](https://documentation.efalia.com/produit/efalia-process/developpeurs/reference-wkyjs.md)               | Bibliothèque JavaScript côté client          |
| [JavaScript dans Process](https://documentation.efalia.com/produit/efalia-process/developpeurs/javascript-process.md)    | Scripts JS dans les formulaires              |
| [Syntaxes JSON/JSONPath](https://documentation.efalia.com/produit/efalia-process/developpeurs/syntaxes-json-jsonpath.md) | Formats de données                           |

## Groovy — Connecteur Script

Le `ScriptConnector` et le callback `callbackScript` du connecteur ApiRest utilisent **Groovy**, un langage de script compatible Java : tout code Java est valide en Groovy.

{% hint style="info" %}
Le répertoire des scripts utilisateurs est configurable via la propriété serveur `com.clog.workey.directory.scripts` (voir [Annexes Techniques](https://documentation.efalia.com/produit/efalia-process/administration/annexes-techniques.md)) — par défaut un répertoire `/scripts` sous la racine des données Efalia Process.
{% endhint %}

## Environnements de Test

{% hint style="warning" %}
Utilisez toujours un environnement de développement ou de recette pour vos tests de connecteurs et d'API. Les erreurs peuvent créer des documents parasites ou déclencher des notifications non souhaitées.
{% endhint %}

Pour aller plus loin :

* [Vue d'Ensemble des Intégrations](https://documentation.efalia.com/produit/efalia-process/integrations.md)
* [Installation](https://documentation.efalia.com/produit/efalia-process/installation.md)
* [Administration](https://documentation.efalia.com/produit/efalia-process/administration.md)


---

# 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://documentation.efalia.com/produit/efalia-process/developpeurs/ressources-developpeurs.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.
