5j]dZddlZddlZddlZddlZddlmZmZddlmZddl Z ddl Z dZ dZ dZdZd Zd Zd Zd Zd Ze e eeeeeeef ZeeehZdZdZeefZedediZeej;j<Zedz Z edz Z!edz Z"edz Z#edz Z$dZ%ejLjOddZ(ejLjOddZ)ejLjOddZ*e*rde*ndZ+ejLjOddZ,dgZ-ej\Z/ddl0Z0e0jbdZ2d dddd!d"Z3d#Z4d]d$Z5d%Z6d&Z7d'Z8d(Z9d)Z:d*Z;d+Zd.Z?d/Z@d0ZAe d1e d2ed3ed4ed5ed6ed7ed8ed9i ZBd:ZCd;ZDd<ZEd=ZFd>ZGd?ZHd@ddAdBZIdCZJdd@ddDdEZKdFZLdGZMdHZNdIZOdJZPdKZQeMeNeOePeQfZReMdLeNdMeOdNePdOeQdPiZSeMdQeNdReOdSePdTeQdUiZTdVdWdXZUdYZVdZZWd[ZXdd@ddDd\ZYy)^u notifications.py — Event-driven notification dispatch core for Togen (DVI-333). Foundation module for the Togen Notifications System (DVI-332). Provides: * Namespaced event constants (EVENT_*). * notify(event, context) — resolves personal recipients, renders the branded HTML template for the event, and sends via Microsoft Graph on a background thread (mirrors the existing fire-and-forget send pattern in app.py). * send_html_email(to, subject, html) — shared Graph sendMail helper, reused by app.py callers (e.g. the News email path). * render_email_shell(...) — the branded, Outlook-safe table HTML shell. * A file-based idempotency log (notification_log.json) so recurring events never double-send to the same recipient. Recipient resolution OR-merges two independent sources, de-duplicated by email: 1. Per-WO opt-in (individual): the submitting user who checked "Enable notifications about this work order" — carried in the WO JSON sidecar under ``_notify``. Notifies only that submitter, about only that one work order. 2. Admin-wide grid prefs: the 3x5 User Settings / WO Admin "Settings" grid is a Work Order Admin preference that applies to ALL work orders submitted by ANY user. Every user whose grid enables (WO type x event) is notified, regardless of who submitted the work order. The grid save route is admin-gated in app.py, so only WO Admins can persist these prefs. This module is intentionally self-contained (it does not import app.py) so it can sit beneath app.py in the import graph and be imported/tested in isolation. It reads the same env vars and on-disk JSON layout that app.py uses. N)datetimetimezone)Pathzworkorder.createdzworkorder.status.in_progresszworkorder.status.completedzworkorder.status.cancelledzworkorder.recurring.due_soonzworkorder.recurring.overduezworkorder.evh.awaiting_approvalzworkorder.evh.finalizedzworkorder.evh.rejectedzscada.data.stalezscada.sensor.out_of_range stale_data out_of_range user_settingsznotification_log.jsonzwor_primary.jsonzwor_policy.jsonzrpm_approval.jsonwo_notificationsAZURE_CLIENT_IDAZURE_CLIENT_SECRETAZURE_TENANT_IDz"https://login.microsoftonline.com/AZURE_MAIL_FROMz$https://graph.microsoft.com/.defaultztogen.notifications Notification)subtitle meta_htmlcta_html footer_htmlc0dj||||||S)zWrap content in the branded, Outlook-safe (table-based) HTML email shell. Same markup as app.py's news shell, generalized via the ``subtitle`` slot so every notification type can share one branded template. a7
togen
{subtitle}

{title}

{meta}
{body}{cta}
{footer}
)rtitlemetabodyctafooterformat)r body_htmlrrrrs $/var/www/html/togen/notifications.pyrender_email_shellrs, 3B fhe))+ /E#/cdtr trtstj dy t j ttt}|jt}|jd}|stjd|S#t$rtjdYywxYw)zBAcquire an app-only Graph token. Returns access token str or None.z9Graph token unavailable: Azure credentials not configuredN) authorityclient_credential)scopes access_tokenz,Graph token request returned no access_tokenzGraph token acquisition error) _AZ_CLIENT_ID _AZ_SECRET _AZ_AUTHORITY_logwarningmsalConfidentialClientApplicationacquire_token_for_client _GRAPH_SCOPESgeterror Exception exception) app_clientresulttokens r_acquire_graph_tokenr5s j] PQ 77 ]jR 44M4J >* JJE F  67sA#BB/.B/c xtstjdyt|tr|g}n|Dcgc]}|s| }}|syt }|sy|d|d|Dcgc]}dd|ii c}d}|r.|Dcgc]}d|d |j d d |d d !c}|d<|dd} tjdtdd|dd| d} | jdvr/tjd| j| jddyycc}wcc}wcc}w#t$rtjdYywxYw)apLow-level Microsoft Graph sendMail. Synchronous. Returns True on accept. ``to`` may be a single address or an iterable of addresses. ``attachments`` is an optional list of ``{"name", "contentType", "contentBytes"}`` dicts where ``contentBytes`` is the base64-encoded file payload (Graph fileAttachment shape). From address is ``AZURE_MAIL_FROM``. z*Cannot send email: AZURE_MAIL_FROM not setFHTML) contentTypecontent emailAddressaddress)subjectr toRecipientsz#microsoft.graph.fileAttachmentnamer8zapplication/octet-stream contentBytes)z @odata.typer>r8r? attachmentsfalse)messagesaveToSentItemsz'https://graph.microsoft.com/v1.0/users/z /sendMailzBearer zapplication/json) Authorizationz Content-Type<)headersjsontimeout)zsendMail failed (%s): %sNi,TzsendMail error)rr(r) isinstancestrr5r._http_requestspost status_coder/textr0r1) tor<htmlr@ addressesar4rBatt graph_bodyresps r_send_graph_mailrXs{  AB"cD "(1aQ( (  "E  &48CLMa.9a.9MG # "  AF "ww!#= ? #N 3   "  %AJ""5o5Fi P#*5'!2 2    : - JJ143C3CTYYtPS_ UM)N " 2  '(s)D D  D4$D$A#DD98D9ct|||S)aSend a branded HTML email via Microsoft Graph sendMail. Synchronous. ``to`` may be a single address string or an iterable of addresses (all are placed on a single message's toRecipients list). From address is ``AZURE_MAIL_FROM``. Returns True on a 200/202 accept, False otherwise. This is the shared helper extracted from app.py's admin/news send paths; callers that need fire-and-forget behaviour should run it on a thread. )rX)rQr<rRs rsend_html_emailrZ s B ..rc rtj|jd}t||||||dgS)uSend an HTML email with a single file attachment via Graph sendMail. ``content`` is the raw file bytes; it is base64-encoded into a Graph fileAttachment. Synchronous; returns True on a 200/202 accept. Added for the SCADA report scheduler (DVI-486), which emails generated XLSX reports — ``send_html_email`` is HTML-only. Graph's simple sendMail caps total message size around 4 MB, so callers should guard large attachments before invoking this (the report scheduler skips XLSX payloads over 3 MB). ascii)r>r8r?)r@)base64 b64encodedecoderX)rQr<rRfilenamer9 content_typeencodeds rsend_email_with_attachmentrcsFw'..w7G  GT'#   rcbt|tr|jjSdSNr )rKrLstriplower)addrs r_normalize_emailri5s%#-dC#84::<   @b@rc#K|r|sy ttjd}|D]} t j |j }t|ts8|jt}t|ts^|j|xsi}|j|s|jdxs |j}|s|y#t$rYywxYw#tjtf$rYwxYww)a|Yield the email of every user whose grid enables (wor_type x event). Scans every ``USER_SETTINGS_DIR/*.json``. The grid is admin-wide: a match means that user wants this notification for ALL work orders of this type, regardless of submitter. Because the grid save route is admin-gated in app.py, only WO Admins can have a ``wo_notifications`` block persisted, so this effectively yields the WO Admins subscribed to the cell. Each user's email is read from the stored ``email`` field when present, falling back to the settings filename stem (which equals the lowercased email for normal addresses). N*.jsonemail) sortedUSER_SETTINGS_DIRglobOSErrorrGloads read_textJSONDecodeErrorrKdictr.USER_SETTINGS_NOTIFY_KEYstem)wor_typeeventfilesfpsettingsprefs type_prefsrls r_iter_grid_recipientsr~9s (--h78 zz",,.1H(D)  56%& YYx(.B >>% LL)4RWWE   $$g.   sWDCD#C&AD.!DD C# D"C##D&D?DDDc#K|rtjsy tjtj }t|tsy|j|}t|tr.|D](}t|ts|js%|*yy#tj t f$rYywxYww)zYield every email on the Primary list for this WO type (DVI-405). Primary recipients receive ALL workorder events for their WO type, regardless of submitter or per-event grid prefs. N) WOR_PRIMARY_FILEis_filerGrqrrrsrprKrtr.listrLrf)rwdataemailses r_iter_primary_recipientsr]s +335zz*4467 dD ! XXh F&$ A!S!aggi   ' *s5C'B#AC CC#B?<C>B??Cc^|r|rtjsy tjtj }t|tsy|j|}tt|txr|j|S#tj t f$rYywxYw)zFTrue if the company Policy grid enforces (wor_type x event) (DVI-597).F) WOR_POLICY_FILErrGrqrrrsrprKrtr.bool)rwrxrr}s r_policy_enforcesrrs '>'>'@zz/3356 dD !(#J  :t,F1F GG  ' *s'BB,+B,scada_notificationscpg}t}|s|S ttjd}|D]} t j |j}t|ts8|jt}t|tr|j|so|jdxs |j}t|}|s||vs|j||j!|j#|S#t$r|cYSwxYw#t jtf$rYwxYw)aResolve de-duplicated emails of users who opted into a SCADA pref. Scans every ``USER_SETTINGS_DIR/*.json`` for a truthy ``scada_notifications[pref_key]`` (e.g. ``"stale_data"`` / ``"out_of_range"``). Email is read from the stored ``email`` field when present, falling back to the settings filename stem. Returns a list of original-cased email strings, order-stable, no duplicates. rkrl)setrmrnrorprGrqrrrsrKrtr.SCADA_NOTIFY_KEYrvriaddappendrf) pref_keyorderedseenryrzr{r|rlnorms rresolve_scada_recipientsrsG 5D (--h78* zz",,.1H(D)  -.%&eii.A  W%0& D$ HHTN NN5;;= )* N#  $$g.   s"D#D DDD54D5c gt  fd}|jdxsi}t|tr(|jdr||jd|jd}t ||D] }|| t |D] }|| t ||rg|jdxsi}|jdxs7|jdxs$|jdxs|jd}|||tttfvrD|jdxsgD] }|| |jd xsgD] }|| S) uResolve the de-duplicated personal recipients for an event. Three independent (OR-merged) sources, de-duplicated by lowercased email: Source A — per-WO opt-in (individual): ``context["notify"]`` (the sidecar ``_notify`` block) of shape ``{"enabled": bool, "email": str}``. Notifies only that submitter, about only this one work order. Source B — admin-wide grid prefs: every user whose User Settings / WO Admin "Settings" grid enables (``context["wor_type"]`` x event), regardless of who submitted the work order. Source C — Primary list: every email flagged Primary for ``context["wor_type"]`` receives all events for that type (DVI-405). Source D — Policy-enforced grid: when the company Policy grid enables (``context["wor_type"]`` x event), the requesting user of the work order is notified as a matter of policy, regardless of opt-in (DVI-597). Returns a list of original-cased email strings, order-stable, no duplicates. ct|}|r6|vr1j|j|jyyyNrirrrf)rhrrrs r_addz resolve_recipients.._adds;% D$ HHTN NN4::< (%4rnotifyenabledrlrwrequestor_emailsubmitter_emailevh_dept_emailsevh_recipients) rr.rKrtr~rrEVENT_WO_EVH_AWAITINGEVENT_WO_EVH_FINALIZEDEVENT_WO_EVH_REJECTED) rxcontextr notify_blockrwrl requestorrhrrs @@rresolve_recipientsrs|&G 5D);;x(.BL,%,*:*:9*E \  g &'{{:&H&x7 U  *(3 U %({{8,2 !%%&78-$((1- $56- G,  Y &(>&(([[!239r D J [[!128b D J  NrctjsgS tjtj }t |t r|SgS#tjtf$rgcYSwxYwr) NOTIFICATION_LOG_FILErrGrqrrrKrrsrp)rs r _load_logrsc ( ( * zz/99;<!$-t525  ' * s8AAA10A1c||t|tjtjj d}t 5t}|j| tjtj|ddddy#t$rtjdY)wxYw#1swYyxYw)z>Append a {wor_id, event, recipient, sent_at} entry to the log.)wor_idrx recipientsent_at)indentz'Failed to persist notification_log.jsonN)rirnowrutc isoformat _log_lockrrr write_textrGdumpsrpr(r1)rrxrentrylogs r _record_sentrs%i0<< -779  E Fk 5 F ! , ,TZZA-F G FF  F NND E F FFs*B:#*BB74B:6B77B::Cct|}t5tD]J}|jd|k(s|jd|k(s-|jd|k(sBdddy dddy#1swYyxYw)zATrue if (wor_id, event, recipient) was previously logged as sent.rrxrNTF)rirrr.)rrxrrrs r already_sentrsw I &D  Ah6)aeeGn.Ek*d2     s""A4A4 A4A4)A44A=)zWork Order {ref} submittedz:Your work order has been submitted and is awaiting review.)zWork Order {ref} is in progressz$Work on your work order has started.)zWork Order {ref} completedz)Your work order has been marked complete.)zWork Order {ref} cancelledz#Your work order has been cancelled.)z#Recurring Work Order {ref} due soonz1A recurring work order you submitted is due soon.)z"Recurring Work Order {ref} overduez4A recurring work order you submitted is now overdue.)u(RtS Approval needed — Work Order {ref}zXYour department's sign-off is required before this equipment can be returned to service.)u5Equipment released to production — Work Order {ref}zwAll required departments have approved the Equipment Validation Handoff. The equipment has been released to production.)u*RtS Approval rejected — Work Order {ref}z_A return-to-service approval was rejected. The work order has been reopened for further action.c|jd}|r dt|dS|jd}|r t |SdS#ttf$rd|cYSwxYw)z6Human-friendly work-order reference for subjects/body. wor_number#05drr )r.int TypeError ValueErrorrL)rnumwids r_wor_referencerJsn ++l #C  s3xn% % ++h C3s8"":& se9  sAAAcxt|jddjddjddS)N&z&z>)rLreplace)values r_escrVs1 J WS' "773#7V8LNrcftjjdxsdjdS)z5Public Togen base URL for building in-app deep links.TOGEN_BASE_URLzhttps://togen.icastinc.com/)osenvironr.rstriprr _base_urlr[s( JJNN+ , ,+VVC[9rc ddlm}|jd}|dvry t|d}td||}djt|t| S#tt f$rt |}YVwxYw) aA deep-link button into WO Admin focused on this work order (DVI-1174). Links to ``?open_wo=`` which the frontend resolves by opening the WO Admin tool and selecting the WO (approver-only users land on the Approvals tab). SSO-gated; recipients without WO Admin access land on the Togen home (graceful). Returns "" when the context carries no work-order number. r)quoterrer rz /?open_wo=aG
{label}

Opens this work order in Togen (sign-in required).

)linklabel) urllib.parserr.rrrrLrrr)rrrrr4rs r _wo_cta_htmlras# ++l #C js8C.k]*U5\N 3D G  f$t*DKf01 z "Cs A%%BBc tj|}|sy|\}}t|}|j|xsdj }g}dD]M\}} |j| } | s|j djt |t | O|rddj|zdznd} |jd } | rd jt | nd} d jt || | }d }|tk(rdnd}t||}tt ||d||}||fS)zGRender (subject, html) for an event given its context. None if unknown.Nr )ref)) Requestorrequestor_name)Locationlocation)Buildingbuilding)Urgencyurgency)zDesired completiondesired_completion_date{lbl}{val}lblvalU
descriptionzd

{}

zL

{intro}

{table}{desc})introtabledescz

You are receiving this because you enabled notifications for this work order.

zView & approve in TogenzOpen this work order in TogenzWork Order Update)rrrrr) _EVENT_COPYr.rrrfrrjoinrrr)rxrcopy subject_tmplrrr<rowsrkeyr detail_tabler desc_htmlrr cta_labelrrRs rrender_event_emailr|sr ??5 !D L%  !C!!ciR!0668G DK @ s kk#  KK4;DI>  @ @  %')wwt} 57A B ;;} %D  88>tDz8J  T%[ 9U  1/47L.L*5GY/H 7m$  D D=rct||}|stjd|y|\}}|jd}|tv}|D]1} |r|rt ||| r|| ||} | s"|s%t ||| 3y)z:Send to each recipient once, honoring the idempotency log.z notify: no template for event %sNr)rr(r/r.RECURRING_EVENTSrr) rxr recipientssenderrenderedr<rRrguardroks r _dispatchrs!%1H  5u=MGT [[ "F % %E3 V VUI F  Iw - &  2 3rT) backgroundrc|tvrtjd|gSt||}|sgS|xst}|r2t j t||||fd}|j|St|||||S)uResolve recipients, render the event template, and send. Args: event: one of the EVENT_* constants. context: dict carrying recipient-resolution inputs (``notify``, ``submitter_email``/``email``, ``wor_type``) and template fields (``wor_id``, ``wor_number``, ``requestor_name``, ``description``, …). background: when True (default) dispatch on a daemon thread (mirrors the existing fire-and-forget pattern); when False, dispatch inline (useful for tests / synchronous callers). sender: callable (to, subject, html) -> bool used to actually send; defaults to :func:`send_html_email`. Injectable for tests. Returns the resolved recipient list (so callers/tests can assert on it). znotify: unknown event %rT)targetargsdaemon) WORKORDER_EVENTSr(r/rrZ threadingThreadrstart)rxrrrrsendts rrrs  $$ -u5 #E73J   $_D   E7J#Ed T    %*d3 rc |tk(r|jd}d}|jd}|jd}g}|+|jddjt |f|+|jddjt |f|r|jd t |fd }d }n|t k(r|jd xs|jd xsd} |jdxsd} d}|jddk(r"| rdt | znd} |jd} |jd} |jd}|jd}|jd}|jd}dj| }dt | fddjt | | t |fddjt || t | fg}|9|7|jd d!jt || t || fd"}n%|jd#}|jd$}|jd%}|d&vr:|d&vr6d'jt |t || rdt | znd}nb|d&vr,d(jt || rdt | znd}n2|d&vr,d)jt || rdt | znd}nd*}d+j| }dt | fd,d-jt || rdt | zndfd.|fg}d/}nydj d0|D}|rd1|zd2znd}d3jt ||4}d5}tt ||d6|7}||fS)8ukRender (subject, html) for a SCADA event. None for an unknown event. Context keys: stale event — ``stale_after_minutes`` (int), ``last_reading_time`` (str or None), ``age_minutes`` (int or None). out-of-range — ``sensor`` (display name), ``value`` (str), ``low`` / ``high`` (str/num or None), ``unit`` (str, optional). stale_after_minutesz!SCADA alert: no new data receivedlast_reading_time age_minutesNzStale-after thresholdz{} minzTime since last readingz Last readingu}The SCADA collector has not received a new reading within the configured window. Data may be stale — check the data source.zSCADA data is stalesensorrSensorunitr zSensor out of rangereasonrate_of_change rate_delta rate_windowrate_max_delta rate_span rate_fromrate_toz!SCADA alert: {} changing too fastzChange observedz{}{} in {} minzAllowed changeu≤ {}{} within {} minReadingsu {}{} → {}{}ziA monitored SCADA sensor changed faster than its allowed rate of change in the most recent data received.rlowhighreu {} – {}{}u≥ {}{}u≤ {}{}u—zSCADA alert: {} out of rangez Current valuez{}{}zConfigured rangezKA monitored SCADA sensor has reported a value outside its configured range.c3ZK|]#\}}djt||%ywrrN)rr.0rrs r z%render_scada_email..Bs9E4<3 49#. /Es)+rrF

{intro}

{table}rrz

You are receiving this because you enabled SCADA notifications in your Togen settings.

z SCADA Alertrrrr)EVENT_SCADA_STALEr.rrrEVENT_SCADA_OUT_OF_RANGErr)rxrminsr<lastagerrrrrusufdeltawindowlimitspanfrmrQrrrrngrow_htmlrrrrRs rrender_scada_emailr5s !!{{015{{./kk-(   KK0(//$t*2MN O ? KK2HOODI4NO P  KKd4 5S% * *X&J'++g*>J({{6"(b% ;;x $4 4*.C$t*$2DKK -E[[/FKK 01E;;{+D++k*CY'B9@@HG4<("$4$;$;KtDz%34!#;#B#BKtF|$56 D2> Z)?)?ItT"Xt*567HEKK(E++e$C;;v&D*$Z)?#**49d4j?C#T *:MJ& ''S C$t*4DSUVZ' ''T $S4:5ETVW4;;FCG4<( &--U FJtDz1APR#TU#S) D )EwwE@D EEHAI %'/ 02< =NP Q d5k 6  4 5kYK 9D D=r)rrrc, |tvrtjd|gStt|sgSt ||}|sgS|\ |xst  fd}|r'tj|djS|S)u*Send a SCADA monitoring email to opted-in users. Recipients default to everyone whose ``scada_notifications`` enables the pref mapped to ``event`` (see :data:`SCADA_EVENT_PREF`); pass an explicit ``recipients`` list to override. Unlike :func:`notify`, idempotency is the caller's responsibility — the SCADA collector only calls this on a state transition (entering staleness / a sensor going out of range), so emails are not re-sent every poll. Returns the resolved recipient list (so callers/tests can assert on it). znotify_scada: unknown event %rc(D] }|yrrrrRrr r<s r_runznotify_scada.._runv# +I GT * +rTrr) SCADA_EVENTSr(r/rSCADA_EVENT_PREFr5rZrr r  rxrrrrrr9rRr r<s ` @@@r notify_scadar?[s L  3U; -.>u.EF  !%1H  MGT  $_D+T288:   rrpm_notificationszrpm.part.awaitingzrpm.part.approvedzrpm.part.orderedzrpm.part.deliveredzrpm.part.stockedawaitingapprovedr deliveredstocked)zpart awaiting approvalzis awaiting approval)z part approvedzhas been approved)z part orderedzhas been ordered)zpart deliveredzhas been delivered)z part stockedzhas been stockedzMobile MachinezPreventative Maintenance) mobilemachine preventivec|sgS tjtj}t |tsgS|jd}t |tsgS|j|}t |trA|Dcgc]5}t|jst|j7c}SgS#tjt f$rgcYSwxYwcc}w)zCompany-level policy-enforced RPM recipients for ``wor_type`` (DVI-614 follow-up). A user on this list receives every RPM part event for the type, regardless of their per-user grid. Returns original-cased emails. policy_notify) rGrqRPM_APPROVAL_FILErrrsrprKrtr.rrLrf)rwrpnlstrs r_rpm_policy_notify_emailsrLs  zz+5578 dD ! / "B b$  && C>Hd>SC :q3q6<<>CFLLN :[Y[[  ' *  ;s'CC'&C'C$#C$c gtc tj|}|r|s S fd}t|D] }||  t t j d}|D]} tj|j}t|ts8|jt}t|ts^|j|xsi} t| tr| j|s||jdxs |j S#t$r cYSwxYw#tjtf$rYwxYw)a^De-duplicated emails of users to notify for (wor_type x event): the per-user opt-in grid (``rpm_notifications[wor_type][col]`` across every USER_SETTINGS_DIR/*.json) OR-merged with the company-level policy-enforced allowlist for the type (which receives all events). Returns original-cased email strings, order-stable, no duplicates.ct|}|r6|vr1j|j|jyyyrr)rlrrrs rrz$resolve_rpm_recipients.._adds;& D$ HHTN NN5;;= )%4rrkrl)r RPM_EVENT_COLr.rLrmrnrorprGrqrrrsrKrtRPM_NOTIFY_KEYrv) rwrxcolrrlryrzr{r|r}rrs @@rresolve_rpm_recipientsrRs=MGT   E "C *+84 U (--h78 / zz",,.1H(D)  ^,%& YYx(.B :t,1D  X\\' " -bgg. / N!  $$g.   s$ D(.#D9( D65D69EEctj|}|sy|\}}|jdxsd}tj||xsd}|jdxsd}|jdxsd}|jdxsd} |jd xsd} d j|} | r| d j| z } d t |fg} |r| j d t |f| j dt |f| r| j dt | f| r!| | k7r| j dt | fdj d| D} d| zdz}dj|t |}dj||}d}tt |j|d|}| |fS)zRender (subject, html) for an RPM part event. None for an unknown event. Context keys: ``wor_type``, ``wo_label`` (WO number/label), ``wo_title`` (display title), ``part_name``, ``part_number`` (all strings, optional).Nrwr z Work Order part_namez(unnamed part) part_numberwo_labelwo_titlezRepair Parts: {}z ({})PartzPart #zWork Order typeTitlec3HK|]\}}dj||ywr!rr"s rr$z#render_rpm_email..s3?.6S# 3C( )?s "rrz2A repair part {verb} on a {type_label} work order.)verb type_labelr%r&z

You are receiving this because you enabled Repair Parts notifications in your Togen settings.

zRepair Parts Managerr') _RPM_EVENT_COPYr._RPM_TYPE_LABELrrrrr capitalize)rxrrsubject_phraser[rwr\rTrUrVrWr<rr4rrrrrRs rrender_rpm_emailras   u %D ND{{:&,"H $$Xx/G<HJ K(<,>(++ T)_ % &D XtK012KK"D$456 \4>23H( Wd8n-.ww?:> ??H  %'/ 02< = A G G d:. H 0E Q e< 0 : >,,./9'[ BD D=rc> |tvrtjd|gSt|j d|sgSt ||}|sgS|\ |xst  fd}|r'tj|djS|S)uxSend a Repair Parts Manager part-event email to opted-in users. Recipients default to everyone whose ``rpm_notifications`` grid enables (``context['wor_type']`` x event). Like :func:`notify_scada`, idempotency is the caller's responsibility — callers fire only on a state transition. Returns the resolved recipient list (so callers/tests can assert on it).znotify_rpm: unknown event %rrwc(D] }|yrrr8s rr9znotify_rpm.._run=r:rTr;) RPM_PART_EVENTSr(r/rRr.rarZrr r r>s ` @@@r notify_rpmre(s O# 159 +GKK ,CUK  w/H  MGT  $_D+T288:   rr)Z__doc__r]rGrrrrpathlibrr*requestsrMEVENT_WO_CREATEDEVENT_WO_STATUS_IN_PROGRESSEVENT_WO_STATUS_COMPLETEDEVENT_WO_STATUS_CANCELLEDEVENT_WO_RECURRING_DUE_SOONEVENT_WO_RECURRING_OVERDUErrrr frozensetrr(r)r<r=__file__resolveparent _BASE_DIRrnrrrrIrurr.r%r& _AZ_TENANTr'rr-Lockrlogging getLoggerr(rr5rXrZrcrir~rrrrrrrrrrrrrrrrr5r?rPEVENT_RPM_PART_AWAITINGEVENT_RPM_PART_APPROVEDEVENT_RPM_PART_ORDEREDEVENT_RPM_PART_DELIVEREDEVENT_RPM_PART_STOCKEDrdrOr]r^rLrRrarerrrr}s{> ' !!4 > < < > = A 9 8 /7!#;< |n N " " $ + + /!$;; 11//  33. 0"5  4b9  0"5 EO4ZLAUW **..!2B778  INN  w./6D!#bb*/Z$8v /8A!H* H )!HG\F"" "   "!C% P #N 9 169@3$*.d!PbJ04T$d%..-/- jjiki  PDBFB &, \&(V2j.2d4r