Takes a variable number of parameters
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.
Takes one parameter, OutputText
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes three parameters, Url, InputQuery, OutputQuery
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.
Takes 3 parameters, Location, Mode, Text
Has one parameter, Options
Takes two parameters, Source, Value
Takes one parameter, Source
Has two parameters: Source, Options
Takes two parameters, name, value
Takes three parameters, Location, ClassNames, AlertText
Takes two parameters, Title, Path
Takes one parameter, Source
Takes 2 parameters, pNum1, pNum2
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes two parameters, Source , Search
Takes one parameter, bNoHeaders
Takes 2 parameters, pString1, pString2
Takes one parameter, a top query destination variable
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes two parameters, FileName, Options
Takes two parameters, FileName, bUseHeader
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes no parameters
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes two parameters, FilePath, bUseHeader
Takes one parameter, Type
Takes two parameters, FieldBase, FieldNamesList
Takes one parameter, Name
Takes one parameter, Status
Takes three parameters, Location, Mode, TemplateName
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes three parameters, QueryName, FieldBase, FieldNames
Takes no parameters
Takes one parameter, a single character
Takes two parameters, Data, Options
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
Has no parameters
Has one parameter, a Content.Lang prefix
Takes one parameter, QueryName
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Has no parameters
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.
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 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.
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.
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.
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.
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.
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.
Takes one parameter
Takes one parameter bNoHeaders and returns the result to an assigned variable
Has no parameters
Takes one parameter
Has no parameters
Has two parameters: Source, Options
Takes one parameter, a string containing a date and time
Has one parameter
Takes no parameters
Takes three parameters, QueryName, FieldBase, FieldNames
Takes a variable number of parameters.
Takes 3 parameters, QueryName, SourceQuery, bWork
Takes one parameter, QueryName
Takes one parameter, FilePath
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes two parameters, FileName, FileData
Takes two parameter, URL, InputQuery