The AIDC Cloud
First, think of a time you booked a flight online. In a similar way, you use a flight-booking web interface (often called a ‘wizard’) to reserve a flight, an AIDC Cloud administrator uses a web-based ‘wizard’ to configure AIDC workflows.
The AIDC Cloud administrator will have one or more AIDC tasks for their authorized mobile app-users to accomplish (we call those tasks ‘Services’). They use a web-based wizard to configure the mobile app to capture, collect and connect the resulting data exactly as necessary to accomplish the intended task.
Once the administrator has created these Services, they need to assign them to app-users for use in the field. They create unique app usernames (often an email address) with passwords and then email those app-users their credentials.
With a few clicks, they associate specific app-users to specific Services, depending on the task at hand. When the app-user signs into the mobile app they automatically see only those Services which the administrator has assigned. They can then begin their assigned tasks.
Admins can change or revoke the app-user credentials can be at any time. Also, they can change, add, or remove the assigned services remotely. Importantly, the updates would be effective instantly.
What is a ‘Scan Record’?
- Who scanned (app username)
- What they scanned (the barcode scanned)
- When they scanned the barcode (time and date stamps)
- Where they scanned (GPS or lookup)
- How they scanned (scan, lookup, manual entry, NFC)
- Why they scanned (the workflow name and service ID)
What is ‘Associated Data’?
When setting up your workflows, you can add app-user prompts (Questions) to present to your authorized app-users, including:
- Form fields
- Multiple-choice (single answer or multi-answer)
- Dropdown menu
- Secondary barcode scans
- Photo capture
- Signature Capture
- Custom Questions – HTML (offline)
- Custom Questions – URL (online)
Validation serves many purposes. Most importantly, it structures workflows for app-users to accurately capture data. Bad data is very expensive. Therefore, validation is an important part of the workflow and AIDC.
For example, if the app shows the app-user that an item is ‘Invalid’, they will not collect data for that item. Also, simply showing users an item description and attributes after a scan can help them from entering bad data. Here are some validation options:
- Validate against database
- Custom On-Device Validation
- Conditional Validations
- A/B Compare Validation
- Validate to our server or yours
- On-Device or Online
- Custom Questions
- Pattern Validation
- Regex Validation
- Scan Builder
Connect Your Data
Primarily, there are two considerations. First, you can get your data to the mobile app. Secondly, you can connect the mobile app’s scan records to your databases. Here are a few options:
- Web UI to manually upload and download data to/from our servers
- API to automate the insertion to and retrieval of data from our server
- Postback URL (app posts scan records to your server and your server posts back to the app-user)
- Scheduled exports via FTP, Dropbox, and email
- Direct integration (custom) or using API connectors (Zapier)