Pre-Process Scripting Requirements - Application Enabler - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Premier - Essential - Standard

Application Enabler

Platform
OnBase
Product
Application Enabler
Release
Foundation 23.1
License
Premier
Essential
Standard

The VBScript file must have the extension 'aes' (Application Enabler Script). The name itself must be the exact name of the configured screen. There is no limit to the number of Keyword Types that can be included in this script file. There is one 'aes' file per screen. The aes file should be placed in the same directory as the Application Enabler executable file. It must be saved in Unicode encoding.

Note:

When deploying Application Enabler using ClickOnce with a default configuration file, the path to the aes file must be specified in the PreProcess Scripts Location field in the Application Enabler configuration file. You can also use the PreProcess Scripts Location field to specify a shared location so multiple workstations can use the same configuration file.

The msscript.ocx file must be registered on the client workstation. Depending on your operating system, this is accomplished by running one of the following commands from the Start | Run prompt:

Regsvr32.exe c:\windows\system\msscript.ocx

or

Regsvr32.exe c:\windows\system32\msscript.ocx

Note:

For more information regarding msscript.ocx, please see the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/184739.

Note:

For 64-bit operating systems, regsvr32 must be run from the Windows\SYSWOW64 directory.

Note:

For added restrictions in DDE Scripting, see DDE Pre-Process Scripting.