Oracle answers questions like how does this feature work? or what does our spec say about expired cards? from documents, and tells you which documents it used.
Where Answers Come From
Section titled “Where Answers Come From”| Source | What it holds | Who can use it |
|---|---|---|
| Your Canon documents | The specs and documents your team uploaded to Canon | Anyone who can read Canon in that project |
| Hawzu documentation | These pages: how Hawzu itself works | Everyone |
Oracle picks the source from your question. It can use both when a question covers both, such as “how do I set this up, and what does our spec require?”
Reading the Answer
Section titled “Reading the Answer”Each answer says which source it used, just above the text: From your Canon documents, From Hawzu documentation, or From your documents and Hawzu’s.
Below the answer, it lists its sources:
- A Hawzu source shows the page title and links to it.
- A Canon source shows your document’s title and the page or section it read. It has no link, because the document lives in your project.
Choosing the Source Yourself
Section titled “Choosing the Source Yourself”Inside a project, the What to search list sits next to the question box, on both the Oracle page and the assistant panel. Pick a source to make Oracle search only there.
-
Open the What to search list.
-
Pick Auto (Oracle decides), Records (your project’s records), Canon (your own documents) or Docs (Hawzu’s documentation). In the assistant panel, the Canon option shows your workspace name, or My documents.
-
Ask your question.
Only sources available in this project are listed. A chosen source is a little faster than Auto, as well as more certain.
Getting a Better Document Answer
Section titled “Getting a Better Document Answer”Document answers are only as good as the passages Oracle can find, so how you phrase the question matters more here than it does for records:
- Name the thing. “What does our checkout spec say about promo code expiry?” finds a passage. “Tell me about checkout” finds many and picks none.
- Ask one thing at a time. Two questions in one sentence usually get one good answer and one thin one.
- Use the same words your document uses. If your spec says “voucher”, ask about vouchers, not coupons.
If an answer is thin, check whether the topic is in Canon at all before you rephrase. See Check a topic in Canon and Canon Best Practices.
When Nothing Covers It
Section titled “When Nothing Covers It”Oracle says so, and names where it looked:
I couldn’t find that in the Hawzu documentation or in your project documents.
It doesn’t fill the gap from general knowledge. If your Canon doesn’t describe a behaviour, Oracle says so. That gap is usually worth knowing about.