We’d like to share some improvements and news:


Pipeline Executor

We’ve built a new component that allows you to invoke other pipelines. Pipeline Executor enables other pipelines to be synchronously or synchronous invoked. To read the article about the component, click here.


We’ve ratified the DB Informix database for you to use it when different versions of the DB component are being configured.


  • We’ve added “Http Status Message” in the response of the endpoints call of the REST V2 component, when this information is present in the endpoint response.

  • Now it’s possible to configure REST V2 with the disabled connections pool - given that, the component better handles some endpoints that require new connections at each call.

  • It also became possible to configure REST V2 with the SSL session invalidation for each request.

Read the complete article about the component by clicking here.


We’ve created new functions to optimize your experience with integrations in the Platform. These are they:








To know how to use these new conditional functions, click here.


We’re always investing in the visual experience improvement of the Digibee Platform.

This time, we’ve created icons and shapes to ease the component identification:

  • Choice: will have the unique diamond shape;

  • Streamers (or components with subpipelines): will have the shape of a pentagon.

The icons of the other components remain the same.


Now we hide data of sensitive fields in the accounts configuration screen while typing.


We’ve changed the behavior of the search filter when dates are used. See the example:

Initial date: 21/12/2020 15:47

End date: 21/12/2020 15:52

This is how the search will be like:

Initial date: 21/12/2020 15:47:00.000

End date: 21/12/2020 15:52:59.999

We’ve also fixed a few bugs:

  • CSV to JSON V2: we’ve eliminated a failure that would, in some situations, ignore the delimiter during the CSV to JSON conversion through the use of CSV to JSON V2.

  • Triggers HTTP: we’ve fixed the bug that wouldn’t let multi-instance pipelines requests to be made if HTTP triggers were selected (REST, HTTP or HTTP File).

  • Choice: we’ve solved the problem that would allow the configuration of the name of a Choice component line with the following invalid characters: &, ? and /

  • Runtime: we’ve fixed the bug that wouldn’t remove the implanted infrastructure of pipelines with too-large names during redeploy.

Did this answer your question?