Takes one parameter, TableName
Takes one parameter, TableName
Takes one parameter, TableName
Takes one parameter, TableName
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
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 two parameters, a TableName1 and TableName2
Takes two parameters, a TableName and ProcName
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 two parameters, a TableName and FieldName
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes one parameter, the name of a database table
Takes one parameter, TableName
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes one parameter, TableName
Takes two parameters, ExcelTableData, Options
Takes one parameter, TableName
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
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 two parameters, TableName, AutoAlias
Takes two parameters, TableName, FieldList
Takes two parameters, TableName, ProcList
Takes two parameters, TableName, RltnList
Has no parameters
Takes one parameter, Source
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes one parameter, a Source value
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 2 parameters, Result, Status
Takes two parameters, TableName and a boolean expression
Takes three parameters, TableName, Alias, Password
Takes one parameter, TableName
Takes one parameter, TableName
Takes one parameter, in the form of: Table|{Alias}|Field
Takes two parameters, ChildTableName, Mode
Takes two parameters, ChildTableName, Mode
Takes two parameters, DBTableName, DBTableRecordAlias
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes two parameters, TableName, IfLenFld
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters, TableName, IfLenFld
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes one parameter, TableName
Takes two parameters, TableName, RecordAlias
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes one parameter, TableName
Takes one parameter, TableName
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
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.
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.
Compress any value/table
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.
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.
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.
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.
Takes two parameters, Name, Value
Takes two parameters, Name, Value
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
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.
Has one parameter
Has one parameter.
Parameter is a space separated list of field names to be displayed.
Takes one 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.
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 one parameter.
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.
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
A command to help build spreadsheets
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FileName, Options
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Has no parameters.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes two parameters, FieldBase, FieldNamesList
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes one parameter, Data
Takes two parameters, FieldBase, FieldNames
Takes one parameter, a single character
Takes one parameter, FieldBaseToTrim
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes one parameter, FieldName
Takes no parameters
Has no parameters
Takes no parameters
Takes one parameter, Source
Has one parameter, a Content.Lang prefix
Takes two parameters: Username, GroupTypes
Takes any unspecified data, intended for use by external systems
Has one parameter, Options
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.
Takes one parameter, a Label
Takes one parameter.
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 three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, User and Password
Has one parameter.
Has no params
Has no params
Has no parameters
Takes three parameters Method, URL, Body
Takes one parameter, Control
Takes no parameters
Takes a single parameter, Source
Takes one parameter, Source
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes one parameter, FieldName
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
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.
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 one parameter, the URL to purge from CloudFlare's cache
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.
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.
Has no parameters.
Has no parameters
Has no parameters
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.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Accepts a space separated list of field names.
Has no parameters
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes two parameters, SubjectPrefix, EmailBody
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes one parameter, Index
Takes one parameter, Type
Takes one parameter, the Name of the critical section
Takes two parameters Command, Options
Takes one parameter, a List of possible group types
Takes one parameter, Name