Name the fields
Keep the blend name, origin and approved price in fields that can be inspected and updated.
← All features
Keep product facts in records you can reuse
Give recurring facts named fields, select a current record for a draft and review any change to the source separately.
Start creating in Chat ↗Define the facts once, then choose a record
Illustrative coffee collection: each blend is a structured item, separate from the writing made from it.
Select one current record
Review the chosen record revision as context for a product description. If its fields change before preparation, refresh the selection.
Approve source edits separately
Check the generated draft against the record. A proposed change to the source item needs its own review before saving.
A draft is not a record update
Creating copy does not silently replace structured facts. See one record used as context or the record workflow.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartDefine and populate approved collection fields.
- Request or actionSelect one exact record for a Writing request.
- ReviewCheck the draft against fields and review any writeback separately.
- Saved resultA saved draft and any separately approved record revision.
- ContinueReuse the correct record version for later work.
Example AskGL request
Choose Writing · with selected record
Write a short description of this blend using only the selected name, origin and approved tasting notes.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Related workflows
THE USEFUL DETAILS
Good to know.
Creation notes
Prepare your starting point
Populate fields such as name, origin, date or approved notes with information you can verify. Choose the intended record and inspect its values before preparation. Ask for a defined audience, length and format, and omit missing information rather than filling it with a plausible invention.
Write from a content recordReview what you keep
Check every claim against the selected fields. Refresh context if a record changed before preparation. A proposed record update is a separate decision with its own save flow; generating useful copy does not automatically authorize changing the underlying source. Keep the accepted draft and current facts recognizable for reuse.
Compare Knowledge and recordsCommon questions
Is every catalog capability enabled?
No. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
How should I choose the next tool?
Use the contextual links for the source, artifact or decision you have now. A feature explains a tool, a workflow explains its steps and an output guide explains the saved result.