The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
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.
Takes one parameter, Source
Parameter is a comma separated list (using CSV rules and not in quotes) of the fixed hard coded values to select from
Takes two parameters Command, Options
Takes two parameters, Source and Search
Takes five parameters, Lat1, Long1, Lat2, Long2, Options
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 one parameter, QueryName
Has one parameter, a Content.Lang prefix
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Takes two parameters, the variable name and a value
Cloudflare automatically provides free client-facing certificates for your domain, even if using their free service. In addition, they provide free Origin Certificates to encrypt the connection between Cloudflare and your origin Moxie.Build server. Use this article if you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.
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 two parameters, FieldBase, FieldNames
Takes 7 parameters, FieldBase, Destination, Source, OffsetVal, Operator, OpValue, IfLenFld
Takes two parameters, ExcelTableData, Options
Takes 5 parameters, Location, Mode, Title, Element, Class
Takes 10 parameters, Location, Mode, Title, TitleLink, Class, Fixed, bUseContainer, bNotResponsive, bInverted, HtmlPre, HtmlApn
Takes 7 parameters, Location, Mode, Title, TitleLink, Class, HtmlPre, HtmlApn
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Has no parameters
Takes two parameters, Title, Path
Takes one parameter, Type
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
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.
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
This is our current Privacy Policy, last updated 2016-01-12.
Parameter is a comma separated list (using CSV rules and not in quotes) of the options made available to the user which are enforced on save.
This is our current Terms of Service, last updated 2016-01-12.
Moxie.Build, in short, may be used and licensed free of charge for education and non-profit organizations. Whenever it is used by government or for-profit organizations 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.
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.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
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.
Parameter is a space separated list of field names to have the display table sorted by when displaying search results in the Admin interface.
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.
A Public Method may be called from any other Procedure, by the Default plug-in as part of the CMS.
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.
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.
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.
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.
Accepts a space separated list of field names.
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 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.