Table Builder Features and Instructions
Note: This feature will formally launch July 1, 2019. To use the beta version please contact firstname.lastname@example.org.
Fundamentally the Table Builder utility allows administrators to build a parent table (think of a “sheet” in Excel) and child table views where app users scan a barcode and answer data collection prompts (“Questions”) to create, edit and view as fields in each table view.
How does this differ from our standard Record Scans or Validate Scans service types? With those standard service types, only the admin can view scan records. With Table Builder, assigned app-users can see the current answers and optionally edit those answers. Also, a summary table is auto-generated for administrators to view and share a summary table.
1 – Scan to Build an Asset Table.
Configure the codeREADr mobile apps so your app users can add data to specific tables by scanning targeted barcodes and then entering information associated with each barcode to populate fields within a table view.
2 – App Users Edit and/or View an Asset’s Current Status In-App
When your app users scan a barcode, they can be given the right to add new table rows or to edit and view existing rows based on their assigned task.
3 – Admin Summary View Shows Current Status of All Assets
A “Share Link” is auto-created for administrators and authorized personnel showing the latest edits to an asset’s status in the table. A full history of all scans is also available for viewing online or for exporting.
Sample Work Flow
Share Link View of Current Status
|Barcode Scan||Database Text||App-User Selects from Dropdown Menu||Date Auto-Captured||Date Auto-Captured||App-User Selects Install Location||Date Auto-Captured||Edit Template to View Other Data|
|Asset ID||Description||Silicone Used||Assembly Date||Shipping Date||Install Location||Install Date||Configure|
|A1234567890||Model XYZ-A||S1111001||June 10, 2019||2019-6-7||NYC, Loc 129||June 20, 2019|
Table Builder – Multiple Table Views – Instructions
Multiple table views are created from a parent table. Each child table view can be used to collect unique data (“answers”) and can have a distinct view of previously collected answers. Each view is typically assigned to a specific app-user along with the option to edit or just view any of the answers in from the parent table. This type of service is ideal when each app user collects data for their own, unique task – such as when tracking processes, production, shipments, etc.