Add Multiple Database Records:
The Grid Add Maintenance template can be used to create web applications that allow end users to rapidly add multiple records to the database through a single screen.
Back to Diagram

URL Redirection:
m-Power developers have the ability to specify a URL to redirect to after adding a new record. For instance, maintainers are often linked to from retrievals and reports in order to add a single database row. After adding the row, a URL redirect can be used to return to the original data list. The URL redirection can be conveniently specified within the application properties. More Information
Back to Diagram

Modify Primary Tables Only:
m-Power developers can specify whether each maintenance application can be used to edit only primary tables or to edit primary and secondary tables. By default, maintenance applications will only allow modification of the primary table whenever a table join is made. This setting can be altered via application properties, and prevents unwanted modification of secondary tables.
Back to Diagram

Easily Upload Files:
m-Power developers can specify a field to store file names, and at runtime, one or more files can be uploaded at once easily. Using m-Power's upload feature, dynamic file paths, and files with the same name can all be easily handled.
Back to Diagram

Use Alternative Input Methods:
m-Power maintenance templates can utilize radio buttons, check boxes, calendar pickers, and external drop-down lists to populate input values. These can easily be created via field settings within the m-Power interface and m-Painter to improve application functionality and appearance.
Back to Diagram

Back to the Top

Description: Allow developers to specify their application's description.

Program Name: This will be the application’s name, by default m-Power uses the letter M (Maintenance) followed by a five digit number.

Template: You can select a template by scrolling through the available templates. The templates define the general layout and functionality of the resulting application. This section will list all the available maintenance templates; you will see a small screenshot of what that template looks like at runtime. Learn more about templates.

Here you will find the settings for all the fields in the application. The options are:

Delete: You can delete fields by clicking the checkbox and clicking Accept. If a field has a red circle with a cross line, that means that the field is being used somewhere else in the application (sequence, calculation, etc.), and, due to this dependency, is not available for deletion. Note: deleting a field will remove the field from the application only, the table will be unchanged.

Field Name: This is the same name the field has in the table.

Table: The name of the table where that field exists.

Field Description: This is the text that will appear in the column header for that field, you can modify this field to suit your needs. This field will populate with the field description from the table by default, but it can be customized at the application level.

Type: A drop down list that allows developers to designate whether a field is to be displayed (visible, but not edited on the database), hidden (no action), or updated. There may be situations where a field is needed for calculation purposes, but the field does not need to be displayed at runtime. Note: sequence keys must be set to update to ensure your application functions properly.

Size: This displays the length of a field. If a field has a length consisting of two numbers separated by a comma, the first number will be the integer length and the second the decimal length of the field.

Numeric Format Code: For numeric fields, you can modify the way the numbers will display, this includes displaying commas or not, how to display negative numbers, etc. Multiple formats are built in for developers to use, shall you need a different format code, m-Power allows developers to create their own User Defined Format codes; these codes will add logic for common types of fields such as: Currency, Time, or Dates. Accessing the User Defined Format Codes from the Admin section will also allow developers to modify current codes. Learn more.

Lowercase: This option determines whether or not an alpha field can be submitted to the database with lowercase letters. If this is set to "no," the field will be converted to uppercase when it is submitted.

User def: If you would like a user to be able to upload a file over a field, select the letter 'U' from the dropdown. The remaining options have been deprecated. For information on uploading files to a server, click here.

Note: Do not confuse the User Defined Format Code with the User Defined Functions (UDF). The latter is a feature that allows developers to create or incorporate programing functions into m-Power. Learn more about UDFs.

Validity Check Relation: This setting, combined with the Validity Check Value setting will allow you to restrict what information may be entered into your maintenance application. Valid relationships are:

EQ Equal to
GE Greater than or equal to
GT Greater than
LE Less than or equal to
LS Is in the list
NS Not in the list
LT Less than
NE Not equal to
NG Not greater than
NL Not less than
RG Is in the range
RB Radio Button
CB Checkbox

Validity Check Value: This is the value that you want to compare the field value entered to in order to restrict the user from proceeding. A common use of this and the previous setting is to prevent the user from leaving a character field blank. This is done by setting the Validity Check Relation to "NE" and setting the Validity Check Value to be "*BLANK". This will prevent the user from entering a blank value into the field.

Default Value for Add: Text entered here will be entered into the field initially when a new record is being added. Users may change it to whatever they wish, however this is what they see first. A common use of this setting is to add "Insert Full Name Here" into a name field.

*AFTERADD This location calls the object only after a user adds a row.
*AFTERPRC This location calls the object after the last row is processed.
*BEFOREADD This location calls the object only before a user adds a row.
*BEFOREPRC This location calls the object after the first row is processed.
*INITADD This location calls the object when the page loads.
*REDIRECT This location is deprecated in this template.
*FLDVALID This location calls the object to validate fields before add.
Learn more