Introduction Leap JSON is a specification that dictates how a client should request resources and how a server should respond to the request. Leap JSON requires use the Leap JSON media-type application/vnd.leap+json for exchanging data. Conventions The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”,…
Status This page represents version 1.0 of the Leap JSON Request specification. New versions of Leap JSON will always be backward compatible; using a never remove, only add strategy. To request changes to the specification or report an error please contact support. Request Format This section describes the structure of…
The attached license covers the use of several pieces of IP owned by Softeon, Inc. Including but not limited to: Leap Framework, ElasticWMS Application, Leap Application Infrastructure, and Leap Event-Streams. See the attached 2020 license file.
We often get the question – why features? When we started thinking about the idea of creating an entirely new architecture, we felt like we had to take a step back and really start with High-Level Business problem statements, work them into high-level solutions, and then, finally, into architecture/technical solutions….
Brief Architecture When developing new Forms and Flows it’s not necessary for a complete understanding or in-depth coverage of all parts of the Form Flow Engine. Instead, we will focus on the parts of the architecture that we will be interacting with the most: Web Client and Engine Client. Web…
Welcome to WordPress. This is your first post. Edit or delete it, then start writing!