Search Results for post

 

 

 

 

Group

Takes 7 parameters, FieldBase, GroupBy, GroupTotals, GrandTotals, Seperator, TotalPre, TotalPost

 

Folder and File Structure

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 , or when troubleshooting server errors.

 

WorkIf

Takes one parameter, FieldName

 

Moxie.cfg Config

The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running

 

Select / Case / End Select

Takes a variable number of conditional statements to compare against a single source

 

If (Not) / Then

Takes a single Field name, with an optional Not operator, followed by the conditional statement

 

If (Not) / And / Or / ElseIf / End If

Takes a variable number of conditional statements

 

Remote

Takes three parameters, Url, InputQuery, OutputQuery

 

PaaS

Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery

 

HtmlForm

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod

 

HtmlButton

Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod

 

WebSafe$

Takes one parameter, Source

 

HttpStatus

Takes one parameter, Status

 

HtmlHistory

Takes two parameters, Title, Path

 

CFApi$

Takes three parameters Method, URL, Body

 

Sort

Takes two parameters, FieldBase, SortFieldList

 

UrlEncode$

Takes one parameter, Source

 

Http$

Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders

 

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.

 

 

Privacy Policy

This is our current Privacy Policy, last updated 2016-01-12.

 

 

Learn More About the Content Management System

Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.

 

 

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.

 

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.

 

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

 

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.

 

ReorderTableRltns

Takes two parameters, TableName, RltnList

 

ReorderTableProcs

Takes two parameters, TableName, ProcList

 

EndSession

Has no parameters.