Case Tally Categories
Case Tally Categories
Purpose and when to use this record
Group case-specific tally definitions into understandable reporting sections.
At a glance
-
Identify it by: Name.
-
Why care: Use the agency’s approved terminology and access policy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.
Before you begin
You need the Brisk storespermission for the action you are taking on case tally categories. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.
Find and review case tally categories

Use generatedthe referenceCase Tally Categories list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.
Open the Case Tally Category whose Name match the task. If it is awaitingmissing, workflowclear review.the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.
Create a recordCase Tally Category

TheCreate evidencea packetCase identifiesTally Category only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and make later selection harder.
-
Select the business context first.
-
Enter the required identifying and operational values: Name.
-
Review Sort Order against the source
locationdocument or approved setup decision. -
Save the Case Tally Category, then confirm Name on its detail page before continuing.
After saving: Open Case Tally Definitions and confirm the Case Tally Category 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 Case Tally Category
Delete this page.Case Tally Category 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.
View
Before confirming, check for related Case Tally Definitions. Brisk may refuse deletion when another record detailsdepends
Theon evidencethis packetone; identifiesresolve the viewduplicate andor sourceuse locationthe forsupported thiscorrection action.workflow Confirminstead user-facingof stepsbreaking beforethe approving this page.trail.
Find
On andthe reviewconfirmation recordspage, 
Theverify Name. After confirmation, return to the Case Tally Categories list screenand inmake sure only the Briskintended documentationCase demo.
Review Case Tally Category details
The evidence packet identifiesUse the viewdetail page as the shared record of what this Case Tally Category currently means. Verify Name, and sourceSort locationOrder before relying on it for thisa action.decision.
Compare user-facingthe stepsCase Tally Category with its source document or approved setup request before approvingdeciding thisthat page.it needs correction.
Next check: Open Case Tally Definitions and confirm the Case Tally Category 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 recordCase Tally Category
TheEdit evidencethis packetCase identifiesTally Category when the viewunderlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and sourcecreate locationa new one.
-
Open the detail page. Compare Name with the supporting document or approved request.
-
Recheck the identifying information shown on the screen. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.
-
Save the change, return to the list, and confirm that the Case Tally Category now appears under the expected Name.
After the change: Open Case Tally Definitions and confirm the Case Tally Category appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.
Fields and business rules
Brisk stores 2 user-relevant fields for this action.Case ConfirmTally user-facingCategory, stepsincluding before0 approvinglinked-record selections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.
| Field | Required | What it controls |
|---|---|---|
| Name | Yes | Sets the name of the category. |
| Sort Order | No | Sets the order that this category appears on cases and reports. |
What happens next
Open Case Tally Definitions and confirm the Case Tally Category appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.
DeleteCommon amistakes and troubleshooting
-
The record
Thewillevidencenotpacketsave:identifiesRecheck Name and any message beside theviewfield.andA required related record may also be inactive or unavailable to your role. -
The values look right but the result is wrong: Compare this Case Tally Category with the source
locationdocumentfororthisapprovedaction.setupConfirmdecision,user-facingthenstepscheckbeforetheapprovingdownstreamthisscreenpage.where it is used.