Entry templates and recurrence
How to start new entries from prepared content, and have entries made automatically on a schedule.
An entry template is a starting point for new entries. It holds the body and property values you would otherwise type every time, such as the agenda outline of meeting notes or a task's default status.
Making and using templates
Open the Templates (템플릿) menu beside Add item at the top of the database.
- New template: a template page opens. Whatever body and property values you fill in are copied into new entries.
- Pick a template under Starting point for new items and press Add using this template to make an entry from it. Edit template changes the template.
- Choose Default for this view or Default for the database and Add item uses that template. Clear default goes back to starting from a blank entry.
Changing a template does not change entries already made from it.
Databases inside a template
A database inside a template page is made anew under each entry made from that template: by Add item, by recurrence, and by an automation's or a button's Add page.
- Up to 500 of its rows come along as samples; with more, its structure only. It comes only if you can manage the database the new entry goes into (a private database is the exception: it comes private to whoever made the entry); otherwise you are told it was left out.
- The entry's body is written first, and once the database is copied, linked database views, buttons and mentions in the body are turned to the new database. For a moment the template's database may show there.
- Automations and repeat schedules of the template's database come switched off.
- An automation's Add page copies the databases with their sample rows up to 20 times an hour per rule. Beyond that, or with more than 200 copies already waiting, the databases come as their structure only (no rows), and the run log's step says why. The count is taken from the run log, so a server restart does not reset it.
- If the server restarts while the database is being copied, the entry made then may lack the template's database.
- An entry made by recurrence is filled in at the next recurrence pass.
- Entries made by automations and buttons are filled in when the server starts again. Runs more than 7 days old are not gone on with.
- An entry made by hand is filled in when the same request comes again, and otherwise stays without it.
- In an automation's or a button's run log, the Add page step reads In progress until the copy ends, then completed or failed (with the reason). A step not gone on with within 7 days reads as failed.
Recurrence
Recurrence makes a new entry from a template on a schedule. Use it for work that comes round regularly, such as weekly meeting notes or a month-end check.
- In the Templates menu, pick a template and open Recurrence settings (반복 설정).
- Choose a Recurrence schedule: daily, weekly, every two weeks, monthly, quarterly, yearly, or custom (set the interval and unit yourself).
- For weekly, choose the Days of the week; for monthly, the Day of the month (the same day as the start date, or the last day of the month).
- Set the Recurrence start date and the Created time. The next creation time and its time zone are shown.
- If needed, choose a Property for the occurrence date, or turn on appending the occurrence date to the title.
- Press Start recurrence.
- The template's name gets · Recurring, and Recent occurrences opens the entries made or shows why one failed.
- Pause and Resume stop it for a while; Turn off recurrence ends it.
- Entries are made with the permissions of whoever set up the recurrence. When someone else saves the settings, it becomes that person.
- Occurrences that fell while the server was stopped are skipped, not made late in a batch.
- Changing recurrence needs Manage permission on the database.