Please Roll back to the previous client installation program that includes AutoVue

We all know that AutoVue is no more included with Meridian for additional licenses or new customers. But please, roll back to the previous client setup program at least for existing customers or add an hidden option to the Meridian msi Client setup program. Meridian installation is already complicated enough. In my opinion, the final customer shouldn’t have to install all the components separately.

Thanks a lot.

  • Pierre Riegert
  • Jun 3 2019
  • Will not implement
  • Attach files
  • Admin
    Coen Vromans commented
    4 May, 2021 11:31am

    We also looked in the more user-friendly alternative for unsecure, unsupported, Java based AutoVue viewer and selected HTML5 viewer PDFTron. We have looked at the pros and cons of several viewers and PDFTron is the best alternative.

  • Damien Flux commented
    5 Sep, 2019 03:24am

    We're also going to experience extra workload after the installation has been completed.

    Requiring users to either repair the install or edit the registry settings every time Java is updated will create a significant amount of extra time and work, particularly in enterprise environments with a large number of client machines.

    I am concerned that these changes will result in upgrades being postponed or cancelled as our customers seek more user-friendly alternatives.

  • Melissa Neal commented
    8 Jul, 2019 02:31pm

    I can understand both sides of the argument regarding the AutoVue installation, but I must agree wholeheartedly with his comments regarding patching. At this time, I've written 3 separate instructions to the client regarding server patches for 2018R2, and I'm in the process of writing up a fourth. I appreciate that development is responsive to our needs in providing fixes for the issues that arise, but there has to be a better way to manage the scores of patches that are presented for application to the server(s) and clients.

  • martin samson commented
    25 Jun, 2019 12:08pm

    There used to be a time when we at least had installers for outr patchs. Or we had service pack releases which came at a greater rate than once a year. I don't know why we moved away from this methodology but I do wish we would go back to it.

  • Mauricio Portal commented
    25 Jun, 2019 11:53am

    My big wish is that the BCME install work like an MS-Office install or any other modern installation of the app, install and work.

  • Gregory Valtierra commented
    24 Jun, 2019 09:06pm

    I agree that adding the components needed for AutoVue should be an option for the install, especially since many customers that upgrade would still be using AutoVue.

  • Chris Tsangarides commented
    13 Jun, 2019 09:22pm

    Hello Pierre,

    Thank you for your detailed explanation of the challenges you experience with the installation of Meridian.

    I understand the installations with all the variables is more and more complex. Your comments and suggestions have been shared with our development team to help make the process easier and faster.

    And, yes, I do remember the days when AutoManager was a powerful viewer. AM-WorkFlow and Meridian were created to make life easier … not more difficult.

    Please continue the add to the discussion here on the Ideas portal, or reach out to your BlueCielo/Accruent contact directly.

    Thank again very much,

    Chris Tsangarides
    Product Manager
    Accruent

  • Pierre Riegert commented
    5 Jun, 2019 07:20am

    Hello Chris,

    The thing is that Meridian installation becomes more and more complex and requires always more manual steps like registry settings or parameters to update in various text files, etc. If you add the huge number of patches (16 patches to install manually after Meridian 2018R2), you could admit that Meridian installation is all but simple.

    In release 2019, Accruent separates Meridian and AutoVue installations and the specific documentation can only be found in the knowledge base and we must now manually take care about JRE components. Of course, it not a huge additional work load.

    However:

    * We need to provide separate installation scripts to the IT Department in charge of creating the installation packages deployments (often an external resource based in India or elsewhere)
    * We also need to explain the right order for the installation packages (CAD Software, then Meridian Client, the JRE components, then AutoVue, and probably patches or registry settings)

    Even if I can understand why AutoVue must definitively disappear, I just say that the new setup procedure is adding more complexity to a process (Servers and Client installation) that is already complex with a lot of manual steps.

    Only the more recent customers have acquired Meridian Publisher and adopted PDF rendition for viewing and redlining. Older customers are still using AutoVue and consider this feature as one of the more important of Meridian Software. Remember: At the beginning of Cyco Software, AutoManager was just a powerful file viewer.

    As a conclusion, please consider my post as a general warning regarding the complexity of Meridian Installation. Within the years, Meridian trend to become a patchwork of multiple pieces of software and technologies instead of a coherent integrated solution. At least, Accruent should simplify the setup procedures and clarify the documentation.

    With Kind Regards

    Pierre

    De : Accruent <0ec0bba6a3b03a985fbd9b6d-accruent1@mailer.aha.io>
    Envoyé : mardi 4 juin 2019 18:04
    À : DIRIBEO - Pierre Riegert
    Objet : Chris Tsangarides responded to idea MER-I-318 Please Roll back to the previous client installation program that includes AutoVue

  • Chris Tsangarides commented
    4 Jun, 2019 04:02pm

    Thank you for your suggestion.

    If I understand correctly, you’re requesting for the Meridian Client setup package for 2019, and going forward, to go back to including the AutoVue components.

    So that we can help make it clear to our team, can you help me understand how much extra work is expected by your team now that AutoVue is a separate install?

    It will also help to understand how many of your customers you expect will want/require the use of AutoVue going forward.

    Chris Tsangarides
    Product Manager
    Accruent