Skip to main content

Xurrent Documentation Assessment

Assessment Date: February 9, 2026 Scope: Xurrent integration documentation accuracy and alignment with codebase


Executive Summary

Status: ❌ DOCUMENTATION INACCURATE

The Xurrent documentation contains a critical navigation error that will prevent users from accessing the feature. The documented path does not match the actual implementation in the codebase.


Critical Issues

1. Incorrect Navigation Path ❌

Documentation States (Line 129):

1. Navigate to **CMDB****Integrations****Xurrent**
2. Click **Add Integration**

Actual Implementation:

  • Location: frontend/src/components/Layout/MainMenu.tsx (Lines 878-963)
  • Correct Path: DiscoveryIntegrationsConfigure Xurrent

Evidence from Code:

// MainMenu.tsx Line 878-909
{/* Integrations Menu Item */}
<ListItem
button
sx={{ pl: 4 }}
onClick={handleIntegrationsClick}
>
<ListItemText
primary="Integrations" // This is under "Discovery" parent
/>
</ListItem>

// MainMenu.tsx Line 917-928
<ListItem
button
sx={{ pl: 6 }}
onClick={() => navigate('/integrations/xurrent/config')}
>
<ListItemText
primary="Configure Xurrent" // This is the actual menu label
/>
</ListItem>

Routes Configuration (routes.tsx Lines 75-80):

{/* Xurrent Integration Routes - To match MainMenu paths */}
<Route path="/integrations/xurrent/config" element={<XurrentIntegrationList />} />
<Route path="/integrations/xurrent/config/:configId" element={<XurrentConfigDetail />} />
<Route path="/integrations/xurrent/wizard/new" element={<XurrentIntegrationWizard />} />
<Route path="/integrations/xurrent/wizard/:configId" element={<XurrentIntegrationWizard />} />
<Route path="/integrations/xurrent/export" element={<XurrentIntegrationList />} />

Impact: CRITICAL - Users following documentation will not find the feature


Actual Menu Hierarchy

Discovery (parent menu)
├── Scan Data
├── Import to CMDB
├── Discovery Agents
├── Discovery Schedules
├── Discovery Tokens
└── Integrations (submenu)
├── Configure Xurrent → /integrations/xurrent/config
└── Export to Xurrent → /integrations/xurrent/export

State Management

  • Handler: handleIntegrationsClick() (Line 319)
  • State Variable: integrationsOpen (Line 266)
  • Parent: Discovery section (discoveryOpen state)
  • Menu Icon: 'Sync' icon for Integrations submenu

Other Documentation Issues

2. Button Label Mismatch ⚠️

Documentation: "Click Add Integration" Likely Reality: The button may be labeled "Add Configuration" or "New Configuration" (needs verification in XurrentIntegrationList component)

Action Required: Verify button label in XurrentIntegrationList.tsx


3. Secondary Navigation Path ⚠️

Documentation States (Line 218):

1. Navigate to **CMDB****Integrations****Xurrent**
2. Click on an existing configuration

Actual Path: Same issue - should be DiscoveryIntegrationsConfigure Xurrent

Impact: MEDIUM - Affects Classic View section


Verified Correct Information ✅

Screenshots

All referenced screenshots exist in the correct location:

  • /img/CISync/Xurrent/1-basic_config.png
  • /img/CISync/Xurrent/2-ci_ctypes.png
  • /img/CISync/Xurrent/2.2-add_ci_type.png
  • /img/CISync/Xurrent/2.3.png
  • /img/CISync/Xurrent/3.1-configure_ci_type.png
  • /img/CISync/Xurrent/3.2-product_mapping.png
  • /img/CISync/Xurrent/3.3-single_type_mapping.png
  • /img/CISync/Xurrent/4-review.png

Routes

All documented routes are properly configured:

  • /integrations/xurrent/config - List view
  • /integrations/xurrent/config/:configId - Detail view
  • /integrations/xurrent/wizard/new - New wizard
  • /integrations/xurrent/wizard/:configId - Edit wizard
  • /integrations/xurrent/export - Export view

Component Structure

All referenced React components exist:

  • XurrentIntegrationList.tsx
  • XurrentConfigDetail.tsx
  • XurrentIntegrationWizard.tsx
  • ProductMappingTab.tsx
  • FieldMappingTab.tsx
  • ExportTab.tsx
  • AIChangeManagerTab.tsx

Required Fixes

Priority 1: Critical Navigation Path

File: /Volumes/ProjectsCS/killit_v3/documentation/docs/integrations/xurrent.md

Line 129 - Change from:

1. Navigate to **CMDB****Integrations****Xurrent**
2. Click **Add Integration**

To:

1. Navigate to **Discovery****Integrations****Configure Xurrent**
2. Click **Add Configuration** (or verify actual button label)

All other occurrences (Lines 218, etc.) - Same fix required


Priority 2: Verify Button Label

Component to Check: frontend/src/components/CMDB/Integrations/XurrentIntegrationList.tsx

Action: Verify the exact label of the button that opens the wizard

  • Expected locations: "Add Configuration", "New Configuration", "Create Integration"
  • Update documentation to match actual button label

Priority 3: Screenshot Verification

Action: Review all screenshots to ensure they show:

  1. Correct navigation path (Discovery → Integrations)
  2. Correct button labels
  3. Current UI state (Material-UI theme, layout)

Particularly Important:

  • 1-basic_config.png - Should show the wizard entry point
  • All screenshots should reflect the Discovery menu structure

Testing Checklist

Before documentation is marked as "reviewed":

  • User can successfully navigate to Xurrent configuration using documented path
  • All menu labels match documentation exactly
  • All button labels match documentation exactly
  • Screenshots accurately reflect current UI
  • Routes work as documented
  • No broken links in documentation
  • "Related Documentation" links are valid

Additional Recommendations

1. Add Troubleshooting Section for Navigation

Add FAQ:

**Q: I can't find the Xurrent integration under CMDB**

A: The Xurrent integration is located under **Discovery****Integrations****Configure Xurrent**,
not under CMDB. This reflects the integration's role in the discovery and synchronization workflow.

2. Update Architecture Notes

Consider adding an "Architecture" or "Design Decision" note explaining why Xurrent is under Discovery:

### Why is Xurrent Under Discovery?

The Xurrent integration is strategically placed under the Discovery menu because:
- It synchronizes discovered configuration items (CIs) to Xurrent
- It's part of the discovery-to-ITSM workflow
- It follows the data flow: Discovery → Integration → ITSM

3. Add Visual Navigation Guide

Consider adding a screenshot showing the actual menu structure with the correct path highlighted.


Database Schema Verification

File: backend/models/menuitem.js

Schema Structure: ✅ Verified

  • Contains proper menu hierarchy support (parentId, level)
  • Supports different menu types (parent, sub, item, separator)
  • Has action types (link, table, custom)
  • Includes permissions and roles

Note: The actual menu items are likely stored in MongoDB, not hardcoded. The MainMenu component reads from database or uses static configuration.


Conclusion

Summary of Findings:

  1. CRITICAL: Navigation path is completely wrong (CMDB vs Discovery)
  2. ⚠️ WARNING: Button label may be incorrect (needs verification)
  3. CORRECT: All routes, components, and screenshots exist
  4. CORRECT: Technical content and feature descriptions appear accurate

Recommendation: BLOCK DOCUMENTATION PUBLICATION until Priority 1 fix is verified and deployed. This is a user-blocking issue that will cause immediate frustration and support tickets.

Estimated Fix Time:

  • Documentation update: 15 minutes
  • Screenshot verification: 30 minutes
  • Testing with actual application: 15 minutes
  • Total: ~1 hour

Risk if Not Fixed:

  • 100% of new users will be unable to find Xurrent integration
  • High support ticket volume
  • Loss of user confidence in documentation quality
  • Potential impact on product adoption and satisfaction

Sign-off

Documentation Status: ❌ NOT READY FOR PUBLICATION Next Action: Fix navigation path and verify button labels Review Required: Full navigation path walkthrough with actual application


Assessment completed using codebase analysis tools and menu structure verification