Office Routing Plus Changelog:
Critical Updates
- Those who are upgrading to Office 2010 and use document forms or macros, you will want to be on ORP 3.0.0.6 or greater. We've enhanced support for the legacy change to documents.
- If your company is on 3.0.0.4 or 3.0.0.5 and you use MS Word you may be experiencing errors with opening routed Microsoft Word documents on some computers. Version 3.0.0.6 fixes this issue; see 3.0.0.6 for more information.
- Version 3.x and up now supports routing documents with any email client, so Microsoft Outlook client is not required on the machine that you install Office Routing Plus on. This version also now saves user settings per user rather than per machine; see 3.0.0.0 for more information.
- Users on 2.0.1.0 through 2.0.1.2 should consider version 2.0.1.3 or higher. This is a critical update if your users use the Send Initiator Updated File "At each step"option, as this feature was not working properly from version 2.0.1.0 through 2.0.1.2.
-
Users on 2.0.1.0 or lower who try to add 10 or more recipients will also want to upgrade to the newest release, as adding 10 or more recipients was resulting in unexpected sorting of the recipients.
-
Customer on 1.x versions will most definitely want to consider upgrading to the newest version as there are many new enhancements after the 1.x versions. Most notably, versions 2.x now use the Microsoft Outlook address book running on client machines to choose recipients from instead of Microsoft Active Directory (for customers still wanting to use AD this feature remains).
- Improved all at once routing feature.
- Improved load time performance.
- Introduced a unique routing id set on every routing document that goes out.
- Fixed a minor outlook emailing issue. (this edit was posted 10/26/2011)
- Improved status message emails to include current routing slip status within email.
(read more details here)
- This release only affects Microsoft Word version 2003 and lower. In previous versions, if a user opened Microsoft Outlook first and then opened Word and if Microsoft Outlook 2003 is setup to use Word as the email editor, then ORP would not show up in Word when you launched Microsoft Word after launching Microsoft Outlook first. The fix was to go to the view menu and select officeRouting to turn this menu on. Version 3.0.0.8 addresses this issue, so that ORP will always show up in Microsoft Word.
- This release only affects Microsoft Word. ORP now fully handles routing macro enabled documents. A new message has been added that will explain to users that if they have just chosen to enable macro embedded files, they should not choose "Yes" yet to route to the next recipient. Note that unlike non macro embedded file types, ORP will save the open document by default before you route it without prompting you, if this is a .docm file type.
- This version also no longer adds the temporary document that gets routed to the recent documents list in Microsoft Word.
- This release also now sets the regional and cultural settings back to what they were previously at locally on the machine after the ORP form is closed (in previous releases, the culture context was set to US when Word/Excel opened and it was left on US until Microsoft Word/Excel closed. This caused a problem with other Add-Ins that may be running in Microsoft Office on computers that are set to non US based settings).
- This release only affects Microsoft Word. In version 3.0.0.4 (released April 27th, 2011) ORP was updated to be able to route documents that have active-X legacy controls. Prior to this release the temporary document that gets created on the fly and routed as a file attachment would generate duplicate active-x legacy controls on the document from some machines running Word 2007/2010. Version 3.0.0.4 resolved this issue by changing how the temporary document that gets created on the fly and attached as a document is saved, but this version created a new bug where some users were reporting that if they had the default save option in Microsoft Word 2007/2010 set to a 97-2003 document type (i.e. .doc instead of .docx) then the documents were always getting saved and routed by ORP with a .doc (2003) format, even though the extension was still saying that the document type is a .docx file (2007/2010 document). This then would cause a problem on the next user's machine who tried to open the routed document--the error usually contains "catastrophic failure" or something about the document being in an invalid format. This problem has been fixed in version 3.0.0.6.
- This version also adds the ability to route macro embedded file types (.docm).
- German version is now compatible with Microsoft Windows 7 font settings at 125% (or higher)
- The tracking feature that was made available in 3.0.0.3 is now defaulted to be off instead of on.
- Added feature for 2007/2010 users who add "legacy Active-X controls" to Microsoft Word documents. Prior to this version some users were reporting that the controls would duplicate on the form after being routed.
- Added a feature for the Microsoft Word version of the add-in for turning on or off tracking changes feature from within the add-in form.
Version 3.0.0.2 (November 26, 2010)
- The fixes in this release are only relevant if you were using version 3.00 and if you setup any computers to use NON-Outlook settings.
- Email Client Settings screen when customizing SMTP settings would disable the email box when authentication required checkbox was marked on. This now lets you put in the email address either way.
- Setting "Select Recipient Mode" to manual will now cache the recipients you enter so you build a list of recipients as you use the system. Recipient names can also be imported by modifying the RoutingCachedManualRecipients.txt file by hand.
Version 3.0.0.1 (November 16, 2010)
- The fixes in this release are only relevant if you were using version 3.00 and if you setup any computers to use NON-Outlook settings.
- Note, if you were running 3.0.0.0 before going to 3.0.0.1 and if you manually configured the smtp settings to something other than the Microsoft Outlook client, then you will want to reconfigure your email client settings again with this release (or any future releases of Office Routing Plus). This is because versions after 3.0.0.0 now have a few additional fields for manual smtp configuration settings.
- If the initiator chose to send the updated file at each step back to himself and if the client is setup to use non outlook settings (a feature new to version 3.00) then there was an error in sending the updated file.
- Also, if the client is setup to use non outlook settings then the routed files were not getting deleted from the temp routing docs path.
- Office Routing Plus is now fully functional, independent of Microsoft Outlook or any specific email client running on the client machine.
There is now a configuration button in the program, which will allow the end user to select Microsoft Outlook as the client, or to enter custom
SMTP settings for any Email program. Users may also use the new configuration tool to set the recipient selection mode--meaning where ORP should
get recipient names from to display as potential routing recipients. The options are: Microsoft Outlook, Microsoft Active Directory, or Manual (which lets users just type in
any recipient name without a listing of users from their organization).
-
Another important change in this release is that ORP now stores all config files per user rather than per machine (ORP utilizes
the %AppData% folder, intended by Microsoft Windows for per user settings for applications. In Microsoft Windows XP this would be C:\Documents and Settings\*user name*\Application Data\Office Routing Plus\.
On Vista and Windows 7, it is at C:\Users\*user name*\AppData\Roaming\Office Routing Plus. For existing customers whose configuration files are currently stored per machine, after obtaining this version,
ORP will copy the existing settings from this machine to the user AppData folder referenced above.
-
This version also uses a different method for loading the 3rd party Redemption product, which is used to communicate with Microsoft Outlook. This will address some of the errors that we occasionally see with redemption not loading
properly on some machines.
-
Aesthetic changes to the main form.
Version 2.0.2.0 (October 20, 2010)
- Additional internal changes to the Installer.
Version 2.0.1.9 (October 17, 2010)
- Office Routing Plus now has an additional feature that will help some organizations with the "out of office" situation. If a document initiator routes a document to user B and user B then routes to C and then immediately user B gets an "Out of Office" reply from user C, then what user B can now do starting in this version,
is open the document back up on his/her computer and go to the add-in menu and simply delete user C from the recipient list. Versions of Office Routing Plus prior to this release would never let anyone delete a recipient who has already been routed to. This version allows a user to delete a recipient that has been routed to,
only if the recipient you are trying to delete was the last recipient this document has been routed to and if you are the one who routed it. When recipient B removes original recipient C in this way, he/she will be prompted to send a message to the original recipient C so that that recipient will know that they have been removed from the routing
on this document--recipient B has the option of customizing the message that will be sent to recipient C, or if desired, recipient B may choose to not send an email at all. Once recipient B has removed recipient C, then all he/she needs to do is click "Add Recipient" and add a different recipient to route to in place of the original user C and then simply use the up
arrow to move the new recipient to the desired order in the recipient list. We are currently working on a "Enhanced ORP" product that will give further functionality with regard to out of office scenarios and documents getting stuck--the enhanced product will show anyone who has purchased the enhanced license exactly where documents are in real time, as well as the current state of the document. Anyone who is
involved in the routing of a document could see this information (not just the initiator). The enhanced product will also keep a complete history of the routing of all documents and store the actual document as well for easy retrieval of routed documents.
An additional change in version 2.0.1.9 is to the prereqs in the installer. Previously, we were looking at word.application.version to see what version a machine is on and then deploy the appropriate prereqs based on the version. The problem was that some computers had a value of "12" (2007) present even when they were still on 2003. We now look at the HKEY_CLASSES_ROOT\Word.Document\CurVer key instead to determine current version.
Version 2.0.1.8 (October 4, 2010)
- Additional changes to the Installer (see version 2.0.1.7) below for more on the new Installer that Office Routing Plus now uses.
Version 2.0.1.7 (October 1, 2010)
- Office Routing Plus now uses the Advanced Installer product to author deployment packages. This has allowed Integrity Solutions to create one installer to deploy the Office Routing Plus add-in, which is independent of the version of Microsoft Office (or Windows) that a deployment machine is running. Previously we had to deploy two installers--one for Microsoft Office 2007 and one for Microsoft Office 2003. The new installer will now dynamically determine if a computer is on Microsoft Office 2003, 2007, or 2010 and will deploy the required prerequisites accordingly.
Also, this new installer makes it very easy to push out the Office Routing Plus add-in silently (unattended) to any machine. Just call setup.exe /qn. See http://www.office-routing.com/en/help.php#installing for more detailed and up-to-date information on installing Office Routing Plus.
Version 2.0.1.6 (September 18, 2010)
- Addresses the following error that occurs when opening a routed document "the file format or file extension is not valid...Verify that the file has not been corrupted and that the file extension matches the format of the file."
This error only occurred in the following scenario: the routing initiator is on Microsoft Office 2007 and he/she chooses to save the document as a 2007 file (.xlsx or .docx).
The initiator includes someone in the routing list who is still on Microsoft Office 2003. When the 2003 user would open the document and send it to the next recipient,
that user would get the error indicated above. If users are not on 2003 in your environment this error would not affect you. Also, if you do not want to implement this upgrade, a workaround is to always have initiators who are using 2007 save the document in 2003 compatibility mode.
Version 2.0.1.5 September 7, 2010)
- German label was showing up in English versions on the Add to Favorites Recipient List (clicking the star icon with the plus brings you to Favorites Recipient List).
Version 2.0.1.4 (September 4, 2010)
- Additional changes for German labels/messages.
Version 2.0.1.3 (September 1, 2010)
- Fixed "File does not exist." error. This was a problem with the
Send Initiator Updated File "At each step" option. The problem was it was not
saving the file correctly and so it could not find it to send it. This error
only affected routing slips where the initiator chose "At each Step" for the "Send Initiator Updated File" option
(which only existed since version 2.0.1.0).
Version 2.0.1.2 (August 7, 2010)
- IMessage: Interface not supported errors. Tries to connect to Microsoft Outlook
with a regular logon method if the mapi marshalling (via Redemption)
fails.
Version 2.0.1.1 (July 20, 2010)
- Fixed issue where adding 10 or more recipients sorted recipients incorrectly.
Version 2.0.1.0 (July 20, 2010)
- Changes for optionally attaching file for tracking the changes to file
at each step of the routing process when sending tracking status emails to initiator.
Version 2.0.0.9 (July 20, 2010)
- Office Routing Plus is now compatible with Microsoft Office 2010
Version 2.0.0.8 (May 17, 2010)
- Office Routing Plus now uses a custom template for saving changes to the
menus in word via the customizationContext property. This should take care
of prompts that ask the user to save changes to a template when they never
made changes (it was actually ORP making changes to the menus by adding the
orp menu and this was getting saved to whatever template they had open).
- No longer do anything at all with disabling or enabling the old routing menu in 2003.
Version 2.0.0.7 (May 7, 2010)
- Changes for wording and overall logic for "all at once routing".
Some of the messages and statuses of controls were not correct for this.
- Changes for wording and overall logic for "all at once routing".
Some of the messages and statuses of controls were not correct for this.
- Additional changes to German labels/messages.
- If the document has not been saved and you are closing and it has a
routing slip it will not prompt you to route it.
Version 2.0.0.6 (April 22, 2010)
- - Added full support for German product (German captions and messages).
Version 2.0.0.5 (April 19, 2010)
- Fixed error when canceling out of global address list (GAL) (no_mapi..etc)
- When canceling out of global address list it would remove any recipients
that were previously added before entering the GAL
- 2007 version only - wouuld not let you add a recip if multiple recips
were already added - it would always add just the last recip
- 2003 version only - removed message that said "this document has an old
routing slip" for docs that had old routing slips
- When Microsoft Excel or Microsoft Word was closed and ORP detects a routing slip that where
the next recipient can be route to, it would prompt to route and after hitting yes,
it would then ask "route to recipient (name)?". removed this prompt
- When excel or word was closed and ORP detects a routing slip that where
the next recipient can be route to, it would prompt to save, even if hte only
thing that was not saved in the document was the updated routing slip changes
reflecting that you just routed it. There is no longer a prompt now to save
if the only thing that was unsaved was the fact that you just closed and chose
to route the document--it now assumes that you want to save that routing
history with the document.
Version 2.0.0.4 (April 12, 2010)
- - Fix in place for conflict with vba projects that were password protected.
A password prompt would come up whenever you tried to close excel or word if the file being opened had VBA code that is password protected.
Version 2.0.0.3 (March 31, 2010)
- - Fix for routing all at once--error message was saying could not
resolve recipients when you routed all at once on version 2.0 and up.
This has been fixed.
Version 2.0.0.2 (Mar 11, 2010)
- - We no longer try to add an extension (xls, xlsx, doc, docx, etc) to a
document we are routing if an extension does not exist. Instead, ORP will just tell
the user that the file has not yet been saved yet and it will make the user save it
before routing.
- - We no longer try to kill Microsoft Outlook thread as it appears that
you can't have multiple sessions of outlook running anyhow and if it was
not already running when you launched ORP then when you close
excel/word, it seems to close outlook automatically (if it was not
already running) as part of the garbage cleanup
version 2.0.0.1 (Feb 13, 2010)
- This now sets up a folder upon install under the main ORP folder for
storing temporary documents. But ORP still uses the temproutingfileattachment.txt
file so that admins can change the location of where temporary documents get saved. A \ in the front means it
is in the ORP install folder.
(Mar 08, 2010)
- Setup (Primary Interop Assemblies) PIA added 2003 or 2007 pia as pre-Req for installation files.
version 2.0 (Feb 12, 2010)
- Added ability to connect to the Global address list on Microsoft Outlook client
instead of Microsoft Active Directory (can still use Active Directory Optionally)
Also added the ability to save recipient lists
(Feb 10, 2010)
- Installer change -
added config files folder under install folder and set permissions
on the folder upon installation so that Microsoft Vista and Microsoft Windows 7 users have
permissions.
(Feb 12, 2010)
- Installer change -
added Saved Recipients folder under install folder and set
permissions on the folder upon installation so that Vista and Win7 users
have permissions.
version 1.0.0.2 (Feb 01, 2010)
- Changed tempFileAttachment to delete just the file that was just created as an attachment to be mailed when routing after the document is sent
(previously it would delete the entire folder)
Request an Evaluation copy