Takes 3 parameters, FieldBase, Fields, SearchTerms
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.
In this example, we use a plain old Moxie.Build system and compare it to the MEAN Stack equivalent by building two functionally equivalent versions of a fleshed out To Do List Application. Both versions utilize local user authentication, a relational database system and the security measures found in typical production-level applications on the web today.
Takes one parameter, Status
Takes two parameters, Source, Search
Takes one parameter, Name
Takes no parameters.
Takes one existing Source value, and two parameters, Search, NewVal
Takes two parameters, Source, Search
Takes two parameters, Source, Search
Takes two parameters, Source and Search
Takes two parameters, Source and Search
Takes two parameters, Source and Search
A command to help build spreadsheets
Takes 10 parameters, FieldBase, From, To, Subject, Body, bMerge, AttachName, AttachPath, Slow, IfLenFld
Takes five parameters, FieldBase, Destination, Action, Source, IfLenFld
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes six parameters, FieldBase, GroupByField, Destination, Action, Source, IfLenFld
Takes three parameters, ChildTableName, ParentTableName, Mode
Takes two parameters, ChildTableName, Mode
Used to manipulate a WorkQuery into a JSON type
Takes two parameters, FileName, Options
Takes one parameter, FieldName
Takes 5 parameters, DestinationQuery, SourceQuery, DestinationMatchField, SourceMatchField, Mode
Has no parameters
Takes no parameters.
Takes one parameter, ServerLogText
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.
Parameter must first specify only looking at Parents ( PARENT ) or only looking at Children ( CHILD ). The remainder of the parameter should be the table and field name you are after in the form of TableName.FieldName.
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.
Parameter is the table and field name that you want to sum in the form of TableName.FieldName. The specified Table must be a Child of the calling Record.
Takes 1 Parameter which is the Table name that you want to count the Attached Records in. The specified Table must be a Child of the calling Record's Table.
Takes two parameters, Source, Search
Has one parameter, Options
Has two parameters: Source, Options
Takes two parameters, Source , Search
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes two parameters, Source, Match
Takes two parameters, Source, Match
Takes two parameters, Source , Search
Takes two parameters, Source, Match
Takes two parameters, Source, Match