TeamWork Release Notes

TeamWork Version 4.0.38  (4/13/2009)

• Fixed hyperlinks so that they will work with Office 2007 and Office 2003 when using Word as the e-mail editor.

TeamWork Version 4.0.37  (8/21/2008)

· Setup updated, fixed and tested for Vista and Office 2007

· If you place a standard TeamScope REG license file called "TeamWork.REG" in the same folder as the setup EXE the setup will execute that file.

· If you run the Setup on Vista and the UAC is not turned off the request dialog to shut down Outlook will not display in most cases.  Either turn off the UNC on Vista or simply remember to turn off Outlook before running the Setup.

· Fixed issue with license Limit issue when using TeamScope CRM LO license.  Prior versions would only work if Product=OutlookCRM not TeamScope CRM.  Limit was then getting incorrectly used to check the number of items in the Task folder.

· If OneOffSafe=1 then the task notification then just uses an E-mail item instead of a Task assignment.   This is to deal with problems in Outlook with task assignment between different versions of Outlook. 2000 to 2003.  OneOffSafe was not being used in any of the current code.

· LinkType=Icon no longer works due to issue with Redemption.  Code will put in Outlook GUID link in its place.

· Added licensing "org" check before "user" check to support "org" licensing.

· TeamWork Analyzer v2.1.0:  Added error check and logging at the item level.

· Fixed incorrect msgbox dialog in the WF.Process that said:  "The field 'X' needs to have a value before this item can be saved or moved to the next step."  The problem is that this should only get triggered if the user has selected a next step.

· Changed the dialog text from "… can be saved or moved to the next step" in the dialog to just say "… can be moved to the next step." as the item can be saved, just not moved on.

· Fixed issue where if you opened (or created) an item from a different folder and you were running in an OST (Favorites) the relative navigation would not work.  (You had to always use a full path all the way from Public Folders on down)  [Related to the issue with .Parent not working properly in Favorites]

TeamWork/OEL Version 4.0.20  (8/28/2005)

• Outlook Extensions Library (OEL) is now a licensing subset of TeamWork and thus a separate OEL EXE and installer is no longer needed
• New Workflow Agent -- provides for exception notification, enhanced task notification, and other misc. new features
• Grid and Calendar OCX controls updated to v4.0
• All sample and template forms have been updated to use the new v4.0 OCX controls
• Several fixes were made to the Workflow Designer
• Fixed bug when selecting the Items List form, that the library EXE was not closing out and remained in memory
• Fixed startup/shutdown issue where the library EXE was in some cases being chosen as the monitoring app instead of the Outlook form itself. This would cause the library to not close out properly, leaving things around like Locks, etc.
• All MsgBox dialogs were set to display and keep them on top of any other windows
• Fixed a number of issues with the Task Assignment when not in Test/Review mode
  

OEL Version 3.0.8  (11/15/2004)
TeamWork Version 3.3.13  (11/15/2004)

• Changed from a DLL to an ActiveX EXE to support separate multiple instances
• Licensing module was revised to fix the Org and other related licensing issues
• Help file updated (rev 3.0.e) to remove references to Beta and Workflow Agent
  

OEL Version 3.0.2  (10/6/2004)

• Fixed issue with ExitState not being set in History.Process
  

Version 3.0.9  (8/18/2004)

• Userproperties.Find issue in script code removed as it caused problems on Outlook 2002 in a PST
• Fixed/changed AddMsgSection -- was "x","y" is now "x;y" for parameter list
• Fixed MsgDataValidate (needed to call AddMsgSection)
• Changed validation message: "...can not be saved or moved to the next step."
  

Version 3.0.5  (6/28/2004)

• Added function to flush the cache
  

Version 3.0.4  (6/21/2004)

• Initial Version 3 Beta release