Private Method contained within a given procedure.
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.
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.
In this example, you will see how to use a public method that works on or with the current WorkQuery that you pass into the method.
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 three parameters Method, URL, Body
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, FilePath
Cloudflare automatically provides free client-facing certificates for your domain, even if 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 if you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.
Takes one parameter, OutputText
Takes a variable number of parameters.
Takes three parameters, Url, InputQuery, OutputQuery
Takes a variable number of conditional statements to compare against a single source
Takes one parameter, SlowWritePercent
Takes a variable number of parameters
Has no parameters
Takes no parameters
Takes two parameters Command, Options
Takes two parameters, TableName, IfLenFld
Takes two parameters, Location, Mode
Takes no parameters
Takes three parameters, FieldBase, Fields, IfLenFld
Takes two parameters, Location, Mode
Takes three parameters, FieldBase, Fields, IfLenFld
A .mox file, with MOX code in it, can be run from the command line while a Moxie.Build system is not otherwise already running.
Takes no parameters
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
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.
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.
An Include Procedure cannot be executed directly, the contents of its source code can only be Included into other Procedures using the Include command.
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.
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.
A set of instructions that can be called with parameters to run in the current scope.
Takes one parameter, ProcedureName
Takes one parameter, Control
Takes one parameter, QueryName
Takes no parameters
Takes a variable number of parameters
Takes a variable number of conditional statements
Takes one parameter, a Label