Takes one parameter, TableName
Takes one parameter, TableName
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes two parameters, a TableName1 and TableName2
Takes two parameters, a TableName and ProcName
Takes one parameter, the name of a database table
Takes one parameter, TableName
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, FieldList
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes one parameter, TableName
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
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 seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes two parameters, TableName, ProcList
Takes two parameters, ExcelTableData, Options
Takes two parameters, TableName, RltnList
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 one parameter, TableName
Takes two parameters, a TableName and FieldName
Takes one parameter, TableName
Takes one parameter, TableName
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes two parameters, TableName, AutoAlias
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes two parameters, CSVData, bNoHeaders
Takes two parameters, FileName, bHasHeader
Has no parameters
Takes two parameters, FileName, bHasHeader
Takes two parameters, Data, bHasHeader
Takes one parameter, bNoHeaders
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes one parameter, Source
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes one parameter, a Source value
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes 2 parameters, Result, Status
Takes two parameters, FileName, bUseHeader
Takes two parameters, TableName, IfLenFld
Takes three parameters, TableName, Alias, Password
Takes two parameters, TableName and a boolean expression
Takes three parameters, TableName, Alias, Password
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes one parameter, in the form of: Table|{Alias}|Field
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.
Takes one parameter, TableName
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, ChildTableName, Mode
Takes two parameters, TableName, RecordAlias
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes one parameter, TableName
Takes one parameter, TableName
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes one parameter, TableName
Takes two parameters, ChildTableName, Mode
Takes one parameter, TableName
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld
Takes two parameters, DBTableName, DBTableRecordAlias
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes two parameters, TableName, IfLenFld
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
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 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.
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.
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
In this example, we use a plain old Moxie.Build system and compare it to the MEAN Stack equivalent by building two functionally equivalent versions of a fleshed out To Do List Application. Both versions utilize local user authentication, a relational database system and the security measures found in typical production-level applications on the web today.
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.
Compress any value/table
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes one parameter, TemplateData
Takes one parameter, Type
Has no parameters.
Takes four parameters, FieldBase, Destination, Function, IfLenFld
Takes two parameters, FieldBase, SortFieldList
A command to help build spreadsheets
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes four parameters, FieldBase, FieldName, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Has no parameters
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes two parameters, Source, Value
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, Source, Value
Takes two parameters, Source, Value
Takes no parameters
Takes one parameter, a List of possible group types
Takes one parameter, Source
Takes two parameters Command, Options
Takes one parameter, Name
Takes one parameter, Source
Takes one parameter, Source
Takes two parameters, Title, Path
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes one parameter, Source
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, Source
Takes two parameters, FieldBase, FieldNamesList
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes one parameter, a single character
Takes nine parameters, FieldBase, Destination, Function, Source1, Source2, Source3, Source4, Options, IfLenFld
Takes one parameter, FieldName
Takes no parameters
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes a variable number of parameters
Takes two parameters, Name, Value
Takes one parameter, Data
Takes no parameters
Takes two parameters, FieldBase, FieldNames
Takes two parameters, FieldBase, FieldNamesList
Takes two parameters, Name, Value
Takes two parameters, FieldBase, FieldNameList
Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld
Takes three parameters, FieldBase, Destination, SourceFields
Takes one parameter, QuantityToAdd
Has no parameters
Takes two parameters, FileName, Options
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes three parameters, FieldBase, Fields, IfLenFld
Takes three parameters, QueryName, FieldBase, FieldNames
Takes two parameters, FileName, bHasHeader
Takes one parameter, FilePath
Takes two parameters, PathToFile, Options
Takes two parameters, Data, Boundary
Takes 5 parameters, FieldBase, GroupBy, MergeField, Delimiter, bKeepBlanks
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Has no parameters
Takes one parameter, FieldBaseToTrim
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
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.
Has no parameters
Accepts a space separated list of field names.
Takes three parameters
[Col] takes one parameter
Takes one parameter
Parameter is a space separated list of field names to be displayed.
Has no parameters.
Parameter is a space separated list of field names to be displayed when the user is viewing results from the Search List in the Admin interface.
Takes one parameter, the Name of the critical section
Takes four parameters, DestinationQuery, SourceQuery, UniqueField, UniqueValue
Takes two parameters, destinationQuery, sourceQuery
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
Has no parameters
Takes two parameters, SubjectPrefix, EmailBody
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 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 two parameters, DestinationQuery, SourceQuery
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.
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".
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.
Takes 3 parameters, Event, DestinationID, Path
Takes 1 parameter, a formatting mask
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.
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.
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.
Has 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.
Takes one parameter.
Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.
Has one parameter
Accepts a numeric value as a parameter.
Has no parameters.
Has no parameters.
Parameter is a value or an expression to be used when a record is created if no value is specified during the creation. The value or expression is run through the Assignment Attribute in order to calculate it's result.
Accepts one parameter which is the raw HTML content to be placed in the form, above the Field's location.
Takes 1 parameter, a formatting mask
Accepts one parameter which is the raw HTML content to be placed in the form, below the Field's location.
Takes a single parameter, a QueryName
Takes no parameters
Takes two parameter: FieldName, Delimiter
Takes one parameter, FieldName
Takes two parameters: Username, GroupTypes
Takes a single parameter, Source
Takes one parameter, Source
Has one parameter.
Takes two parameters, User and Password
Takes three parameters Method, URL, Body
Takes one parameter, Source
Takes one parameter, Source
Has no params
Has no parameters
Takes one parameter, Index
Takes one parameter, Source
Takes one parameter, HtmlEscapedString, and returns the Unescaped Version of this string
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 one parameter, Source
Has one parameter, Options
Has two parameters: Source, Options
Takes one parameter, Source
Takes one parameter, Source
Takes two parameters, Source, Value
Takes three parameters, Url, InputQuery, OutputQuery
Takes three parameters, QueryName, FieldBase, FieldNames
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes one parameter, SlowWritePercent
Takes a variable number of parameters
Takes one parameter, ServerLogText
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, a Label
Takes a single parameter, a FieldBase
Takes one parameter, Control
Takes any unspecified data, intended for use by external systems
Has one parameter, a Content.Lang prefix
Takes no parameters
Takes one parameter.
Takes no parameters.
Takes one parameter
Has no parameters
Has no params
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.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
A traditional way to check for hard errors and enable those errors to error softly.
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.
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.