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.
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.
An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.
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.
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.
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.
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 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.
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.
Private Method contained within a given procedure.
Takes one parameter, ProcedureName
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.
For small and simple procedures that are not expected to grow in complexity over time, simple routing based on URL parameter values from a [Pull] directly from the Request query is sufficient and requires less code. For complex procedures that are expected to grow and evolve over time, a larger more robust foundation for the routing should be used.
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.
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.
Takes a variable number of parameters
Takes one parameter, FilePath
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes no parameters
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 two parameters, FileName, bHasHeader
Used as a scoping keyword, similar to WorkWith/End WorkWith .
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, Text, Title
Takes two parameters, Location, Mode
Takes one parameter, Value
Takes one parameter.
Takes three parameters, Url, InputQuery, OutputQuery
Takes a variable number of conditional statements to compare against a single source
Takes two parameters, Title, Path
Takes two parameters, Location, Mode
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes 3 parameters, Location, Mode, Text
Takes one parameter, Source
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
Has no parameters
Takes one parameter, TableName
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes one parameter, TableName
Takes two parameters, a TableName and ProcName
Has no parameters.
Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
Takes no parameters.
Takes one parameter, TestCondition
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.
Accepts a space separated list of field names.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
Takes a variable number of parameters
Has no parameters
Parameter is divided into two parts, the Test and the Result if True. The test comes prior to the keyword of Then and the Result if True comes after.
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 learned about Managing Files .
Has one parameter.
Takes a variable number of conditional statements
Has no parameters
Takes any unspecified data, intended for use by external systems
Has one parameter, a Content.Lang prefix
Takes one parameter, a Label
Takes one parameter, the text of the exception to throw.
Takes one parameter, the text of the error to throw.
Takes one parameter, the Name of the critical section
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes no parameters
See Text Operators