android:tracktools:tracktoolsstories
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
android:tracktools:tracktoolsstories [2019/06/01 00:37] mikeclapp [Assign Trackers] |
android:tracktools:tracktoolsstories [2019/06/07 23:35] (current) mikeclapp [Assign Trackers Main Screen] |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| ===== Login ==== | ===== Login ==== | ||
| + | We use are standard login screen from most apps to log into the server and see just what trackers are assigned to that company. | ||
| + | {{:android:tracktools:login.png?400|}} | ||
| + | |||
| + | |||
| + | |||
| + | Changing logins can be done by going to Settings (gear on action bar) | ||
| + | |||
| + | {{:android:tracktools:tracktools_preferences.png?400|}} | ||
| ===== Assign Trackers Main Screen ===== | ===== Assign Trackers Main Screen ===== | ||
| Line 21: | Line 29: | ||
| {{:android:tracktools:trackertools_main.png?400|}} | {{:android:tracktools:trackertools_main.png?400|}} | ||
| + | |||
| + | |||
| + | Add a battery indicator to current settings. | ||
| Line 38: | Line 49: | ||
| Joe Foreman goes to look at SmartTrack and wonders where the heck is the machine track. He remembers he forgot to move it from the old project to the new. He picks that tracker, sees the current settings are to the old tracker and does a Set after changing the project. All new points are going to now show up. | Joe Foreman goes to look at SmartTrack and wonders where the heck is the machine track. He remembers he forgot to move it from the old project to the new. He picks that tracker, sees the current settings are to the old tracker and does a Set after changing the project. All new points are going to now show up. | ||
| - | If he was really slow to catch the mistake he has tracks from previous days going to the wrong project. He presses history and he sees previous days of tracks. He taps the checkbox to select any number of days and does a Move to Project from the menu. The program prompts him for the new project and he selects it. The server does this and then refreshes the history to show the tracks have moved. Partial tracks moved to a project should be combined with any other tracks for that machine/tracker that were on that day. The likely scenario is he figures out the project mistake halfway through the day so he wants them combined. | + | If he was really slow to catch the mistake he has tracks from previous days going to the wrong project. He presses history and he sees previous days of tracks. He taps the checkbox to select any number of days and presses the move button and the bottom of the screen. The program prompts him to select the new project and he selects it and presses Ok. The server does this and then refreshes the history to show the tracks have moved. Partial tracks moved to a project should be combined with any other tracks for that machine/tracker that were on that day. The likely scenario is he figures out the project mistake halfway through the day so he wants them combined. |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| + | {{:android:tracktools:trackerhistory.png?400|}} | ||
| + | This example screen shows a likely scenario where user has forgotten to move the tracker on 5:30. Setting the tracker to the new project has broken days track but not moved previous data for 5/30. The expectation would be that the user would pick the 5/30 checkbox and press the Move button and choose the new project. That days data would merge together. | ||
| - | === Tracker info === | ||
android/tracktools/tracktoolsstories.1559349455.txt.gz · Last modified: 2019/06/01 00:37 by mikeclapp
Page Tools
