We've reached a point where QBO 3 is now being used in PROD environments (ETS), and forms the core of new development (Valuations Hub, SkipTrace, Freddie DCS, VIP Collect).
So far, the bulk of QBO 3 address user interface and bulk database operations. The next tactical steps include:
IService interface: ability to invoke QDS service orders from QBO 3 classes
Ability to invoke QBO 3 methods from QBO 2.0 events (rebuild of the Event Handler Service on .NET 4)
Ability to process imports from QBO 3 (mostly a UI exercise now)
Ability to generate documents from QBO 3
UI components needed:
Alert / Notification control and behavior
Widget pop-in and pop-out
Calendar control
Photo control
Import wizard control
Strategic items include:
Implementing IQueue interface to handle queuing and async processing
Implementing Decision processing
Flushing out use cases for an IImport interface
Implementing INotification (data listeners and method listeners)
Future thoughts:
Observer pattern across classes:
Process/RaiseEvent "Bankruptcy Declared"
raise this event though the ObjectTree
need a configuration section to define what to do upon seeing a particular event raised
common pattern with notifications?
Thoughts from the AWS Conference - Nov 18, 2013 3:5:58 PM