- Dikirim
- 29 Maret 2026 pukul 20.07 UTC
- Penulis
- kamo
- Berkomitmen
- c8ef7ad
The previous implementation only filled 8 of 20+ SignatureContent fields, causing malformed signatures with no images, name, or contact info. Now replicates the email composer's exact data flow (MessageTool.tsx): 1. Fetch session via /api/security/session/current (gets memberId, orgId) 2. Fetch sender member + org in parallel (same endpoints as composer) 3. Build ALL previewContent fields: name, title, dept, email, phone, website, company*, social links, avatar URL 4. Resolve image URLs based on template config source (member-avatar, logo-simple, logo-full) — same resolveImg logic as composer 5. Subject: '{First Last} from {Org} invited you to a meeting' 6. Host: '{First Last} from {Org}'