DBi Warehouse Shipments Scheduling Framework




Resources



Application
Building Blocks




DBiWSF Objects



Developer
Resources




Developer documentation



Smart Client
Web Demo





Designing with
DBiWSF
Movies


DBiWSF Intro




Data binding



DB
iWSF Objects



Business Rules



Reporting



User Interface



Integration

DBi Warehouse Shipments Scheduling Framework - Points of Integration

 

Working with the Framework Source Code

Integrating to Other Data, the dbiWSF is designed to be fully event driven. The framework includes a set of UI objects that wrap the DBI commercial UI controls to trigger events before and after changes have been made to most objects allowing tight integration with existing applications.

For example, when a shipment is created the beforeShipmentAdded event is fired. This has all the information for the shipment just created. In this event the developer can call out to their existing POS application and get a list of all orders that do not have a shipment id. You can then call up a dialog to attach that shipment to your POS data, and conversely as you have the object captured in the event, you can set the OrderID on the shipment to correspond to the data you just pulled out.

 

Integrating dbiWSF with existing systems

Combined with existing .NET applications or any POS or CRM system that has an SDK you can easily synch the data and use it throughout the dbiWSF.

 As the demo app illustrates, a modified Northwind database is connected to provide PurchaseOrders and SalesOrders to highlight some of the key features of the dbiWSF, including CargoType management, breakout docks and UI Filtering. This is one of the most powerful features of the dbiWSF product and the generalization of the event arguments makes coding a breeze.

For example, when an objShipment is modified in the dbiWSFSchedule or the dbiWSFDayView, the objShipment is returned as an event argument, not just the dbiTimeBar Item or dbiAppointment Item. That way the developer can code one method to handle the shipment change and call it from any one of the framework controls or your own custom controls.

 

Incorporate data from existing applications

The fact that the UI layer is completely isolated from the dbiWSF and dbiBusinessRules means the developer can use the same objects in any .NET interface (such as ASP.Net or Silverlight) and pass those objects between different UI layers with ease. Together with the simplicity of the framework�s databinding model (you need only add a field to the table and a corresponding property to the base object, you don�t have to change any select/insert/update/delete commands) developers can easily extend the framework objects to incorporate data from existing applications.

For example a shipment may have several unique features in your organization�s POS system that you want to incorporate at the base object level. Simply add a property to the objShipment and create a field in the Shipments table with the same name. The developer now has full access to that property anywhere the shipment is used. For implementations that require even more flexibility, the source code is fully documented and allows the developer to add their own tables and objects. By default those tables and objects will inherit the same databinding included with the product.




























       
         
         
    Introductory movies    
    Developer Resources  
    Review - developing with the Framework, a documented guide  
       
    Contact DBi  
           
      all rights reserved  |  copyright  2017   |  Terms of Use    
           
      http://www.dbi-tech.com