Blueprint Types

Blueprint Types

Purpose and when to use this record

Classify assemblies and formulas for organization, filtering, and manufacturing behavior.

At a glance

• Identify it by: Name.

• 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 storespermission for the action you are taking on blueprint typestypes. asIf parta ofCreate, theEdit, manufacturingor 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.

Create a recordblueprint type

TheCreate evidencea packetblueprint identifiestype only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

1. Select the business context first.

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

3. Review Schedule On Order, and Demanufacture On Return deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the blueprint type, then confirm Name on its detail page before continuing.

After saving: Open Item Assemblies and confirm the blueprint type 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 blueprint type

Delete this page.blueprint type 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 Blueprint Types list and make sure only the intended blueprint type was removed.

ViewReview recordblueprint type details

The evidence packet identifiesUse the viewdetail page as the shared record of what this blueprint type currently means. Verify Name, Schedule On Order, and sourceDemanufacture locationOn Return before relying on it for thisa action.decision.

Confirm

Compare user-facingthe stepsblueprint type with its source document or approved setup request before approvingdeciding that it needs correction.

Next check: Open Item Assemblies and confirm the blueprint type 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 blueprint type

Edit this blueprint type when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

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

2. Recheck the identifying information shown on the screen. These values are most likely to change material demand, production status, output quantity, and cost.

3. Save the change, return to the list, and confirm that the blueprint type now appears under the expected Name.

After the change: Open Item Assemblies and confirm the blueprint type appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordsblueprint types

The evidence packet identifiesUse the viewBlueprint Types 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 blueprint type whose Name match the task. If it is missing, clear the list filters and sourcerecheck locationthe identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 3 user-relevant fields for this action.blueprint Confirmtype, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbefore

Field	Required	What packetit identifiescontrols
Name	Yes	Human-readable name for this action.blueprint Confirmtype.
Schedule approvingOn Order	No	If enabled, all items manufactured set to this page.blueprint type will create scheduled manufacturing instances.
Demanufacture On Return	No	If enabled, any time an item of this type is returned, its constituent parts will be returned to inventory instead of the manufactured good.

What happens next

Open Item Assemblies and confirm the blueprint type 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

  Thewill evidencenot packetsave: identifiesRecheck Name and any message beside the viewfield. andA required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Compare this blueprint type with the source locationdocument foror thisapproved action.setup Confirmdecision, user-facingthen stepscheck beforethe approvingdownstream thisscreen page.where it is used.