Skip to main content

Navigation Menus

Navigation Menus

Purpose and when to use this record

Configure which Brisk storesmodule groups and favorites appear in a named navigation menusmenu.

as

At parta ofglance

  • Identify it by: Name.

  • Why care: Setup changes can alter navigation, alerts, and authorization for many users. Test the setupeffect module.with Thisthe generatedintended referencerole or device before broad use.

Before you begin

You need the Brisk permission for the action you are taking on navigation menus. 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 recordNavigation Menu

Brisk Navigation Menus create screen displayed with fictional documentation-demo data.
The Navigation Menus create screen in the Brisk documentation demo.

TheCreate evidencea packetNavigation identifiesMenu only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

  1. Select the business context first.

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

  3. Review Show Favorites, Show Sales, Show Ecommerce, Show Inventory, Show Accounting, and Show Manufacturing, plus the remaining screen fields deliberately; these choices control availability or workflow rather than merely describing the record.

  4. Save the Navigation Menu, then confirm Name on its detail page before continuing.

After saving: Open Menu Links and confirm the Navigation Menu appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete a Navigation Menu

Delete this page.Navigation Menu 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.

Before confirming, check for related Menu Links. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name. After confirmation, return to the Navigation Menus list and make sure only the intended Navigation Menu was removed.

ViewReview recordNavigation Menu details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Navigation Menu currently means. Verify Name, Description, Show Favorites, and sourceShow locationSales before relying on it for thisa action.decision.

Confirm

Compare user-facingthe stepsNavigation Menu with its source document or approved setup request before approvingdeciding that it needs correction.

Next check: Open Menu Links and confirm the Navigation Menu appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Edit an existing Navigation Menu

Edit this Navigation Menu when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

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

  2. Recheck Show Accounting. These values are most likely to change navigation, notifications, access, and other users’ behavior.

  3. Save the change, return to the list, and confirm that the Navigation Menu now appears under the expected Name.

After the change: Open Menu Links and confirm the Navigation Menu appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordsnavigation menus

Brisk Navigation Menus list screen displayed with fictional documentation-demo data.
The Navigation Menus list screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewNavigation Menus list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.

  • The initial order emphasizes Id. Select a column heading when you need a different comparison.

Open the Navigation Menu whose Name match the task. If it is missing, clear the list filters and sourcerecheck locationthe identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 17 user-relevant fields for this action.Navigation ConfirmMenu, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbeforeapproving
Field Required What packetit identifiescontrols
NameYesHuman-readable name for this action.navigation Confirmmenu.
Description NoLeave any notes about this page.menu here.
Show FavoritesNoShow or hide the favorites submenu.
Show SalesNoShow or hide the sales submenu.
Show EcommerceNoShow or hide the ecommerce submenu.
Show InventoryNoShow or hide the inventory submenu.
Show AccountingNoShow or hide the accounting submenu.
Show ManufacturingNoShow or hide the manufacturing submenu.
Show ManagementNoShow or hide the management submenu.
Show ReportsNoShow or hide the reports submenu.
Show SetupNoShow or hide the setup submenu.
Show ServiceNoShow or hide the service submenu.
Show TimeNoShow or hide the time submenu.
Show PayrollNoShow or hide the payroll submenu.
Show Law EnforcementNoShow or hide the law enforcement submenu.
Show MunicipalNoShow or hide the municipal submenu.
Show Multi-StoreNoShow or hide the multi-store submenu.

What happens next

DeleteCommon amistakes and troubleshooting

  • The record

    Thewill evidencenot packetsave: identifiesRecheck Name and any message beside the viewfield. andA required related record may also be inactive or unavailable to your role.

  • The values look right but the result is wrong: Compare this Navigation Menu with the source locationdocument foror thisapproved action.setup Confirmdecision, user-facingthen stepscheck beforethe approvingdownstream thisscreen page.where it is used.