0978e485dc
Problem:
- After wizard form submission, need to wait for claim data from n8n
- Claim data comes via Redis channel claim:plan:{session_token}
- Need to display confirmation form with claim data
Solution:
1. Backend: Added SSE endpoint /api/v1/claim-plan/{session_token}
- Subscribes to Redis channel claim:plan:{session_token}
- Streams claim data from n8n to frontend
- Handles timeouts and errors gracefully
2. Frontend: Added subscription to claim:plan channel
- StepWizardPlan: After form submission, subscribes to SSE
- Waits for claim_plan_ready event
- Shows loading message while waiting
- On success: saves claimPlanData and shows confirmation step
3. New component: StepClaimConfirmation
- Displays claim confirmation form in iframe
- Receives claimPlanData from parent
- Generates HTML form (placeholder - should call n8n for real HTML)
- Handles confirmation/cancellation via postMessage
4. ClaimForm: Added conditional step for confirmation
- Shows StepClaimConfirmation when showClaimConfirmation=true
- Step appears after StepWizardPlan
- Only visible when claimPlanData is available
Flow:
1. User fills wizard form → submits
2. Form data sent to n8n via /api/v1/claims/wizard
3. Frontend subscribes to SSE /api/v1/claim-plan/{session_token}
4. n8n processes data → publishes to Redis claim:plan:{session_token}
5. Backend receives → streams to frontend via SSE
6. Frontend receives → shows StepClaimConfirmation
7. User confirms → proceeds to next step
Files:
- backend/app/api/events.py: Added stream_claim_plan endpoint
- frontend/src/components/form/StepWizardPlan.tsx: Added subscribeToClaimPlan
- frontend/src/components/form/StepClaimConfirmation.tsx: New component
- frontend/src/pages/ClaimForm.tsx: Added confirmation step to steps array
57 lines
2.2 KiB
SQL
57 lines
2.2 KiB
SQL
-- Миграция для добавления полей unified_id, contact_id, phone в таблицу clpr_claims
|
|
-- Дата: 2025-11-21
|
|
-- Описание: Добавляем поля для хранения идентификаторов пользователя напрямую в таблице заявок
|
|
|
|
-- 1. Добавляем unified_id (уникальный идентификатор пользователя из CRM)
|
|
ALTER TABLE clpr_claims
|
|
ADD COLUMN IF NOT EXISTS unified_id TEXT;
|
|
|
|
-- 2. Добавляем contact_id (ID контакта в RetailCRM)
|
|
ALTER TABLE clpr_claims
|
|
ADD COLUMN IF NOT EXISTS contact_id TEXT;
|
|
|
|
-- 3. Добавляем phone (номер телефона пользователя)
|
|
ALTER TABLE clpr_claims
|
|
ADD COLUMN IF NOT EXISTS phone TEXT;
|
|
|
|
-- 4. Создаём индексы для быстрого поиска
|
|
CREATE INDEX IF NOT EXISTS idx_clpr_claims_unified_id
|
|
ON clpr_claims(unified_id)
|
|
WHERE unified_id IS NOT NULL;
|
|
|
|
CREATE INDEX IF NOT EXISTS idx_clpr_claims_contact_id
|
|
ON clpr_claims(contact_id)
|
|
WHERE contact_id IS NOT NULL;
|
|
|
|
CREATE INDEX IF NOT EXISTS idx_clpr_claims_phone
|
|
ON clpr_claims(phone)
|
|
WHERE phone IS NOT NULL;
|
|
|
|
-- 5. Комментарии к полям
|
|
COMMENT ON COLUMN clpr_claims.unified_id IS 'Уникальный идентификатор пользователя из CRM (формат: usr_xxx)';
|
|
COMMENT ON COLUMN clpr_claims.contact_id IS 'ID контакта в RetailCRM';
|
|
COMMENT ON COLUMN clpr_claims.phone IS 'Номер телефона пользователя (формат: 79262306381)';
|
|
|
|
-- 6. Опционально: заполняем существующие записи из payload (если есть)
|
|
UPDATE clpr_claims
|
|
SET
|
|
unified_id = payload->>'unified_id',
|
|
contact_id = payload->>'contact_id',
|
|
phone = payload->>'phone'
|
|
WHERE unified_id IS NULL
|
|
AND (
|
|
payload->>'unified_id' IS NOT NULL
|
|
OR payload->>'contact_id' IS NOT NULL
|
|
OR payload->>'phone' IS NOT NULL
|
|
);
|
|
|
|
-- Проверка результата
|
|
SELECT
|
|
COUNT(*) as total_claims,
|
|
COUNT(unified_id) as with_unified_id,
|
|
COUNT(contact_id) as with_contact_id,
|
|
COUNT(phone) as with_phone
|
|
FROM clpr_claims;
|
|
|
|
|