Hello, we are having some weird little issues with a variety of things, and every time we call and get them fixed but they recently mentioned that they have an update from 19.0.0 to 19.1.1 but there isn't a what's new document for this update so does anyone know what this specifically addresses because I really don't want to go through the hassle if its some little stuff. Thanks!
Solved! Go to Solution.
Hello @ianjonesvb
The newest release, as of now, is v19.0.1.11 and the biggest issue this release resolved was the problem with generating the Short Call List report. This was a patch release and not a major release, so there will likely be additional patches to fix other things in the near future.
Hello @ianjonesvb
The newest release, as of now, is v19.0.1.11 and the biggest issue this release resolved was the problem with generating the Short Call List report. This was a patch release and not a major release, so there will likely be additional patches to fix other things in the near future.
How does "development" prioritize which issues (they are numerous, believe me) that should tackled first? For instance, there are many issues with v.18 xxx, for instance just to name one off the bat the cause of the balance mismatches, that will just carry forward with each release ....
And, furthermore, does the release of v.19.xxxx indicate that there will be no more further releases of previous updates? So, if that's the case, then v.18 is at a standstill?
Lastly, will development make public the future "patches" and specific issues that it deems fixed?
@ianjonesvb you hit the nail on the proverbial head. You stated there's little difference between v.18 and v.19, so go ahead and upgrade. My point is ... when are ALL (I'll even be happy with SOME) of the issues that have been brought to development's attention, and reported I may add, not just here in the Exchange, but elsewhere, and not only by dental offices, but also by Support techs, going to be corrected? For example, suppose there is an issue/bug/problem "A", Support knows about it, has figured out work around "B" to overcome the issue. After sometime has passed, issue "A" is no longer an issue, and can be .... let's just say ... "it's been reported" .... crickets ... crickets .... I gave one example - balance mismatches (I believe caused by epayments, v.2) ... there are many more ...
I see you asked about how we prioritise the defects that go into each release. There are a few things we look at when building out a release and choosing the defects to address. The first being the impact the defect has on an office, and its ability to continue business as usual with it place, those with the highest impact make it further up the list. The second is the number of customers it affects, we use data from our support calls to help us understand the number of users who are encountering the issue whilst they go about their business. Then finally we look at time, often there are a bunch of small size defects, spelling mistakes, refresh issues etc, whilst not impactful on your business are a daily annoyance, so once we have the killer defects defined and added to the release we add in the filler defects to keep us busy until our release deadline. Hope this all makes sense.
Carestream Dental LLC
3625 Cumberland Blvd. Ste. 700
Atlanta, GA 30339
© 2019 Carestream Dental, LLC. All Rights Reserved