September 2021

Release Notes

Photo by Marvin Meyer on Unsplash

In September 2021, we released several new updates, including enhancements to loop over function, Airtable and Webflow nodes, and web scraper console. On top of that, we have fixed over 15 bugs, making the user experience seamless for Byteline users. 


Friendly Loop Over 

In the earlier versions, the loop over function used to be a little complicated, and users often found it difficult to use. However, with Byteline’s September release, all you have to do is tick the loop over checkbox and select the corresponding node, the output of which you want to iterate from the drop-down menu. 


Actions consumed in the flow Instance Status 

Earlier, users could only collect information about start time, end time, and status of the flow. However, with the latest update, you can now check how many actions were consumed by a particular flow instance while checking the status. 

Alternatively, users can check the action consumed by visiting the dashboard option in the navigation bar of the Byteline console. Here, actions will be displayed on flow level instead of flow instance level. 


DataType Field on Airtable and Webflow Update Tasks 

In the update tasks for both Airtable and Webflow, we have added a data type button on the left of the text field, which is clickable and allows you to select the data type in which you want to save the field. So, whenever the data is sent to Webflow or Airtable, it is sent in the format chosen. By default, the data type is automatically figured out by Byteline; but in case it's incorrect you can use this drop down to change.

For example, if you want to fetch the price of cryptocurrencies, then you will have to select Number (as a format) from the dropdown menu. This will ensure that the data is collected in the selected format. 




Determine Webhook Data Structure 

A Webhook is a flow trigger that is activated by making an HTTP request to the URL configured for that Webhook. We already offer users to create a flow with Webhook as a trigger node, but now we have introduced a feature that lets users easily configure the input data structure to a Webhook-based flow.

Click on the link stating - "register body format now" and wait for a few seconds for API call to come in. 

Here, we have used Postman to investigate the data of a Webhook but users can use any other tool as well. 

For this purpose, you will have to copy the URL from Byteline and paste it into the Postman. 

After that, you will be able to view the body you are sending, as shown in the snippet shared below. Once checked, then hit the Send button. 

Next, navigate back to Byteline, and you will observe a message - "Input Structure Recorded," which means that the users can investigate the input data within the Webhook. 

New Paste Button for the Web Scraper Console 

In the new update, we have added a new button named Paste from the Chrome Extension to the web scraper console, which helps users directly paste the selected value to the Byteline console instead of manually copying and pasting the value.  

Next, we have added an Advanced button. By default, all the XPaths in the web scraper configuration are in a read-only format, as shown in the snippet below: 

However, users can now exercise an option to edit those values by clicking on the Advanced button.,

In advanced mode, you can also use ‘Add Array Field, Add Single Field and Add Repeating Field buttons to manually add more fields to the scraper configuration.

Enhancement to Node Configuration  

With the new update, users cannot add the next node without configuring the previous node. If users will try to add a node without configuring the previous node, they will receive the following error message: 


More Filter Criteria 

We have added more conditions to filter your data, which are explained below:

Begins With: All the records of the variable field should begin with the value in the comparison value field.

Contains: All the records of the variable field should have the text selected in the comparison value field.

Not Contains: All the records of the variable field should not have the text selected in the comparison value field.

Is Empty: The attribute value is empty, and no data exists. 

Is Not Empty: The field specified should not be blank, and it must have a value.

Equals: The value of the selected field should exactly match the specified comparison value. 

Not Equals: This is the opposite of Equals. The value of the selected field must NOT exactly match the specified comparison value.

Lastly, we have fixed over 15 bugs in the September release. 

Stay tuned for more amazing updates, and feel free to connect us for any doubt!