Takes one parameter, TableName
Takes one parameter, a Source value
Takes one parameter, TableName
Takes one parameter, a Source value
Takes one parameter, TableName
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, ChildTableName, Mode
Takes one parameter, in the form of: Table|{Alias}|Field
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes two parameters, TableName, RecordAlias
Takes two parameters, TableName, AutoAlias
Takes three parameters, TableName, Alias, Password
Takes three parameters, TableName, Alias, Password
Takes two parameters, DBTableName, DBTableRecordAlias
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Has no parameters
Takes two parameters, ChildTableName, Mode
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes two parameters, TableName and a boolean expression
Takes two parameters, a TableName and FieldName
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, FileName, Options
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Has no parameters.
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, Location, Mode
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes two parameters, Name, Value
Takes no parameters
Takes a variable number of parameters
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, FieldBase, FieldNameList
Takes one parameter, a single character
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes one parameter, a Label
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
Has no parameters
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List in the Admin interface.
A traditional way to check for hard errors and enable those errors to error softly.
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Parameter is a space separated list of field names to be displayed.
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 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 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, Source
Takes one parameter.
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.
Has one parameter, Options
Takes one parameter, a top query destination variable
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, Extra.
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.
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
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.
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. To use different values than labels, for each comma separated pair, specify the value first inside of { } followed by the label.
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 this attribute is used with a Top Query in MOX, it will ensure the field value matches one of the options; if not, it will throw a run time error.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running
Takes two parameters: Username, GroupTypes
Takes one parameter.
Takes two parameters, User and Password