Release Notes for Xerox DocuShare Client

v.6.0.5 Build 95

- New Features and Fixes

· Improved DocuShare email listing on MS Outlook

The Outlook Client lists email messages more quickly with less memory usage. Moving or copying between DocuShare Collection objects is improved as well.

· Improved email uploading on MS Outlook

Moving or copying email from your Inbox to a collection on DocuShare occur in the background. Because Outlook is not tied up with the upload processing, you should be able to go back to other email tasks much more quickly.

Note that if you cancel the background operation, the DocuShare Client stores canceled email items in the Deleted Items folder of your default messaging store (which is typically the store folder called Mailbox). Canceled items will not be moved to Inbox if they originate there.

Note also that for performance's sake, a user is advised not to open the destination folder of email being copied or moved while the background processing is in progress. If the folder is opened (presumably to see uploaded notes showing up in the list), the DocuShare Client needs to retrieve DocuShare properties for each of uploaded mail note, and so, can cause a delay to the upload processing.

· Fixed email uploading issues

If it lacked a To recipient but had a Cc recipient, an email message did not upload. That was corrected.

If its subject line included a slash character (or any character invalid to the Windows file system in naming a file), and if it contained an attachment, an email message did not upload. That was corrected.

· SiteMinder authentication is now shared between peer processes

Previous builds did not pass credential data to a spawned process. So, if, for instance, an attachment was opened from an email message, MS Outlook could not pass siteminder authentication to the attachment process and could not open the attachment without prompting the user for a password again. This build eliminates the redundant user login.

· Supports SiteMinder card login

This prelease edition implements user authentication based on the CACLogin form. This build adds a POST to pkisso_popup2.html.

The first time it encounters a CACLogin, the Client runs a dialog. Follow the instruction(s) on the CACLogin form to complete the login (which should be a simple click on a button). The next time it needs a siteminder authentication, the Client executes login processing silently.

To clear the siteminder-related configuration, use the Clear Cache button on the Network tab in the DocuShare Client Properites dialog.

CONTENTS

=========

WHAT'S NEW

INSTALLATION

SYSTEM REQUIREMENTS

KNOWN ISSUES

SPECIFICATIONS

ADDITIONAL NOTES

WHAT'S NEW

===========

- Tight integration of DocuShare document check-in and routing with Microsoft Office 2007

- Document routing notification in Microsoft Outlook 2007

- Single installation for all DocuShare Client components with support for installing on Windows Terminal Server

- Reworked library for increased server mapping capacity

- Outlook mail integration supports Unicode and displays foreign language text

Revision 5 fixes these issues:

- The addin for PowerPoint 2007 may not save changes made to a presentation document. This is fixed.

- It is not possible to enter a property value on the Advanced tab because DocuShare Find Files squeezes the value column. This is fixed.

- DocuShare Find Files show Clear and Refresh on the context menu, but the items do nothing. The menu items are now removed.

- My DocuShare Places displays word 'Retrieving' persistently for a custom property in list view of a DocuShare collection, even though the object does not define the property. This is fixed.

- DocuShare Client icon on the system tray does not issue a file check-in announcement for an Excel file after successful check-in. This is fixed.

- A file checked out to Notepad or Wordpad remained locked after it was closed and checked into DocuShare. This is fixed. The lock is removed after the file is checked in.

- A collection could not be copied or moved to a local folder immediately after the DocuShare Client was installed. This is fixed. The new installer restarts the system.

- Earlier versions of the Outlook Client revert to the original file name when a file attachment is selected for forwarding, which may cause a recipient to mis-identify the forwarded file if the file's title has been modified since. The Client now uses the latest title for a forwarded file.

- The IE Integration in an earlier version displays the original file name for a checked out file. The window title bar of an editor application that loads the checked out file displays the original file name instead of the latest title of the file. This behavior has been changed so that a checked out file now recieves the latest title.

- The Outlook Client did not display an added mail item. This is fixed.

- The Outlook Client could not remove a shortcut folder that has become invalid because the target collection has been deleted from the DocuShare server.

- The Outlook Client startup took an excessive time if one or more shortcut folders had been created. This is fixed.

- The Mail Integration submenu is restored. 6.0.4 does not display it even though the Outlook Client is active. It should now appear on the right-click menu that is available from the DocuShare Client icon on the system task bar.

- The My DocuShare Places submenu has added the checkable menu item, 'Ask me if opening DocuShare URL.' When checked, the menu item delegates opening of a DocuShare Collection URL to My DocuShare Places, and the target collection opens in a folder window of Windows Explorer instead of in a web browser window of IE.

- A file could not be dragged and dropped to a DocuShare collection using the Outlook Client. This was fixed.

- When a column of a menu property was added to its view, My DocuShare Places displayed a selected item's index rather than the item's label for the menu property. This is fixed.

- An empty top-level collection could not be opened. This is fixed.

- PropObj now supports stretching of a property control.

- Added base support for loading DSClientAdminConfig.xml from a DocuShare server. The config file can be used to instruct the Client to use a cloned document class as the default class when it uploads a dragged file or checked in file.

- When a file is moved or copied from one collection to another on a DocuShare server, the Windows Client used to run a name conflict check. Depending on the size of the destination collection, the name check caused a long delay (a hung) and prompted some users to kill the Explorer process using Task Manager. Because of this, the default state of the name conflict check option has been changed to an off state. This version of the Windows Client, therefore, moves a file into the destination collection even if the collection contains an item with the same name. To restore the name check, use the 'For upload' checkbox on the More Gateway tab in DocuShare Client Properties. To show the More Gateway tab, click the DocuShare Client Settings menu item from the DocuShare Client icon while pressing a Shift key.

- The Outlook Client fixed a problem with the postprocessing of a move operation. After all items of a large collection were moved to another collection, Outlook hang. This is fixed.

- The Outlook Client could not move back an item just moved from one collection. It caused the server to issue an HTTP 403 Forbidden error. This is fixed.

- Bulk email upload can now be run in the background using a separate thread. The Outlook Advanced dialog in the DocuShare Client Properties dialog has added a couple of checkbox options so that email move or copy operation from an Outlook folder (e.g., Inbox) to a DocuShare collection can be run either in the background or in the foreground. By default, the foreground upload mode is selected for move operations, and the background mode is selected for copy operations. The foreground selection blocks Outlook UI and you will not be able to use Inbox and other Outlook folders while the Client completes the upload processing. It may use less system memory, however. The background selection allows the Client to run the upload processing in the background, thereby, allowing Outlook UI to function in the foreground while the mail messages are uploaded to DocuShare. A move or copy operation between two DocuShare collections is always run in the foreground, thereby, blocking Outlook UI, until the operation completes.

- The routine work folder fixes missing cleanups for obsolete schema and directory data in cache, and for uploaded email data in a backup area.

- ODMA support was not enabled for Word and PowerPoint if corresponding addins were not installed. This was fixed. If the addins are not installed, the Client now provides these apps with ODMA-based connectivity to DocuShare through the app's File Open and Save As menu interfaces.

- IStore::Reset no longer checks for disconnected server maps. It prevented maps in a store image file from getting loaded.

- The Outlook mail integration speeds up the collection listing.

- The Outlook mail integration uploads mail messages in a background thread as soon as Outlook completes passing of message data to the Client. The Client no longer blocks Outlook UI while the uploading completes.

- 6.0.4 and earlier Client copied a mail message from an MS Exchange Inbox to DocuShare with an Exchange-style email address. 6.0.5 uses an SMTP address by default if it is available from the Exchange server.

- LOCALUSERSDIR no longer adds the username to a user's Work folder path on a WTS. LOCALUSERSDIR can therefore be set to a single mapped path, e.g., 'H:\My Documents,' which applies to all users of a WTS machine. The single path actually maps to a different network share assigned to each user, so that the Client installer should not expect the presence of a subfolder specific to each user. 6.0.4 expected a user-specific subfolder like H:\My Documents\joecool if the username is joecool, and created the base work folder, 'DocuShare', in it. 6.0.5 creates the 'DocuShare' base work folder directly in the mapped based folder instead. So, for the example user, joecool, the new installer generates the work folder path as 'H:\My Documents\DocuShare,' instead of 'H:\My Documents\joecool\DocuShare.' By default, the installer uses the new logic. To always select (or unselect) the new logic, create the NoUsernameInLUD dword setting and set it to 1 (or 0), regardless of the operating system.

- This revision supports SiteMinder user authentication based on a client-side digital certificate submission (a.k.a., CACLogin). The first time it encounters a CACLogin, the Client gateway runs a dialog. Follow the instruction(s) on the CACLogin form to complete the login (which should be a simple click on a button). The next time it needs a SiteMinder authentication, the Client executes login processing silently. To clear the siteminder-related configuration, use the Clear Cache button on the Network tab in the DocuShare Client Properites dialog.

Revision 4 fixes these issues:

- Installation issues on WTS and Citrix are fixed. The issues include: the schema data could not be retrieved from a server for a non-admin user; the per-user work folder was not correctly configured for a non-admin user; and, the MS Office addins did not work for a non-admin user. Administrator must install the Remote Desktop Edition of the DocuShare Client to achieve proper Client installation for all users on a terminal server machine.

- The administrative installation UI allows an administrator to preselect installable features of the Client product, specify an alternative base work folder of all users, and create the first server map for all users of a workgroup.

- You can browse DocuShare collections in the File Open and File Save As dialogs on an MS Office application (e.g., Word and Excel) or Windows common dialog application (e.g., Wordpad and Notepad) running on an European or Japanese version of Windows without having installed a localized version of the DocuShare Client. The built-in European language support covers French, German, Spanish, Italian, and Norwegian. Note that this extended language support applies only to the DocuShare Client function of providing the file browse dialogs with browsing of DocuShare collections. It does not, however, mean that the text display of DocuShare UI elements either in the file browse dialogs or on the File menu is converted to the local language.

- MS Word and PowerPoint now works as Excel does with regard to how the File menu and the File DocuShare submenu function. For Word and PowerPoint, the menu items of File Open and File Save As are no longer affected by the Disable ODMA popup menu command of the DocuShare Client. File Open or File Save As starts the native MS Office file browse dialog regardless of the check state of Disable ODMA. That was how the menu items worked for Excel. Now the menu on the three applications works the same. Use the File DocuShare submenu to go straight to the DocuShare file browse dialog. Note that if you do not install the MS Office 2003 or 2007 addin feature of DocuShare Client, Word and PowerPoint follow the ODMA protocol, and act in the same way as any other ODMA editor application (WordPerfect) does. In this case, File Open and File Save As starts the native file browse dialog if Disable ODMA is checked, or starts the DocuShare file browse dialog if Disable ODMA is not checked.

- You can click a DocuShare check-out URL in an email note (e.g., on Outlook) to start a managed file editing session of DocuShare. The DocuShare Client will open the file using an associated editor application in a separate window. Note that the 'Handle checkout from web browser' option must be enabled for this to work. Also, there should be no IE window open prior to the URL click. The host application which shows the check-out URL may or may not use an already open IE window to display the file content.

- The SiteMinder silent login logic was enhanced to support a persisting login. After you log into SiteMinder-protected DocuShare, you remain logged in until you either log out from the server (using the Log Off menu command in My DocuShare Places), or close your Windows session. Also, if the Save credentials from web logon option of DocuShare Client is enabled, once a server map is created for a SiteMinder-protected DocuShare server, you no longer get a logon dialog from SiteMinder until you disconnect the server map. Note that this persistent login support may or may not work depending on the SiteMinder implementation. Note also that the Clear cache button can be used to clear any credentail data currently cached by the persistence support.

- If a password expiration policy is enforced on a DocuShare server, and if the password does expire when you attempt to log into the server or if the password expires while you edit and check in a file checked out from the server, the DocuShare Client correctly posts a Password Expired dialog box and requests you to type in a new password.

- The Disconnect menu command in My DocuShare Places removes all of the selected maps. The command from a previous Client release may not remove some or all of the selected maps.

- A server folder or collection folder opens without taking excessively long time. With a previous version of DocuShare Client, if many server and collection maps have been created (e.g., if you have mapped dozens), the time it takes for the clicked server or collection folder to open and display the content could be long (e.g., tens of seconds). The new version of the Client opens the folder in seconds instead of tens of seconds.

- With the 6.0.3 Client, after creating a server map, you were requested to enter the password again when you opened the server folder in My DocuShare Places, even though the Integrated Logon feature was installed and enabled. This is fixed. You no longer need to re-supply password after the server mapping.

- The Integrated Logon activity logging did not work because of an internal code change. The checkbox for the logging option is removed. It is still possible to obtain troubleshooting information regarding the Integrated Logon function. Ask DocuShare Support for instructions if that is needed.

- The Network tab of DocuShare Client Properties did not populate the dropdown list with client-side SSL certficate stores available on the machine. The dialog box only displayed certificates in the Personal certificate store. Consequently, you could not choose a certificate in a different store. This is fixed. Now, you can open other certificate stores.

- Improved DocuShare email listing on MS Outlook. The Outlook Client lists email messages more quickly.

- Fixed email uploading issues. If it lacked a To recipient but had a Cc recipient, an email message did not upload. That was corrected. If its subject line included a slash character (or any character invalid to the Windows file system in naming a file), and if it contained an attachment, an email message did not upload. That was corrected.

Revision 3 fixes these issues:

- You can now map a server with a long URL.

- You can open My DocuShare Places from the Excel 2007 Save As window.

- When using the Modified column heading and viewing objects in a container, objects modified yesterday appear in the correct category.

- Outlook integration processes no longer continue to run after closing Outlook. This problem was caused by the .NET interface of the Microsoft Outlook 2007 document routing feature. Therefore, the ability to create an Outlook task from a document approval and routing email notification has been removed from this release.

- The responsiveness of the Outlook integration feature is improved. The feature appeared to be busy due to Outlook’s method of browsing DocuShare containers and content.

- You can view HTML formatted email messages stored in DocuShare.

- Outlook 2007 does not crash after copying a collection to another collection.

- The content of email message attachments that have different file formats is intact after the message is sent to DocuShare.

Revision 2 fixes these issues:

- You can open as well as disconnect a mapped custom collection or workspace.

- Explorer does not crash when you repeatedly click the Apply button on the Permissions page.

- Uninstall correctly removes the add-in for PowerPoint 2003; re-installation of the add-in runs without errors.

- The add-in for Excel 2003 now launches.

- The add-in for Word 2003 installs to the correct location on a system running a French operating system.

- A user who did not install the PaperPort Link to DocuShare can use the application.

- Outlook does not crash when you click the Restore Defaults button in the DocuShare Properties window for a mapped server.

- On a server with custom documents, the Save DocuShare Document window displays Document as the default document type and not a custom document.

Revision 1 fixes these issues:

- Outlook mail integration uses up CPU time. (This was later found to be ineffective)

- Outlook mail integration does not support Microsoft Outlook 2007.

- Outlook mail integration does not allow proxy reconfiguration.

- The installer may not perform Client configuration for non-admin users.

- The customization option for installing to My Computer does not work.

- Unchecking the Integrated Windows Logon option removes the integration feature as well.

- The local check-in forms are not unpacked on product installation.

- A file open/save common dialog configuration tool (FDlgConf.dll) is not distributed as part of the Shell integration feature.

- Nested files are copied to a wrong collection if the destination collection is of a custom collection class.

- A worksheet with a reference to a toolbox function may not display correctly.

- Removing a collection map causes Windows Explorer to crash.

- The File Save dialog does not work on Acrobat 8.

- The File Save dialog does not work on WordPerfect X3.

- The Print to PDF command does not work on MS Office apps.

- The XML parser library leaks memory.

- The Change Access Permissions dialog does not display all User/Group names.

INSTALLATION

=============

You must be an administrator on the computer to install and remove DocuShare Client.

SYSTEM REQUIREMENTS

====================

- Microsoft Windows XP Professional with SP2 or Microsoft Windows Vista

- Microsoft Office XP with SP3, Microsoft Office 2003 with SP3, or Microsoft Office 2007

- Microsoft Outlook 2003 or 2007

- Microsoft Windows Sockets (WINSOCK) library version 1.1 or higher

- Microsoft Unified Security Package for the full secure transport support

- TCP/IP network connection to DocuShare version 5.x or higher

- Microsoft Internet Explorer version 6 or higher

- 128MB system memory

- 30MB free disk space for program files

- 64MB (minimum) free disk space on the installation drive for work-in-progress files

- Windows Script Host version 2 or higher if file link updating in HTML and Office files is needed

Required Pre-installations for the Office 2007 Add-ins

- .NET Framework 2.0

- Visual Studio 2005 Tools for Office Second Edition Runtime

- Microsoft Office 2007 Primary Interop Assemblies

KNOWN ISSUES

=============

- After copying mail or file(s) to a DocuShare collection in view, MS Outlook may show a blank list

If this display corruption happens, open your Inbox folder, and re-open the affected DocuShare collection. A correct list should be generated this time. The DocuShare Engineering is investigating into the problem.

- Moving mail with a subject in a foreign language may not work if the background move option is enabled

The Outlook Client is unable to create a backup copy of the mail if the subject line contains foreign text. Outlook will raise an error and the move operation will fail. As a workaround, turn off the background option, or use a background copy operation to upload the foreign mail to DocuShare.

- Copying mail with a CDATA keyword may not work.

The Outlook Client uses multiple CDATA-based escape sequences to encode mail data if it contains literal CDATA text. The 6.x DocuShare server however does not support it. This issue is being investigated by the DocuShare Engineering.

- After copying or moving a collection that contains objects to your local drive, you cannot delete the local folder until you restart your computer.

- In this release the Records Manager feature is disabled; the feature will be available in a future release. You can use the DocuShare Web interface to create records.

- The Save to DocuShare menu command in Excel 2007 fails to save the active workbook if a cell is in edit mode. Make sure no cell is in edit mode when invoking this command.

- In this release the Post in This Folder feature is disabled for posting messages to collections. Use of the feature can result in an error.

- After opening a mapped server or workspace in the Folder List of Outlook 2007, the right pane is blank. This is the result of an Outlook 2007 policy change that disabled the Home Page assignment feature for security purposes. To enable the feature, a change is required to the [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\Security] key in each user's Windows registry file. Contact DocuShare Customer Support for assistance.

- MS Outlook 2007 does not display file content in the preview window for some file types.

- Some files contain no content when copied from a DocuShare collection using MS Outlook 2007.

The mail integration, by default, does not download content data for files of the types not shown below.

*.txt

*.rtf

*.html

*.htm

*.xml

*.pdf

*.jpg

*.gif

*.png

*.bmp

*.doc

*.xls

*.ppt

*.vsd

*.docx

*.xlsx

*.pptx

To force the DocuShare Client to download for a file type not shown above, add the registry entry below, and append the file type specification to the list (with a semicolon separation).

[HKEY_CURRENT_USER\Software\Xerox\DocuShare Client\DSCMS\Settings]

"PreviewableFile.Extensions"=".txt;.rtf;.html;.htm;.xml;.pdf;.jpg;.gif;.png;.bmp;.doc;.xls;.ppt;.vsd;.docx;.xlsx;.pptx"

Note that the list did not includes .pdf for earlier releases of the DocuShare Client, and that with 9.0.5, the list does include .pdf. That is because the new version of Adobe Reader (version 9) includes a built-in preview support for Outlook.

- MS Outlook 2007 does not display DocuShare web view.

When a server folder is opened, the DocuShare Client is supposed to display an HTML page listing the top-level collections in the message listing pane. Also, when a DocuShare Workspace folder is opened, the listing pane should display a corresponding web view from the DocuShare server. However, on Outlook 2007, the web view display does not work.

- Cannot create shortcut to calendar in Outlook.

Creating a shortcut to a DocuShare calendar in Outlook currently does not work.

- The Send To and Address Book components are not automatically installed.

The Outlook mail integration does not pre-select the mail transport and address book features. If you need them, you must use the either Custom Installation or Maintenance screen and explicitly select the features for inclusion in the installation.

-Windows Logon Integration

The installer in typical mode does not enable the option. Admin must use the Custom installation mode.

The option uses a file to save credential data in a hard disk location that may not be accessible to non-admin users depending on the file system permission settings of a target machine. Admin must ensure that the data location is accessible for write operations by all users of the machine. Because of that prerequisite, the option is unselected by default during the product installation. Normally, the file location is stored in the (hidden) directory,

C:\Documents and Settings\All Users\Application Data\DocuShareClient

It is possible to use a different directory. Use MSI property CREDMANDATADIR to specify a new location in an MSIEXEC command line.

Note that even if the Logon Integration feature is installed, the feature is not actually enabled. To enable the feature, each user (including Admin) must run DocuShare Client Properties and select the Integrate with Windows Logon option (in the General tab).

-Visio and Non-Microsoft ODMA applications cannot open a file from or save a file to DocuShare.

Use the DocuShare Client popup menu on the system tray (task bar). Open the submenu, 'My Work Files', and uncheck the menu item, 'Disable ODMA'. Note that unchecking the item causes MS Word and PowerPoint to display a DocuShare ODMA prompt screen whenever you select the application's File Open, File Save, or File Save As menu item.

-DocuShare add-in for Microsoft Excel

Installation of the Excel add-in module enables you to access DocuShare files in collections from Excel. The module adds a DocuShare Open/Save menu to Excel's File menu. These menu commands may fail to respond when the input focus is in an edit control (for example, when editing a worksheet cell). If this happens, press the Escape key to exit the edit process and then make sure the status bar displays a 'Ready' status before selecting the command.

After saving a workbook file that you checked out from a collection, you may see an Excel macro alert when you select DocuShare|Open to check out another workbook. Click the Enable button to have Excel use the DocuShare Excel add-in module.

-Microsoft Office

If you re-install or upgrade Office, it is recommended that you re-install DocuShare Client.

-ODMA and Corel Suite 8

When opening or saving a DocuShare file from a Corel 8 application, the main application window may hide behind a concurrent application. This is an appearance problem and does not affect the editor's connection with DocuShare ODMA or the editor's general functionality. Should this happen, you can minimize the other application window and continue, or you can use the DocuShare ODMA window to open or save the file.

The current DocuShare Client ODMA component does not support Corel 7 applications because they do not comply with ODMA version 1.5 protocol. Limited support may be enabled through special registry setup. Otherwise, you should either not install the ODMA component or temporarily disable ODMA by right-clicking the red Xerox icon and selecting Disable ODMA.

-ODMA and Corel Suite 9

WordPerfect 9 running on Windows 2000 may not close correctly after editing and checking in a DocuShare document. If this problem occurs, disable ODMA.

-ODMA and Lotus SmartSuite 97

When you check out a Word Pro file from a DocuShare collection, Word Pro may display a dialog box and list previously edited files for you to reopen, while the checked-out file is loaded in the background. The file appears partially hidden behind this dialog box. Either close the dialog box or use it to open another file.

Also, under certain conditions, Word Pro may cause an ODMA splash screen to re-appear even if you select No (to indicate you want to use Word Pro's Open or Save As dialog).

You cannot use the DocuShare Client ODMA component with Freelance and 1-2-3 because the applications do not comply with or support ODMA protocols.

-OLE launch causes a "Server Busy" message to display

Depending on the editor application and the type of checked-out file, you may see a "Server Busy" window while you wait for the checked-out file to display. The OLE library on your computer displays this window when the OLE subsystem is waiting for a reply from the editor application. In particular, this window can display when you are trying to check out a file in a format that is older than the application version installed on your computer.

When this windows displays, click the Retry button until the file appears in the editor application. Or, if you know that the file format is outdated, open the editor and then check out the DocuShare file.

-Search|Files in DocuShare does not appear in Start menu after installation

Restart Windows.

-A copied mail message may lose its mail icon

When copying an Outlook mail message (saved to DocuShare using Outlook Client), an HTML icon may appear next to the copied message. Refresh the view to display the mail message icon.

-An icon does not appear next to a copied file

If, after copying a file, an icon does not appear next to the copied file, close and reopen the DocuShare window.

-Limitations in drag and drop support

Dragging and dropping a file shortcut to a DocuShare collection copies the file shortcut (.lnk file) and not the original file referenced by the shortcut.

When dragging and dropping a portion of a file's contents from an application window to a DocuShare collection, DocuShare Client creates a scrap file named "Scrap <editor name>." This feature may not work for some editors.

Dragging and dropping a file to a collection sets the creation date to the date on which it was added to DocuShare; the file’s original creation date is not retained.

-Selecting a collection in the left pane displays the objects in the parent collection

Under certain conditions (for example, when canceling the reopening of a collection), opening a collection results in a DocuShare Client internal conflict. Instead of displaying the content of the collection, Windows Client shows the objects in the collection one level above the collection you were trying to open. If this happens, close the DocuShare window, wait about 10 seconds, and then reopen the window. If that does not resolve the problem, restart Windows.

- Saving an HTML file and its linked files to a collection that contains an HTML file with the same name

DocuShare Client does not display a message when you are checking in an HTML file and its linked files to a collection that already contains an HTML file with the same name. Before checking in the new version of the file, delete the previous version. Also, if necessary, delete the collection that contains the linked files.

- A collection may close abruptly after checking in a file

After a file is checked in, the list of objects in the collection is automatically refreshed. However, there is a known problem with local cache updating of files and collections that causes either the current collection or the entire collection hierarchy to close. Should this happen, close and reopen the DocuShare window.

- Default Upload Property Values page does not open correctly in Netscape

To use the Default Upload Property Values button to specify default property values, your default browser must be Internet Explorer.

- Running searches using custom properties

Although you can specify custom properties on the Advanced Search page in the Find Files in DocuShare window, a search does not find the objects that contain the properties.

- Microsoft FrontPage cannot open a DocuShare file with a long file name

Using FrontPage, you may receive a "Cannot open file..." error when you try to open an HTML file in a collection. If this happens, shorten the file name and try opening the file again. You can change the name by right-clicking the file and selecting Rename.

- Microsoft FrontPage cannot open a DocuShare file in Unicode

Using FrontPage, you may receive a "Cannot open this page, because it is in Unicode format" error when you try to open an HTML file saved to a collection in Unicode format. Earlier versions of DocuShare Client stored a web page from Internet Explorer's Save As dialog in Unicode. FrontPage cannot directly load a Unicode file. To work around this problem, download the HTML file, open it in Notepad, save the file using ANSI encoding, and upload the converted file to DocuShare as a new version of the original HTML file.

- Cannot specify values for custom properties when creating users and groups

Creating a user or group account will fail if a value for a custom property is required for the object. Use the DocuShare Web UI to create the user or group account.

- When adding collections and files, a 409 Conflict Error may occur if a default property value is required

When adding a collection or uploading a file to a DocuShare server that requires a value to be specified for one of the default properties, the operation may fail with a 409 Conflict Error. If this happens, display the server’s properties and click the Default Upload Property Values button to specify a default value to use when adding collections and files.

- A folder containing a file may not upload if a default property value is required

You cannot upload a folder that contains a file if the DocuShare server requires a value to be specified for one of the default document properties. For example, Author is a default document property that an administrator can specify as required.

To upload the file, first create a collection on the server and then drag and drop the file to the newly created collection. The Checkin Wizard opens, allowing you to enter a value for the required property.

- Cannot use Word’s New|Document and Save commands to upload linked files

To upload a Word document that contains linked files, you should use Word's File|DocuShare|Save As command. When the DocuShare Checkin Wizard displays, make sure Express checkin is not selected so you can select the Update linked files option.

- A linked object in a document or worksheet may break

Editors such as Microsoft Word and Excel let you create an embedded object or a linked object from an external file using the Insert|Object command. DocuShare Client supports files that contain embedded objects; it does not support files with links to external files. If you upload a file with a linked object and then open the file, the editor may not be able to resolve the link to the original source file (on your computer) and may display an error. To avoid this problem, do not select the Link to File option on Word's or Excel's Create from File page.

Note: DocuShare Client does support updating hyperlinks that were inserted in a Word document or an Excel worksheet.

- Cannot prevent DocuShare from becoming the default ODMA provider

Unchecking the custom installation option, "Allow DocuShare to become default ODMA provider", does not have the desired result. This option appears on the "Select options" page. To prevent DocuShare from becoming the default ODMA provider, edit DSClient.msi using Microsoft's Orca editor or some other MSI editor. In the Property table, change the value of ODMNewDefault from "DSODMA" to "Other". Save DSClient.msi and run it.

SPECIFICATIONS

===============

- Supported DocuShare server: version 2.0 or higher (some features including the thumbnail view works with version 2.2 or higher). 3.0 or higher is required for saving an HTML page or a Word document that contains references to external files as a compound document with the referenced files stored as compound elements. 4.0 or higher is required for uploading mail messages. 4.1 or higher is required for HIPAA authentication. 5.0 or higher is required for records management functions.

- Supported network configuration: TCP/IP with WINSOCK 1.1

- Supported HTTP transport: Version 1.1

- Secure transport support for Windows 2000 and XP: SSL and TLS. These protocols are supported without support for a temporary or disabled server certificate. A non-authenticating tunneling proxy server may or may not be used. Client certificates are supported.

- Supported web server authentication methods: NTLM, Basic, Siteminder Redirection

- Proxy server support: a limites support is available for a Basic-authenticating proxy. A proxy must comply with the HTTP/1.1 tunneling specification for SSL connection.

- ODMA compliance: version 1.5 document manager interface. The search interface is not supported.

- Client-server interface: per DocuShare 6.0 HTTP HTML/XML protocol

- Supported DocuShare commands: collection- and file-related commands excluding access control commands. Limited administrator functions are supported including creating and editing user account properties. The 3.2 version of the protocol is used to perform compound document processing. The 5.0 version of the protocol is used to perform record management-related processing.

- Supported DocuShare object types: collection and file objects

- Partially supported DocuShare object types: workspace, calendar, bulletin board, saved query, URL, wiki, weblog, user and group objects

- Multi-parented DocuShare objects: fully supported

- Administrative function: user account creation (in the server mapping wizard)

- Language: US English (localized versions are available in separate installation packages)

- Server mapping capacity: 128 maps max.

- Proxy server setting: per mapped server

- Managed folders in shell extension: 1024 max.

- Objects listed per shell folder: 1024 max.

- Document versions in history list: 4095 max.

- Displayable dates: year 1971 through year 2038

- Displayed time zone: local time zone

- Client-server transaction time: GMT

- File type icons: 256 max.

- Shell windows tracked for event notification: 32 max.

- Shell windows monitored for checkout services: 40 max.

- Open/save documents per ODMA session: unlimited

ADDITIONAL NOTES

=================

The picture object library (PICOBJ.DLL) of the SDK uses the JPEGLIB library version 6b (3/27/1998) of the Independent JPEG Group. The JPEGLIB software is copyright (C) 1991-1998, Thomas G. Lane. The legal notes regarding the JPEGLIB use from IJG follows:

The authors make NO WARRANTY or representation, either express or implied,

with respect to this software, its quality, accuracy, merchantability, or

fitness for a particular purpose. This software is provided "AS IS", and you,

its user, assume the entire risk as to its quality and accuracy.

Permission is hereby granted to use, copy, modify, and distribute this

software (or portions thereof) for any purpose, without fee, subject to these

conditions:

(1) If any part of the source code for this software is distributed, then this

README file must be included, with this copyright and no-warranty notice

unaltered; and any additions, deletions, or changes to the original files

must be clearly indicated in accompanying documentation.

(2) If only executable code is distributed, then the accompanying

documentation must state that "this software is based in part on the work of

the Independent JPEG Group".

(3) Permission for use of this software is granted only if the user accepts

full responsibility for any undesirable consequences; the authors accept

NO LIABILITY for damages of any kind.

These conditions apply to any software derived from or based on the IJG code,

not just to the unmodified library. If you use our work, you ought to

acknowledge us.

Permission is NOT granted for the use of any IJG author's name or company name

in advertising or publicity relating to this software or products derived from

it. This software may be referred to only as "the Independent JPEG Group's

software".

We specifically permit and encourage the use of this software as the basis of

commercial products, provided that all warranty or liability claims are

assumed by the product vendor.

The DSClient gateway library uses OpenSSL by the OpenSSL Project for SSL support on Win98/ME. The OpenSSL license follows:

/* ====================================================================

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

Original SSLeay License

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

* This library is free for commercial and non-commercial use as long as

* the following conditions are adhered to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the routines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

* The license and distribution terms for any publicly available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution license

* [including the GNU Public License.]

Windows NT 4.0, Windows 2000, Windows XP, Windows Explorer, Internet Explorer, Microsoft Office 2000 and XP, Word, Excel and PowerPoint are either trademarks or registered trademarks of Microsoft Corporation. Lotus, 123, Freelance Graphics, and Word Pro are either trademarks or registered trademarks of Lotus Development Corporation. Corel, WordPerfect, Presentations, Quattro, Paradox, CorelCENTRAL, InfoCentral and TextArt are either trademarks or registered trademarks of Corel Corporation or Corel Corporation Limited. Adobe, and PageMaker are either trademarks or registered trademarks of Adobe Systems, Inc. Visio is either a trademark or registered trademark of Visio Corporation.