A work order app in which employees can request repairs and fixes.
Function: Planning & Project Management
This handy app helps manufacturing employees request work orders for parts that need repair or replacement. The employee can enter their information, name of the part, details of the issues and priority of the issue. The repairman can then include status and a signature once the repair or replacement has been made. The app user can: - Submit a request with details of an issue - Indicate priority of the issue. Orders can have one of three statuses: Low, Medium, High - Monitor status of the issue as the repairman makes changes
Also see: tablet mode & fullscreen mode
How we built this app
We built this app using the following AppSheet features: Enums, Slices, Grouping in UX views, Column Order in UX views, Signature capture, and Data Validation. Look for the following in this app: [Enums] This app uses Enums in order to indicate the status and priority of the request easily with a drop down. In order to do this, we navigated to Data, then Column Structure and selected "Enum" as the column type. We then manually entered the options we'd like our users to select from. [Randomly generated key] Each order needs to have its own unique order number, and this row can also be used as the key because each entry will be unique. We did this by inputting 'UNIQUE()' into the Initial Value field. More on that here: https://appsheethelp.zendesk.com/hc/en-us/articles/206096807-Specifying-a-key [Slices] We created slices in order to show a different view for the issues that are open and those that are resolved. In order to do this, we navigated to Data, then Slices and added New Slices. We then used the following expressions to indicate the slices we wanted to create: [Status]=In progress, [Status]=Resolved. In order to include these views in the app, we navigated to the UX tab and created new table views for each of these. [Grouping and Column Order in UX] We used grouping in the app in order to make the records easier to navigate. We did this by navigating to the UX tab, and within the view for All Records, we selected Group By: Date in ascending order. In the same section, you'll see the option that indicates Column Order. We selected Requested By, Date, and Order #, which indicates the columns the user will initially see when using the app. [Signature Capture] We included a Signature column in our spreadsheet, which was automatically recognized by AppSheet. This allows users to input a signature and indicate that the work order is complete. [Data Validation] We used data validation within our spreadsheet to create drop downs that AppSheet would automatically recognize. In order to do this, we created another worksheet for Employees that the Requested By column would pull from. We then navigated to Data>Validation within the spreadsheet. When prompted for details, we entered the data range within the Employees spreadsheet. For more information on data validation, read here: https://appsheethelp.zendesk.com/hc/en-us/articles/205319058-Creating-Dropdown-lists-from-spreadsheet-data-validation-rules.
This is a preview of the data sets used in the app.
This is a high-level model of both the data entities and the UI elements in the app.