From the Scripting screen in the Maintenance Client, you can administrate the use of scripting in SuperOffice CRM. Using script files, you can automate various tasks for users in Sales & Marketing.
The scripting function in SuperOffice Sales & Marketing supports two types of scripts:
Scripts can be added as
Using JavaScript
Visual Basic is the default option for scripting. A script file cannot contain both Visual Basic and JavaScript. If you want to use JavaScript, note the following:
-
You need to add the tag //Language=JavaScript at the top of the JavaScript file, so that the script function recognises the script as JavaScript.
-
The following functions are not supported in JavaScript:
-
SOApplication.SOMessagebox(text, flag); is used instead
Adding scripts
Before you can start using a script in SuperOffice Sales & Marketing, you need to add it in the Maintenance Client. To do this:
-
Copy the script (with file type .vbs or .js) that you want to use in Sales & Marketing to the ...\\so_arc\Scripts folder.
-
Open the Scripting screen.
-
Click Refresh at the bottom of the Script files list to refresh the list with scripts that have been added.
-
In the list, check the script you want to use.
-
Check Enable scripting, so that the scripts selected in the Script files list are available to SIX users.
-
If you want to verify that the script does not contain syntax errors, you can click the Validate button.
-
Click Save to save the scripting settings.
Adding personal scripts
You only have access to personal scripts if they are in your user folder (...\so_arc\username\Scripts)
, and they are only available to your user ID.
To add a personal script:
-
Copy the script (with file type .vbs or .js) that you want to use in Sales & Marketing to the ...\so_arc\username\Scripts folder.
-
Open the Scripting screen.
-
Check Enable personal scripting, so that the scripts selected in the Script files list are available to Sales & Marketing users
-
Click Save to save the scripting settings.
Travel
The scripts will automatically be copied to the traveluser during local update.