Script Engine

The Script Engine runs Python logic that you attach to indexing, Caseflow forms, document events, or workflows. You manage scripts in Admin settings → Script Engine → Scripts. A script is reusable logic; a binding or a reference from a form or workflow determines where it runs.

​

Prerequisites and access

The Script Engine must be available in your environment. The client currently also requires the Caseflow area to be enabled to expose these settings. If the section is missing despite the permissions below, ask your environment administrator to check availability. Grant application permissions to the appropriate user groups in Managing permissions: These permissions govern administration. They do not replace the permissions needed to access documents or objects when a script calls Insight.

​

Choose the extension point

The engine also supports dataset and workflow-selector contracts. These are not currently offered by the client’s Scripts type selector; do not look for them in that dropdown.

​

Choose a first exercise

Begin with an input-only example before adding external API calls. That lets you distinguish a caller or binding problem from a connection or credential problem.

​

The lifecycle

1. Create the script record and choose its type.
2. Push Version to save source code and run validation. This does not make the code live.
3. Exercise the behavior in a test environment through its intended form, indexing operation, event, or workflow.
4. Publish a validated saved version, then connect it to the intended extension point.
5. Inspect execution logs and the resulting business data. Publish a corrected version or roll back when necessary.

A new saved version does not replace the published version. Production execution by binding or script slug resolves the script’s published version.

​

Where to read next