Document App — example output

███╗ ██╗ ██████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ██╗██╗████████╗ ████╗ ██║██╔═══██╗██║ ██║ ██╔══██╗██║ ██║ ██╔╝██║╚══██╔══╝ ██╔██╗██║██║ ██║██║ █╗ ██║ ███████║██║ █████╔╝ ██║ ██║ ██║╚████║██║ ██║██║███╗██║ ██╔══██║██║ ██╔═██╗ ██║ ██║ ██║ ╚███║╚██████╔╝╚███╔███╔╝ ██║ ██║██║ ██║ ██╗██║ ██║ ╚═╝ ╚══╝ ╚═════╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ✦ NowAIKit — The #1 AI App for ServiceNow - Running docs-app in direct mode (ollama)... # demo2 — Technical Documentation ## Version: TBD | Scope: [Restricted - Authorization Required] > **⚠️ IMPORTANT NOTICE**: Access restrictions detected. The current authenticated session lacks sufficient privileges to fully enumerate the application. Documentation has been compiled from available data with appropriate limitations noted. Full documentation requires elevated permissions (admin/sysadmin role). --- ## Table of Contents 1. [Application Overview](#1-application-overview) 2. [Data Model](#2-data-model) 3. [Server-Side Logic](#3-server-side-logic) 4. [Client-Side Logic](#4-client-side-logic) 5. [Security Model](#5-security-model) 6. [Flows & Automation](#6-flows--automation) 7. [Service Catalog](#7-service-catalog) 8. [Integrations](#8-integrations) 9. [Portal](#9-portal) 10. [Notifications](#10-notifications) 11. [Known Limitations](#11-known-limitations) --- ## 1. Application Overview ### 1.1 Application Identification | Attribute | Value | |-----------|-------| | Application Name | demo2 | | Scope | Requires admin access to retrieve | | Version | Not available without proper access | | Status | Production/Demo Instance | | Environment | demo2 | ### 1.2 Business Context The application appears to be a demonstration ServiceNow instance based on: - Catalog items related to IT operations, HR, facilities - Security-related processes (Threat Lookups, Microsoft Exchange Integration) - Integration patterns with Azure, Jenkins, and Microsoft services - ITIL-related processes (Change Management, Incident Management) ### 1.3 Key Functional Areas Identified Based on catalog items and flows, the application covers: - IT Service Management: Standard Change Management, Incident Management - Security Operations: Threat detection, Microsoft Exchange integration - HR Operations: Role delegation, Direct Deposit inquiries - Facilities Management: Heating & Cooling requests - Azure Integration: Azure MCA, Azure AD provisioning - Compliance: Privacy tasks, Control objectives mapping - Knowledge Management: Knowledge ownership group management --- ## 2. Data Model ### 2.1 Table Access Status | Status | Description | |--------|-------------| | ❌ **Restricted** | `get_table_schema` - User Not Authorized | | ❌ **Restricted** | `query_records` on `sys_db_object` | | ⚠️ Partial | Business Rules accessible (50+ records) | | ⚠️ Partial | Client Scripts accessible (5 records) | | ⚠️ Partial | Flows accessible (50+ records) | | ⚠️ Partial | Catalog Items accessible (30+ records) | | ❌ **Restricted** | ACLs, Script Includes, Roles | ### 2.2 Schema Discovery Limitation Technical Issue: Current session does not have permissions to query: - `sys_db_object` (table definitions) - `sys_dictionary` (field definitions) - `sys_table` (table metadata) Workaround Needed: Access the instance via a privileged account or use Instance Analytics API. ### 2.3 Inferred Table Structure Based on business rule names and catalog patterns, likely tables include: | Table | Description | Confidence | |-------|-------------|------------| | `snsc_task` | Task-related records | High | | `sys_user` | User-related records | Medium | | `sc_cat_item` | Catalog items | High | | `sys_db_object` | Table definitions | Low (restricted) | --- ## 3. Server-Side Logic ### 3.1 Business Rules Summary Total Business Rules: 50+ (showing 30 from sample) | Business Rule | When | Active | Collection | Purpose | ... (360 more lines — full output truncated for screenshot)