j: dZddlZddlZddlmZddlmZmZmZddl m Z ddl m Z ddl mZejeZdZd Zd d d d d d d d d d Zd dddddZddddddZddddddZddiZdZddlZej8dZddd d!Zd"ed#efd$Z d#e!fd%Z"d"efd&Z#d"efd'Z$d#e!fd(Z%d"ed#e!fd)Z&d"ed*e!d+e!d,e!d-e'd#e!f d.Z( d6d"ed*e!d+e!d,e!d-e'd#e!f d/Z)d"ed#e*fd0Z+d"ed#e!fd1Z,d2ed3ed4ed#efd5Z-y)7aPer-tenant feature toggles, and the email copy that goes with one of them. Storage is one row per key in the tenant's strategist_settings table, under a row lock so two concurrent saves merge instead of one silently overwriting the other. Reads fall back to the older strategist_summaries rows for tenants the migration (scripts/migrate_settings.py) hasn't reached yet. Only some switches have a tool behind them (see FEATURE_TOOLS); the rest are stored so the dashboard works now. Provider settings (PROVIDER_OPTIONS/ PROVIDER_DEFAULTS) pick one option instead of on/off, under a "providers" key -- chat_conversation and send_email are wired into real behavior; ticket_management and product_recommendation are stored only, for now. N)partial)get_latest_summary get_settingupdate_setting)get_google_calendar_connection)get_mailchimp_connection)get_teams_connection tool_settingsemail_settingsTF) send_email voice_mode book_meetingorder_trackingattach_documentsticket_managementcrm_integrationproduct_recommendationchat_conversationr create_or_update_ticket send_documentrecommend_productsr)r rrrr)whatsappslack galaxiq_chat)galaxiq_ticketmanagement)smtp mailchimp)shopify)google_calendarteams)rrr rrrrr)zGeneral enquiriesSalesBusinessz^[^@\s]+@[^@\s]+\.[a-zA-Z]{2,}$z&Thanks for chatting with {{brandName}}u6© {{currentYear}} {{brandName}}. All rights reserved.zzResponses are powered by AI and may contain errors or omissions. Please verify important information before relying on it.)headerfooter aiDisclaimer tenant_idreturnc^|xsdj}|r|jdsd|S|S)zAccept a tenant id with or without the org_ prefix. Schemas are named org_. Callers sometimes pass the bare uuid, and without this a bootstrap would silently create a second, empty schema whose settings the chat would never read. org_)strip startswithr&s ?/var/www/html/strategist-ai/app/services/chat/tools_settings.pynormalise_tenant_idr/ms9b'')I--f5i[!! c^ttttttgdS)N)featuresemail providers ticket_emails)dictFEATURE_DEFAULTSEMAIL_COPY_DEFAULTSPROVIDER_DEFAULTSr0r. _defaultsr;zs*-.>Q9R/02 GGr0c ttfD]E} t||}|r|dnd}|s t j|}t|tsC|cSy#t$r)}tj d|d|d|Yd}~yd}~wwxYw#t jtf$rtj d|d|dYwxYw)aThe tenant's settings as they were stored in strategist_summaries. Used as a read fallback for tenants the migration has not reached, and by the migration itself as its source. Prefers the newer 'tool_settings' row over the older flat 'email_settings' one. rNzCould not read z for : zStored z is not valid JSON; ignoring it.) SETTINGS_KEYLEGACY_SETTINGS_KEYr ExceptionloggererrorjsonloadsJSONDecodeError TypeError isinstancer6)r&keyrowstoredexsaveds r.read_legacy_blobrMs12 $Y4C"SVF  JJv&E eT "L!"   LL?3%uYKr"F G $$i0  LL73%uYK7WX Y  s(AB  BBB 5CCc t|t}t |t r|r|St|S#t$r'}tj d|d|d}Yd}~Jd}~wwxYw)zIThe tenant's saved settings: the settings table first, then the old rows.zCould not read settings for r=N)rr>r@rArBrGr6rM)r&rJrKs r. _read_storedrOsbY 5&$F I &&  3I;bEFs1 A!AA!ct}|s|S|jdxsijD]\}}|tvst ||d|<!|jdxsijD]\}}|t vs|s||d|<|jdxsijD]$\}}|t vs| |t |vs||d|<&|jd}t|tr||d<d|vrt |d|dd<t D]}|j|s|||d|<!|S)zDNormalise a stored blob of either shape into the full settings dict.r2r3r4r5enabledr ) r;getitemsr7boolr8PROVIDER_OPTIONSrGlist)rLsettingsnamevaluestored_ticket_emailss r.apply_over_defaultsr[st{H  *-3::<5 e # #)-eHZ  &5 '*0b779, e & &5&+HW d #, +.4";;=0 e # #%CSTXCY:Y*/H[ !$ ' 0!99_5&-$8!E-1% 2B-C\*#2 99T?&+DkHW d #2 Or0c<ttt|S)zEEvery switch plus the email copy, merged over defaults. Never raises.)r[rOr/r-s r.get_tool_settingsr]s |,? ,JK LLr0r2r3r4r5cht|xs t|}|xsijD]\}}t||d|<|xsijD]*\}}|xsdj xs t ||d|<,|xsijD] \}}||d|<|||d<|S)aApply an update on top of whatever is already stored. Runs inside update_setting's row lock, so `current` is the value nobody else can be writing at the same moment. An empty `current` means this tenant has not been migrated yet, so the old summaries blob is the starting point rather than bare defaults -- otherwise the first save after deployment would wipe their settings. r2r)r3r4r5)r[rMrSrTr+r8) r&r2r3r4r5currentbaserXrYs r._merge_settingsras wE*:9*E FD B--/- e!%eZ- **,Q e${113P7J47PW dQ"R..0( e#([$(  -_ Kr0c :t|}|rG|jDcic],\}}|t|tr|j xsdn|.}}}t |xsit t z }|r&tddjt|t |xsit tz }|r&tddjt|t |xsit tz }|r&tddjt||xsijD]-\}}| |t|vst|dt|d|||D]}t|trd|vsd |vr td tj|jdxsd j st|jdd |d t vstd t d|d |xsijDcgc]\}}| |t"vr|} }}| r^tt%|d} | j'|xsi| D]-}t"|} | j| rt|d| d|xsijddk(rt)|s td|xsijddk(rt+|s td|xsijddk(rt-|s tdt/|t0t3t4|||||} td| djD} t6j9d|d| xsd| Scc}}wcc}}w)zUMerge the supplied switches, copy, provider choices and business emails, and persist.NzUnknown feature(s): z, zUnknown email setting(s): zUnknown provider setting(s): z must be one of z or null, got r3categoryz7Each ticket_emails entry needs both email and category.r)z is not a valid email address.zcategory must be one of z, got r2z cannot be set while z/ is off; enable it first or in the same requestr rzPConnect Mailchimp under Integrations before selecting it as your email provider.rrzXConnect Google Calendar under Integrations before selecting it as your meeting provider.r zXConnect Microsoft Teams under Integrations before selecting it as your meeting provider.c3,K|] \}}|r |yw)Nr:).0nons r. z%save_tool_settings..4sEuq""Es zSaved tool settings for z; off: none)r/rSrGstrr+setr7 ValueErrorjoinsortedr8rUr6_TICKET_EMAIL_REmatchrRTICKET_CATEGORIESPROVIDER_REQUIRES_FEATUREr]updaterrr rr>rrarAinfo)r&r2r3r4r5rXrYunknownentry needing_gateeffective_featuresgatemergedoffs r.save_tool_settingsr|s$I.I'0'8:#ej6LEKKM1TRWW: :(.b!C(8$99G/ &/0J/KLMM%+2%8!99G5diiw6P5QRSS)/r"S)9%::G86'?9S8TUVV!R..0Z e  .>t.D!D&()9$)?(@uiXZ ZZ  " _EeT*gU.BjX]F] MOO#))599W+=+C*J*J*LM EIIg$6#99W!XYYZ (99 ./@.AjHYG\]__ _.7_",C,C,EP[T5(T5N-NPLP!"3I">z"JK!!(.b1  /D,T2D%))$/ f1$8-.// / R\*k9' 2"# # R^,0AA-i8,- - R^,7#I.,- -<HeY VXF Ez 2 8 8 :E EC KK*9+WS]FOLM MK:>Ps 1N'Nct|d}tjDchc]\}}|j|dr|c}}Scc}}w)zTool names this tenant has switched off. The chat loop strips these from the tool list AND from the system prompt, so a disabled capability is invisible to the model rather than merely refused. r2T)r] FEATURE_TOOLSrSrR)r&r2featuretools r.disabled_tools_forr9sC !+J7H&3&9&9&; _]Wd8<r?r7r~rUr9rrrqre_recompileror8rjr/r6r;rMrOr[r]rVrar|rkrrrr:r0r.rs  WWTH@   8 $ &"  2'2"  ?6'*0 3" ,?3;;AB7F D  3 3 G4G 6 'C ' $ FMMM sd4D#'596MQEIM#MMTM"&M>BMNRM``#`#`P#P$P )c)s)#)#)r0