Takes one parameter, Source
Takes one parameter, Source
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes three parameters, Url, InputQuery, OutputQuery
Takes one parameter, the URL to purge from CloudFlare's cache
Takes three parameters Method, URL, Body
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.
Takes two parameters, FileName, URL
Takes two parameter, URL, InputQuery
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, Title, Path
Takes one parameter, Source
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes one parameter, SessionID
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
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.
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.
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.
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.
Takes 3 parameters, Trigger, DestinationID, Path
Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
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.
Markdown enables simple formatting of plain text via easy to remember conventions. This page will provide you with some pointers on what formatting options are available with "Moxie Flavored Markdown".
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 is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Has no params
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
A traditional way to check for hard errors and enable those errors to error softly.
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.
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.
Has one parameter, a Content.Lang prefix
Takes 2 parameters, Result, Status