Changes to Version 6.2.0.2

I would like to advise you that we have just released our 6.2.0.2 build of IPM.

This new revision is our first that is compatible with CRM 2016.

The big changes in this build are the initial release of the new IPM Portal which will be the subject of some new documentation that will get done this week. The Portal is designed to provide third parties with access to IPM documents and also to provide a facility to upload documents. The user interface will be revised over coming releases however the core functionality that will provide external access is complete. It also adds a full tracking mechanism to log third party downloads of documents from our Libraries. It introduces a security model around these downloads complete with auto-generated emails to provide end user logons. Please ensure you are familiar with this whole mechanism before deploying for any clients as it does change the end user experience slightly when downloading using our hyperlink downloads.

The Portal will be a licensable option however for the first 12 months we will make it available to all clients and those that chose to continue using it can elect to have it added to their maintenance contract if they would like to retain it.

A new feature for PO Revisions is also included in this release. When a PO is selected for revision the old revision of the order or more to the point, what should be seen as the old revision of the order is set with a status of “Superceded” and is flagged as inactive. We have been careful in the way we designed this to ensure all the relationships to activities and attachments are maintained against the current revision.

We have also added new support for Sage CRE 300 with a direct read option as opposed to the current Timberline Transaction Synchronisation functionality.

The documentation for all these features will be updated to the IPM Documentation website this week. This site now has a new URL http://ipmhelp.ipmglobal.net

Instructions for upgrade:-

Please download the new IPM v.6.2.0.2 (with new IPM Portal) from our FTP server: both ipm6_2_0_2.zip and ipm6_2_0_2files.zip (IPM Web Server files w/o web.config + PLUGINS DLLs)

IMPORTANT: CORRECT ORDER OF IPM UPDATE (NOT IPM FIRST INSTALLATION):

run first IPM installer to install IPM Web Server
update all IPM Plugins manually using Plugin Registration Tool with new DLLs from ipm6_2_0_2files.zip on our FTP server(there are 2 new IPM Custom Workflow Actions that may not be installed properly by just uploading a solution file)
run second IPM installer to install IPM Configuration Manager
upload 2 new IPM Solutions from the folder where you installed IPM Configuration Manager
run install/update all action for IPM Settings/SystemData in IPM Configuration Manager

If it’s not IPM update – IPM first installation – you should use the default approach – just upload IPM Solutions files – not need to run Plugin Registration Tool before that

There are 5 new Workflows included in this build second unmanaged Solution required for IPM Portal to work

Two of them generates E-mails for users:

IPM Portal - E-mail Address Verification Letter
IPM Portal - New Temporary Password Letter

After testing IPM Portal with original IPM Portal Workflows activated – you need to Deactivate them

and make copies of them:

create new Workflows repeating all parameters and steps from the original Workflows
then customize E-mails subject and body text for your/client’s needs (but use the same approach as in original Workflows)

Also please take into account that IPM web.config file has some changes in comparison with older IPM versions:

1) If you use first IPM installer with your customized/client’s ipm.config file to install IPM Web Server files – then you don’t need to do anything

2) If you may need to replace files in IPM_MSCRM folder manually with files from ipm6_2_0_2files.zip (w/o web.config) from our ftp server,

then please note that web.config file in v.6.2.0.2 has some changes in comparison with previous versions (highlighted below)

in OLD web.config:

<system.web>

</system.web>

in NEW web.config:

<system.web>

</system.web>