I’m creating an app that has scheduling functionality, using timeslots. The user can create slots and associate them with a client. The point where I’m stuck is that I need to have a history of these appointments, as a kind of check-in, where the date of the service is recorded, if the client attended, etc.
I show the week’s schedule to the user like this below. To show it, I have an RG in the timeslots table that has the fields shown in the 2nd image.
I want to create a backend workflow to create the day’s schedules every day at 00:00, for example: Mondays 00:00 it would create two rows in the session table, one for Maria’s session and the other for Pedro. At the end of the day, the user will receive an alert to go to the system and mark these sessions as “Check-In OK” or “No show”.
What’s the question? “The point where I’m stuck is that I need to have a history of these appointments, as a kind of check-in, where the date of the service is recorded, if the client attended, etc.” or creating a recurring WF?
Side point: Do you have a reason why you are storing so many fields to represent a start and end time?
I have two tables, timeslots and sessoes. At timeslots I have all recurrent events (eg.: Monday - Start hour, - Start Min - Finish Hour - Finish Min - Patient: John Doe) and at the table sessoes I need to register in the following model: Date/time - Patient name - Status (OK or No Show).
There are some fields that are not in use, I will remove it.
What I was thinking is to create a backend WF that runs everyday 00:00, check at the timeslots sessions which recurrent events we have for that day and create the registers at sessssoes table.
I’m not understanding the setup. I think there may be more efficient ways to go about it.
Why are timeslots and sessions in separate tables? and whenever a timeslot is created shouldn’t its sistem session be created as well?