Search Results for based

 

Query Based Routing Example

For small and simple procedures that are not expected to grow in complexity over time, simple routing based on URL parameter values from a [Pull] directly from the Request query is sufficient and requires less code. For complex procedures that are expected to grow and evolve over time, a larger more robust foundation for the routing should be used.

 

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.

 

EmptyTable

Takes one parameter, the name of a database table

 

EnsureNavFields

Takes two parameters, FieldBase, FieldNamesList

 

ReplaceAny$

Takes one existing Source value, and two parameters of equal length, SearchVals, NewVals

 

Encrypt$

Takes two parameters, SourceValue, EncryptionKey

 

Dir$

Takes one parameter, a path-mask

 

FolderExists$

Takes one parameter, the path of the folder

 

Exists$

Takes two parameters, DBTableName, DBTableRecordAlias

 

HtmlDropdown

Takes 5 parameters, Location, Mode, Title, Element, Class

 

SSReference

A command to help build spreadsheets

 

HtmlNavbar

Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bNotResponsive, bInverted, HtmlPre, HtmlApn

 

HtmlNav

Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn

 

KeepFor

Takes two parameters, FromIndex, ToIndex

 

ETableStream

Takes two parameters, ExcelTableData, Options

 

Parse

Takes seven parameters, FieldBase, Destination, Source, bAny, Delimiter, Item, IfLenFld

 

KeepIf

Takes 4 parameters, FieldBase, Left, Comparison, Right

 

Day$

Takes one parameter, a date

 

[Ajax]

Takes 3 parameters, Trigger, DestinationID, Path

 

 

Licensing

Moxie.Build, in short, may be used and licensed free of charge for education, development, or non-profit organizations. Whenever it is deployed by government or for-profit organizations to a production environment 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.

 

Get Started with Setting up the Development Environment

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.

 

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.

 

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.

 

PaaS

Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery

 

Cloudflare Integration

Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services

 

Folder

Takes two parameters, FolderPath, Action

 

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.

 

File

Takes 3 parameters, Destination, Action, Source