Create and triage a case
A case is the persistent home for an Atlas investigation. Everything you pin to it stays there — other teammates open the same case and see the same evidence trail.
1 · Create
Section titled “1 · Create”Click Cases in the left nav, then + New case. The form asks for six fields:
- Title — one sentence describing the work (e.g. “Sales-order readiness on S/4HANA 2023”)
- Description — optional context a reviewer should read first
- Owner — defaults to you
- Modules — one or more SAP modules (FI, CO, MM, SD, PP, PM, QM, HR, PS, WM, LE)
- Posture —
clean-core,pragmatic, orunconstrained— scopes the guidance Atlas will emit - Source → target — the two release scopes Atlas will compare against
Submit. Atlas calls POST /api/atlas/cases and opens the case on the Resolve tab.
2 · Triage with an anchored query
Section titled “2 · Triage with an anchored query”The Resolve tab is scoped to the case’s modules and release pair. Pick a starter prompt — “which deprecated APIs does the source release use?” is a good first triage — and press Ask.
Atlas returns a blocker list. Skim it for the top three items; open each drawer and press Pin to case. You now have an evidence backbone for the case.
3 · Check the corpus freshness
Section titled “3 · Check the corpus freshness”Switch to the Corpus tab. Make sure the sources behind your pinned evidence are fresh; a stale source (> 72 h) will downgrade findings silently. If anything is red, add a re-scope note and come back once the crawler has refreshed (the next cycle is every few hours).
4 · Hand off to a teammate
Section titled “4 · Hand off to a teammate”Every case has a shareable URL (/app/cases/<id>). Copy it into chat or a ticket. The teammate opens it and sees the same four tabs, the same pinned evidence, and the same Atlas state — no export, no CSV, no reconciliation.