Use Sidebar LHS to navigate
For global help click here

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 Version History

Version 1 Next »

SaaSplications is an extremely flexible system - but everyone says that - so how are we different?

We develop very fast

When we build applications - we do not build tables

  • We build objects and the logic to be triggered by events on those objects
  • The application server takes care of creating the tables for us during runtime
  • So development is much faster and less risky
  • However reporting tools can still connect using SQL

When we extend we use object inheritance

  • So building an order for clothing uses 95% of the standard order object and adds additional functionality
  • Using central capabilities reduces work involved in extensions
  • So we can develop new functionality rapidly - building on what we have already
  • So Improvements in shared fields on a object are available everywhere they are used
  • So industry specialty areas do not age and get left behind

Our system only runs on our cloud servers

  • We do not have to develop or support for multiple platforms
  • So all our development is ALL application feature improvements

Easy integration, easy screens on devices

No Screens contain logic

  • All logic is on the server
  • All communication with the server is via secure XML linked to a secure session - see Wikipedia on XML  "XML has come into common use for the interchange of data over the Internet."
  • All screens use XML to communicate with the Server linked to a secure session
  • So any screen is a painting exercise (ie just put the fields on the screen) - eg: webstores / customer portals as well as in house screens
  • So screens can be rapidly developed in any medium by anyone who knows that medium (java, html, html5, iphone, android, wordpress, etc = anything)
  • So the system is device agnostic requiring only the required screens to be painted and the fields wired up.

Low bandwidth requirement

Every touch is a round trip to the server

  • The system is chatty - every time a field is updated - the server responds (in many cases no response is required)
  • small packets sent and received of data only
  • So lowest possible bandwith required = fast speed
  • So do not lose work as system stays up to date
  • So values may change as you work through a screen or table
  • There is only one version of the Code

Every company is using the same code

  • The system runs on our cloud hosted servers only - ie we do not have to build and support for multiple platforms
  • So any problem is a problem for every customer - ie a bigger problem for us that for any individual customer
  • So every customer has access to every improvement (subject to licensing)
  • Multiple Enhancements are released daily - often during the day

Records are not "Locked"

  • If multiple persons edit a record then the second person will get a message "this record has been updated" and can be refreshed


  • No labels