A case script is a miniature program or macro a CaseMap user can run on demand. Case scripts are used for a variety of purposes, primarily to automate repetitive and/or complex tasks that users perform in CaseMap. Another purpose is to extend new functionality that CaseMap does not currently provide.
CaseMap scripts are stored within the CaseMap database file. This enables the scripts to be available wherever a case resides. This also makes it easy to share case scripts with other users of a case. You can have as many scripts as you want in a case. You cannot share a case script among multiple cases because it is saved in the database file. You can however save case scripts and then load them into other cases.
Previous case scripts are now merged into CaseMap as Case Tools. For more information, see About Case Tools. |
If you are using CaseMap Server and have a SQL case open, you may not have permissions granted for using case script features. If so, these features will be disabled or grayed out in the Case Scripts menu and in Tools > Options > Scripting. |
Creating case scripting is a complex task that should only be performed by individuals who are familiar with programming and ActiveX scripting. At a minimum, it requires knowledge of a supported scripting programming language. It also requires an understanding of the scripting interfaces CaseMap and other applications provide.
|
Similarities: The script code portion is relatively identical. You can do anything in a case script that you can do in a VBScript or JavaScript file. And both case scripts and file scripts are executed by the Windows Script Host. Differences: Case scripts are run within CaseMap's process space. Therefore, any case script accessing CaseMap's scripting interface will be faster than when run external to CaseMap. Each case script has global access to the CaseMap application object interface. In a case script, you can directly reference any of the CaseMap's application object properties and methods. |
Individual user access for creating, editing, and running case scripts should be controlled by your case administrator. Case scripts can be saved in two categories: My Scripts and All Users Scripts.
You can, however, make a script available to multiple users while still restricting users for some users. And you can set script access rights and options to further restrict use. For more information, see Setting case script access and options |
You can create case scripts in a replica case and have the scripts synchronize in the master case. If the script is edited in the replica it will also synchronize in the master case — as long as the same script was not modified in the master case. If the script was modified in the master case, any edits made to the script in the replica will be discarded. If you make significant changes to a case script in a replica, you should save the script to a file before synchronizing it with the master case. |
Accessing the Case Scripts pane Creating and managing case scripts Copying/loading case scripts to other cases |