TeamWork Release Notes

TeamWork Version 5.0.12  (Dec 8, 2011)

·         For Outlook 2007/2010 we changed Hyperlinks in notifications to now be created by default as an HTML <a href tag instead of the previous versions method of using Outlook Word editor to create the hyperlink.  The Outlook Word version requires that the notification be displayed before sending.
If customers have difficulty with the HTML hyperlinks then they can revert to the Word Editor type hyperlinks by adding a new configuration item.  Users will see the notification email display and immediately send so it will appear to just be window that flashes and is gone.  Create the configuration item with Subject=”Overrides” and a section name of [Override Options] and a key of "Create Hyperlinks With Body Word Editor".  Example:
[Override Options]
Create Hyperlinks With Body Word Editor=Yes
(note: the default used is “No”, meaning create hyperlinks with normal HTML)

TeamWork Version 5.0.11  (Nov 8, 2011)

·         Added “Override” capability to allow admin to specify that step notification messages are to be sent out when the workflow is in “Agent” mode.  This is done by adding an additional Config item to the “Configuration” folder for the workflow, subject=Overrides, content:
[Override Options]
SendStepNotificationsInAgentMode=Yes

Please note: the default is “No” when this override option does not exist.

TeamWork Version 5.0.10  (Nov 4, 2011)

·         Updated library routine which gets an Outlook folder (funNavigate) to get its own Outlook NameSpace object when required.

TeamWork Version 5.0.6  (7/14/2011)

·         Updated forms in the install PST folder to set the code reference to the Configuration folder to match the configuration folder’s new name (“Configuration”) and set the “Workflow” mini tab to be showing when the user opens the form and updated the Design copy of the form and published a backup copy of the form to the Design Form folder.

·         Added support for non-English folder names for “Public Folders, “All Public Folders” and “Favorites”

·         Please note: oLib.Config.SetFolder “ConfigFolderName” is required in the workflow form’s vbScript code so that the form will open without errors when opening the form from a hyperlink in an email in the user’s Inbox.

·         Enhanced the oLib.Config.SetFolder to use a default configuration folder name of “Configuration” when the folder name passed in does not exist

·         Since the Designer just looks for the first configuration folder it finds with a folder name that contains “config” we also updated the workflow initialization routine to set oLib.Config.SetFolder to the folder named “Configuration” if one exists.  The VBScript statement “oLib.Config.SetFolder” is no longer required in the form’s Item_Open function if the workflow configuration folder is named “Configuration”.

·         Updated the Link Type=Hyperlinks to use the Outlook Body Word object to insert the hyperlink in the format that Outlook 2007/10 prefer so that Outlook security settings will not get in the way.

·         Completion and Termination steps are now always set to a status of “Complete#” at the end of processing the previous step.

 

TeamWork Version 4.0.38  (4/13/2009)

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)

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

OEL Version 3.0.2  (10/6/2004)

Version 3.0.9  (8/18/2004)

Version 3.0.5  (6/28/2004)

Version 3.0.4  (6/21/2004)