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.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Takes one parameter, the contents of which are used for the HTTP Reply Body
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.
Has one parameter, a Content.Lang prefix
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.
Has no parameters
Takes two parameters, name, value
Takes two parameters, Location, Mode
Has two parameters: Source, Name
Has one parameter.
Takes three parameters Method, URL, Body
Has one parameter
Takes one parameter, Source
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
Takes one parameter, Source
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes two parameters, Location, Mode
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
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 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes three parameters, Location, Mode, TemplateName
Takes a variable number of parameters
Has no parameters.
Takes one parameter, Type
Takes two parameters, FieldBase, FieldNamesList
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes a variable number of parameters
Takes three parameters, FieldBase, Destination, SourceFields
Takes no parameters
In order for source code to be more readily readable across teams, it is recommended that your source code always be styled according to this style guide.
This is our current Privacy Policy, last updated 2016-01-12.
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 Public Method may be called from any other Procedure, by the Default plug-in, or a Custom COM DLL. Each Public Method may either use specific Input Parameters, or it may accept an Input Query.
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.
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.
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.
A traditional way to check for hard errors and enable those errors to error softly.
Takes one parameter, ServerLogText
Takes one parameter, FieldName
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes one parameter, ProcedureName
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.
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes any unspecified data, intended for use by external systems
Has no parameters