Permanently deleted user
The current process works okay but I feel this could be a solid solution if a few additions where made. I know that there are considerations that I am thinking of but here is what I see it would need.
1. Combine "Date" and "Time" into the same field, where clocking in/out captures the data and time to accurately calculate time on the job. Really comes into play when working over 24 hours.
2. Recall loop on "summary", this would allow for a running total of hours worked. This would require some magic on the engineering side to make this work, I'm sure.
Please UP-VOTE if you think this would be helpful.
2
Comments
Please sign in to leave a comment.
Hi John,
For number two, would something like our Summary field functionality work? It basically does what you're saying, in that it calculates the total value of a number field within a Loop and displays it.
In the App, I have a simple Loop set up with days of the week as the key field. Within the Loop I'm just collecting the date and the total hours worked for that day:
Then on a screen outside of the Loop, I have a Summary field that is summarizing the Hours worked today field across every iteration of the Loop:
Here's how that looks on mobile:
Is that what you're going for?
Sara, thanks for taking the time to put this together and I have thought about converting to a weekly based time card app versus a daily submission.
I suppose this may be the best fit until there is a better solution. There a couple of concerns though, one being that I would not be able to see progress until they submit there time at the end of the week. Seeing a daily submission allows me to catch errors and missed days while we are getting used to logging time digitally. The other issue is getting the guys to saving their progress until the end of the week and dealing with premature submissions.
I believe that with a date/time combined feature along with the ability to recall data from previously submitted tickets would get closer to a true time tracking app. I realize that resources have to be placed where demand is, I just don't want to migrate to a different app to accomplish this (or go back to paper)
What you could do, so you have visibility, is enable mobile editing for your users. Then they could submit on the first day, then go back and edit the same submission each day. The summary will update if you do it that way.
Working with a daily submission, you could do a google sheets integration through Zapier that would create a new row for each submission, with the daily hours total in it. From there, you'd be able to manipulate the data pretty extensively, including doing this type of calculation (full disclosure, I'm not an excel expert, but I've seen this done). That would be more of a pain to set up, but once it's there should be pretty low maintenance.
We always appreciate your feedback! I know time tracking is something a lot of our customers do with GoCanvas, and I know it's something we could do better. It's great to have specific requests and use cases to work towards.
Did the "Summary" field get deleted? Can't seem to find it anywhere. Or is there something specific we need to do to make it available?
Hi @...,
Great question! Summary is no longer an individual field but a function of the Calculation field. The Help Center article, "Using Calculation and Table Calculation in the Builder" is slightly out of date but the instructions are still very similar.
In order to configure a Calculation field to summarize a Number or Calculation within a Table or Loop Screen, add a Calculation field and/or select one that is outside of a Table or Loop Screen to open the Field Settings in the left panel. Toggle Calculation Type to "Sum" and expand the "Sum Field" and choose the field that needs summarized. This is simplified from the Builder BETA where the Screen also had to be chosen.
Hopefully this helps but please let me know if you have any other questions!
That helped immensely! Thank you!