ServerScripts can now be scheduled exactly the same way as scheduled
agents. Advantages of using ServerScripts instead of agents:
1.
Automatic error handling.
This feature ensures that problematic code is detected and
notification sent to administrators.
HOW IT WORKS: A ServerScript set to scheduled mode requires a
scrip tlibrary to be selected, which contains the code to run. The
designer must create a sub called Main () in the script library. This
routine is the entry point to the code. When the ServerScript is
saved, QAF generates a corresponding agent which wraps error handling
code around the Main () subroutine. Future modifications to the
ServerScript are automatically reflected in the background agent. The
background agent need never be modified. Should any errors occur,
details are recorded in a ServerScript log document and optionally,
notification sent to Administrators.
2. ServerScript monitoring
The ServerScripts view in QAF Designer now shows scheduled
ServerScript details including:
Status (enabled / disabled)
Schedule details
Server name
Last-Run date/time
STATS string (display info such as number of docs updated)
Colour coded entries to show status 'at-a-glance'
Timer auto-refresh of ServerScript view
Right-click menu option "View Last Log"
Action buttons "Toggie Selected On/Off" and "Enable Selected" allows
quick and easy enable / disable of selected ServerScripts.
3. Intelligent transport Dev/Test to Production environment
Transporting changes to QAF workflows is a matter of copying & pasting
workflow documents / components from the source to destination. The
post-paste processing has been enhanced as follows:
If the pasted documents contain any scheduled ServerScripts, the
user is prompted to enable them. The option is given to enable all on
the same server or different servers.
The prompt "Would you like to assign new reference numbers to the
pasted documents?" now only appears to users with [QAFDesigner] role.
The messages relating to how pasted documents have been associated with the selected workflow or otherwise now only appears to users with the [QAFDesigner] role.