06/14/19 Guide on New Conversation Functionality

This guide explains how to add the two actions needed to the "Send Message" workflows on the messages page. We can absolutely add this for you; please reach out to support@littlebaytech.com.

How to Add the Needed Actions to the Create New Conversation Functionality

Please note this is only applicable to applications created with the Messaging Template before 06/14/19.

Step 1: Remove the "Trigger View Conversation - Mobile" and "Trigger View Conversation - Desktop" actions from the following workflow:

On the messages page, in the "E. New Conversation" workflow folder, remove the Trigger View Conversation - Mobile and Trigger View Conversation - Desktop actions from the Button Send Message (inside Floating Group - Create New Conversation), *only when Group Conversation's Container's ExistingConversation is empty workflow event:

Step 2: Add the following "Go to page" action in that same workflow event In that same workflow event, add the "Go to Page Messages" action to the end of the workflow, with the parameter c=(Step 1's Create a New Conversation's...)'s unique ID:

Workflow Notes: Go to the messages page, with the parameter c=[Step 1's Create a new Conversation's... unique ID) This action navigates the Current User to the messages page, and removes the "v" and "u" parameters from the page URL. When the page is reloaded, the pageload workflows will then automatically trigger the "View Conversation - Desktop" or "View Conversation - Mobile" custom events so the new Conversation is shown.

Step 3: Remove the "Trigger View Conversation - Desktop" and "Trigger View Conversation" mobile actions in the second Button Send Message Workflow (when the ExistingConversation custom state is not empty) On the messages page, in the "E. New Conversation" workflow folder, remove the "Trigger View Conversation - Mobile" and "Trigger View Conversation - Desktop" actions from the Button Send Message (inside Floating Group - Create New Conversation), *only when Group Conversation's Container's ExistingConversation is not empty workflow event:

Step 4: Add the following "Go to page" action In that same workflow event, add the "Go to Page Messages" action to the end of the workflow, with the parameter c=(Step 3's Make Changes to a Conversation's...)'s unique ID:

Workflow Notes: Go to the messages page, with the parameter c=[Step 3's Make Changes to a Conversation's... unique ID) This action navigates the Current User to the messages page, and removes the "v" and "u" parameters from the page URL. When the page is reloaded, the the pageload workflows will then automatically trigger the "View Conversation - Desktop" or "View Conversation - Mobile" custom events so the existing Conversation is shown.

Last updated