Case Jurisdictions Case Jurisdictions Purpose and when to use this record Maintain the jurisdictions available for assigning responsibility and reporting cases. 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. 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 case jurisdictions. 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. Create a Case Jurisdiction The Case Jurisdictions create screen in the Brisk documentation demo. Create a Case Jurisdiction only after confirming that the source document or operational event has not already been entered. Select the business context first. Enter the required identifying and operational values: Name . Review Active deliberately; these choices control availability or workflow rather than merely describing the record. Save the Case Jurisdiction, then confirm Name on its detail page before continuing. After saving: Verify Active on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed. Delete a Case Jurisdiction Delete this Case Jurisdiction only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for a real event that later changed. If the record is merely obsolete, use Active to remove it from future use while preserving existing references. Before confirming, check for related Arrests , and Cases . 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 Case Jurisdictions list and make sure only the intended Case Jurisdiction was removed. Review Case Jurisdiction details Use the detail page as the shared record of what this Case Jurisdiction currently means. Verify Active before relying on it for a decision. Compare the Case Jurisdiction with its source document or approved setup request before deciding that it needs correction. Next check: Verify Active on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed. Edit an existing Case Jurisdiction Edit this Case Jurisdiction to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed. Open the detail page. Compare Name with the supporting document or approved request. Recheck Active . 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 Jurisdiction now appears under the expected Active . After the change: Verify Active on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed. Find and review case jurisdictions The Case Jurisdictions list screen in the Brisk documentation demo. Use the Case Jurisdictions 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 Jurisdiction whose 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 2 user-relevant fields for this Case Jurisdiction, including 0 linked-record selections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this full reference. Field Required What it controls Name Yes Sets the name of this jurisdiction. Active No If this field is unchecked, this jurisdiction will no longer appear in reports. What happens next Verify Active on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed. Common mistakes and troubleshooting The record will not save: Recheck 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: Compare this Case Jurisdiction with the source document or approved setup decision, then check the downstream screen where it is used.