UI musings.
I'm in the beginning phases of designing the next version of our work order management system. The current version is in MS Access, and we're going to write the next one using ASP.NET and a BPM package.
In the current version, there are specific screens for each job function, but they're all pretty much pointing at the same core table called WO, short for work order. Using ASP.NET, I can either design separate screens for each job function. I can also make one screen and show only the functions available to the current user based on their security level and row. There are pros and cons to each.
Your thoughts?
In the current version, there are specific screens for each job function, but they're all pretty much pointing at the same core table called WO, short for work order. Using ASP.NET, I can either design separate screens for each job function. I can also make one screen and show only the functions available to the current user based on their security level and row. There are pros and cons to each.
Your thoughts?
