# JobBOSS Script Error: How to Diagnose It, and What Triggers and Custom Apps Are

> Source: https://netray.co/erp-help/jobboss-script-error-triggers-and-custom-apps
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

A script error in JobBOSS means custom code attached to a screen or event failed, not that the core application is broken. Note the exact message and the action that caused it, identify which custom script or trigger fired, and test the same action with scripts disabled or on a test copy. Common causes are a changed field or table, a missing reference or driver, a permissions problem, and bad data.

## Kind

error

## System

job-shop-erp

## Erp

JobBOSS / JobBOSS2 (ECI)

## Module

Scripts / Triggers / Custom apps

## Query

jobboss script error

## Alternate Queries

- jobboss2 triggers
- jobboss2 custom apps
- jobboss script error on save

## Applies To

JobBOSS and JobBOSS2 installations with custom scripts, triggers or custom apps. How these are built and where they are stored differs by version, so use ECI documentation and your integrator's records.

## Steps

### Diagnose a JobBOSS script error

**Items:**

- Write down the exact error text, the screen, the action (save, post, open, print) and the user. Take a screenshot.
- Check if it happens for every user and every record, or only for one user or one job. Record-specific errors usually mean bad data.
- Find out what changed: a JobBOSS update, a Windows or Office update, a SQL change, or a new workstation.
- Identify the script or trigger attached to that screen or event. Your integrator or ECI should have an inventory. If there is none, start one.
- Reproduce on a test copy of the database with the same version. Do not experiment in live data.
- Read the script logic for dependencies: table and field names, external files, COM or driver references, network paths and email settings.
- Fix and retest with edge cases (empty fields, large quantities, special characters), then roll out to all workstations and record the change.

## Sections

### Typical causes

**Body:**

- Schema change: an update renames or removes a field the script reads. The script worked for years and fails the day after an upgrade.
- Environment: a script calls Office, a printer, a mapped drive or a driver that exists on some workstations but not others. If the error happens on one PC, compare it with a working one.
- Data: a null value, an unexpected character or a number that is too large. Scripts often assume clean data.
- Permissions: the user cannot read a file or write to a table the script touches.

### Triggers and custom apps in JobBOSS2

**Body:**

A trigger runs custom logic when something happens in the system, such as saving a job or changing a status, for example to validate data or notify someone. A custom app extends the interface with extra screens or workflows that suit your shop.

Both are powerful, and both need discipline: version control, a test copy, documentation of what each one does, and a named owner. Prefer a trigger or custom app over editing the database, since they run through the application and its security.

Check with ECI what the supported extension model is for your edition and version.

### Preventing script errors

**Body:**

- Keep an inventory of every script and trigger with its purpose, owner and dependencies. Test them as part of any upgrade, before production.
- Write scripts to fail gracefully: check for nulls, catch errors, log them to a table or file, and show a plain message rather than a raw stack trace.

## Pitfalls

- Fixing in production without testing.
- No inventory of scripts, so nobody knows what fires when.
- Assuming it is a JobBOSS bug when custom code failed.
- Scripts that depend on a single workstation's local setup.
- Skipping script testing after an upgrade.
- Swallowing errors silently, which hides data problems.

## Ai Angle

An assistant can help read a script and the failing record: given the error text and the job, it can query the data for nulls or odd values and explain what the script expects. It does not edit or run scripts in production. Where code and data are sensitive, a model running on your own servers keeps both inside your network.

## Faq

### What causes a JobBOSS script error?

**Answer:** Usually custom code hitting a changed field, a missing driver or file, a permission problem or unexpected data, rather than a fault in the core application.

### What are JobBOSS2 triggers?

**Answer:** Custom logic that runs when something happens in the system, such as saving a record or changing a status. Confirm availability and syntax for your version with ECI.

### What are JobBOSS2 custom apps?

**Answer:** Extensions that add screens or workflows tailored to your shop, built on top of the application.

### Can I disable a script to find the fault?

**Answer:** On a test copy, yes. Avoid doing it in production, and record what you change.

## Search terms

jobboss script error, jobboss2 triggers, jobboss2 custom apps, jobboss custom script, jobboss customization, jobboss error on save, eci jobboss scripting

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json