ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.
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.
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 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.
Takes one parameter, the name of a database table
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.
Takes two parameters, TableName and a boolean expression
Takes 3 parameters, ParentTableName, ChildTableName, IfLenFld
Has no parameters
Takes three parameters, TableName, Alias, Password
Takes 4 parameters, TableName, Relation, OtherTableName, and a boolean expression (optional)
Takes 3 parameters, ParentTableName, ChildTableName, and a boolean expression (optional)
Takes one parameter, TableName
Takes two parameters, a TableName and FieldName
Takes two parameters, Source, Value
Takes one parameter, Name
Takes one parameter, Source
Takes two parameters, Source, Value
Takes one parameter, Source
Takes two parameters, Title, Path
Takes two parameters, Source, Value
Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string
Takes one parameter, TableName
Has no parameters
Takes one parameter, TemplateData
Takes one parameter, EscapedTemplate, and returns the Unescaped Version of this string
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, TableName
Takes one parameter, FilePath
Has no parameters
Takes three parameters, FieldBase, OldFieldName, NewFieldName
Takes 4 parameters, FieldBase, Left, Comparison, Right
Takes 3 parameters, FieldBase, Fields, SearchTerms
Takes two parameters, Data, Boundary
Takes one parameter, QuantityToAdd
Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes no parameters
Takes three parameters, FieldBase, Fields, IfLenFld
Takes six parameters, FieldBase, Destination, Function, Source, Value, IfLenFld
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes four parameters, TableName, Relation, OtherTableName, IfLenFld
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes 4 parameters, TableName, Relation, OtherTableName, IfLenFld
Takes one parameter, TableName
Takes one parameter, TableName
Has no parameters
Takes three parameters, TableName, Alias, Password
Takes one parameter, TableName
Takes two parameters, TableName, IfLenFld
Takes two parameters, TableName, IfLenFld
Takes three parameters, TableName, SearchTerms, SearchInFields
Takes two parameters, Name, Value
Takes no parameters
Takes one parameter, Source
Accepts a numeric value as a parameter.
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.
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.
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.
A Public Method may be called from any other Procedure, by the Default plug-in as part of the CMS.
Has no parameters.
Has no parameters
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
Takes 3 parameters, Event, DestinationID, Path
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 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 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, below the Field's location.
Takes 1 parameter, a formatting mask
Has no parameters.
Has no parameters.
Takes one parameter, Source
Takes one parameter, FieldName
Takes one parameter.
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, Source
Takes one parameter, in the form of: Table|{Alias}|Field
Takes no parameters.
Has no parameters
Takes any unspecified data, intended for use by external systems
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.
Takes one parameter, Control
A traditional way to check for hard errors and enable those errors to error softly.
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
Takes a variable number of parameters
Takes one parameter, SlowWritePercent