Creating Scheduled Scripts

Scheduled Scripts are accessed from the Scheduled tab of the Scripting Center. See Scripting Switches to enable this feature.

Scheduled scripts are created in a similar same way to form scripts and follow the same Scripting Workflow. Notice that scheduled scripts have additional menu options available from the Status menu:

Run script deployment — Prompts for confirmation and on OK will add a one-time schedule event to the platform script deployment job queue.
Cancel queued runs — Prompts for confirmation and on OK will cancel any jobs queued to run for this script.

Scheduled scripts are not associated with a form and cannot access the NSOA.form functions.

To create a scheduled script:

Go to Administration > Scripting Center > Scheduled.

The scheduled script list appears.
Click the Create button and select New Scheduled script deployment.

The “New document” form appears.
Enter a Filename. You need to specify a unique filename for the script in the Dedicated Scripting Workspace. You can optionally select a document that already has the script you need otherwise an empty script file will be created. If you specify a document to upload then a new script file is created from the specified file and the original file left untouched.
If you want to import an already written script, click Choose File and select the script file.
Click Save.

The scheduled script list appears and includes your new scheduled script.
Click the name of the new script.

The script opens in the Scripting Studio.
Enter the script in the editor and change the information in the Tools and Settings form.
1. Select the user that the script will run for ‘In testing’ state, see Testing and Debugging.
2. Select any libraries referenced by this script.
3. Event is fixed as ‘Scheduled’.
4. Select the Entrance function, the name of your function to run in the editor, see Entrance Function.
5. Use the Code revision comments to comment the script changes made.
6. Click Sace.
Note:
The act of saving a script in the ”Inactive” state will move the script to the ”In testing” state, see Scripting Workflow.