I spent the day at the Users Group meeting for JL Systems last week. JL is introducing a new product, called “New NOAH” (as far as I can tell).
The system is fully browser-based (which is a change from their Access-based legacy system) and is based on the DotNetNuke development framework. This is significant because JL can now tap into a broad range of developers who are building “snap ins” for the DotNetNuke platform, which may allow it to bring new tools to its AMS more quickly.
There are some nice new features, including the ability to modify screens so that you’re seeing the data that’s important to you, in a way that is useful to you. This new product is a nice leap forward for JL, whose NOAH product was getting pretty long in the tooth.
Performance of the database during the meeting was abysmal. Screen changes took many seconds to refresh. I’m going to give JL the benefit of the doubt and blame this on 50 people sharing one wireless access point, and all hitting a development server. But like all browser-based applications, JL needs to pay close attention to performance and screen refresh speeds. This will be especially true of their legacy clients moving from relatively fast Access program to a browser.
Full disclosure: EDM is an independent third-party consulting firm. This means we have no financial relationship with any of the vendors mentioned in this blog. We provide unbiased opinions on what we see.