Every time Fischer & Kerrn releases a new version of ACTIVESIGNATURE it will be announced here. All customers will also get a notification by e-mail when there is a new major release.

Changes compared with version 4.4.6:

Feature changes:

• Send on behalf of button added enabling the user to create new email (or replies/forwards) using other users' signatures.
• Send on behalf of auto-detection: Automatically use signature of other user when replying to email in other user's inbox.

Bug fixes

• Fixed bug where OWA signatures was not set on Exchange 2010.
• Fixed bug resulting in user data cache file not being loaded properly.
• Fixed bug resulting in user data sometimes being incorrect (using data from another user).

Important notes for when upgrading previous versions to this version:

• Clients running any previous version (4.x) can be upgraded to this version just by running the installation package.

Compatibility with previous versions:

• Clients running this version can co-exist fully with clients running any previous version (4.x). New functionality added in this version will, of course, not be available to clients running any previous version.

Changes compared with version 4.4.3:

Feature changes:

• Prompt the user to restart Outlook if necessary to ensure correct e-mail signatures. If this feature is disabled, the user will instead just get a message box telling the user that Outlook should manually be restarted. For certain Citrix environments/configurations this feature should be disabled.
• Set Outlook registry settings specifying default signature names both at startup and after load of configuration to ensure that changes from configuration are reflected in the registry as soon as possible. This minimizes the number of restarts required meaning that it should now always only require one restart of Outlook to ensure the user has the proper signatures.
• Now get user data after getting configuration data, as configuration data can specify additional properties to retrieve for user data. Previously these additional properties would not be available until after next restart of Outlook. This change fixes a bug occurring when using "only when changes" update mode and having default signatures using conditions checking on custom properties.
• When configuration item contains XSLT it is now transformed twice with updated user data each time. This is done to ensure that configuration settings that afflict the user data retrieved will take effect immediately.

Bug fixes:

• Fixed bug where an empty default signature would cause error entries in the log file.
• Fixed bug where default signature settings was not properly set in certain scenarios when using Outlook 2003 or newer.

Important notes for when upgrading previous versions to this version:

• Clients running any previous version (4.x) can be upgraded to this version just by running the installation package.

Compatibility with previous versions:

• Clients running this version can co-exist fully with clients running any previous version (4.x). New functionality added in this version will, of course, not be available to clients running any previous version.

Changes compared with version 4.4.1:

Feature changes:
-   Background coloring of required fields now only applies when required fields are empty.
-   The red color used in the form for viewing/editing user data has been changed to a lighter red to improve readability.
-   Form for viewing/editing user data now supports showing custom field labels as well as explanatory text which can be defined using the administration tool.
-   Form for viewing/editing user data modified to support showing fields in a ''simple mode''.
When showing the form in ''simple mode'', only fields which are editable are shown and the fields are arranged in vertical list and all have the same width.
-   Now saves the active user's user data to file %APPDATA%\ActiveSignature\UserData.xml
This feature was added to allow other applications to easily access the user data Xml of the last user who opened Outlook.

Bug fixes:
-   Fixed bug where Address, Country, Notes, Description fields were not included in the list of fields which name can be customized.

Important notes for when upgrading previous versions to this version:
-   Clients running any previous version (4.x) can be upgraded to this version just by running the installation package.

Compatibility with previous versions:
-   Clients running this version can co-exist fully with clients running any previous version (4.x).
New functionality added in this version will, of course, not be available to clients running any previous version.

Changes compared with version 4.3.1: 

• Support for Outlook 2010 32 bit (currently only supports signature creation for the primary Exchange accouont).
• Added possibility for configuring required user data fields which must contain data before a user can submit changes to user data in AD UPDATE.
• Added possibility for specifying whether the user should be prompted (at Outlook start up) to enter data in fields marked as required if data is missing (AD UPDATE).
• Fixed bug where invalid signature templates would not show up in the administration modules template list
• Fixed bug where the progress bar stops prematurely when an invalid signature template exists.
• Fixed bug where template title did not show properly in the log

Changes compared with version 4.2.39: 

• New feature added: Support for using mailbox as template/license store (public folder store still supported)
• New feature added: Support for additional user data retrieval methods: Exchange only, ActiveDirectory only, ActiveSignature Service (server generated user data file)
• New feature added: Support for extracting custom properties from Active Directory

Changes compared with version 4.2.1:

• New functionality added: ACTIVESIGNATURE AD UPDATE module. Users can now view/edit basic user data using ACTIVESIGNATURE. Edits are saved either locally (in user's mailbox) or globally through web service to AD or another data source. This feature requires the ACTIVESIGNATURE AD UPDATE module.
• Caching algorithm changed to optimize use of cache data in various Microsoft Outlook connection modes.
• Changed method for updating OWA signature to ensure Microsoft Exchange store is opened in non-cached mode. Change made to fully support all connection types/scenarios (e.g. Microsoft Outlook Anywhere, custom authentication etc). 
• Fixed bug where an error (clsSettings::LoadSettingsFromConfigFile) was incorrectly logged when starting Outlook in certain scenarios.
• Fixed bug where temporary e-mail item stays in Deleted Items folder when using Microsoft Outlook as RTF/TXT conversion engine.

Changes compared with version 4.1.22:

• New functionality added: Support for Microsoft Outlook Web Access signatures on Microsoft Exchange Server 2003 and 2007. This feature requires the ACTIVESIGNATURE WEBMAIL module.
• New functionality addad: License status information is now shown in configuration editor 
• Improved loading time of signatures when opening Microsoft Outlook.
• Fixed bug in the WYSIWYG editor.

Changes compared with version 4.1.21:

• Changes made so security registration in Microsoft Outlook is no longer required.

Changes compared with version 4.1.20:

• Fixed bug in template editor where clicking Preview button for Text/RTF formats would show HTML signature if no text/rtf template was defined.
• Added button in source editor for text format to assist user inserting line breaks.

Changes compared with version 4.1.19:

• Fixed bug in template editor where RTF WYSIWYG button was not enabled/disabled correctly and was not working properly for new signatures.
• Fixed bug in template editor occurring if new template was created and then canceled.

Changes compared with version 4.1.18:

• New functionality added: WYSIWYG Editor for RTF format now enabled.

Changes compared with version 4.1.14:

• Domain selection dialog is now forced top most.

Changes compared with version 4.0.9:

• Fixed bug in template source editor where some xml character entities were replaced when reopening source code.

Changes compared with version 4.1.1:

• New functionality added: E-mail address selection feature, so users having e-mail addresses in multiple domains can select which signature to use when creating new e-mails/replies.

Changes compared with version 4.0.5:

• Changes made to better support other programs automation of Microsoft Outlook.

Changes compared with version 4.0.3:

• License item changed to use e-mail address instead of domain user name.

Changes compared with version 3.0.15:

• New functionality added: WYSIWYG editor.