Bugs Fixed:

1) WhatsApp Group contacts were showing in WABA list:

When users synced WhatsApp group contacts using the Sync button in the WhatsApp Groups tab, these contacts also started appearing in the WABA contacts list. This was confusing because the WABA tab is meant only for direct WhatsApp Business API (WABA) contacts, not for group members.

Solution:
We fixed the filter logic so that:

– Only contacts with contact_type = WABA or WABA + WA appear in the Chats (WABA) tab.

– Contacts with contact_type = WA (group-only contacts) appear only in the WhatsApp Groups tab.

This ensures proper separation of group and WABA contacts.

2) Infinity loop error for audio/video message:

To prevent infinite loops, Glific checks if the same message is sent more than 3 times within 6 hours from the same flow_context. If that happens, the flow is stopped with an infinity loop warning. However, for audio and video messages, the message body can be empty, and the system was mistakenly treating them as “same messages.” As a result, even when different audio messages were sent, users were receiving false infinity loop errors.

Solution:We updated the validation so that sending different audio/video messages more than 3 times no longer triggers an infinity loop warning. Now, the check only applies when truly identical messages are sent repeatedly.



3) Better handling of invalid regex in flows:

We have improved how Glific manages flows when an invalid regex is used. Earlier, this could cause the flow to crash, creating a poor experience for beneficiaries.
Now, when a flow is run, if the regex itself is invalid and fails to compile (not just when the data doesn’t match), the flow will automatically move to the failure node.
This ensures beneficiaries continue to have a smooth experience.
At the same time, Glific will send a notification in the platform so that NGOs are immediately aware of the issue and can fix it without delay.

4) Fixed the error while uploading Files to Assistants:

NGOs encountered the error Invalid content-type header while uploading files to the AI Assistants. Because of this, they were unable to upload files to their assistants, disrupting their workflow.

Solution:We resolved the issue so that the API now correctly accepts file uploads without throwing the error. NGOs can seamlessly upload files to their assistants as expected.


New Feature/Enhancements Done:

1)  Added pop up for contact deletion with Default Profile:

​​Earlier, deleting the default profile of a contact in Glific was handled the same way as deleting any other profile. This created confusion, as deleting the default profile essentially means deleting the entire contact.

Solution: We have improved this by adding a clear confirmation pop-up. Now, when NGO POCs try to delete a default profile, they will see the warning:
“Are you sure you want to delete the default profile? Deleting default profile will delete the contact. This is irreversible.”
This ensures users are aware of the impact before proceeding.

2) Added Footer in HSM Templates:

Gupshup had introduced an optional footer field in HSM templates, but Glific did not previously support it.

Solution:We added support for the footer field in Glific’s database and API.
A new footer column has been introduced in the hsm_templates table, and the API has been updated to accept and return this field. Since it’s optional, it doesn’t affect existing templates or workflows, but it gives users more flexibility when designing their HSM templates. 

Documentation Update:

Revamped existing Documentation:

1) Bhashini Integration in Glific: Speech-to-Text and Text-to-Speech:

We reworked on the Bhashini integration guide into a complete end-to-end tutorial for Speech-to-Text and Text-to-Speech. The guide now includes:

• Step-by-step flows with clear inputs, outputs, and parameters
  
• Sample flows, a showcase video, and external blog references
  
• Updated visuals and hosted assets with Google Cloud Storage setup for voice notes
  
• Expanded use cases like multilingual campaigns, regional responses, and transliteration
  

 Please read the documentation here.


2) Filesearch using OpenAI assistants:

We expanded and restructured the File Search Using OpenAI Assistants guide with:

• Step-by-step instructions on creating assistants, using them in flows, and preserving conversational memory with thread_id
  
• Voice workflows with language controls, text/voice responses, and attachment handling
  

Please read the detailed documentation here.

3) Add or Remove the contact to a collection:

Reorganized the Add/Remove Contact to/from Collection guide to make it clearer and more practical. The updated guide now includes:

• Step-by-step flow-based instructions with examples and updated screenshots
  
• Verification steps, publish reminders, and notes on edge cases like deduplication and re-entry
  

 Please read the detailed documentation here.


4) Triggers:

We restructured the Triggers documentation for better clarity and usability. The updated guide includes:

• A dedicated “Triggers” section with step-by-step flow on creating triggers (dates, time, repeat options, weekly selection, collections, save)
  
• Example use cases, updated screenshots, and standardized headers
  
  

 Please read the detailed documentation here.