New Mercury platform FAQs

Why is Connective developing a new version of Mercury? 

Our mission is to support our members in growing and maintaining successful businesses - and a big part of that is technology. Whist Mercury 5 remains a leading technology platform, we understand that as with all things, Mercury must evolve. The new Mercury platform will be built upon the foundations of Mercury 5 - retaining and enhancing the core functionality, whilst introducing new features and integrations.

What is the new Mercury platform? 

We have taken the core functionality of Mercury 5 and split it out into a suite of purpose built applications. Additionally, we have created some brand new functionality into the Mercury platform. 

The new Mercury platform consists of: 

• Apps
• CRM
• Research
• Commissions
• Customer Centre
• Doc Centre (beta)
• Admin (in development)
• Analytics (in development)
• Compliance (planned)
• Asset Finance (planned)

See here for a more detailed overview

When will the final "Production" version of the Mercury platform be available? 

CRM, Research, Commissions and Customer Centre have been released into production. That's not to say there won't be new features and enhancements yet to come though. It simply means that that the features that have been released are now complete.

Why is Doc Centre still in Beta?

A new version of the Doc Centre will be released early in Quarter 2 2020. This follows a decision to make the Doc Centre a feature of the CRM, rather then it being it's own separate application. The decision to make this fundamental change was based on the feedback we have received from users throughout the beta period.

When will the other beta applications be released into production?

Depending on the size and complexity of the application being built, the length of the development lifecycle can differ.

Typically when an application hits the beta phase it is nearing the end of the development phase and is considered almost ready to go out to production – but the beta phase is intended to find out how ready it is. We rely on the feedback of brokers to tell us how close we are – what we got right, and what needs a little (or a lot) of fine tuning.

Feedback is logged in our Ideas Portal and bugs can be logged in any of the Applications.  

Am I making changes to my real data when I use the new platform? 

Yes. The new Mercury platform uses the same backend as Mercury 5. Meaning you are using your actual, "live" production data when you use one of the applications. Everything that you do in the new platform (even if it is in beta!) will impact Mercury 5. 

Will my existing workflows (tasks/statuses) still work in the new Mercury platform?

Yes. Your workflows, task-templates, statuses etc. will all be used in the new Mercury apps. No need to re-establish any workflows.

As a general rule of thumb, the core functionality of Mercury won’t change. We are improving and refining some existing features, and introducing a number of brand-new features. 

A few outdated pieces won't be rebuilt in the new platform, but these are generally bits of legacy functionality which are no longer in common use.

Can I use new Mercury and still use Mercury 5 or do I need to switch over entirely? 

You can use both. You can switch between Mercury 5 and the new platform whenever you like. Everything that you do in the new platform will be reflected in Mercury 5 - though some of the new features and functionality will only be available in the new Mercury platform.

Why aren't my merge documents downloading in the new platform? 

The very first time you use merge documents in the CRM the popup blocker may prevent the document from downloading. If you opt to allow popups then you should be able to use the merge templates after that.

What is a beta? 

A beta version of an application is a pre-release version that is given out to a group of users to test under "real" conditions.

Beta versions usually follow an alpha or "in-house" version which has been tested for general functionality and to ensure the code does what it is intended to do.

A beta version is usually fairly close in look, feel and function to the final product; though some tweaking and redesign to the interface and functionality may occur as a result of the user feedback obtained from the beta testers – that's the purpose of the beta testing phase.

Why does software need to go into beta? 

To ensure software is fit for purpose the developers usually get the software tested by users under "real" conditions. This beta period allows users to test and take advantage of the new features and functionality before the final release, in exchange for providing feedback on the new software. This allows the development team to gather feedback from the users on the software, fine tune workflows and usability, and potentially add new features or functionality as suggested by users.