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.
An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes one parameter, ServerLogText
Takes one parameter, FieldName
Takes a variable number of parameters
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes six parameters, FieldBase, Destination, Source, Left, Comparison, Right
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes a variable number of parameters
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
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.
This is our current Privacy Policy, last updated 2016-01-12.
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 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.
Takes one parameter, ProcedureName
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.
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.