Pendragon Forms

Features

FAQ

View Shopping Cart

Pendragon Forms is commonly used for building mobile work order management systems. 

Here's how they work.  A dispatcher at the central office creates a record detailing the time and place of the work to be done, and the name or ID or the technician who will be performing the work.

The main Work Order form is set to deliver records to mobile devices according to the name of the technician.  When the technician synchronizes his/her mobile device, it downloads the work order record.

Once the record is synchronized to the device, the technician can jump into the record, and travel to the client site to perform the work.

At the client site, the technician records details of the work.  The details might consist of a text description of the work done, or might consist of a checklist of inspection tasks.

Once the work is complete, the technician marks the record completed.  The next time the technician synchronizes, the record is stored at the server.  Typically, work order forms are configured to be removed from mobile devices once the work is completed.

Our sample form illustrates how this can be done.  If you are planning to implement a work order system, you can download our work order form and try it out.  Of course, you will want to customize it for your particular business.

In our example, we not only record a text description of the work being done, but also collect a list of parts, and calculate a total fee for the work done.

We also have a mapping feature.  iOS and Android devices are able to display Google map data, and Pendragon Forms VI can as the system to do this using a LAUNCH statement.  On our location page, we added a Map button:

A map button is just an ordinary button with the following script:

click:
  launch "http://maps.google.com/maps?q=$5$"

Clicking the button opens a Google maps search window for the address in field 5

To store a list of parts used on the work order, we need to create a parent child relationship between the Work Order record and our Work Order Parts records.  In Pendragon Forms VI, this is done using a Subform List field.  A Subform List field appears as a button that takes you to related records in another form.  Work Order Parts is just another Pendragon Forms VI design.  The link between a form and subformis on their shared fields.  In this case, both Work Order and Work Order Parts have an Order ID field.

Clicking the Parts subform button displays a list of parts already attached to the Work Order record, and gives the user the option to add a new part.

When the user taps New to add a new part to the work order, the user can tap a Lookup button to look up the part to add.  The lookup function refers to a third form called Work Order Parts List.

We include a quantity and price for each part, and calculate the subtotal with a script.

When we return to the Work Order record and advance to the Fee Calculation screen, we use another script to sum up the subtotals for the parts on this work order record, and compute the hourly rate times the number of hours worked.  We round up the hours worked to the next highest number of hours.

Finally, the technician has screens for accepting patment and for marking the work order as complete.

On the Administrative PC, Pendragon Forms automatically creates a database table for storing data, and a Microsoft Access form for viewing and editing that data:

Here is a link to a ZIP file containing this form design: WorkOrder.zip

To import this form, unzip the file and import the .pff files into Pendragon Forms VI. After you have frozen the Work Order Parts List form, you can import data from the WorkOrderPartsList.CSV file using the From ASCII function.

Get Started

Download 14-Day Trial

Learn More

Tutorial: Quick Start Guide

Product Features

How Pendragon Forms works