Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add separate WhatsApp Business templates for signature request and completion notifications

Aperta
  • Qualcosa non va?
#7,986 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php
Ambito
backend

Direzione di ricerca

Non sono indicati file né test. Inizia tracciando i percorsi delle notifiche WhatsApp Business di LibreSign per le richieste di firma e le firme completate, quindi valida entrambi i flussi con l’app TwoFactor Gateway e un account WhatsApp Business configurato. Il lavoro è completato quando ogni evento usa il proprio modello, i messaggi di completamento rispettano l’impostazione delle notifiche del firmatario e gli screenshot mostrano entrambi i messaggi.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

LibreSign currently uses the same WhatsApp Business message template for different stages of the signing workflow. Signature requests and signature completion notifications have different purposes and recipients, so each event should use its own dedicated template.

To reproduce
  • Enable WhatsApp Business notifications for LibreSign.
  • Send a document to a recipient for signature.
  • Verify the WhatsApp message received by the signer.
  • Complete the signature process.
  • Keep the notification for completed signatures enabled for the signer.
  • Verify the WhatsApp message received after the signature is completed.
  • Observe that the same WhatsApp Business template is currently being reused for both events, even though they represent different notification contexts.
Expected behavior

Add separate WhatsApp Business templates for signature request and completion notifications

To reproduce

  1. Enable WhatsApp Business notifications for LibreSign.
  2. Send a document to a recipient for signature.
  3. Verify the WhatsApp message received by the signer.
  4. Complete the signature process.
  5. Keep the notification for completed signatures enabled for the signer.
  6. Verify the WhatsApp message received after the signature is completed.
  7. Observe that the same WhatsApp Business template is currently being reused for both events, even though they represent different notification contexts.

Expected behavior

LibreSign should use two different WhatsApp Business templates:

  • Signature request template

    • Sent to the person who must sign the document.
    • Triggered when the document is sent for signature.
    • The message must inform the recipient that a document is waiting for their signature and provide the signing link.

  • Signature completed template

    • Sent to the signer after the signature process is successfully completed.
    • It must only be sent when the signer has the corresponding completion notification enabled.
    • The message must inform the signer that the document has been successfully signed.
Screenshots
Image
Additional context
Additional context

To reproduce and validate this issue locally, the TwoFactor Gateway app must be installed and configured in the development environment.

A WhatsApp Business account must also be configured so the notification templates can be tested through the actual integration and both message flows can be validated locally.

When submitting the PR, please include screenshots of the implemented solution showing how both WhatsApp messages are received:

  • The message requesting the recipient to sign the document.
  • The message confirming that the document was signed successfully.
Lingua principale
PHP
Stelle
818
Fork
146
Merge medio
6h 48m
PR unite (30g)
622

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.