| |
Results |
|
TeamScript not allowing rerun of the same script
|
After upgrading to 66109, this script will no longer let the user pass on the second run , unless the check box is on the screen and not read only. Once the field is shown during that transition, and not read only, it will work as expected.
|
|
|
|
Pre-transition context scripts are executed twice
|
When running a team script in pre-transition context, they will be run twice.
|
|
|
|
Who is running external commands that were issued by a Teamscript or Mashupscript?
|
External commands issued from Teamscripts are run as the IIS Worker Process owner, the user that owns the IIS services. They are NOT run by the IUSR or the user who logged in through the webinterface. This means that the scripts are
|
|
|
|
Unable to execute a command line using Ext.CmdLineWait() function
|
When using Ext.CmdLineWait() in App Script, commands are executed in the context of the Internet Information Services (IIS) application pool. If the script is called from a transition or URL, the script runs under the application pool for the TMTrack virtual directory which defaults to DefaultAppPool. If the script is called from a notification in 10.1+, it will run under the gsoap_pool.
|
|
|
|
Rnd function returns the same number each time it is called
|
The VBScript Rnd function returns the same number each time it is called within the same script even if the Randomize function is called multiple times.
|
|
|
|
DbLongToDate function doesn't put a zero in front of single digit dates...
|
1- Use the small script below: 'Get the current date in number of seconds since Jan. 1, 1970
|
|
|
|
Defect: Wrong result in DbLongToDate function (Unix)
|
Example: 1- If you use the small script below: 'Get the current date in number of seconds since Jan. 1, 1970
|
|
|
|
Using TeamScript to Call Functions in a DLL- TeamTrack 6.5 and later
|
Note: Scripts that call DLLs that were developed in TeamTrack 6.3 and earlier will not work with this new interface. You must modify your scripts to use the new interface as described below.
|
|
|
|
"Script not found" error when adding a Unix-stored TeamScript
|
When running on a non-Windows server, and opting to have TeamScripts in the file system, when a user enters the Unix path in the Windows admin, the administrator throws an error that the script cannot be found.
|
|
|
|
Electronic Signatures Fail During Quick Transitions
|
Electronic Signatures will fail when the scripts are ran against a transition marked as a "Quick Transition".
|
|
|
