SOFTWARE DEVELOPMENT KIT (SDK)

The SDK Access Module allows clients to run 3rd Party Applications which link to Sage Evolution.  Developers can also use the Full SDK to interface to Sage Evolution. 

A software development kit (SDK or "devkit") is typically a set of software development tools that allows for the creation of applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, or similar development platform.

The SDK has two portions to it:

 

SDK developer - This is not available on evaluation basis and to gain access to it, you will have to purchase the software. This software is the portion the developer would use to write the integration between their third party application and Sage Evolution.

 

SDK connector - This is available on an evaluation basis and to gain access to it, we can arrange temporary registration to be issued if you need to try the third party program, alternatively, you can purchase the SDK Access Module. This enables whatever integration was written to ‘talk’ to Sage. This is the part an end-user would need to purchase to use integration written by a developer.

 

One Developer can have multiple clients connecting to it as it is re-usable. Therefore, the Developers have to purchase ONE SDK DEVELOPER but every client using their integration has to purchase a connector (SDK Access Module).

A software development kit (SDK or "devkit") is typically a set of software development tools that allows for the creation of applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, or similar development platform.

 

If you are the developer and will use the development in house, you do not have to purchase the SDK connector. However, if you opt to resell your developed software, your clients will have to purchase the SDK connector.

 

The SDK itself is compatible with all versions of Sage, you would however need to write the integration itself to be compatible as well.

 

The Sage SDK is typically used for transaction processing and account maintenance, and these records can originate from any external source, whether it is an external database, XML, web service, or custom user interface. The Sage SDK consists of an Application Programming Interface (API) that exposes typical Sage functionality to application developers.

 

 

The API embeds Sage business logic enabling external applications to interact directly with Sage databases. Third party developers can currently interface with Sage on the database level; however, through the introduction of the SDK, the relevant processing logic gets taken care of, development time is dramatically reduced, and data integrity is ensured.

 

Since the Sage SDK is packaged as a Microsoft .NET 2.0 assembly, the ideal platform for utilising the SDK is of course the .NET framework. However, to accommodate the many third party developers utilising various other mainstream languages, integration through COM is possible using development environments such as Visual Basic 6, Visual C++, Visual Basic for Applications, and Delphi.

 

 

The following Sage modules are currently supported, in whole or in part.

 

  • General Ledger
  • Accounts Receivable
  • Accounts Payable
  • Inventory
  • Order Entry(Sales and Purchase Orders)
  • Serial Number Tracking
  • Multi-Warehousing
  • Customer Account Consolidation
  • Job Costing

 

You would thus need to define the business and application process on how you will process invoices, receipts etc.