Introduction to RASON
About RASON Models and the RASON Server
Rason Subscriptions
Rason Web IDE
Creating and Running a Decision Flow
Defining Your Optimization Model
Defining Your Simulation Model
Performing Sensitivity Analysis
Defining Your Stochastic Optimization Model
Defining Your Data Science Model
Defining Custom Types
Defining Custom Functions
Defining Your Decision Table
Defining Contexts
Using the REST API
REST API Quick Call Endpoints
REST API Endpoints
Decision Flow REST API Endpoints
OData Endpoints
OData Service for Decision Flows
Creating Your Own Application
Using Arrays, For, Loops and Tables
Organization Accounts

Model Versions

Every RASON model (named or unnamed) or decision flow that is posted to the RASON Server will have a resource ID of the model instance that was run (including "quick" or synchronous calls). Although for synchronous calls (such as POST rason.net/api/optimize, POST rason.net/api/simulate, etc.) the resource ID will never be referenced by the RASON client; it only appears in the JSON response and the RASON event log (see below). This new resource ID is now included in the "status" returned for each response as "id": resourceId; for example:

  
    "status":{
       "code": 0,
       "id": "11+2019-03-15-00-56-32-664488",
       "codeText": "Solver found a solution.  All constraints and optimality
        conditions are satisfied."
    },
  

Every model/flow that is updated on the RASON Server (via PUT rason.net/api/model/{nameorid}) will have a new ID for the new version; the old ID will identify the old version. GET rason.net/api/model/id can be used to retrieve the text of the current or any past version. Resources are persisted until explicitly deleted by a user and model text is stored under the resource ID. The result is a simple "version control system". Users can reference any model version desired.

Back to Model Names