Takes 1 parameter, a formatting mask
Takes 1 parameter, a formatting mask
Takes two parameters, a source value, and a formatting mask.
Takes 1 parameter, a formatting mask
Takes 1 parameter, a formatting mask
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
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.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
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.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Takes one parameter, a date of the form yyyy-mm-dd
Takes one parameter, in the form of: Table|{Alias}|Field
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.
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 one parameter, Source
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, ErrMsg
Takes two parameters, Title, Path
Takes two parameters, Location, Mode
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, a Source value.
Takes one parameter, a string containing a date and time
Takes one parameter, a string containing a date
Takes one parameter, FieldName
Takes one parameter, a string containing a date and time
Takes one parameter, a numeric value
Takes one parameter
Takes one parameter.
Has no params
Takes three parameters Method, URL, Body
Takes one parameter, a value in number of bytes.
Takes one parameter, Source
Takes one parameter, bNoHeader
Takes one parameter, a top query destination variable
Takes one parameter, Source
Takes two parameters, Source, Search
Has two parameters: Source, Options
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Takes one parameter, a Date value
Has one parameter, Options
Takes two parameters, FileName, Options
Takes three parameters, FieldBase, Fields, IfLenFld
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes two parameters, FileName, bUseHeaders
Takes three parameters, FieldBase, Fields, IfLenFld
Takes two parameters, WorkFieldBase + FieldToParse, Delimiter
Takes two parameters, Data, bHasHeader
Takes two parameters, FieldBase, PivotField
Takes three parameters, FieldBase, Destination, SourceFields
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bNotResponsive, bInverted, HtmlPre, HtmlApn
Has no parameters.
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
A command to help build spreadsheets
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes one parameter, QuantityToAdd
Takes one parameter, TableName
Takes one parameter, Name
Takes two parameters, FieldBase, FieldNamesList
Takes no parameters
Takes three parameters, Location, Mode, TemplateName
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Location, Mode, ActionPath, Name, Class, Prompt
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes no parameters
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes one parameter, FilePath
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes a single variable, the relative path to the directory from root of project
Takes 5 parameters, FieldBase, Destination, Action, Source, IfLenFld
Used to manipulate a WorkQuery into a JSON type
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Has no parameters
Takes no parameters
Has no parameters.
Takes one parameter.
Has no parameters.
Takes 3 parameters, Trigger, DestinationID, Path
Has no parameters.
Has no parameters.
Accepts 3 parameters, first is required, 2nd and 3rd are optional.
Takes one parameter.
Has no parameters.
Accepts a numeric value as a parameter.
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. If the Parameter is just the single word Checkbox, then instead of a drop down list with values, the user will be given a single checkbox: If the field is unchecked the value will be blank, and if it is checked the value will be "y". When used with a Top Query in MOX, this will ensure the field value matches one of the options, if not it will throw a run time error.
Has no parameters.
Accepts a numeric value as a parameter.
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 using the Content Management aspects of the Moxie.Build system.
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.
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.
Web Portals & Databases
This is our current Terms of Service, last updated 2016-01-12.
Has no parameters.
Takes one parameter which is the keyboard key which will be used as the Access Key for a given Database Table's field.
*Note: By default, each Field's Access Key will be initialized to the first character of the Field's Label.
The MOX language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
Moxie.Build, in short, may be used and licensed free of charge for education, development, or non-profit organizations. Whenever it is deployed by government or for-profit organizations to a production environment 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.
This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.
This is our current Privacy Policy, last updated 2016-01-12.
Takes a variable number of parameters.
Takes one parameter, ServerLogText
Takes one parameter, Value
Used as a scoping keyword, similar to WorkWith/End WorkWith .
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes a variable number of conditional statements
Has one parameter.
Takes one parameter, TestCondition
Takes one parameter, Source
Has no parameters
Has no parameters. If the field is blank it will remain blank.
A traditional way to check for hard errors and enable those errors to error softly.
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
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.
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.
Effective Websites. Downtown Quality, Small Town Affordability.
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.
Has no parameters.
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 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 two parameters, FolderPath, Action
Takes a single parameter, a QueryName
Takes a single parameter, a FieldBase
Takes 3 parameters, Destination, Action, Source
Has no parameters
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Has no parameters