Appearance
Events Overview
Events track operational activities that happen around parties, assets, inventory, services, field work, delivery work, inspections, and billing. An event can be a simple activity record, or it can become a controlled workflow with documents, participants, charges, approvals, inspections, and accounting handoff.
Use Events when the business needs to answer:
- What activity happened?
- Who or what was involved?
- Which service, location, or business unit owned the activity?
- Was the activity billable?
- Which documents, inspections, or follow-up actions are linked to it?
- Has the activity been approved, completed, billed, or posted?
How Events Fit In
Events are a shared operational layer. They do not replace specialized modules such as Billing, Inventory, Inspections, Production, Agriculture, or Resource Capacity. Instead, events give those modules a common way to record business activities and connect them to supporting evidence.
Service modules may open event flows with narrower context, but that does not create a separate event ledger. The event header, participants, child lines, approval state, and linked follow-up remain owned by the shared Events primitive.
Common examples include:
- Farmer deliveries and field operations.
- Service visits and client appointments.
- Production activities.
- Asset maintenance events.
- Inspection-triggering activities.
- Billable service events that later become invoice charges.
Main Areas
The Events module is split into setup and operations.
Setup is where administrators define event types and document transaction types. This controls what users can create, what fields are expected, whether an event can be billable, and whether supporting documents are required.
Operations is where users create events, maintain their details, attach evidence, move events through approval, complete them, and review linked document transactions.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Event Types | Events -> Setup -> Event Types | Define allowed event categories, billable behavior, required evidence, workflow expectations, and accounting handoff rules. |
| Document Transaction Types | Events -> Setup -> Document Transaction Types | Maintain event-supported document types when an activity needs structured document evidence. |
| Events | Events -> Operations -> Events | Create and review operational activities, participants, locations, resources, charges, documents, inspections, and workflow state. |
| Document Transactions | Events -> Operations -> Document Transactions | Review structured documents linked to events or service operations through the shared document ledger. |
| Contextual Event Entry | Production, Agriculture, Resource Capacity, Inspections, or Billing service areas | Open the same shared event workflow with domain, party, location, resource, or evidence requirements already narrowed for the user. |
Event Detail Areas
An event detail page can show different tabs depending on the event type and permissions:
- Items: stock-affecting or operational item lines linked to the event.
- Charges: billable lines that can be generated, added manually, waived, removed, approved, and submitted for finance posting.
- Observations: measurements, notes, abnormal readings, and operational findings.
- Resources: operational resources or capacity slots booked for the event.
- Documents: structured document transactions linked to the event.
- Inspections: inspection records connected to the event.
- Workflow: approval and follow-up state.
Users should treat the event as the activity header and the tabs as the supporting evidence.
For agriculture and similar service stories:
- the event explains what happened operationally
- linked documents explain structured commercial or evidential detail
- linked inspections explain pass/fail, grading, or checklist truth
- linked payments, billing, stock, or GL effects remain in their owner primitives
Status And Control
Events are designed to support controlled workflows. Depending on setup, an event may be created as a draft, submitted for review, approved, completed, cancelled, billed, or posted to accounting through downstream processes.
The exact buttons available to a user depend on permissions and the event type configuration. A user may be allowed to view events but not approve them, or create events but not post charges.
For billable events, charge approval and finance posting are separate from ordinary event completion. An event can be operationally complete while charges still need approval, correction, or finance review.
For a concrete billable activity example, see Event Type To Billing.