Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes one parameter, Name
Has no parameters
Has no parameters
Takes no parameters
Takes one parameter, an IPv4 Address
Takes no parameters
Takes one parameter, Name
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes one parameter, FieldName
Takes one parameter, a comma separated list of FieldNames
Takes 3 parameters, QueryName, SourceQuery, bWork
Takes one parameter, QueryName
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes one parameter, Name
Takes two parameters, FieldBase, FieldNamesList
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes a single parameter, a QueryName
Takes two parameters, FileName, bHasHeader
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes two parameters, FileName, bHasHeader
Takes a single Field name, with an optional Not operator, followed by the conditional statement
Has 5 parameters, DestFileName, Action, SrcFileName, Val1, Val2
Takes three parameters, ServerName, Port, bSecure, Send
Takes three parameters, Location, ClassNames, AlertText
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, TableName, IfLenFld
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, Name, Value
Takes one parameter, FieldName
Takes two parameters, DBTableName, DBTableRecordAlias
Takes one parameter, TableName
Takes two parameters, Name, Value
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters: Username, GroupTypes
Takes one parameter, FieldName
Takes two parameters, FileName, FileData
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes up to 6 parameters, FieldBase, FileName, Action, Val1, Val2, IfLenField
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
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.
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNameList
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes one parameter, TableName
Takes two parameters, a TableName1 and TableName2
Takes one parameter, TableName
Takes one parameter, TableName
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes two parameters, FileName, bUseHeader
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes two parameters, FileName, bUseHeaders
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, FileName, bUseHeader
Takes one parameter, TableName
Takes two parameters, TableName and a boolean expression
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes two parameters, a TableName and ProcName
Takes two parameters, a TableName and FieldName
Takes two parameters, TableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes one parameter, TableName
Takes one parameter, the name of a database table
Parameter must first specify only looking at Parents ( PARENT ) or only looking at Children ( CHILD ). The remainder of the parameter should be the table and field name you are after in the form of TableName.FieldName.
Takes two parameters, FileName, Options
Takes two parameters, FieldBase, FieldNames
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes three parameters, Location, Mode, TemplateName
Takes two parameters, name, value
Takes one parameter, the Name of the critical section
Takes one parameter, the name of the query
Takes one parameter, TableName
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes two parameters, FileName, bHasHeader
Parameter is a single new field name or a space separated list of new field names.
Parameter is a space separated list of field names to be displayed.
Takes one parameter, TableName
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.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
Takes one parameter, Name
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNames
Accepts a space separated list of field names.
Takes two parameters, TableName, IfLenFld
Takes one parameter, TableName
Takes two parameters, TableName, RecordAlias
Takes one parameter, TableName
Takes one parameter, TableName
Takes two parameters, TableName, FieldList
Takes three parameters, TableName, Alias, Password
Takes two parameters, TableName, AutoAlias
Takes three parameters, TableName, Alias, Password
Takes two parameters, ChildTableName, Mode
Takes one parameter, TableName
Takes two parameters, ChildTableName, Mode
Takes two parameters, TableName, ProcList
Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml
Takes two parameters, QueryName, Title
Takes two parameters, FileName, URL
Takes one parameter, FieldName
Takes two parameters, the variable name and a value
Takes one parameter, ProcedureName
Takes one parameter, QueryName
Takes 1 Parameter which is the Table name that you want to count the Attached Records in. The specified Table must be a Child of the calling Record's Table.
Takes two parameters, TableName, RltnList
Takes one parameter, QueryName
Takes two parameters, FieldName, Value
Parameter is the table and field name that you want to sum in the form of TableName.FieldName. The specified Table must be a Child of the calling Record.
Takes one parameter, a domain name
Takes two parameters, FieldBase, FieldNamesList
A command to help build spreadsheets
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, FieldBase, SortFieldList
Takes three parameters, Login, Password, bRememberMe
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes one parameter, Data
Takes two parameters, [WorkWith]+Scope, EmbedScope
Has no parameters.
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes two parameters, Location, Mode
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes 3 parameters, Folder, Filter, bShowImgSize
Takes one parameter, a FieldBase
Takes two parameters, ExcelTableData, Options
Takes a variable number of parameters
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes one parameter, a single character
Takes three parameters, FieldBase, Destination, SourceFields
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes two parameters, FieldBase, PivotField
Takes two parameters, FilePath, bUseHeader
Takes no parameters.
Takes one parameter, FilePath
Takes no parameters
Takes one parameter, FieldBaseToTrim
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
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
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
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 PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS 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.
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 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 one parameter, a Label
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes six parameters, DestQuery, SourceQuery, DestDestFld, DestXFld, DestYFld, SourceYFld
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes a single parameter, a FieldBase
Has no parameters
Takes one parameter, the URL to purge from CloudFlare's cache
Takes two parameters, FolderPath, Action
Takes 3 parameters, Destination, Action, Source
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.
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".
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
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.
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.
Developing in Moxie.Build on localhost give you the advantage of working with the template files natively. When working on procedures (MOX code) you need to access that through the Procedures page in the Admin area of a Moxie.Build system, if running the server on localhost or on a remote server. When running on a remote server, you can edit the template files via the Files page in the Admin area.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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 managing files and folders in the Moxie.Build system.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
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.
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.Build , or when troubleshooting server errors.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes one parameter.
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
Takes 3 parameters, Trigger, DestinationID, Path
Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
Takes five parameters, DestQuery, SourceQuery, SourceXFld, SourceYFld, SourceZFld
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, Source
Takes one parameter, a top query destination variable
Takes one parameter, Source
Has one parameter, Options
Takes three parameters Method, URL, Body
Has no parameters
Takes one parameter, a path-mask
Takes two parameters, User and Password
Has no parameters
Takes one parameter, Type
Has no parameters
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 2 parameters, pString1, pString2
Takes 2 parameters, pNum1, pNum2
Takes two parameters, Location, Mode
Takes 3 parameters, Location, Mode, Text
Takes no parameters
Takes one parameter, FieldBase
Takes one parameter, FieldBase
Cloudflare automatically provides free client-facing certificates for your domain, even if using their free service. In addition, they provide free Origin Certificates to encrypt the connection between Cloudflare and your origin Moxie.Build server. Use this article if you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.
Takes one parameter, FilePath
Takes a variable number of parameters
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes any unspecified data, intended for use by external systems
Takes a variable number of parameters.
Takes three parameters, Url, InputQuery, OutputQuery
Takes no parameters
Takes one parameter.
Parameter is a space separated list of fields to choose from
Takes no parameters
Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
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.
Takes one parameter, TestCondition
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.