Core Concepts
Statuses and Lifecycle
Forge uses status fields to model the life of events, attendees, tickets, sessions, speakers, sponsors, invoices and payments. Each status below is a Salesforce picklist value, so the names are exactly what you see in Salesforce reports. Knowing which status drives what saves a lot of confusion, because several statuses on one record are independent of each other.
Event
Event Status
| Status | Meaning | Notes and recommendation |
|---|---|---|
| Draft | The event is being built. | A cloned event always starts as Draft. Keep it Draft until tickets, dates and forms are ready. |
| Active | The event is ready for business. This is the Salesforce default for a new event. | Needed before you can publish. On the Events list it is labelled Published, with the tooltip This event is live and accepting registrations, but the public page only goes live once you also publish. |
| Completed | The event is over. | Set it after the event so it stops looking upcoming. |
| Canceled | The event was called off. | Set it, then notify registrants and process refunds yourself: Forge does not do either automatically. |
You change status from the event's Overview (each change asks you to confirm; Canceled shows an extra warning). Salesforce describes the field as the Internal status of this Event.
Publish, registration and visibility
Status is only one of the switches that decide whether people can register. Publish (the Visible field in Salesforce, labelled Publish) is the one that makes the event reachable on its web address and in public groups and lists; until you publish, the event is reachable only through its preview link.
| Setting | What it controls | Recommendation |
|---|---|---|
| Status = Active | Whether the event is ready to be published. Publish is blocked unless the event has a start date, Status Active, (when your Event Settings require one) at least one ticket and (when walk-up registration is on) a ticket marked as the walk-up ticket. | Activate first, then publish. |
| Publish | Whether the event appears publicly. After the first publish the button reads Update, which re-sends later edits. | Click Update after editing a published event so the public page catches up. |
| Hide Register Button | If Yes, the registration button is hidden on the event page. | Use it for events that are announce-only. |
| Waitlist Enabled (event or ticket) | When remaining seats reach 0, people can still register but are waitlisted. Waitlist Capacity caps the waitlist; Remaining Waitlist Capacity shows what is left. Not available for products or donations. | Turn on waitlisting for popular events and set a waitlist capacity so it does not grow without limit. |
| Capacity (Total Capacity, Attendee Limit Buffer) | Total Capacity is the sum of ticket quantities unless you override it. Remaining Capacity = Attendee Limit minus Attendee Limit Buffer minus Registered. | Use the buffer to hold seats back for walk-ups or VIPs. |
An Active event that is not published is invisible to the public. After you change the status of a published event, check its public page.
| Forge | SF Object | SF Field |
|---|---|---|
| Event status | conference360__Event__c | conference360__Status__c |
| Publish (public visibility) | conference360__Event__c | conference360__Visible__c |
| Hide Register Button | conference360__Event__c | conference360__Hide_Register_Button__c |
| Waitlist enabled | conference360__Event__c | conference360__Waitlist_Enabled__c |
Attendee: three independent statuses
An Attendee record (conference360__Attendee__c) carries a Registration Status, an Attendance Status and, when approvals are in use, an Approval Status. They do not move together: a person can be Registered and still have Attendance Pending until they check in.
Registration Status
| Status | What it means | What it triggers or counts as |
|---|---|---|
| Lead | The earliest stage in the funnel: a prospect who has not been invited. | Not counted as registered. |
| To Invite | Queued to receive an invitation that has not been sent. | Not counted as registered. |
| Invited | An invitation was sent and the person has not responded. | Not counted as registered. |
| Pending | Registration has started or is waiting on a later step, such as payment. | Not counted as registered. |
| Registered | Registration is complete. | Counts as registered on Overview and reports. Fires the Registration confirmation email when it is enabled. |
| Waitlisted - Pending | The person is on the waitlist waiting for a seat. | Fires the Waitlisted email when it is enabled. A person who gets a seat moves to Registered and fires the Waitlist released email. |
| Waitlisted - Rejected | The waitlist request was not accepted. | Treated as a decline. |
| Awaiting Approval | Registration needs organizer approval before it is confirmed. | Grouped with waitlisted people in the Attendees tab. |
| Rejected | The organizer declined the registration at the approval step. | Fires the Cancellation email when it is enabled. |
| Declined | The person turned the invitation down. | Fires the Cancellation email when it is enabled. |
| Canceled | The registration was canceled. | Fires the Cancellation email when it is enabled. Refunds are separate: update the invoice and transaction yourself. |
The Reports funnel shows the stages in this order: Lead, To Invite, Invited, Pending, Registered, Declined, Canceled.
Attendance Status
| Status | Meaning | Recommendation |
|---|---|---|
| Pending | Default. Not yet marked attended or a no-show. | Leave it until the event. |
| Attended | Checked in. Set automatically when the person is checked in through the Blackthorn mobile app; it can also be set manually or by a Salesforce process. | Use the Attendance update email trigger to thank people who attended. |
| No-Show | Registered but did not attend. Set manually or by a custom process flow. | Use it with the Not checked in filter to follow up after the event. |
Approval Status
Pending, Approved or Rejected. It belongs to the approval workflow and is separate from Registration Status.
| Forge | SF Object | SF Field |
|---|---|---|
| Registration status | conference360__Attendee__c | conference360__Registration_Status__c |
| Attendance status | conference360__Attendee__c | conference360__Attendance_Status__c |
| Approval status | conference360__Attendee__c | conference360__Approval_Status__c |
Ticket (Event Item)
| Status | Meaning | Recommendation |
|---|---|---|
| Planned | Configured but not on sale. | Keep it Planned while you configure. |
| On Sale | Available to buy. Set it when you are ready for people to purchase. | Switch to On Sale at launch. |
| Sold Out | Quantity is used up. | Waitlisting may apply if enabled. |
| Closed | The sales window ended or the ticket was closed. | Use for an expired early-bird ticket. |
| Unavailable | Pulled from sale without deleting it. | Use it instead of deleting a ticket that already has sales. |
The Tickets list also shows a calculated pill: Closed when the sales end date has passed, Sold out when sold equals Quantity Available, otherwise Open. The pill is a quick read and is not the editable Status. Sales Start and End dates and times use the event's time zone.
Session
| Status | Meaning |
|---|---|
| Draft | Being planned. Not visible. |
| Active | Visible to attendees. Salesforce's help text: set to Active for it to be visible. |
| Canceled | Called off. |
| Postponed | Delayed, to be rescheduled. |
| Completed | Finished. |
Speaker and sponsor
| Record | Statuses | Notes |
|---|---|---|
| Speaker | Planned, Invited, Confirmed (default), Attended, Declined, Canceled, No Show | Set Confirmed when you are ready to show the speaker on the event's link. |
| Sponsor | Planned, Invited, Confirmed, Declined | Set Confirmed once the sponsor has agreed. |
Money statuses
Invoices and transactions have their own statuses (Draft to Voided for invoices; Open to Failed for transactions, plus a separate Payment Status that only applies once a transaction is Completed). They are defined in full on Money Concepts.
Audience sync states
| State | Meaning |
|---|---|
| Draft | Saved, never synced. |
| Syncing | A sync is running; you cannot send yet. |
| Ready / Done | Synced and usable. |
| Failed | The last sync failed; the reason is shown. |