Originally Posted by
mlx52
My feeling on the widget is that unless it's a simple task like checking someone in, or boarding an "on-time" flight, native SHARES will still need to be used to re issue a ticket, interline, etc. Much in the way that when FastAir, first rolled out many agents found it easier to enter native Apollo for more complex tasks (although in this case, they won't have a choice). What I don't know is if like FastAir, Check It will be the foundation for the GUI or is a temp solution.
People I have spoken with have said that the full FastAir replacement is still being developed, however, I have the fear that they will implement the widget and go with the mentality of "good enough."
I spoke with a very experienced UA TA tonight and we discussed the transition to SHARES. She mentioned the large increase in the amount of time and typing required for most functions using the current implementation of SHARES and the impact this would have on the ability of agents to help customers.
We also discussed the new GUI that was in development and she reiterated that it was expected at the end of 2012. She was hopeful that the new GUI would bring her capabilities at least back to what she currently has with the legacy UA system.
Another part of our conversation was about the reasoning behind switching to SHARES even though it was not as customer friendly (in her opinion) as the legacy UA system. She understood the corporate rationale behind changing and was willing to work very hard to make things function with the new system.
Our conversation seemed to be right in line with what I've been reading in the more reasoned posts on FT about the changeover to SHARES.