In Glific, we’re all about making things easy and automated, just like every human—we love simplicity! Our goal is to create a user-friendly experience so that everything is straightforward and hassle-free. To achieve this, Glific has launched new automated features in the flow. This is designed to provide a smooth and user-rich creation of the flow.

Development updates

Language Alert: We’ve implemented a Language Alert feature, If messages in different languages aren’t updated for all nodes in a flow, a warning will pop up. This feature helps users by highlighting the nodes where updates are missing, ensuring comprehensive language coverage for a seamless user experience. It serves as a reminder to keep all translations up to date.

Automatic “wait for response” node after “interactive message: node: Enabling the auto-population of “wait for response” node from preceding interactive message nodes, including a list of options from interactive message, would significantly enhance the speed and simplicity of creating flows. This improvement ensures a smoother workflow by reducing the manual effort required to input data, thereby optimizing the overall user experience.

Autosuggest variable in “send message” node: when writing a variable inside the Send Message node. Example, as a user types “@contact,” a dropdown menu would appear, displaying available options like “@contact.name.” This autocomplete functionality simplifies the variable creation process by offering predefined choices, ensuring accuracy and consistency in variable names and reducing the chances of errors.

Next node after the “interactive message” node should be “wait for response”: In the flow editor, the next node after every “interactive message” node should be a wait for response node, if not then a warning message will pop up in the flow editor screen while publishing the flow.

Trigger starts with HSM : When creating a trigger and selecting a flow, if the chosen flow doesn’t begin with an HSM message, a warning message will appear. The rationale behind this is that regular messages won’t reach users outside the 24-hour window.

HSM Template attachments : The HSM Template wasn’t being sent because the image was not attached to the template message. To fix this problem, we are using a smart checker. This checker would automatically make sure that all needed attachments, like images, are included in the HSM template created in the flow editor. This solution helps avoid issues and makes sure that the template follows the right structure for successful delivery.

We believe these enhancements will contribute to a smoother user experience and more efficient workflow.