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.
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes three parameters, Url, InputQuery, OutputQuery
Takes two parameter, URL, InputQuery
Has no parameters
Has no parameters
Has no parameters
Takes two parameters, Source, Match
Takes one parameter
Takes one parameter
Takes one parameter, FilePath
Takes two parameters, FileName, FileData
Takes three parameters, QueryName, FieldBase, FieldNames
Has no parameters
Has no parameters
Takes one parameter, OutputText
Takes two parameters, ExcelTableData, Options
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes no parameters.
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
A command to help build spreadsheets
Takes one parameter, a single character
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Has two parameters: Source, Options
Takes one parameter, a Source value
Accepts a numeric value as a parameter.
Accepts a numeric value as a parameter.
Has no parameters.
Has no parameters.
Takes one parameter
Accepts a numeric value as a parameter.
Has no parameters.
This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.
Prerequisites: This tutorial assumes that you have already set up a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.
Takes no parameters
Allows any extra HTML Attributes to be specified in the Control's HTML Tag
The MOX language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
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.
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes one parameter, QueryName
Takes one parameter, QueryName
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.
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.
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.
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.
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.