The Java applet previously used as the SCORM API adapter has been re-written using Javascript to remove the requirement that a Java runtime be installed on student systems. All previously existing functions have been duplicated so from the viewpoint of a lesson, there will be no difference in behavior.

From a WBT Manager courseware administion viewpoint there are a couple of differences and improvements.

• The API adapter is now attached to the student menu instead of the course menu. This allows a course which contains a single lesson to launch the lesson directly from the student menu without an intervening course menu. There is a new menu style flag for this (described below).
• API debug information is now displayed in a separate browser window instead of in a special pane on the course menu.

To enable menu-less launch of a lesson a "nomenu" flag has been added for use in menu styles. A script is included in this patch to add 2 new styles with this flag set. Additional styles may be created using the instructions in the WBT Manager Installation and Customization Guide. Include "nomenu=1" as a parameter to the menugen URL (e.g.; crsmenu.asp?nomenu=1&api=1).

Run the script to load the pre-defined menu styles as follows:

1. Launch the RUNSQL.EXE program from the patch directory.
2. Select the DSN connected to the WBT Manager database and log on using the same database account and password as is used for the System Administrator module.
3. Select the database\C2009121602.sql script file and click the "Execute" button.
   The script should be executed without stopping until the program displays "End Of File.". If you execute the script more than once you will see error messages beginning with "error ignored by directive". This is not a problem.

The message template files in the msgtemplates folder are being updated in this patch. If you have been using the WBT Manager External Script Interface and have customized those files you will need to copy your changes to the new versions of the files or copy the changes from the patch into your customized files. The new versions of the message templates are different in that they HTML encode any passed in parameters which are displayed by the message to prevent script encoding exploits. For example:

Before: <%=Request("errortext")%>

<P><%=StringItems.LookupValue(g_nLangOffs+185172)%> <%=Request("errortext")%></P>

After:

<P><%=StringItems.LookupValue(g_nLangOffs+185172)%> <%=Server.HTMLEncode(Request("errortext"))%></P>

Before applying this patch:

1. Copy the new versions of the msgtemplate files from web_module\standard_files\msgtemplates to a working folder.
2. Add your custom changes to the files in the working folder.

After the patch is applied copy the customized versions of the files to the msgtemplates folder on the web server.

Replaced files