Alcohol License Details

Alcohol License Details

Purpose and when to use this record

Record alcohol-specific classifications, endorsements, dates, and conditions attached to a municipal license.

At a glance

• Identify it by: Permit Number, Authority, Issue Date, and Expiration Date.

• Check its business context: License.

• Why care: Names, periods, classifications, due dates, status, charges, and payments form an official account history. Correct them from the supporting filing, application, receipt, or ordinance.

• 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 storespermission for the action you are taking on alcohol license detailsdetails. asIf parta ofCreate, theEdit, municipalor module.Delete This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid License records ready first. Those selections determine where this Alcohol License Detail belongs and which later screens can find it.

Create aan recordAlcohol License Detail

TheCreate evidencean packetAlcohol identifiesLicense Detail only after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: License.

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

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

4. Save the Alcohol License Detail, then confirm Permit Number, Authority, Issue Date, and Expiration Date on its detail page before continuing.

After saving: Verify Active, and License on the detail page, then continue the municipal workflow only when those values agree with the source locationdocument and actual work performed.

Delete an Alcohol License Detail

Delete this Alcohol License Detail 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 thisthe page.record is merely obsolete, use Active to remove it from future use while preserving existing references.

On the confirmation page, verify Permit Number, Authority, Issue Date, and Expiration Date. After confirmation, return to the Alcohol License Details list and make sure only the intended Alcohol License Detail was removed.

ViewReview recordAlcohol License Detail details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Alcohol License Detail currently means. Verify Issue Date, Expiration Date, and sourceActive locationbefore relying on it for thisa action.decision.

Confirm

Follow user-facingLicense stepsto beforedetermine approvingwhether the issue is on this Alcohol License Detail or on one of those linked records.

Next check: Verify Active, and License on the detail page, then continue the municipal workflow only when those values agree with the source document and actual work performed.

Edit an existing Alcohol License Detail

Edit this Alcohol License Detail 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.

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

2. Recheck Issue Date, Expiration Date, and Active. These values are most likely to change license, compliance, filing, charge, payment, and official account history.

3. Save the change, return to the list, and confirm that the Alcohol License Detail now appears under the expected Active.

After the change: Verify Active, and License on the detail page, then continue the municipal workflow only when those values agree with the source document and actual work performed.

Find and review recordsalcohol license details

The evidence packet identifiesUse the viewAlcohol License Details list to find the correct record before opening or changing it. Compare Permit Number, Authority, Issue Date, and sourceExpiration locationDate. Records with similar names or numbers can still belong to different License.

• The initial order emphasizes Expiration Date, and License Number. Select a column heading when you need a different comparison.

Open the Alcohol License Detail whose Permit Number, Authority, Issue Date, and Expiration Date 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 7 user-relevant fields for this action.Alcohol ConfirmLicense user-facingDetail, stepsincluding before1 approvinglinked-record selection and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

location stepsbeforeapprovingthispage.

Delete a record

stepsbeforeapproving

Field	Required	What it controls
License	Yes	The evidencelicense packetassociated identifieswith thethis viewalcohol andlicense sourcedetail.
Permit Number	No	The permit number recorded for this action.alcohol Confirmlicense user-facingdetail.
Authority	No	The evidenceauthority packet identifies the view and source locationrecorded for this action.alcohol Confirmlicense user-facingdetail.
Issue Date	No	Date recorded for issue date on this page.alcohol license detail.
Expiration Date	No	Date recorded for expiration date on this alcohol license detail.
Active	No	Whether this alcohol license detail is active and available for use.
Compliance Notes	No	The compliance notes recorded for this alcohol license detail.

What happens next

Verify Active, and License on the detail page, then continue the municipal workflow only when those values agree with the source document and actual work performed.

Common mistakes and troubleshooting

• The record will not save: Recheck License 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: Open License from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.