Search Results for input

 

Public Method

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.

 

PaaS

Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery

 

Remote

Takes three parameters, Url, InputQuery, OutputQuery

 

Trigger

Takes two parameter, URL, InputQuery

 

ApplyLang$

Takes one parameter

 

AmPm$

Takes one parameter

 

[TQName]

Has no parameters

 

InStrAny%

Takes two parameters, Source, Match

 

InStr$

Takes two parameters, Source, Match

 

InStr%

Takes two parameters, Source, Match

 

[DateTime] (Top Query)

Has no parameters

 

TRONLog

Takes one parameter, OutputText

 

TRON

Takes one parameter, FilePath

 

 

[Time] (Top Query)

Has no parameters

 

 

ETableStream

Takes two parameters, ExcelTableData, Options

 

Lookup

Takes six parameters, FieldBase, Destination, Table, Alias, SourceField, IfLenFld

 

HttpsEnsure

Takes no parameters.

 

WithGroup

Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld

 

SSReference

A command to help build spreadsheets

 

FixFields

Takes one parameter, a single character

 

HtmlUpload

Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText

 

JsonEncode$

Has two parameters: Source, Options

 

IsValidAlias$

Takes one parameter, a Source value

 

InStrAny$

Takes two parameters, Source, Match

 

WebSafe$

Takes one parameter, Source

 

TimeDif$

Takes two parameters, Source, Value

 

RecoverHtml$

Takes one parameter, EscapedHTMLString, and returns the Unescaped Version of this string

 

Thread

Takes a variable number of parameters

 

[Placeholder]

Takes one parameter

 

[Min]

Accepts a numeric value as a parameter.

 

[MaxLen]

Accepts a numeric value as a parameter.

 

Message Handler

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.

 

Table Action

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.

 

[Time] (DB Field Attribute)

Has no parameters.

 

MOX Coding and Programing Language Syntax Documentation

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.

 

Learn More about Frontend Development

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.

 

 

[Max]

Accepts a numeric value as a parameter.

 

[DatePicker]

Takes no parameters

 

[Custom] HTML Field Attribute

Allows any extra HTML Attributes to be specified in the Control's HTML Tag

 

PaaS Method

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.

 

NewEComQuery

Takes one parameter, QueryName

 

ForEach

Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]

 

ProcECom

Takes one parameter, QueryName

 

SaveFile

Takes two parameters, FileName, FileData

 

[Pull] List of Fields from another Query

Takes three parameters, QueryName, FieldBase, FieldNames

 

Record Report

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.

 

Record Action

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 Report

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.

 

Remote 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.