> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/developer-documentation/case-scripting.md). # Case Scripting Scripts that run when a case is opened, saved, or asked for a value.
Case scripting lets you attach your own JavaScript to a case, so that AgileCase runs your code at a particular moment: when the case is opened, when it is saved, or whenever a particular field's value is needed. {% hint style="info" %} If you want a script built but would rather not write it yourself, get in touch at for information and pricing. {% endhint %} ## The three kinds of script
TypeWhat it is forTarget
On Load ScriptsRun in the browser when a case is opened. Alter the case screen, surface buried data, warn the user.On Load Scripts
On Save ScriptsRun on the server when a case is saved. Send email, add tasks, update fields, call webhooks.On Save Scripts
Calculated FieldsRun on the server whenever a field's value is needed, and return it. Totals, fees and derived text that have to reach a document or a report.Calculated Fields
Where a script runs is what decides how you write it. An on load script is ordinary browser JavaScript and reads case data through the [Case Data API](/developer-documentation/case-data-api.md). On save scripts and calculated fields both run on the server with no access to the page, and reach the case through the [Service object](/developer-documentation/case-scripting/on-save-scripts/script-api-reference.md) — the difference between them is that an on save script acts on the case, while a calculated field only returns a value. {% hint style="info" %} On load and on save scripts are created under **Scripting** in the settings menu. A calculated field is not: it is a custom field type, configured on the field itself. Scripting confined to a single custom field tab is a separate feature again. For a calculation or a formatting change that only has to appear on screen while the user works, use a JavaScript label field, covered in [Custom Form Scripting](/developer-documentation/custom-form-scripting.md). {% endhint %} ## Managing scripts Creating, changing and removing scripts works the same way for on load and on save scripts. A calculated field is edited wherever its custom field is configured.
TaskWhat it coversTarget
Adding a New ScriptNaming a script, choosing when it runs, picking case types and writing the content.Adding a New Script
Editing a ScriptOpening an existing script and changing it.Editing a Script
Deleting a ScriptRemoving a script permanently.Deleting a Script
## Which case types a script applies to Every script is attached to one or more case types when you create it, so a script written for one workflow does not affect another. A script with no case types selected never runs. This is set on the scripting form and can be changed later, as described in [Editing a Script](/developer-documentation/case-scripting/editing-a-script.md).