Foodservice Tables

Foodservice Tables

Purpose and when to use this record

BriskMaintain storesdining foodservicetables, tablesseating ascapacity, partdisplay order, availability, and current server assignment.

At a glance

• Identify it by: Table Name.

• Check its business context: Current Server.

• Why care: Customer, warehouse, quantities, prices, tax, payment, and fulfillment represent different parts of the salestransaction. module.Review Thiseach generatedbefore referencetreating the sale as complete.

• Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on foodservice tables. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create a recordFoodservice Table

TheCreate evidencea packetFoodservice identifiesTable after searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

1. Select the business context first: Current Server.

2. Enter the required identifying and operational values: Table Name.

3. Review Active deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Foodservice Table, then confirm Table Name on its detail page before continuing.

After saving: Verify this Foodservice Table in Sales, and Suspended Sales before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Foodservice Table

Delete this Foodservice Table only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Active to remove it from future use while preserving existing references.

Before confirming, check for thisrelated action.Sales, Confirmand user-facingSuspended stepsSales. beforeBrisk approvingmay refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Table Name. After confirmation, return to the Foodservice Tables list and make sure only the intended Foodservice Table was removed.

ViewReview recordFoodservice Table details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Foodservice Table currently means. Verify Active before relying on it for a decision.

Follow Current Server to determine whether the issue is on this Foodservice Table or on one of those linked records.

Next check: Verify this Foodservice Table in Sales, and sourceSuspended locationSales before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing Foodservice Table

Edit this Foodservice Table to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Current Server with the supporting document or approved request.

2. Recheck Active. These values are most likely to change customer totals, tax, payment, fulfillment, and receivables.

3. Save the change, return to the list, and confirm that the Foodservice Table now appears under the expected Active.

After the change: Verify this action.Foodservice ConfirmTable user-facingin stepsSales, and Suspended Sales before approvingstaff thisbuild page.new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review recordsfoodservice tables

The evidence packet identifiesUse the viewFoodservice Tables list to find the correct record before opening or changing it. Compare Table Name. Records with similar names or numbers can still belong to different Current Server.

• The initial order emphasizes Sort Order, and sourceTable locationName. Select a column heading when you need a different comparison.

Open the Foodservice Table whose Table Name match the task. If it is missing, clear the list filters and recheck Active rather than creating a replacement immediately.

Fields and business rules

Brisk stores 5 user-relevant fields for this action.Foodservice ConfirmTable, user-facingincluding steps1 beforelinked-record approvingselection and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation stepsbeforeapprovingthispage.

Delete a record

steps

Field	Required	What packetit identifiescontrols
Table Name	Yes	Human-readable name for this action.food Confirmservice user-facingtable.
Seats	No	The evidenceseats packetvalue identifies the view and source locationrecorded for this action.food Confirmservice user-facingtable.
Sort Order	No	The sort order value recorded for this food service table.
Active	No	Whether this food service table is active and available for use.
Current Server	No	The current server associated with this food service table.

What happens next

Verify this Foodservice Table in Sales, and Suspended Sales before approvingstaff thisbuild new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

• The record will not save: Recheck Table Name and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Active, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Open Current Server from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.