Sometimes you are not sure what Journeys contain an external form or a form that is used on your portal.

When viewing your Journeys list, it should be now very clear which of them contain a published external form and which are connected to your company portal.

Why did we implement this improvement?

• We wanted to give our users a better overview of what journeys contained external forms as they were quite hidden

Another great improvement - this time to the table overview of Travellers!

We had many complaints regarding how hard it was to view field content that was long and in reality sometimes it was impossible from the table view.

Now you can simply click on the field in the table and it will open a modal where you can view and edit the information.
​

Additional notes

• Currently you can only view and edit fields of the type Text-short and Text-long
• You can not edit inline text that is from actions in the journey workflow

Why did we implement this improvement?

• View large information bits with ease
• One of the most requested improvements we have had 🌟
• Easier to edit Traveller information - skip the whole "edit" process

If you work with custom integrations a lot this improvement might help you quite a bit.

When dealing with third-party software and their API's they tend to handle empty values differently. With this new setting, you can determine how this integration will send empty fields to the third-party software.

The options are the following:

"Send empty string as empty ("")" which will

• This will send the empty string as an empty string e.g. "fieldName": "".

Send empty strings as null

• Will send all empty fields as the value "null"

Skip empty fields in requests

• This functionality will not send the empty fields at all, so skip it out of the request entirely

You can find this configurations under the "Settings" section inside your integration.

Why did we implement this improvement?

• More control of Integration requests
• Regularly requested, indirectly or directly by users

We are so very proud of this one - it is huge!

You can now customize your Journey tables to contain information from your journey 🤯
​
​What does that mean exactly?

Journey workflows can contain a lot of information, sometimes this is information that you want to have in your overview to compare between all the travellers in your current journey.

Example of this would be something like a form sent out to a supervisor where they select a birthday gift for their employee.

With this new feature, you can add the form response of all those supervisors as a column to your table, giving you a better overview.
​

We highly recommend you read the full article on this feature and examples.

Why did we implement this feature?

• A much request feature for a high percentage of our users
• Fits in perfectly with where we are going with the product
• Reduces the need to source private data to third party table software only for the purpose of overview

We have just released a brand new action, this is a big one!
​

With this new action you can use Python code to manipulate any data from within the journey you are working in and output it any way you want.

As you can imagine that is incredibly powerful.

The steps are easy to follow:

• Add the action where you want to use it in your workflow
• Add the inputs you want to use in your code
• Generate the code functionality you want by using AI
• Test your results
• Profit!

We highly recommend you view the help article for more examples and details.

Why did we implement this improvement?

• Give users the ability to handle more dynamic cases when working with all types of data throughout their workflows
• Remove the need for custom actions or one time implementations edge cases that still need to be implemented e.g. when sending an text message to someone that has a birthday on February the 29th (leap year)

To help with your overview we have added a new feature which allows you to quickly see if there are any Travellers that contain Warnings or Errors
​

Warnings

Warnings are soft notifications that alert you that something might go wrong, meaning, the information required to run a certain action is not present at the current point in time.

One example for this is, let's say you have an SMS action that relies on a Travellers phone number to be able to send out successfully. You don't have the phone number in the beginning of the journey but you will retrieve in a form somewhere in the middle.

Errors

Red error warnings indicate that an action has hit an error when it tried to run and needs to be looked at right away.

You can click on the red flag icon, and it will open the Issues sidepanel and highlight the error for you to fix, easily and quickly.

You can also add filters easily here so if you only want to view Travellers that have an error present you can do that (see image below).

Why did we implement this improvement?

• It was unclear what Traveller Journeys had live errors and how users were able to identify / find them
• With the warnings highlight, users are more aware of things that might be not configured properly before running the journey in its entirety

We just added a much requested improvement to Journeys 📃
​

The Documents section under each workspace has been re-designed to be easier to use 🙌
​

The new design should allow you to experience a more intuitive flow when working with documents and configuring variables for future use in your Journeys.
​
The release includes the following improvements

• Working with 'large' documents that have many field variables and setting field types has been significantly improved
• Improved UI/UX when working with many documents in a workspace and viewing their state
• Documents can now only be set as active or in-active, the "draft" state has been removed
• Improved flow when previewing documents with test data
• You can now set default values that will appear when the document template is used in journey builders (can always be edited later)
• Improved UI for different screen sizes
• Easier to edit and rename contract documents

Why did we implement this improvement?

• Frequent feedback from end-users told us that the old UI was a bit complex and sometimes hard to work with
• Adding new documents and configuring field variables and types was un-intuitive
• Configuring field variable types did not work well in different small screen sizes e.g. laptops
• Previewing documents with data was un-intuitive and rarely used as a result

You can now customize the name and favicon of your portal under the Portal settings🛠️

When doing this the browser tab will now show your company name and icon.

Why did we make this improvement?

• To help our users make the Portal section feel more in theme with their company theme

To help you find the important information faster, we have added a new feature to Journeys: Favourites!
​

You can now mark any Journey, Document or Form that you are working on, or that you might visit frequently, as Favourite. This will pin it to the main navigation side-panel for easy, quick future access.

Why did we make this improvement?

• As the Journey count starts growing - finding the most relevant and important Journeys has become more tedious, with this feature you can control and highlight Journeys that are most relevant to you at any given time

Do you have a list in Journeys that is maintained in another system, meaning that any change made there, you have to manually update in Journeys as well?

For example you might want to always keep an up to date list of Slack channels in your Journey system or a Department list that is managed in your payroll system.

Well that problem is now gone! With the the new "Synced list" functionality you can create a new list that uses options from another system as a source, and is updated every day automatically.

You can set up a sync list with any system that is connected to your Journeys account.

We recommend looking at our in depth help article for more details and setup instructions.

Why did we make this improvement?

• We saw that the majority of our users were creating lists that were actually derived from other systems such as payroll, shift management & e-signing. Most, if not all, had given us feedback that it was impossible to maintain these lists manually between systems
• It was important that this was a feature that was possible from within the system so users would not have to rely on IT support for setting this up