Experiences with EB2.1 .netui interface

[Leo van Delft]

Hi,

I am curious about experiences with the new interface of QAD the so called .netui.
Questions I have:

• How is the performance?
• Are there possible ways to tune it?
• What infrastructure, hardware software, do you have and how many users.
• How do the users react?
• What about support, simplified screens new browsers favorites etc.

And of anything else you can think of in this matter.

Regards,

Leo

 

[gatsbyinca]

• How is the performance?

Performance depends on what your users are used to...if they are coming from a ChUI / GUI system that flys then they will be disappointed. We tried to get all users onto .NET UI after our recent upgrade but there was a near riot on the 1st day...so we reintroduced GUI for the users that do high data entry intensive jobs (in our case...Customer Service & Shipping). Still, there are complaints from time to time...but the other users accept the .NET UI.

• Are there possible ways to tune it?

I don't know...but you can simplify screens to eliminate fields that require no data entry and even entire frames if possible.

• What infrastructure, hardware software, do you have and how many users.

Windows, Dell & ~60 users

• How do the users react?

Near riot if they do hands down data entry! The big killer for us was the inability to "type ahead" i.e. for experienced users, they know the screens and what data is required. In our version of .NET UI, it didn't support the concept of "type ahead". My understanding is that as of the current release (requires SP6 of eB2.1), this problem has been addressed. Too late for us but definately worth investigating if I was you.

• What about support, simplified screens new browsers favorites etc.

It's good stuff and QAD are moving in the right direction IMHO. Support is good out of QAD tech support. I think most of the guys are in NJ.