Sage 300 ERP 2012
Our Sage 300 ERP 2012 release is now in beta. I thought I’d put together a blog post that summarizes and lists all the other blog posts I’ve written for this release along with a few updates on things that made it into the release since these were written.
When we release Sage 300 ERP, it isn’t just the core ERP modules, it also includes many other Sage integrated products, many of which we are now supporting new versions as well. Plus Sage 300 ERP acts as a platform for many third party modules that extend Sage 300 ERP into many vertical industries.
Summary of Articles on Sage 300 ERP 2012
Here are the various components of Sage 300 ERP 2012 that I’ve blogged on:
Sage Advisor Update
Sage Advisor PEP
Sage 300 ERP 2012 Payment Processing
Sage 300 ERP Inquiry Queries for 2012
Value Added Application Features for Sage 300 ERP 2012
Sage Visual Process Flows
What’s New in the Sage CRM Integration for Sage 300 ERP 2012
SageCRM 7.1 Released
Sage 300 on Windows 8
Sage 300 ERP 2012 Supported Platforms
SData Enhancements for Sage 300 ERP 2012
SData Referenced Resources
All in all quite a large and varied set of new features and services.
Roadmap diagrams are always dangerous to put in a blog posting, since once posted, this will be on the Internet for a long time. And as always things are continuously subject to change. At this point the 2012 release is looking good, we were code complete back in June, we are now in beta and our regression testing is going well.
Updates On Previous Blog Posts
Just a few updates since all the previous blog posts.
First we are still adding tweaks here and there to Sage 300. For instance one of the leading causes of tech support calls is from people that tried to activate a new version without backing up their database first. Then activation fails and their database is half converted, now what to do? So tech support asked R&D to change the activation warning screen from just popping up a warning message box, which everyone ignores, to the following:
The hope of this is that it gets more attention and that more people will back up their data before performing activation. Generally we look at the leading reasons for calls to tech support and see if we can alleviate them in the program by making things clearer, easier or better documented.
I blogged on the new functionality in payment processing (credit card processing) earlier in the development process. At that point the team working on it was feature complete on what they had promised for the release. However since then, they have taken the time to incorporate User Centered Design advice into the feature to make it much easier to use. As a result the screens look quite different from my original blog posting. For instance below is the updated screen for capturing batches of pre-authorized payments.
In a similar way the team has made quite a few tweaks throughout the various screens related to credit card processing to either reduce the number of screens, or provide ways to fill them in easier (like providing a way to default addresses), or generally making the labels much clearer. Hopefully all these usability changes will make our Sage Exchange integration a much more enjoyable feature.
By the same token, the Sage Advisor Update screen has gone through several usability revisions and looks much better now. Since this feature is all about update, the first thing that will probably be updated on your system is this component, since it likes to update itself.
For Lanpak usage, we no longer use multiple lanpaks if you login to multiple companies on the same workstation. However we will continue to use multiple lanpaks if you login using multiple Sage 300 users. This should help with the TCO for companies that divide their accounting across multiple Sage 300 company databases.
Quality Debt Reduction
With every release we want to improve the quality of Sage 300 ERP. With this release we have cataloged all known defects at the start of the release and a release certification requirement is that the number of total defects must be lower at release by 15%. So from release to release the number of open defects is reducing. There is also a lot of work going on so we prioritize these defects so that the ones that affect customers the most (based on severity and frequency) will be fixed first. We want to ensure this isn’t a numbers game where we just fix lots of issues about under-lining or field widths in reports. The real aim to ensure we have real measurable metrics that are published in a dashboard that is visible to everyone in Sage up to the CEO, to ensure we are improving quality in a real and measurable way. At this point our quality debt reduction stands at 45%; hopefully, this will improve a bit further by release.
We have a lot of new functionality in the Sage 300 ERP 2012 release. Please check out the beta, if you are qualified. This release leverages shared components from other Sage groups such as the Visual Process Flow tool from the Sage ERP X3 group, the Sage Advisor Update from Sage UK and Sage Advisor PEP from the Sage 50 US team in Atlanta. There are improvements to the platform with enhanced SData support, paving the way for future development. There are many application features. There is updated platform support and updated support for newer versions of other integrated Sage products.
The Sage 300 ERP development group is very excited about this release, and hope everyone has a great experience with it.