Difference between revisions of "GE ConnectR Script Definition"
Jump to navigation
Jump to search
(New page: == Overview == Scripts in GE's ConnectR allow you to use VBScript and JavaScript to programatically process messages. == Known Issues == '''Deleting Scripts''' - You receive an error s...) |
John.Buckley (talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:ConnectR]] | |
== Overview == | == Overview == | ||
| − | Scripts in GE's ConnectR allow you to use VBScript and JavaScript to programatically process messages. | + | Scripts in GE's [[ConnectR]] allow you to use VBScript and JavaScript to programatically process messages. |
| − | |||
== Known Issues == | == Known Issues == | ||
'''Deleting Scripts''' - You receive an error stating that the script is in use; however, it isn't. As of v4.6.2, the stored procedure that checks whether a script is used has a bug where if the ScriptID (from dbo.ScriptDefinition) starts with the name numbers as another script that is in use, it will report a false positive that the script is in use. Let's use an example Script1 has an ID of 1. Script12 has an ID of 12. If Script1 is not in use, but Script12 is, you will not be able to delete Script1. No workarounds exist. | '''Deleting Scripts''' - You receive an error stating that the script is in use; however, it isn't. As of v4.6.2, the stored procedure that checks whether a script is used has a bug where if the ScriptID (from dbo.ScriptDefinition) starts with the name numbers as another script that is in use, it will report a false positive that the script is in use. Let's use an example Script1 has an ID of 1. Script12 has an ID of 12. If Script1 is not in use, but Script12 is, you will not be able to delete Script1. No workarounds exist. | ||
Latest revision as of 14:32, 16 November 2012
Overview
Scripts in GE's ConnectR allow you to use VBScript and JavaScript to programatically process messages.
Known Issues
Deleting Scripts - You receive an error stating that the script is in use; however, it isn't. As of v4.6.2, the stored procedure that checks whether a script is used has a bug where if the ScriptID (from dbo.ScriptDefinition) starts with the name numbers as another script that is in use, it will report a false positive that the script is in use. Let's use an example Script1 has an ID of 1. Script12 has an ID of 12. If Script1 is not in use, but Script12 is, you will not be able to delete Script1. No workarounds exist.