Takes one parameter, a Date value
Takes one parameter, a string containing a date time
Has no parameters
Has no parameters.
Has no parameters
Has no parameters
Has no parameters.
Has no parameters.
Has no parameters.
Has no parameters.
Takes no parameters
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes one parameter, a Source value.
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Has no parameters
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes one parameter, Source
Has no parameters
Deprecated, use AmPm$
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.
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, a date
Takes one parameter, a date of the form yyyy-mm-dd
This is our current Terms of Service, last updated 2016-01-12.
This is our current Privacy Policy, last updated 2016-01-12.
Takes one parameter, Source
Takes two parameters, Source, Options
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes two parameters, Title, Path
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes one parameter, Source
Takes one parameter, Source
Takes two parameters, Source, Value
Takes one parameter, Source
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes one parameter, a gregorian number
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes one parameter, Source
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes one parameter, Source
Takes three parameters, Login, Password, bRememberMe
Takes one parameter, Source
Has one parameter, Options
Has two parameters: Source, Name
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes two parameters, ExcelTableData, Options
Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld
Takes two parameters, FieldBase, FieldNames
Takes two parameters, Name, Value
Takes no parameters
Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost
Takes two parameters, FileName, Options
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNamesList
Takes 3 parameters, Folder, Filter, bShowImgSize, bShowAccessed
Takes two parameters, a TableName and FieldName
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Has no parameters
Takes two parameters, name, value
Takes no parameters.
Takes three parameters, Login, Password, bRememberMe
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, Name, Value
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Has no parameters.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
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.
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.
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.
We empower your customers to take action.
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 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.
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.
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.
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.
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.
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.
Takes 3 parameters, Event, DestinationID, Path
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.
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.
Has no parameters
Takes three parameters Method, URL, Body
Takes one parameter, Source
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
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.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
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.
Takes no parameters
Cloudflared Tunnel exposes applications running on your local web server on any network with an internet connection with an outbound tunnel that connects directly to Cloudflare's edge network without the need to configure inbound firewall rules.
Has one parameter.
Takes three parameters, QueryName, FieldBase, FieldNames
Takes any unspecified data, intended for use by external systems
Takes one parameter, Control
Takes a single Field name to test if it is true, with an optional Not operator to test if false, followed by the conditional statement
Takes one parameter, SlowWritePercent
A type of Prefix which allows the developer to separate blocks of code into organized, defined parts to help provide clarity of the logical block and add structure to the code.