Customising Event Templates
Summary
Event templates allow a workspace to define its own vocabulary for asset events. Instead of using only the built-in event kinds (acquire, move, consume, etc.), a studio can create named templates like "Sent to Casting", "QC Passed", or "Stone Set" that match the language and workflow of their workshop.
Note: Event templates are not yet available in the current version of Jewlerist. This article describes the intended functionality and will be updated when the feature is released.
Who this is for
This article is for studio managers and workspace owners who want to customise the event vocabulary to match their production workflow.
What event templates will do
When event templates are available, each template will define:
- A name: The label shown to users (e.g. "Sent to Casting").
- Which asset kinds it applies to: A template can be limited to specific asset types (e.g. only metal lots and jewelry pieces).
- An optional system code: A stable mechanical behaviour (e.g. a "consume" template reduces the remaining grams on a metal lot).
- Required fields: Additional data that must be provided when recording the event (e.g. a vendor, a weight, or a photo).
Templates will be managed from the workspace configuration and will be available to all team members when recording events on assets.
Why event templates matter
Different studios name their production steps differently. One studio might say "Sent for casting", another might say "Out to caster", and another might say "Casting stage". Event templates let each workspace use the language that matches their workflow, while still recording the same underlying mechanical behaviour.
This improves clarity for team members and makes the event timeline more meaningful.
Current behaviour
Until event templates are released, all events use the built-in event kinds listed in Recording Asset Events. You can use the Notes field on each event to add context that a template would otherwise capture.