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.
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.
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.
Takes a variable number of parameters
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc..]
Takes one parameter, TemplateData
Takes one parameter, a top query destination variable
Takes one parameter, the contents of which are used for the HTTP Reply Body
Takes a variable number of parameters, FieldBase, Test1, Test2, [etc...]
Takes a variable number of parameters
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes 3 parameters, Location, Mode, bWithNoHeader
Takes a variable number of parameters, FieldBase, Destination, Source, Test1, Test2, [etc...]
Takes one parameter
Parameter is a space separated list of field names to be displayed.
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.
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 one parameter.
Has no parameters
The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
Takes a variable number of parameters
A traditional way to check for hard errors and enable those errors to error softly.