|
Long-time customers may recall the problems faced when we
upgraded from version 6 to version 7. Then we were no longer
able to read the old binary format files from previous versions.
This made it imperative to convert everything before the
migration. What is worse, is that the saved components formerly
usable in previous versions were no longer usable at all. We had
to go back to a previous install and save them in the new format.
The main problem was that the new format had several bugs. We
did not employ it for this reason, and our advice was to use the
old format when people reported all sorts of problems. Forcing
customers to use the new format in 7.0 did actually force these
issues to become highlighted, so most were fixed by 7.1. There
were some, like the default field usage issue, that never did get
fixed. Listening to customers when we reported the errors in
version 6 could have saved a lot of problems for all concerned.
In the move from version 5 to version 6, there were a huge
number of minor but important changes. We know the list well,
as we had more version 5 systems running than most. Most
systems took a month or more to update. Much of the
functionality just had to be rewritten.
Fortunately there have not been any upheavals like that up to
now. Most updates have been minor and cosmetic, or consisted of
additional features that did not much affect many existing ones.
That is, up until now. For this upgrade, although much of the
existing functionality will ostensibly work as is, there is quite a
bit that will not. Accordingly you have to plan how to firstly find
out what will and won’t work, and how you can manage to fix that
which will not, even before you consider the rewrite.
|
1. The Benefits of Metastorm BPM ...
