From SeedCode Documentation

GoZync4: UseCases

A couple examples of some of our favorite GoZync workflows.

Mobile Work Orders

This is probably the most common scenario among our users: work orders or appointments are created in the main office's FileMaker software and assigned to individual technicians for a specific day.
This techs then sync their FileMaker Go solution in the morning--they may not even come in to the office--retrieving a list of their appointments for the day, and sometimes pulling down explicit instructions, invoices with line items, or other specs about the job.
Once on site, technicians complete the order, add new line items to the invoice, and capture pictures of the work done or a customer signature. These are then synced back to the office throughout the day as new or changed work orders are pulled down.
Because GoZync pulls down just the work orders assigned to a given technician for that day, each morning the tech's old orders are deleted from their iPad when they sync, as are any incomplete orders that may have been reassigned to another tech in the meantime.
This workflow is common to:
Repair Technicians
Home Health Aids
Sales People
Plumbers

Inspections

Mobile users sync each morning to get a list of locations to be inspected. If there are a large number of locations, something like GoMaps helps to visualize all the locations, color coding them by urgency or type.
Each inspector receives their own list of locations and after visiting each site completes a simple form about what's going on there and takes pictures of the situation.
Completed inspections are synced back to the main office throughout the day if the inspector has cell signal, or at the end of the day if cell signal is spotty.
Customer are using this workflow for:
Construction Inspections
Forestry Surveys
Retail Display Audits
Oil Rig Safety Compliance

Product Catalogs

Catalogs can be stand-alone apps or be included inside other mobile apps like work orders. Event when they work along side another app, many customers build the product catalog as a separate file (or at least as a separate data file) and take advantage of GoZync's file delivery features to let users download new copies of the app when catalog info changes. This is often much faster than actually "syncing" the data down to mobile devices, especially if the catalog data contains a lot of photos.
Users can click "check for new version" inside the catalog application and pull down new catalogs when there is a new version on the sever. GoZync cleanly replaces their existing catalog so there is never any confusion about which file on their iPad is the latest version.
Retrieved from http://www.seedcode.com/pmwiki/pmwiki.php?n=GoZync4.UseCases
Page last modified on August 11, 2013, at 03:48 PM