IndySoft Project Editor

Script projects are stored system-wide in the database and can optionally include custom forms and GUI. These projects are modified through the IndySoft Project Editor. Whenever there is interface for adding a custom script (i.e. event scripts, equipment scripts, template scripts, etc.) you will note there are 2 types of scripts:

Script Types (click to expand/collapse)

Script-only means there is a single script that comprises the custom rule - this was the only type of scripting available in IndySoft prior to version 9. Custom rules that are 'project'-based simply point to a project name. This project can be used across multiple trigger actions and/or multiple events. There are 4 actions available for existing/new script projects:

| New Project
| | New script projects must be given a name that is unique system-wide in the database for the selected script type (equipment, events, templates, order system, login, task, etc.). An optional group name is allowed - this is helpful for remembering the script purpose. Script projects can be created in 3 ways:

New script projects (click to expand/collapse)

When creating a blank project, select either Pascal or Basic for the syntax of the main unit. The main unit is typically named Unit1 - this unit runs when the project is executed, so it has the responsibility of launching any extra units with dialogs, etc. Note: this setting only affects the syntax of the main unit - it is possible to have a Pascal main unit that launches a Basic unit/dialog, and vice versa. Scripts can also be cloned from a project (of the current script type) already in the database. Finally, a new script can be created from a backup of a previous project. Projects can be backed up from within the IndySoft Project Editor...File...Backup Project. | View/Edit ProjectThis option will launch the IndySoft Project Editor, which serves as an embedded development environment - complete with a debugger, watches, object inspector, code window, and many other options. Any changes to script units will be prompted for save when exiting the IndySoft Project Editor. | Delete ProjectUse this option to permanently remove a script project from the database. Important: scripts can only be deleted if they are currently being used on the current custom rule. | Restore Selected Project From BackupThis option allows a project to be restored from a prior backup (that was created from within the Project Editor...File...Backup Project option). Important: this will permanently overwrite the current script project with the version in the backup zip. |

IndySoft Project Editor Interface
The Project Editor will be familiar to any developers that have experience with RAD tools like Delphi, Visual Studio, etc. The project editor is typically only used in interaction with IndySoft technical personnel or custom consultation. Please contact IndySoft for more details. This powerful feature allows custom rules to include forms with custom functionality like edit boxes, instructions, specialized logic, and even select/edit/delete operations against the IndySoft database.

IndySoft Project Designer Dialog (click to expand/collapse)

IndySoft project scripts have access to Pascal-Library Custom Scripting Functions, VBScript-Library Custom Scripting Functions, Common IndySoft Procedures/Functions, and all script-type-specific procedures/functions. For example, and project launched from an Event Trigger Action would include Event Script Procedures/Functions, a project launched from an Equipment Trigger Action would include Equipment Script Procedures/Functions, etc.

The creation of IndySoft projects is advanced functionality typically done in consultation with IndySoft Support - please contact IndySoft for additional details. |