Precisely Enterworks

 View Only

  • 1.  Best Practices: Version Upgrades

    Posted 07-27-2021 13:26
    Hello EnterWorks User Community!

    We've been in Enterworks for a few short years now, and we would like to hear some best practices that other companies have implemented.  I may post a few questions on best practices in this forum, but I bet there are many things that we haven't even thought of yet.  We' love to hear your thoughts and experiences as well.

    One topic that has been on our minds recently:  how often do you upgrade versions?  Every release?  Only when there is functionality or a fix that you need?  Some other timing?

    We'd love to hear what your company is doing.

    Thanks!

    ------------------------------
    Tracy Ishman | Senior Product Data Analyst
    Steelcase, Inc | 2312255012
    ------------------------------


  • 2.  RE: Best Practices: Version Upgrades

    Employee
    Posted 08-16-2021 02:00
    Tracy,

    For minor releases, the general recommendation is to upgrade on an as-needed basis.  If a new patch/revision addresses one or more issues that affect your implementation, or includes new functionality that you want to use, then it would be appropriate to deploy the appropriate or patch/revision.  Since it will be necessary to conduct regression testing for a patch, it may make sense to update to the latest revision/patch.  The accumulative list of changes between the current, in-use version and the candidate patch should be reviewed to assess the scope of regression testing that may be required (changes for functionality that is not being used can be ignored).  Unless scheduling and resource limitations make it impossible to upgrade to the latest revision/patch, then selecting the oldest revision/patch containing the needed fixes/enhancements will reduce the amount of testing required while still providing the needed changes.

    There is an advantage to periodically updating to the latest release.  First, it provides the latest fixes and new functionality.  But more importantly, it will reduce the scope of subsequent changes should an even newer revision/patch be required to address any newly-discovered issue.

    -Brian

    ------------------------------
    Brian Zupke | Senior Technical Support Engineer
    Winshuttle North America | 9099009179
    ------------------------------

    Original Message