Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The eLandings team recommends making use of the eLandings public web services. This will allow third-party developers much more flexibility in their development to build exactly what the users need and want. Making use of the web services will also make it far easier to automate data exports from eLandings and imports to eLandings from third-party applications. For example, if a third-party application makes use of the public web services, the third-party application could:

  • Easily create code to update the third-party database from eLandings automatically on a given time interval (for example, every 5 minutes)
  • Easily create a button within the third-party application called "Get Reports" to get a list of landing/production reports from eLandings that match 22 search criteria.
  • Easily create a button within the third-party application to "Get Report" to get a landing/production report from eLandings
  • Easily create a button within the third-party application to "Save Report" or ¿Submit Report¿ to the eLandings system
  • Easily create a button within the third-party application to "Get User Info" associated with a eLandings user id

The eLandings team recognizes that making use of eLandings public web services requires skilled programmers. Programmers who are unfamiliar with the concepts of web services and XML data handling, may find initial success more difficult using this approach. Development timelines should reflect developers familiarity with these concepts.

  • No labels