Search Results for request

 

Get Started with Development Examples

This list of examples is going to grow over time. We are open to requests, as well as submissions if you have something you would like to share.

 

Query Based Routing Example

For small and simple procedures that are not expected to grow in complexity over time, simple routing based on URL parameter values from a [Pull] directly from the Request query is sufficient and requires less code. For complex procedures that are expected to grow and evolve over time, a larger more robust foundation for the routing should be used.

 

HttpSoap$

Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml

 

HttpCookie

Takes 6 parameters, Name, Value, Path, Domain, Expires, Other

 

Tcp$

Takes three parameters, ServerName, Port, bSecure, Send

 

UrlEncode$

Takes one parameter, Source

 

HtmlHistory

Takes two parameters, Title, Path

 

Command Line with .mox file

A .mox file, with MOX code in it, can be run from the command line while a Moxie.Build system is not otherwise already running.

 

Cloudflare Integration

Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services

 

Moxie.cfg Config

The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running

 

Http$

Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders

 

CFApi$

Takes three parameters Method, URL, Body

 

Pull

Takes three parameters, QueryName, FieldBase, FieldNames

 

Parse

Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld

 

Text

Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld

 

Value

Takes four parameters, FieldBase, Destination, Function, IfLenFld

 

Time

Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld

 

LoadTableFields

Takes one parameter, TableName

 

Raw

Takes one parameter, the contents of which are used for the HTTP Reply Body

 

ETableStream

Takes two parameters, ExcelTableData, Options

 

Num

Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld

 

Geo

Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld

 

WorkIf

Takes one parameter, FieldName

 

PaaS Method

A PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS statement is used.

 

Message Handler

A Message Handler is only ever called by the Database on a Database Event. These Event Messages allow a Developer to intercept operations taking place on a per-record level and implement Event based business logic.

 

Record Action

Record Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Record.

 

Public Method

A Public Method may be called from any other Procedure, by the Default plug-in, or a Custom COM DLL. Each Public Method may either use specific Input Parameters, or it may accept an Input Query.

 

MOX Coding and Programing Language Syntax Documentation

The MOX coding and programming language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.

 

 

Table Action

Table Actions are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As an Action, the Procedure is expected to perform some sort of task, such as an automated set of updates to the Database Table.

 

Folder and File Structure

Brief overview on the file structure and contents under Moxie. The files and folders discussed in this post are those that are essential when upgrading to the most recent version of Moxie , or when troubleshooting server errors.

 

Record Report

Record Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.

 

LangWith

Has one parameter, a Content.Lang prefix

 

Foreign

Takes a single parameter, a QueryName

 

SaveHttpFile

Takes two parameters, FileName, URL

 

[Pull] List of Fields from another Query

Takes three parameters, QueryName, FieldBase, FieldNames

 

Table Report

Table Reports are presented to the users of the Default Admin interface and are also intended to be made available in a dynamic way to users of a customized front end. As a Report, the Procedure is expected to produce output to be displayed to the user.

 

Remote Method

A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.

 

ETableReply

Takes 2 parameters, Result, Status

 

[Ensure] Field Exists

Takes a variable number of parameters, a comma separated list of TopQuery variable names