Bugs Fixed:
1) Ensuring that multiple profiles are displayed on the Contacts screen (View Contact Profile):
Previously, when contacts had multiple profiles, they were not displayed on the Contact Profile Page (View Contact Profile).
This issue caused confusion when checking profiles, so we have fixed it by making changes in the Glific backend.
After Fix:
2) Webhook nodes should function even with identical URLs:
When more than one webhook node with the same URL was placed in a flow, the subsequent webhook nodes failed if they were triggered within 1 minute of the previous webhook node.
As a temporary workaround, we had recommended adding a 1-minute wait between the nodes.
This issue has been resolved now through backend customisation of the constraint.No need to add a 1 minute wait time for a response between two consecutive webhook nodes.
3) Collections were not visible on the chat screen : Raised by 1 NGO Lend A Hand India
Earlier, when attempting to search for a collection name in the Collection tab on the right side of the Chat screen, it wasn’t appearing.
The fixing of the search bar in the collections tab on the right side of the chat screen made searching and navigation more simple and easier to find collections. Added screenshots below for reference.
Before Fix:
After Fix:
4) Certain keywords were not triggering the flow:
We observed that some keywords were not triggering the flow. Upon further investigation, we found that flows created by copying an existing flow were causing errors and not triggering.
To resolve this, please go to the flow’s edit page and click “Save” again. This will fix the issue, as we have made updates in our backend to address these situations in future.
5) Auto-translate: Handling contact and flow variables:
Some of the flow results in the “Send Message” node were being translated into the respective regional language for example hindi,marathi etc.
We have implemented a backend fix to ensure that variables (contact and flow results) mentioned in the “Send Message or Interactive message” content are not altered and remain as they are in any of the translated languages.
Enhancements Done:
1) WhatsApp Groups: Storing the status of the Maytapi-connected phone in Glific.
When the Maytapi-linked phone got disconnected from the Maytapi console, the messages stopped and were not getting sent. We had to manually check the console each time this happened.
To avoid this, we stored the phone’s status in the database using the Maytapi /status API
2) Allow NGOs to independently add new contacts in bulk : Raised by multiple NGOs
Uploading new contacts had to be routed through the Glific team, as NGOs didn’t have the ability to do it themselves.
We had received multiple requests from NGOs hence now we have introduced a new feature in Contact Management that allows NGOs to upload contacts in bulk independently. Please refer to this documentation for the upload procedure.
Documentation Updated:
New Documentation Added :
1) Structured responses in GPT webhook functions:
Recently openAI added a new feature called structured responses in which we can give the expected response schema in the request itself, thus we can have responses in reliable json formats. We are leveraging this and parsing the response, if its json then add the key-value pairs to the results variable. Read more about it here
Existing Documentation Revamped:
1) Link to Google Sheets:
We have updated the “Write to Google Sheets” section in the documentation with the following changes:
- Removed the range inputs
- Added instructions to specify the subsheet within Google Sheets
- Updated the screenshots for clarity
For more details, please read here
2) Analytics Page :
In response to numerous requests from our NGO partners, we published a detailed guide on the Analytics Page this month. This page offers out-of-the-box, generic insights into your chatbot’s metrics.
3) Masked Phone Numbers:
Previously, all phone numbers were visible to all users, but they are now displayed in a masked format to enhance user privacy.
However, NGOs can opt to use unmasked phone numbers when creating their own dashboards if necessary.For more information, please refer from point number 19.