The Upgrade Process for May 2020 or later versions of the Application

An upgrade only takes about 5-10 minutes and is included with annual maintenance.
In May 2020 we changed the structure of the application, and we have some new changes in the app that we need to clarify for you.
Do your staff access the app form Citrix or Terminal Server
                            or
Do they launch directly from their workstations?
If from  Citrix or TS  – then you won’t notice much change.
If form workstations, the users likely have shortcuts to a common share folder.
That will approach will be changing, we would want to push the client software out to each workstation now.
Our new version of the client has an app launcher, it communicates with an internet licensing engine to check which date version of the software your Budget Administrator has chosen for you to run on.
(Being that this is ERP software, your budget administrator typically would not want the software auto-updating, without forewarning or testing, they do not want to risk anything adverse happening in the middle of a budget cycle)
If the client software version does not match the company profile, it will automatically download the appropriate version of the software for that workstation.
(so the clients will now essentially auto-update and we in IT don’t need to physically update the app for the users)
We will need you to check your firewall settings to see if you are blocking zips or dll downloads.
if so we will ask you to set up an exception for a particular URL.
Contact support for that information.
Upgrade with a SQL Server Migrations

If you are on the legacy version of the app we will have a few extra steps, we will need to know the new SQL Server Name\Instance too issue you a new physical license.

You will copy the new license into the DynamicBudgets-App folder replacing the prior license file.
You will physically copy the new application files and paste/replace in the DynamicBudgets-App folder.
If you staff run from a common share folder, you will have to have all users logout, or you will have to kill any open processes if the user is not responding.
We will work with your budget administrator, run the server config update utility and point to the new SQL server to rebuild the data adaptors to GP.
We will log into the app, goto Manage Servers, and update the SQL Server reference, test the connection, and save.
If you are on the May 2020 version of the app or later, you will inform us of the new SQL Server Name\Instance.
We’ll adjust your company profile in the licensing engine.
We will work with your budget administrator, run the server config update utility and point to the new SQL server to rebuild the data adaptors to GP.
We will log into the app, goto Manage Servers, and update the SQL Server reference, test the connection, and save.

This is the biggest advantage of the new application, users do not need to log out of the app while we run and upgrade, even if on a centrally installed TS or Citrix server, the App Launcher will download a new datestamp folder for the new build.

Active sessions can continue to work while we upgrade.
Once the upgrade is complete the budget administrator will ask your staff to log out and log back in, and their clients will download and launch the latest build of the software.