Skip to main content

​
Secret administration

You need script-engine.admin to open Admin settings → Script Engine → Secrets. Script management alone does not allow secret administration. Create a secret with a Key Name, value, description, and scope. Choose a specific script when only that script needs the credential; Global makes it available to all scripts. At runtime, scripts obtain the value from context["secrets"] using the key name. The list returns secret metadata, not stored values. To rotate a value, edit the entry and supply its replacement. Key names are unique across the secret store, including script-scoped entries; use distinct names for distinct credentials.
Hiding values in the administration list is not a barrier against someone who can author code that receives those secrets. Treat script-authoring access as trusted integration access. Do not place secret values in source, commit messages, returned data, or log messages.
Deleting a secret removes it from future execution contexts. Review dependent scripts before deleting or changing its scope. Changing a credential here does not revoke it at the external provider.

Secret metadata shows the script scope without exposing a stored credential.

​
Inspect execution logs

With script-engine.view or a higher Script Engine permission, open Admin settings → Script Engine → Execution Logs. Filter by success/failure, user, or date interval, then apply the filters. The current type dropdown offers the Caseflow types; leave it at All when investigating event hooks or workflow actions. Use Load More for older results. Open a row to inspect the script and version IDs, type, entity ID, execution mode, user, duration, time, error, and correlation ID when present. Input and output details appear only when payload capture is available; their absence does not mean the script received no input.

An execution detail identifies the script version, caller, status, correlation ID, input, and output.

​
Diagnose by symptom

When escalating, include environment, time, script slug and executed version ID, entity ID, correlation ID if shown, and the operation that triggered it. Exclude credentials and unnecessary business data.

Introduction to Workflows

Understand how the Nobly Insight workflow engine automates document and case processes — definitions, triggers, nodes, actions, and tasks.