Be sure to read about the November 5, 2013, updates to this detection method!
In OnBase 13 and later we have modified Configuration to detect VBScripts that may be using the DMCoreX API. To access this, in Configuration go to the Queries menu and select VBScripts. The dialog now looks like this:
This method works because any VBScript that uses the DMCoreX API requires a Main() function to work correctly. Therefore, if we search for the string “Function Main(“ we can identify any script that is using the DMCoreX API and highlight it in the dialog.
This check is very easy to run, but does have several limitations:
[1] It is entirely possible to use the string “Function Main(“ in a VBScript that does not use the DMCoreX API, so it is possible that this will highlight some VBScripts that do not actually use the DMCoreX API.
[2] The Web Services Toolkit API does not have this requirement, so this method does nothing to identify VBScripts that may be using it.
[3] It is only available in OnBase 13 and later, so any customer who is on a prior version and wishes to upgrade directly to OnBase 15 will not be able to use it.
[4] It does nothing to find scripts or custom applications that use the DMCoreX API that are not stored in the OnBase database.
This change was made in Configuration in OnBase 13 with SCR 150910.
