Takes one parameter, Source
Takes one parameter, bNoHeaders
Takes two parameters Command, Options
Takes one parameter, Type
Takes two parameters, Source, Options
Takes two parameters, Source, Value
Takes one parameter, Index
Takes two parameters, SourceValue, Width
Takes two parameters, Source, Options
Takes two parameter: FieldName, Delimiter
Takes two parameters, Source, Values
Has two parameters: Source, Name
Takes two parameters, Source, OptionsAndSecret
Takes one parameter, TableName
Takes two parameters, FileName, bUseHeader
Takes two parameters, FileName, Options
Takes two parameters, FilePath, bUseHeader
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes up to 6 parameters, FieldBase, Destination, Action, Source, Value, IfLenField
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Has no parameters
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, Data, Options
Has one parameter.
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 as part of the CMS.
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 2 parameters, Result, Status
Takes two parameters, SubjectPrefix, EmailBody
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.
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.
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".
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
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.
Has no parameters.
Takes two parameters, SourceValue, Position
Has no parameters
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
Takes one parameter bNoHeaders and returns the result to an assigned variable
Takes two parameters, User and Password
Takes two parameters, SourceValue, Width
Takes one parameter.
Takes a variable number of conditional statements to compare against a single source
Has 4 parameters, Destination, Action, Source, Value
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.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes two parameters, FilePath, ForceFlush