Mastering Catalog Integration & Multi-Knowledge Base Assistants
🎯Mission Briefing
The name's Dork. 007 Dork, and I have a license to question.
THE SITUATION: A customer has experienced turnover in their development department. There's yelling. Lots of yelling. "WHAT DO THESE VALUES MEAN?!" echoes through the halls. Dashboard fields are a mystery. Status codes are hieroglyphics. Chaos reigns.
YOUR MISSION: Add unstructured application design documentation to the Qlik catalog, create a new knowledge base from those existing files, and enhance your Field Training Assistant with this intelligence. Then query the original programming team's documentation to understand what those mysterious values actually mean.
DELIVERABLE: An enhanced assistant that can answer questions about both agent information AND application design documentation, demonstrating how knowledge bases can share files and grow in power over time.
PREREQUISITES:⚠️ You must complete Module 1 first! You'll need your existing Field Training Assistant from that mission.
📦Field Equipment
What You'll Need:
Access to Qlik Answers in your environment
Completed Module 1 (Field Training Assistant must exist)
Q Division Application Design documents (2 PDF files included in download)
This time, we're taking a different approach. Instead of uploading files directly to a knowledge base, we're adding them to the Qlik catalog first. Why? Because catalog files can be shared across multiple knowledge bases and assistants - upload once, use everywhere!
Navigate to your Qlik hub and locate the file upload area.
⚠️CRITICAL: At the bottom of the upload dialog, verify the space selector is set to "Q Division Field Academy" - do NOT let it default to your personal space!
Unzip your mission pack and drag and drop both PDFs into the upload area:
Q Division Data Model documentation
Q Division Case Status documentation
Watch as they load into your catalog. You now have 2 additional files in your Q Division Field Academy space.
Step 2: Create Your Application Design Knowledge Base
Click to create a new knowledge base and name it: "Q Division Application Design"
This knowledge base will contain information about how your Q Division application (which you'll build in a future module) was originally designed by the programming team.
Here's where it gets interesting. In Module 1, we walked through browsing and uploading files directly. But now those files already exist in your catalog!
Instead of the "Upload files" option, choose "Use from catalog".
Filter to show files from "Q Division Field Academy" space.
Select both documents:
✓ Q Division Data Model
✓ Q Division Case Status Documentation
Click to add them to your knowledge base.
Step 3: Index Your Application Intelligence
If you're wagging your finger at the screen right now saying "But 007 Dork, you forgot to index!" - EXCELLENT! You're learning!
Navigate to your new "Q Division Application Design" knowledge base and check the index status. It will show "Never been indexed."
Click "Index All" and wait for completion. Each document should index quickly.
Refresh and verify: "Index Status: Completed" ✓
Step 4: Enhance Your Existing Assistant (DO NOT Create a New One!)
Here's the power move. We're NOT creating a new assistant. We're making your existing assistant smarter by adding a second knowledge base to it.
Navigate to the Answers section and find your assistants.
Pro tip: If you're lost in a sea of documents, use the filter at the top to show "Assistants only" - you'll recognize them by their distinctive icons.
Open your "Field Training Assistant" that you created in Module 1.
You'll see it already has access to the "Agent Information" knowledge base (it's even grayed out to show it's already connected).
Now click to add another knowledge base. Filter to "Q Division Field Academy" space.
Select "Q Division Application Design" and add it.
Boom. Your assistant now has access to TWO knowledge bases. This is how assistants grow in power over time!
Step 5: Query Application Design Documentation
Time to test your enhanced intelligence network. Expand the assistant chat interface and ask:
"Can you help me understand how agent case status is tracked and what the values mean?"
Watch the reasoning panel (because we're operatives, not civilians):
Answers Agent activates first - collecting data sources and formulating a strategy
Knowledge Base Agent takes over - searching through your newly indexed documentation
The response flows back with the Answers Agent delivering the answer
You should receive information about the case status phases:
Open - Initial case creation
In Progress - Agent is actively working
Escalated - Requires higher authority
Resolved - Agent work is complete
Closed - Client has verified resolution
Step 6: The Critical Detail (Remember This!)
Pay special attention to this distinction: "Resolved" means the agent's work is done, but the case is NOT physically closed yet because we're waiting on client verification.
🎯FIELD NOTE FOR FUTURE MISSIONS: Remember this distinction between Resolved and Closed! In an advanced training module, we're going to revisit this question when building applications. If you're not aware of this difference, your case number counts won't add up correctly, and you'll be scratching your head wondering why. Hint, hint, wink, wink!
Click on the citations to see exactly where in the documentation this information came from. Jump directly to the source documents if you want to read more context.
✅ Mission Debrief
What You've Accomplished:
✓ Uploaded files to the Qlik catalog (not directly to a knowledge base)
✓ Created a knowledge base using catalog files
✓ Enhanced an existing assistant with multiple knowledge bases
✓ Queried unstructured documentation about data meaning (not the data itself)
✓ Understood the critical difference between Resolved and Closed status
✓ Learned how knowledge bases can share files across assistants
Validation Check: Can you ask your Field Training Assistant questions about BOTH agent information (Module 1) AND application design (Module 2)? If yes, your assistant is now multi-talented! 🎯
The Big Picture: You've just learned how to scale your Q Division intelligence network. As you find more sources of unstructured data - design docs, meeting transcripts, training videos, data dictionaries, programmer notes - you can add them as new knowledge bases. Your assistants grow smarter over time without starting from scratch.
Challenge Exercise (Optional): One of the documents now available to you in the assistant describes the application. Find out how much you can learn about the application data model and master items without reading the PDF. You will soon earn the privilege of accessing the Q Division operational data application.
📚 Field Notes: Technical Deep-Dive
Why Upload to Catalog vs. Direct to Knowledge Base?
Catalog Upload Benefits:
Reusability: One file can be used in multiple knowledge bases
Governance: Centralized file management and version control
Efficiency: Upload once, reference many times
Organization: Better file discovery across your environment
🎬 Mission Accomplished, Operatives!
You've successfully enhanced your Field Training Assistant with application design intelligence. Over time, your assistants can grow in power as you find more and more sources of unstructured data and create more and more knowledge bases.
Your assistant started with only the ability to answer questions about agents themselves. Now it also supports questions about application design from the original programming staff - an application that will be revealed to you soon, operatives. But let's face it: you have more training to do before you're entrusted with Q Division Operation Data.
Remember: The most dangerous weapon in your arsenal isn't a golden gun - it's a golden question! 🎯
Dork 007 Dork, signing off. Keep your documentation indexed and your queries semantic.
Questions? Feedback? In this AI powered world with meeting transcripts automatically generated, what do you think of this idea of a knowledge base that stores them? Have you had situations in the past where a developer had left and you really could have used access to their original documentation?👎
