jmcqueen
351f89a9a4
Multi-integration Webex chat/HTTP bot that unifies phone, AV, and network status for retail store support. Consolidates data from Webex Calling, Meraki, Workspace ONE (MDM), Atlas AMP, RED digital signage, and OptiSigns into rich per-store status commands. Key surfaces: - /phonestatus, /avstatus — per-store phone & AV device reports with clickable Meraki deep-links and per-port detail. - /webexhost — check/assign Webex Meetings host licenses via the Service App; adaptive-card confirmation flow, HTTP-API-gated. - /offboarduser — full Webex Admin offboarding (auth revoke, device wipe, license removal); adaptive-card confirmation. - /jirapoll — on-demand trigger for the hourly Jira poller. - /bulkavstatuscsv — bulk store CSV export with concurrency limits. Automation: - Hourly Jira poller (node-cron) with an X.AI (Grok) ticket classifier that categorizes unassigned tickets as phone/av/skip, extracts store numbers from free-text, and enriches Jira with the same detailed markdown the chat commands emit (converted to Jira ADF, preserves bold + Meraki links). Idempotent via a `bot-enriched` Jira label. Architecture: - Node.js 20+, ESM, Express 5, webex-node-bot-framework. - Layered integrations (integrations/*), services (services/*), commands (commands/*), utils (utils/*). - Shared markdown renderers (services/renderers/*) feed both chat handlers and the Jira poller so the two surfaces stay in sync. - Hand-rolled markdown-to-ADF converter (utils/markdownToAdf.js) — no new npm dependency. - Node built-in test runner (`node --test tests/*.test.js`), 30 tests covering the converter, renderers, and poller ADF assembly. Docker + docker-compose deployment. Config via .env (see .env.example for the full option surface).
42 lines
No EOL
1.5 KiB
JavaScript
42 lines
No EOL
1.5 KiB
JavaScript
// src/commands/woSummary.js
|
||
import { collectWoSummary } from '../services/woService.js';
|
||
import { logger } from '../utils/logger.js';
|
||
|
||
export async function handleWoSummary(bot, trigger) {
|
||
logger('wo:summary', 'Handler entered');
|
||
|
||
// Support both Webex (args) and HTTP (query)
|
||
const query = trigger.query || {};
|
||
const args = trigger.args || [];
|
||
|
||
// Get work order number from args or query param
|
||
const woNumber = (args[0] || query.woNumber || query.wo || query.workorder || query.id || '')
|
||
.trim();
|
||
|
||
if (!woNumber || !/^\d+$/.test(woNumber)) {
|
||
const usage = '**Work Order Summary Usage:**\n' +
|
||
'`/woSummary 123456` → Get detailed summary for a specific work order\n\n' +
|
||
'Also works via HTTP: `?woNumber=123456`';
|
||
|
||
await bot.say('markdown', usage);
|
||
return;
|
||
}
|
||
|
||
logger('wo:summary', `Fetching summary for work order ${woNumber}`);
|
||
|
||
try {
|
||
const summary = await collectWoSummary(woNumber);
|
||
|
||
let reply = `**Work Order Summary – ${woNumber}**\n\n`;
|
||
reply += `${summary || 'No summary data available.'}\n`;
|
||
reply += `\n*Last checked: ${new Date().toLocaleTimeString()}*`;
|
||
|
||
await bot.say('markdown', reply.trim());
|
||
|
||
logger('wo:summary', `Successfully returned summary for WO ${woNumber}`);
|
||
|
||
} catch (err) {
|
||
logger('wo:summary', `Error fetching summary for WO ${woNumber}: ${err.message}`, 'error');
|
||
await bot.say('markdown', `❌ Error fetching work order summary for **${woNumber}**: ${err.message}`);
|
||
}
|
||
} |