Takes one parameter
Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals
Takes one existing Source value, and two parameters, Search, NewVal
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
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.
Upgrade Notes
In order to Upgrade an existing copy of Moxie.Build V4 or V5 to the most recent version of V5, you can use the Upgrade example files found in the Tools folder to help automate upgrading multi-service systems, or you can just replace the following files/folders:
Moxie.exe
Moxie.dll
Default.dll
/DBStore/BuiltIn.*
/Lib
/Public/BuiltIn
/Templates/Admin
/Templates/Clean
/Templates/Default
/Templates/Default5
/Templates/Report
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes one parameter, TableName
Takes one parameter, a single character
Takes 5 parameters, FieldBase, FolderPath, Action, Source, IfLenFld
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes a variable number of parameters
Takes two parameters, FieldBase, FieldNamesList
Takes one parameter, TableName
Takes two parameters, Location, Mode
Takes three parameters, Location, ClassNames, AlertText
Takes 6 parameters, Location, Mode, ActionLabel, ActionScript, Class, Extra.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, Source
Takes one parameter, Source
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, Extra.
Takes 3 parameters, Location, Mode, Text
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes one parameter, Type
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, TableName and a boolean expression
Has no parameters
Takes two parameters, Location, Mode
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes two parameters, Location, Mode
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes two parameters, [WorkWith]+Scope, EmbedScope
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes no parameters
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes 6 parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes 4 parameters, FieldBase, Destination, SourceFields, Delimiter
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes up to 6 parameters, FieldBase, Destination, Action, Source, Value, IfLenField
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
A command to help build spreadsheets
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes three parameters, FieldBase, Destination, SourceFields
Takes two parameters, FieldBase, PivotField
Takes three parameters, FieldBase, Fields, IfLenFld
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.
Accepts a space separated list of field names.
Takes three parameters
Accepts 3 parameters, first is required, 2nd and 3rd are optional. A trailing optional expression after an = sign may also assign a value on the same line.
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 Public Method may be called from any other Procedure, by the Default plug-in as part of the CMS.
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.
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.
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.Build , or when troubleshooting server errors.
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.
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.
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".
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.
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.
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.
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.
Takes one parameter.
Accepts a numeric value as a parameter.
This style guide provides comprehensive standards for writing clean, maintainable, and consistent MOX code for Moxie.Build. Code examples on this page are for illustrative purposes and are only intended to demonstrate style conventions.
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.
Takes 3 parameters, Event, DestinationID, Path
Takes two parameters, FileName, FileData
Takes one parameter, Source
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Takes two parameters: Username, GroupTypes
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.
Takes one parameter.
Takes one parameter, a numeric value
Takes one parameter, Source
Takes three parameters, TableName, Alias, Password
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, Source
Takes one parameter, a Source value
Takes one parameter, Source value
A set of instructions that can be called with parameters to run in the current scope.
Takes one parameter, a comma separated list of FieldNames
Takes two parameters, FileName, FileData
Takes 3 parameters, DestinationQuery, SourceQuery, bMoveIt
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Takes a variable number of conditional logical if statements
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.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes a variable number of parameters
Takes a variable number of conditional statements to compare against a single source
Takes one parameter, ServerLogText
Cloudflare automatically provides free client-facing certificates for your domain, even when 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 when you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.