The 2020.1 Patch: What Does It Mean to Me? FAQs
Q: When is 2020.1 scheduled for release?
A: 2020.1 is available in the coming days after this webinar’s completion. It will be announced on Tyler Community.
Q: Will this be the only patch for year-end 2020?
A: Yes, tax forms will be coded in 2020.1 only. If you are on 2019.1 already, it is a patch to get there and not a big upgrade.
Q: Are patches cumulative, or do we have to install every one?
A: Unlike the Managed Internet Update (MIU), patching in Tyler Deploy is cumulative.
Q: Can we go directly from release 2018.1 to 2020.1?
A: Yes, this is a direct upgrade path, like 2019.1.
Q: When building new servers if we are already on Tyler Deploy, how do we migrate to the new machines?
A: You would need to reach out to us to get started. A transfer tenant would be created for you to work with in Tyler Deploy.
Q: Do we need a new license key for 2020.1?
A: If you are on 2019.1, you can use that license key for 2020.1. 2018.1 clients need a new license key.
Q: Are there any pitfalls to automatic updating?
A: We cannot think of any pitfalls to configuring automatic updates in test. If you automatically update production, be sure you are ready for that code in your production environment.
Q: What credentials should I use to log into Check.TylerTech.com?
A: Here is a guide for using Check.TylerTech.com.
Q: If we update in test past our live version, but then want to revert back to match live, after using Deploy, how do we go about that?
A: Reversion in deploy (or the MIU) is difficult. The website itself is made up of thousands of files, as is the database itself. VM snapshots and db backups remain the best options for this.
Q: Do you suggest to use the Check Pre-reqs function, or can we bypass that in most cases?
A: Other Tyler products use Check Pre-reqs more than New World ERP. We built the pre-req checks into our installers themselves, so we did not need to rely on a user using Check Pre-reqs.
Q: Applying Tyler Deploy patches is a much slower process than applying MIU patches. Can it be made faster?
A: This is true; however, Tyler Deploy has better scheduling options than the MIU ever did and can email users as well when a deployment succeeds or fails. We envision Deploy as a more hands-off deployment process. Deploy is also more accurate at deploying patches as it deploys full builds instead of file deltas like the MIU, which relied on sequential updating.
Q: If we are on 2019.1 already, do we need an RFS to upgrade to 2020.1?
A: No, the hard work is already done. You can watch this video to learn how to apply the New World Orchestrator update through Tyler Deploy.
Q: Is there a specific day patches are released?
A: No, we try to release them on Fridays every other week; however, if there is a problem in the patch that we have found in testing, we will hold and release when the problem is fixed. Likewise, if there is a need to get the patch out more quickly due to a severe need, we may ship before Fridays by shifting more resources to testing the patch.
Q: What is the force redeployment option in Tyler Deploy and why would I use it?
A: Deployments will skip steps that are determined not to be needed by default. A force redeployment will deploy all steps. A good example provided in the webinar by an attendee was changing the history years in DSS that DSS pulls.
Q: Should I wait for the patch notification to hit my inbox until applying a patch?
A: There should be no need for this. This question was driven by a recent patch that had a deployment issue, which is an issue we take seriously and try to stop at every turn. When a patch has hit Tyler Deploy you should feel safe to deploy it. The lag between a patch showing up and the email going out from Tyler Community is merely a logistical process in moving paperwork through.
Q: How do we get the patch and upgrade notifications?
A: On Tyler Community, under New World ERP and Blogs, you can subscribe to notifications from the "Latest Patches" blog.
Q: Are there any known conflicts when copying live data to test when test is 2020 but prod is 2019.1.29?
A: No, the Database Upgrade Utility would be used as in prior versions. The change is aesthetic as the database upgrade would work the same.
Q: We have a one-time install scheduled to go from 2018 to 2019. Will it be best to change it to 2020, or should we let our IT use Tyler Deploy to then patch from 2019 to 2020?
A: 2020.1 is nearly immediately available. Going to 2020.1 is likely the better approach here.
Q: If we are hosted, how do we get upgraded?
A: Please create a case. Our scheduling resource has been reaching out to clients, but we may be reaching out to the wrong contacts to get something scheduled.
Q: Why do sub-patches (2019.1.33.1) not have release notes when patches (2019.1.33) do?
A: For the most part, we use the fourth digit of the numbering scheme for deployment changes only, meaning that ERP code did not change; it was an install change to make deployments go more smoothly. As such, we do not tend to publish release notes for these changes.
Q: We are building servers this summer; what version should we install first, 2019.1 or 2020.1?
A: We would recommend installing 2020.1 on the new servers.
Q: Our entity upgraded in January, 2020; why would we be on 2018.1? If 2020.1 was already released, why did they not upgrade us to 2020.1?
A: 2019.1 was available at this time, but at some sites, a decision was made on the client side to go to 2018.1 and not 2019.1, which would be a patch to 2020.1. This decision could have been made for hardware or other reasons.
"The 2020.1 Patch: What Does It Mean to Me?" Webinar Recording