Takes one parameter, TableName
Takes one parameter, a Source value
Takes one parameter, TableName
Takes one parameter, a Source value
Takes three parameters, TableName, Alias, Password
Takes two parameters, the User Alias, and the User PW to check
Takes two parameters, TableName, RecordAlias
Takes one parameter, in the form of: Table|{Alias}|Field
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes two parameters, DBTableName, DBTableRecordAlias
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes no parameters
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes two parameters, ChildTableName, Mode
Has no parameters
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, a FieldBase and FieldNamesList
Takes two parameters, TableName and a boolean expression
Takes two parameters, TableName, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes two parameters, Location, Mode
Has no parameters.
Takes two parameters, FileName, Options
Takes one parameter, a single character
Takes two parameters, FieldBase, FieldNameList
Takes a variable number of parameters
Takes two parameters, FieldBase, FieldNamesList
Used to manipulate a WorkQuery into a JSON type
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes one parameter, a Label
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Some Work Query command parameters can accept a source of either a Work Query Field name or a text literal. Text literals in these cases are prefixed with a backtick ` character.
This utility program manages a server install with one or many Moxie.Build services running by taking care of nightly tasks via a scheduled task
A traditional way to check for hard errors and enable those errors to error softly.
Has no parameters
Parameter is a space separated list of field names to be displayed.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results.
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List.
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 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.
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.
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 four parameters, FieldBase, Destination, Source, IfLenFld
Has one parameter, Options
Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, Extra.
Takes one parameter, a top query destination variable
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.
Parameter is a comma separated list (using CSV rules and not in quotes) of the options made available to the user which are enforced on save. If the Parameter is just the single word Checkbox, then instead of a drop down list with values, the user will be given a single checkbox: If the field is unchecked the value will be blank, and if it is checked the value will be "y". When used with a Top Query in MOX, this will ensure the field value matches one of the options, if not it will throw a run time error.
Takes one parameter.
Takes one parameter.