Mixers
Mixers
Purpose and when to use this record
Maintain the mixers or production resources available when scheduling and recording batches.
At a glance
-
Identify it by: Name.
-
Check its business context: Uom.
-
Why care: Confirm item, formula, unit, warehouse, quantity, and production state together; mistakes can distort both material consumption and finished-goods cost.
Before you begin
You need the Brisk permission for the action you are taking on mixers. 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.
Have valid Uom records ready first. Those selections determine where this mixer belongs and which later screens can find it.
Create a mixer
Create a mixer after searching for the person, organization, item, location, or resource under alternate names and identifiers. Merge or correct an existing master record instead of creating a duplicate.
-
Select the business context first: Uom.
-
Enter the required identifying and operational values: Name, Size, and Uom.
-
Review the identifying information shown on the screen against the source document or approved setup decision.
-
Save the mixer, then confirm Name on its detail page before continuing.
After saving: Verify this mixer in Item Assemblies before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.
Delete a mixer
Delete this mixer 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.
Before confirming, check for related Item Assemblies. 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 Mixers list and make sure only the intended mixer was removed.
Review mixer details
Use the detail page as the shared record of what this mixer currently means. Verify Name, Size, and Uom before relying on it for a decision.
Follow Uom to determine whether the issue is on this mixer or on one of those linked records.
Next check: Verify this mixer in Item Assemblies before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.
Edit an existing mixer
Edit this mixer to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.
-
Open the detail page. Compare Uom with the supporting document or approved request.
-
Recheck the identifying information shown on the screen. These values are most likely to change material demand, production status, output quantity, and cost.
-
Save the change, return to the list, and confirm that the mixer now appears under the expected Name.
After the change: Verify this mixer in Item Assemblies before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.
Find and review mixers
Use the Mixers list to find the correct record before opening or changing it. Compare Name. Records with similar names or numbers can still belong to different Uom.
Open the mixer whose Name match the task. If it is missing, clear the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.
Fields and business rules
Brisk stores 3 user-relevant fields for this mixer, including 1 linked-record selection 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 | Human-readable name for this mixer. |
| Size | Yes | Represents the capacity of the mixer. |
| Uom | Yes | Sets the unit of measure on the mixer size. |
What happens next
Verify this mixer in Item Assemblies 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 Name, Size, and Uom and any message beside the field. A required related record may also be inactive or unavailable to your role.
-
The values look right but the result is wrong: Open Uom from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.