Vehicles

Vehicles

Purpose and when to use this record

BriskMaintain storesagency vehicles asused partfor ofdispatch, mileage, and transportation records.

At a glance

• Identify it by: Car Number, and Description.

• Why care: Use the lawagency’s enforcementapproved module.terminology Thisand generatedaccess referencepolicy. 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 vehicles. 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 recordvehicle

TheCreate evidencea packetvehicle identifiesonly after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first.

2. Enter the required identifying and operational values: Car Number, and Description.

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

4. Save the vehicle, then confirm Car Number, and Description 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 locationdocument and actual work performed.

Delete a vehicle

Delete this vehicle 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 thisa action.real Confirmevent user-facingthat stepslater beforechanged.

approving

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

Before confirming, check for related Logs, and Transportation Entries. Brisk may 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 Car Number, and Description. After confirmation, return to the Vehicles list and make sure only the intended vehicle was removed.

ViewReview recordvehicle details

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

Compare the vehicle 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 sourceactual locationwork forperformed.

Edit an existing vehicle

Edit this action.vehicle Confirmto user-facingcorrect stepsor beforecomplete approvingthe thissame source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.

1. Open the detail page. Compare Car Number, and Description with the supporting document or approved request.

2. Recheck Active. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.

3. Save the change, return to the list, and confirm that the vehicle 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 recordsvehicles

The evidence packet identifiesUse the viewVehicles list to find the correct record before opening or changing it. Compare Car Number, and sourceDescription. locationCompare the full identifier rather than relying on a similar name.

Open the vehicle whose Car Number, and Description 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 3 user-relevant fields for this action.vehicle, Confirmincluding user-facing0 stepslinked-record beforeselections approvingand 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
Car Number	Yes	The designated number of the vehicle.
Description	Yes	Provides a description of the vehicle.
Active	No	If this field is unchecked, this vehicle 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.

EditCommon anmistakes existingand troubleshooting

• The record

  Thewill evidencenot packetsave: identifiesRecheck Car Number, and Description and any message beside the viewfield. andA 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 vehicle with the source locationdocument foror thisapproved action.setup Confirmdecision, user-facingthen steps before approving this page.

  Delete a record

  The evidence packet identifiescheck the viewdownstream andscreen sourcewhere locationit foris this action. Confirm user-facing steps before approving this page.used.