In this new improvement of our branch functionality, we are adding the option for you to collapse certain parts of your workflow which should help a lot when working with large workflows.
There are two notable improvements
You can now collapse either a single branch
or the entire tree
When creating a branch action, each branch will get its own label which is anchored at the top. This label can be renamed to what you feel like fits the best for the purpose of the branch.
Why did we make this improvement?
We have just implemented our largest feature yet - Tables 3.0!
With this new feature you have much more control when it comes to creating and managing the custom overview you want for your Travellers and subsequent data related to their journeys.
This new table was implemented both under the Traveller Profile section & when viewing Travellers inside a specific ourney.
It is good to know that every user has their own unique view so don't be afraid to make it your own, it won't affect other users!
You can now create and manage workspaces in Journeys. Each workspace has their own Journeys, Forms and Documents so it should be a lot easier for you to keep these items in order.
Additionally we added our first level of access control with the ability for you to create private workspaces that are only accessible to the creator and team members that are manually given access to said workspace.
Why did we make this improvement?
If you have journeys that rely on external users starting them by filling out a form, you might be having the problem of 'where is the best place to expose all these forms'.
Now you have an easy way to share all your processes that are started by external people.
We are introducing the Portal!
All companies now have their own dedicated Portal where they can publish external forms too and subsequently share with their company.
For more details on the portal - review our wonderful help article!
Why did we make this improvement?
You can now find three new actions in the journeys action sidepanel.
You can now add default values to your integrations so when the action is added to a journey the value is already set
Additionally we changed the way you test your endpoints which are now performed in a modal where you first configure your test values and then secondly view the response.
The table overview in journeys is an important part of your experience and value with Journeys. Each journey can have their own unique fields that can be shown in the table and are saved for each Traveller in that particular journey, we call these fields "Journey fields".
If you receive a piece of information from an action in a journey and you want to have it in the table overview, you can use this new action to put the value there fand show it in the overview.
Example of usage
You have a journey that has 2 custom journey fields "Last day of work" and "Reason for leaving". In the beginning of a journey the "Last day of work" is empty and fetched from a form in the journey. The tricky part is that in your journey, you can receive the last day of work date from two different Input forms, that are on two separate branches but you don't know which one will be run as they are conditioned. By using the Update Journey Fields action on both branches after the Input form action, you can put the received value in to the "Last day of work" field regardless of which branch is run.
Everyone that goes through a journey has
Why did we make this improvement?
There have been some improvements made to the custom integration builder.
Additionally we changed the way you test your endpoints which are now performed in a modal where you first configure your test values and then secondly view the response.
Why did we make this improvement?
When working with images in our form builders, you now have a revamped UI for the search and select process of new images from the Unsplash library.
We also added a new drag and drop component so that you can now drag new images from your folder to the form.
Why did we make this improvement?
One of our most used action types is getting a much deserved improvement.
In the condition action you can now find a lot of new condition types
One example, you can now add condition checks to see if a text contains a specific substring or if it is empty or not.
There are a lot more improvements as well for other types then text - check it out too see more!
Why did we make this improvement?
We just added a huge improvement to our form builders
You can now:
Why did we make this improvement?
Care for more of a darker theme on your software? Well now you can switch between dark and light mode as you like, it's easy!
Just click on your profile name in the bottom left corner and select the theme you'd like
Why did we make this improvement?