Takes a variable number of parameters
Takes no parameters
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
A set of instructions that can be called with parameters to run in the current scope.
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 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.
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.
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.
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 three parameters, Location, Mode, TemplateName
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes one parameter, Status
Has two parameters: Source, Options
Takes one parameter, Type
Takes one parameter, Name
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
Takes one parameter, a path-mask
Takes one parameter, TemplateData
Has two parameters: Source, Options
Takes two parameters: Username, GroupTypes
Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes two parameters Command, Options
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Has one parameter, Options
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes 2 parameters, pNum1, pNum2
Takes one parameter, Source
Takes 2 parameters, pString1, pString2
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Has no parameters.
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes two parameters, Data, Options
Takes one parameter, FieldName
Takes no parameters
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 four parameters, FieldBase, Destination, Source, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes two parameters, FieldBase, FieldNamesList
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes one parameter, TableName
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Has no parameters
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
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 four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, Name, Value
Takes two parameters, TableName, IfLenFld
Takes one parameter, Source
Has no parameters
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.
Parameter is a space separated list of field names to be displayed.
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.
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.
Takes one parameter, the URL to purge from CloudFlare's cache
Takes one parameter, the Name of the critical section
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.
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.
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.
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.
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.
Moxie.Build supports translating any user-facing text into multiple languages from a single database table. Procedures, templates, and database field metadata all share the same translation store, so a string written once is reusable everywhere.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
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".
Accepts a numeric value as a parameter.
Has one parameter
Takes 3 parameters, Event, DestinationID, Path
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.
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.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes a variable number of parameters
Takes two parameter, URL, InputQuery
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
Takes one parameter
Takes three parameters Method, URL, Body
Takes one parameter
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 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, Value
Takes one parameter, a Label
Takes a variable number of conditional logical if statements
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Takes two parameters, SubjectPrefix, EmailBody
Takes no parameters
Has one parameter.
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes three parameters, Url, InputQuery, OutputQuery
Takes one parameter, QueryName
Has no parameters
Private Method contained within a given procedure.