Search Results for custom

 

[Custom] HTML (DB Field Attribute)

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

 

TemplateCustom

Takes one parameter, TemplateData

 

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.

 

Wisebox Solutions Inc.

We empower your customers to take action.

 

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.

 

Get Started by Making it Your Own

This video demonstrates how to get started with Moxie.Build with basic customization.

 

Moxie.Build for Developers

Moxie.Build Keeps it Simple The full stack in one app, delivered by one company. Coding with the MOX server side scripting language is concise, well structured, and keeps your focus on the data. Use Moxie.Build in your company to pull together resources, centralize data, customize business workflows, and act as a highly accessible web portal for staff and customers alike.

 

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

 

AntiCsrf$

Has no params

 

[Meta]

Takes no parameters

 

Ctid$

Has one parameter.

 

Raw

Takes one parameter, the contents of which are used for the HTTP Reply Body

 

Format$

Takes two parameters, a source value, and a formatting mask.

 

Meta

Takes any unspecified data, intended for use by external systems

 

CFPurge

Takes one parameter, the URL to purge from CloudFlare's cache

 

Setup Table

The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.

 

[#] Format (Top Query)

Takes 1 parameter, a formatting mask

 

[_#] Format if not blank (Top Query)

Takes 1 parameter, a formatting mask

 

TemplateType

Takes one parameter, Type

 

HtmlNav

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

 

SendEmail

Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld

 

HtmlNavbar

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

 

HtmlTable

Takes 6 parameters, Location, Mode, Class, bNoHeader, bNoAutoAlign, bNoIDTags

 

HtmlRaw

Takes 3 parameters, Location, Mode, bWithNoHeader

 

SkipCalls

Takes no parameters

 

NewTable

Takes two parameters, TableName, AutoAlias

 

Format

Takes five parameters, FieldBase, FieldList, Mask, bBlanks2Zero, IfLenFld

 

SaveRawFile

Takes two parameters, FileName, bUseHeaders

 

Plus8Encode

Takes three parameters, FieldBase, Fields, IfLenFld

 

 

[Raw] Raw HTML

Accepts one parameter which is the raw HTML content to be placed in the form at the Field's location.

 

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

 

 

[_#] Format if not blank (DB Field Attribute)

Takes 1 parameter, a formatting mask

 

Templates Documentation

Prerequisites: This tutorial assumes that you have already learned about Managing Files .

 

[#] Format (DB Field Attribute)

Takes 1 parameter, a formatting mask

 

 

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.

 

 

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.