Schedule Experimental
Calendar
A calendar on the canvas. Each appointment is on while it is happening, and can start whatever you wire to it.
| Port | Side | What it carries |
|---|---|---|
data | In | Optional. Dated records, such as unpaid invoices, shown on the calendar beside your appointments. |
appointment | Out | One per appointment, named after it. On while the appointment is happening, off otherwise. |
events | Out | Your appointments and any records wired in, as one dated list. |
What you choose
When things should happen. Drag across the calendar to make an appointment; it starts out called Trigger. Click it to give it a title, a description, a start and an end, or make it all-day.
An appointment can repeat every day, every week or every month. Drag it to move it.
Resize the card to change the view: day, two days, week, month, or a timeline.
What Fluidly decides
Each appointment has its own port, created when you wire from it. The port is on from the appointment's start until its end, and off the rest of the time — so an Email wired to it sends once, as the appointment begins.
For a repeating appointment, Fluidly works out the next time it falls and switches the port on again then.
As an enable
Wired to another trigger's enable, an appointment limits it to a window: a Range trigger that only watches during office hours, or a button that only works in closing week. The trigger is on only while both agree.
Records on the calendar
Wire dated records to data and they appear among your appointments — invoices on their due dates, for instance. They are read-only here; change them at their source. More than one source goes through a Sum first, which checks the currencies match.
Experimental
The Calendar works, but is still changing. Expect its card and behaviour to move on before it settles.
Example
Calendar (every Friday, 16:00–16:30) → Email, with Bank Account → Text box → body: the week's closing balance in your inbox every Friday afternoon.