An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.
Takes one parameter, ProcedureName
Moxie.Build, in short, may be used and licensed free of charge for education and non-profit organizations. Whenever it is used by government or for-profit organizations the license is granted on a subscription basis.
Moxie.Build includes a number of open source components as part of its distribution; each is subject to their own licenses as included with the files for those components.
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes two parameters, Source, Value
Takes two parameters, Source, Options
Takes two parameters, Source, AllowedCharacters (case sensitive)
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes one parameter, Type
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 three parameters, Location, ClassNames, AlertText
Has one parameter, Options
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Has one parameter.
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
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 2 parameters, pString1, pString2
Takes two parameters Command, Options
Takes 2 parameters, pNum1, pNum2
Takes one parameter, TableName
Takes two parameters, FileName, Options
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Has 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 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes no parameters
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes two parameters, TableName, IfLenFld
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes two parameters, FieldBase, FieldNameList
Takes two parameters, Data, Options
Takes two parameters, FieldBase, FieldNamesList
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Has six parameters, UniqueParent, DestField, FieldBase, UniqueChild, EmbedFields, Options
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 3 parameters, Event, DestinationID, Path
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.
Accepts a numeric value as a parameter.
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.
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.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
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.
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.
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 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.
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 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".
Takes a variable number of conditional statements to compare against a single source
Takes three parameters, Url, InputQuery, OutputQuery
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
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.
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.
We empower your customers to take action.
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 three parameters, Destination, Action, Source
Private Method contained within a given procedure.
Takes any unspecified data, intended for use by external systems
Takes a variable number of conditional logical if statements