Pages

Pages

Purpose and when to use this record

BriskBuild storesand pagespublish asa partstorefront ofinformation page with stable URL, navigation placement, content, and search metadata.

At a glance

• Identify it by: Hero Cta Label.

• Check its business context: Store.

• Why care: Store, publication, consent, payment, and fulfillment states affect what customers see and what staff must act on; check the ecommercecorrect module.store Thisbefore generatedsaving.

  reference

• 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 pages. 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.

Have valid Store records ready first. Those selections determine where this Page belongs and which later screens can find it.

Create a recordPage

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

1. Select the business context first: Store.

2. Enter the required identifying and operational values: Store, and Title.

3. Review Template, Is Published, and Show In Navigation deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Page, then confirm Hero Cta Label on its detail page before continuing.

After saving: Verify this action.Page Confirmin user-facingthe stepsnext transaction or assignment screen before approvingstaff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Page

Delete this page.Page 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 Is Published to remove it from future use while preserving existing references.

On the confirmation page, verify Hero Cta Label. After confirmation, return to the Pages list and make sure only the intended Page was removed.

ViewReview recordPage details

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

Follow Store to determine whether the issue is on this Page or on one of those linked records.

Next check: Verify this Page in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and sourceactive locationstate now rather than after transactions accumulate.

Edit an existing Page

Edit this Page 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 Store with the supporting document or approved request.

2. Recheck Template, and Is Published. These values are most likely to change storefront visibility, customer communication, payment, or fulfillment.

3. Save the change, return to the list, and confirm that the Page now appears under the expected Template, and Is Published.

After the change: Verify this action.Page Confirmin user-facingthe stepsnext transaction or assignment screen before approvingstaff thisbuild page.new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review recordspages

The evidence packet identifiesUse the viewPages list to find the correct record before opening or changing it. Compare Store, Title, Slug, and sourceSummary. locationRecords with similar names or numbers can still belong to different Store.

• Keyword search checks Title, Slug, and Nav Title.

• Narrow the list with Store filters.

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

Open the Page whose Store, Title, Slug, and Summary match the task. If it is missing, clear the list filters and recheck Store, Template, and Is Published rather than creating a replacement immediately.

Fields and business rules

Brisk stores 18 user-relevant fields for this action.Page, Confirmincluding user-facing1 stepslinked-record beforeselection approvingand 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.

Edit

anexistingrecord

Confirmuser-facingstepsbeforeapprovingConfirmuser-facingstepsbeforeapproving

Field	Required	What it controls
Store	Yes	The store associated with this page.
Title	Yes	The evidencetitle packet identifies the view and source locationrecorded for this action.page.
Slug	No	URL-safe this page. Delete a record The evidence packet identifies the view and source locationidentifier for this action.page.
Summary	No	The summary recorded for this page.
Nav Title	No	The nav title recorded for this page.
Template	No	The template recorded for this page. Available values: Default, Landing, FAQ, About.
Hero Title	No	The hero title recorded for this page.
Hero Subtitle	No	The hero subtitle recorded for this page.
Hero Cta Label	No	The hero cta label recorded for this page.
Hero Cta Url	No	The hero cta URL recorded for this page.
Content Blocks	No	Structured content blocks data stored for this page.
Seo Title	No	The SEO title recorded for this page.
Meta Description	No	The meta description recorded for this page.
Seo Keywords	No	Comma-separated focus keywords used for on-page SEO guidance and meta tags.
Body	No	The body recorded for this page.
Is Published	No	Whether this page is published.
Show In Navigation	No	Whether the show in navigation option applies to this page.
Sort Order	No	The sort order value recorded for this page.

What happens next

Verify this Page in the next transaction or assignment screen before staff build 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 Store, and Title 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 Template, and Is Published, 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 Store from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.