Some 90 days ago we changed the ProvideX business, in that
we licensed support of our non-Sage ERP customers to a third party. What I want
to accomplish in this entry is describe to you how that has benefited Sage ERP MAS
90 and 200.
We actually started on this journey before October with the
work we did to support the Sage ERP MAS 200 SQL release 4.45. The work on the
ADO interface, and associated performance enhancements, was done with an
exclusive focus on its utility to the 4.45 release. Some of our external
customers did benefit from the ADO interface which is great for them, and they
were not our focus.
Change is never easy, and saying good bye to the great
people we have worked with around the world was difficult. What this change has
brought to the team is a singular purpose, and with it renewed enthusiasm and
energy. Supporting non-Sage ERP customers meant balancing the needs of Sage ERP
products and our external customers. This was not always easy. For example, we
supported more than thirty different operating systems when you take versioning
into account. Some of those platforms were quite old which restricted what we
could do with the source code. So what does our new reality look like?
The first thing we did was drop every platform except a
couple of Linux variants. No, I am not saying we are going to support Sage ERP
MAS 90 and 200 on Linux, I am saying that we are not eliminating the
possibility of doing that (If you like that idea, go vote for it on the MAS 90
and 200 feedback site: http://www.sagemas.com/MAS_90_200_feedback). That
freed up a bunch of our time which we are now dedicating to listening to our
customer, namely Sage ERP MAS 90 and 200.
Secondly, when a new feature is proposed that requires the
modification of either the ProvideX language, or the ProvideX development
environment, we only have to ask one question:
Is this the right feature for the MAS 90 and 200 customer?
In the past we asked that question, and then we had to ask
“How does that affect our other customers?”, and “What platforms will this work
on?”, and “Will anyone need it work another way?”. Suddenly a simple change
which could have dramatic effects on the usability of MAS 90 and 200 becomes a
complex web of dependencies. Now we make the change if it is the right change
for MAS 90 and 200 customers, and then we test it extensively with Sage ERP MAS
90 and 200, a vastly simplified development process.
So we are very excited to be fully integrated into the
Sage ERP group, contributing to better products for our Sage customers.
on:
Sage ERP MAS 200 for SQL Version 4.45 and Improvem..
ebjelovs
