Time
is money!
First, let's take a look at HP Service Desk drawbacks, fially, they were the reason for this project creation.
The lack of functional capabilities, forcing to buy an expensive HP Service Desk Client license. A fact that a number of employee in big enterprises using Service Desk, could be an order of tens.
Too simple user interface could mess the one accustomed to Service Desk Client application.
The Lack of the required flexibility. An employee, responsible for the changes inclusion to the existing set of jsp pages have to think simultaneously about how not to brake the jsp-structure cohesion as a HTML-document and to take care about java-code validity, which is the same in most cases but the names of classes and variables.
Common drawback is a constantness of an object editing forms and listings. It's impossible, for example, to use a built-in to all Service Desk objects data validity control. To know about an error in a form field one have to send a request to save all the form via HTTP POST and analyse a response error messages. This limit could be removed only by building a client application as java-applet or java-program, or by building additional invisible java-applet which hides interaction with server or ... but that one would be another task.
As an advance there could be solely the fact, that this package was created and is maintained by the whole HP Service Desk developers group, having all project documentation on both open and closed API and ,naturally, biggest experience in the problem domain analyses/ program design/API design.
And now about Business Experts Addon advances. Of course, this project was created and is maintained just to overcome all of the above drawbacks, but not to be a complete replacement of HP Service Pages: it uses forms and source code for user authorisation from the Service Pages. The last isn't a big drawback, because for the autorization one have to fill in a username/password/time zome, then Service Pages Addon takes control thread.
