Takes one parameter, ServerLogText
Takes 8 parameters, ServerName, Port, bSecure, Path, ExtraHttpHeaders, Envelope, ExtraBody, xml
Takes three parameters, ServerName, Port, bSecure, Send
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.
This utility program manages a server install with one or many Moxie.Build services running by taking care of nightly tasks via a scheduled task
Takes 9 parameters, ServerName, Port, bSecure, Mode, Path, ContentType, extraHeader, body, rtnHeaders
Download Free Download of Moxie.Build Delivered as a simple .zip file, so that you can set it up however you like. This approach allows you to custom install many services on one server , or just run it as an app without an install.
All recent changes to Moxie.Build are documented in the Confirmed for Next Release list on our public Trello Board
In order to Upgrade an existing copy of Moxie.Build V4 to the most recent version, you can use our Upgrade system that is designed to help automate multi-service systems, or you can just replace the following files/folders: Moxie.exe Moxie.dll Default.dll /DBStore/BuiltIn.* /Lib /Public/BuiltIn /Templates/Admin /Templates/Clean /Templates/Default /Templates/Report
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.
Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in managing files and folders in the Moxie.Build system.
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.
A traditional way to check for hard errors and enable those errors to error softly.
CloudFlare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services
Takes 6 parameters, Location, Mode, ActionLabel, ActionPath, Class, ActionMethod
Takes one parameter, Value
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Takes two parameters, QueryName, Title
Takes three parameters, Url, InputQuery, OutputQuery
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes one parameter, Type
Takes one parameter, Name
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes one parameter, Status
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, name, value
Takes no parameters.
Takes 3 parameters, Trigger, DestinationID, Path
The MOX language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
This hands-on experience article is written by an experienced PHP developer, and serves as an overview to help you understand the similarities and differences.
Takes a variable number of parameters, a comma separated list of TopQuery variable names
Has one parameter.
Takes two parameters, Text, Title
Takes one parameter, QueryName