Scripting Engine Overview

Back Top Previous Next
scriptingengine

 

As this is an area that requires advanced skills, this Help File is not the appropriate place to explain this function in detail. Following is some basic information only. Contact support@happen.biz if further information is required.

 

Jim2 makes extensive use of scripting technology, providing unparalleled power to tailor to specific company and/or industry requirements.

 

As a default, the scripting engine is not available. This is to protect from potential issues with the database. This is also governed by Jim2 Security.

 

All information in this area is only relevant if on premises customers have permission to access the scripting engine. Scripts are written in DelphiScript (Pascal).

 

Scripts can easily be imported, and instantly become seamlessly integrated into Jim2.

 

Info

Note: The Scripting Engine is not accessible for Jim2.Cloud customers at any time.

 

The Scripting Engine opens in its own window, and appears as a second icon in the Windows task bar. When open, it also appears under switch windows located in the Jim2 Quick Access Toolbar.

 

scriptengswitch

 

The fully featured scripting engine supports:

Multiple script editing

Syntax highlighting

Editor code folding

Debugger break points

Editor bookmarks

Code completion (Shift+space within the code editor)

Code helper palette (available functions, variables, types, etc.)

Tool palette (form component selection, etc.)

Object inspector with properties and events editor

Form structure

Unit Code, Design and Info tabs

Debug panel with Local Variables, Watches and Call Stack

Report selection (allows execution of script against selected report within the scripting engine).

 

Library scripts

Library scripts are used for scripted Jim2 functions, such as the creation of ABA files, and for common code to be shared across multiple scripts. They can be included in scripts via the object Pascal Uses Unit syntax.

 

Server side scripting

The script and report run on the server, rather than locally on the Jim2 Client. The main advantage of this is, if a script can run server side, the associated report is available via Jim2 Mobile, including:

 

Script Name

Examples of related System Reports

Statement

CardFiles > CardFiles > Statement

Debtors > Debtors > Statement

Invoice

Invoices > Invoices > InvoiceSale

Invoices > Invoices > InvoiceSaleSimple

Invoices > Invoices > InvoiceService

Invoices > Invoices > InvoiceServiceSale

Job

Jobs > Jobs > Job Receipt

Jobs > Jobs > Job-Onsite

Job w/o Logo

Jobs > Jobs > Job

Jobs > Jobs > Manufacturing Job

Jobs > Jobs > Job No Comment

 

hmtoggle_arrow1Separating user input from report generation

 

Further information

Scripting Security

Script Editor at a Glance

Event Scripts

Menu Scripts

Importing/Exporting Scripts