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