(786) 292-3563 contact@digibee.com

Release Notes

Find the latest Digibee Hybrid Integration Platform Release Notes here.



January 19, 2021





The component now supports Oracle Netsuite ERP. This new database only allows inquiries to the base and it’s not possible to perform INSERT, UPDATE and DELETE operations. To know which other databases are supported by the Platform, click here.




The help menu inside the pipeline canvas is more complete. On top of having a way to start a conversation with our support team, you also can:

  • access the help center and search about anything related to the Platform;
  • check the list of our most recent news, in case you’ve missed our communications;
  • click on the icon to the keyboard shortcut, which used to be at your page top. 



    We’ve also fixed a bug:

    • SAP: when a call with an invalid payload to a RFC was made, an inconsistency in the SAP component used to affect the functioning of the other calls. Now, even if this error occurs, the pipeline works normally for the correct calls. If you use this component in your pipelines, redeploy them for the correction to be applied.






      January 5, 2021




      JSON Transformer

      We’ve created a new component so you can transform your JSONs in a quicker and more efficient way, without using codes. To know more about JSON Transformer, click here.


      Parallel Execution

      We’ve delivered a new component that allows you to create parallel execution flows. Click here to read the article.




      We’ve added to the REST and HTTP triggers a new parameter that allows you to define the maximum size of the payload sent in a request. The configuration values are:

      • 1MB
      • 2MB
      • 3MB
      • 4MB
      • 5MB


      The current limit value used in all the pipelines is 5MB.



      We’ve also fixed a bug:

      • Multi-instance: the Platform would incorrectly allow the registration of fields with numerical values only, making them unusable due to the lack of support for names composed only by numbers. Therefore, a rule has been created to prevent the creation of invalid fields.






        December 22, 2020





        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.


        REST V2

        • 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:

        • ISOBJECT
        • ISARRAY 
        • ISBOOLEAN 
        • ISNUMBER
        • ISSTRING 
        • ISNULL 
        • SWITCHCASE 

        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.



        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. 




        December 08, 2020



        • Stream File Reader Pattern: the new component has been created for stream file reading based on start and end patterns, such as XMLs, logs, specific tags search, multilines and REGEX blocks, enabling complex structure reading. Click here to read the article. 

        • JSON to CSV V2: the redesigned version of JSON to CSV, on top of transforming a JSON into CSV, also supports Double Braces. To read the article about the component, click here.



        The REST and HTTP triggers don’t demand “content-type” for the GET method anymore.


        We’ve evolved the redeployment and version change process to make sure the former pipeline remains active until the new pipeline is available to replace it.

        We’ve created the possibility to check in the deployment card if a pipeline is being reinitiated due to Errors or because it got Out of Memory.

        Important: redeploy your pipeline to activate this feature.


        To make your experience with with executions in the Platform even better, we’ve made some adjustments in the dashboards screen:

        • the tab known as LOGS has been renamed to FINISHED EXECUTIONS and also improved to ease the search for executions;
        • a new section allows you to find pipeline logs much more easily, check their details and see the origin executions;

        • this new section allows you to check pipeline internal logs that aren’t related to executions (pipeline initialization, components configuration errors), that couldn’t be accessed through the Platform before;

        • it became possible to search information in pipeline internal logs, for example logs issued by the Log component;

        • when you use the “log message” filter, the pipeline internal logs search results are highlighted;

        • the optimized search system includes the exhibition by the pipeline key and more evident and accessible action buttons in the lists view. 


          We’ve improved the appearance of the Pipeline Canvas for you to have a cleaner and more pleasant visual experience.




          We’ve also fixed a few bugs:

          • REST, HTTP and HTTP File Trigger: we’ve fixed the problem that would generate flawed deploy when the methods were written with lowercase or were invalid. Now you can configure these triggers both with uppercase and lowercase

          • HTTP File Trigger / HTTP Trigger: we’ve solved the issue that wouldn’t let the response header Authorization to be created when HTTP File Trigger or HTTP Trigger was used in a pipeline that generates a JWT token. 

          • Pipeline Engine: we’ve fixed the bug that disabled the use of JWT tokens in pipelines configured with HTTP File or HTTP Trigger

          • DB V2 / Stream DB V3: we’ve adjusted the failure that would return, for some databases, the original column name instead of the name that was configured in the alias under select. Besides, we’ve created the “Output Column From Label” property to control this behavior.

          • Mongo DB / Object Store: we’ve solved the problem that would stand in the way, in some cases, of the correct return of objectId-type attributes outside the root level for the Mongo DB and Object Store components. 



            November 24, 2020



            • DB V2: the DB V2 component now supports the Firebird database. To review the article, click here

            • Email V2: we’ve redesigned the email dispatch component, whose new version supports Double Braces and attachments. Click here to read the article.


            LOGS SCREEN

            • Payload field: we’ve created a new article that explains how the payload field works in the logs search screen of the Platform. Click here to read it. 

            • Truncated payloads: now we exhibit alerts that inform the absence of the complete payload depending on its size. Previously, the payload was identified with the @@DGB_TRUNCATED@@ property. 


            We’ve added support to specific permissions per environments. For example: DEPLOYMENT:CREATE{ENV:TEST} for exclusive access to the TEST environment and DEPLOYMENT:CREATE{ENV:PROD} for exclusive access to PROD environment. The DEPLOYMENT:CREATE permission remains valid and gives access to both environments.



            To improve your experience with the Functions of the Platform, we’ve created groupings for the articles:

            • comparison
            • numerical
            • conditional
            • data
            • file
            • JSON
            • math
            • string
            • utilities

            Understand the new division by clicking here.

            We’ve also fixed a few bugs:

            • Logs and re-execution payloads exhibitions: we’ve fixed an issue that would make the incorrect truncation of numbers with many digits and and some highly precise numbers.
            • SFTP: we’ve fixed a bug that would cause registers duplicity in the directories list operation of the SFTP component. 
            • Object Store: we’ve fixed the problem that, in some situations, wouldn’t create the index even if Object Store was defined as unique. From now on, if the pipeline isn’t able to create the index after 3 attempts, its initialization won’t be made. 



            November 10, 2020



            SFTP: new attributes are returned when a list in the SFTP component directory is made, containing files and directories information. To read the complete article about SFTP, click here.



            The XOR function accepts multiple parameters. To read about this and other functions, click here.

            We’ve also fixed a few bugs:

            • File Reader: we’ve fixed the bug that wouldn’t consider the “Maximum File Size” property configuration. To guarantee the backwards compatibility, we’ve added a new property called “Check File Size”, which validates if the File Reader component should verify the size of the file before it gets read or not.

            • Invalid components: we’ve added a verification process that prevents invalid or inexistent components in a determined Realm to be added to the Canvas. 
            • Upgrade of Major Version: we’ve fixed the problem that would invalidate the Capsules/Libraries in your pipeline after the upgrade of the pipeline Major Version. 
            • Large and fractional numbers display: we’ve fixed an issue that would make the incorrect truncation of numbers with many digits and and some highly precise numbers in TEST MODE deployments. 

            • Errors treatment: as announced in previous communication, we solved the matter that was causing behavior change in the error treatment of components that have subpipeline and, given that, there’s no compatibility break in already-deployed pipelines. 




              October 27, 2020


              • Throw Error: we’ve delivered a component that allows errors to be thrown in desired points of a pipeline under execution, which gives you more control over the error/execution scenarios. To know Throw Error, click here
              • Block Execution: we’ve developed a component that allows you to group parts of the pipeline inside a block to obtain more organization and deal with errors. To read about Block Execution, click here

              • Do-While: we’ve updated the documentation of the component so you understand the errors treating better. Click here to read the article about Do-While. 
              • Retry: we’ve updated the documentation of the component so you understand the errors treating better. Click here to read the article about Retry.  

              • REST: we heard your feedback and realized the logs concealment in the REST calls caused visibility decrease. For this reason, we’ve reverted the action in order not to negatively impact you. 


              • Images: we’ve adopted a vectorial format for the components icons of the pipeline Canvas. Given that, on top of having more high-quality images, the uploading time decreased. 

              • Visual improvements: to improve your experience, we’ve refined the login screen of the Platform, adjusted the failure that would let the sidesheet to be improperly closed and made other changes in the interface consistency. 


                  We’re reviewing our documentation for you to have access to complete and updated reading. We invite you to revisit the following articles:


                  We’ve also fixed a bug:

                  Retry: we’ve fixed the bug that would appear in successful flows, when the Retry component was configured with 1 try and had the “failOnError” option enabled. Click here to access the reviewed article about this component.



                  September 29, 2020


                  Presentation: the components are listed with more friendly names.


                  Google: the Google provider has been updated to allow the same Google account to be used in different accounts with identical scopes without causing undue expiration. To enjoy this news, update your account.



                  GRAPHIC INTERFACE

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

                  This time, you’ll see the changes in the:   



                  • Two Factor management 
                  • password change 



                  • consumers  
                  • globals
                  • accounts 
                  • relations 
                  • multi-instance



                  • general view
                  • logs 


                  With that, the experience on all the screens is renewed.

                  We’ve also fixed a few bugs:


                  • Forgot password: we’ve made adjustments in the error indications so that you know when the link of the “Forgot my password” function expired.
                  • Components configuration: we’ve corrected a problem that caused incorrect component settings to appear in some unusual situations.
                  • Pipeline execution: we’ve eliminated the Zip File Closed error that would occur after the pipelines deployment, in the first executions.




                  September 01, 2020


                  REST V2: you can download files through REST V2 calls, being also able to immediately transform them to base64, binary format or raw content reading. Besides, now the component allows the use of HTTP 1.1 protocol to be forced during the call. To read the article about REST V2, just click here.


                  Email Trigger V2: we’ve created a new version of the trigger that, on top of improving the functionalities of its previous version, now supports attachments receival. Click here to read the article about Email Trigger V2.


                  Images: the Platform illustrations and icons are in vector format. With that, the images have more quality and the uploading time decreases.

                  GRAPHIC INTERFACE

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


                  This time, you’ll see the changes in: 


                  • pipelines listing screen
                  • historical version 
                  • Runtime screen

                  We’ve also fixed a few bugs:

                  • Stream Excel: the component now correctly reads numbers with floating point. 

                  • Two-factor authentication: we’ve adjusted a temporary error that wouldn’t let users to go for the two-factor authentication to login to the Platform. 

                  • OAuth 2: we’ve eliminated the access issue to the OAuth 2 services that would occur in some pipeline redeployment cases. 

                  • “File” property: we’ve corrected a problem that wouldn’t let your pipeline to return a property called “file”. 

                  • Components tooltip: we’ve eliminated the problem that would present an incorrect message [Object object] in the components tooltips in every screen. 



                  August 18, 2020


                  • DB V2: the new functionality rollback is supported in batch mode and is applicable when at least one error occurs in the execution. Besides, the list of errors is shown if there’s any failure during the execution in batch. To understand better how this new functionality can help you to use this component, click here to read our article. 

                  • REST V2: we’ve added support to AWS-4 account types so that you can authenticate in the AWS service, such as Lambda and DynamoDB, that you wish to use through the REST V2 calls. To know it better, click here.

                  We’ve also fixed a few bugs:

                  • DB V2: we’ve adjusted the exhibition of the batch mode execution status when failures occur in the use of the Oracle database. We’ve also adjusted an issue configuration screen of this component, that used to exclude the correct item in the “Type Properties” session. 

                  • Pipelines: we’ve fixed the problem that wouldn’t allow a new version of the pipeline to be created from another one that was archived. 



                    August 04, 2020


                    RabbitMQ Trigger: we’ve created a new trigger that receives messages from a RabbitMQ broker. Click here to access the article. 



                    • S3 Storage: now the component supports pagination in the listing operation, on top of moving files between remote directories. 
                    • GZip V2: the new version of the component, which supports Double Braces, compresses and decompresses files, as well as data from your pipeline. Click here to access the article about GZip V2


                    We’ve added unprecedented functions to the Platform so you are faster in the integration process, since it’s not necessary to go for complex solutions anymore. Check the new available functions:

                    • TOSTRING 
                    • SUBSTRING 
                    • BASEDECODE 
                    • BASEENCODE 
                    • SPLIT 
                    • JOIN 
                    • TOINT 
                    • TOLONG 
                    • TODOUBLE 
                    • LEFTPAD 
                    • CAPITALIZE 
                    • NORMALIZE 
                    • RIGHTPAD 

                    To understand better and know how to use them, click here to access our article. 



                    Visual identity: the website has our new logo, as well as new fonts and colors – we’ve made the Platform visually more elegant, without affecting any functionality. 



                    Now our Platform allows the OAuth2 account type to be used as the provider of Mercado Livre. 


                    We’ve also fixed a few bugs:


                    • Chat: we’ve made adjustments so that the chat messages notifications are on the interface in the pipelines creation screen. 

                    • JMS: we’ve corrected the problem that used to close the connection pool of this component and suspend the dispatch of new messages. 



                    July 24, 2020


                    • HTML To PDF: the component allows the creation of files in PDF, with images and layouts from a HTML. To know it better, click here and read our article. 
                    • Assert V2: the version of the component allows you to set the validation conditions through Double Braces, as well as internal messages and flows interruption when errors occur. Click here to know more.  
                    • FTP/SFTP: we’ve added the MOVE function to these components, that moves a file from one remote directory to another. 


                    SENSITIVE DATA

                    We’ve added the possibility of defining sensitive data (sensitive fields) in Realm level, ensuring global governance. To make this request, get in touch with us via chat. 


                    We’ve also fixed a few bugs:


                    • SFTP: we’ve worked on the error that used to ignore Remote File Name during the upload operation. 
                    • Zip File: the component no longer exposes the full file path when an error occurs. 
                    • Password change: we’ve updated the error message when the new user password is changed to an already-used version. 
                    • Multi instance: we’ve fixed the error that used to disable the redeployment of a multi instance pipeline. 
                    • Users management: we’ve added a validation that prevents the registration of existing users. 
                    • CSV To Excel: the Fail On Error property isn’t ignored during the use of this component anymore. 

                    • One Drive: we’ve eliminated the error that used to occur in the listing of the root and in the use of names with space.






                    July 07, 2020



                    • REST V2: we’ve inserted to the connector the capacity to send file in the request body.   
                    • CMS: when the ENCAPSULATED option is enabled, the content of the specified fields (SIGN FIELDS option) out of the payload (SIGN option) is included in the signed message.  
                    • RabbitMQ: we’ve developed a new component so that you can publish messages in a RabbitMQ queue. To know more about the component, click here and read our article.  
                    • OneDrive: we’ve updated the connector with the last version of Microsoft SDK and included new functionalities, such as LIST, SEARCH, pagination, among others. 



                    DOUBLE BRACES

                    We’ve developed 2 new functions with Double Braces so that you can confirm the existence of a file (FILEEXISTS) and the size of a file (FILESIZE). Click here to read our article and understand these functions better.  


                    OAUTH MICROSOFT

                    We’ve updated the Microsoft OAuth (oauth-2) authentication flow to the latest version. 



                    We’ve come up with the integrated authentication, that allows you not only to centralize the access control,but also to include and exclude your collaborators from our Platform in your identity provider. If you’re interested in activating this solution, get in touch with us via chat. 



                    We’ve also fixed a few bugs:

                    • Stream DB V3 / DB V2: parameters values are now substituted according to the order presented in Double Braces. 
                    • Mongo DB: the values generated by the ObjectID objects constructor are being shown in the correct way when applied in attributes different from “_id”.
                    • Double Braces: we’ve fixed a Double Braces interpretation error that was happening during the evaluation of multiple expressions in an unique property (in particular, when using the UUID function multiple times). 
                    • User Status: now the recently-created user gets the “Redefine password” status. 






                    June 22, 2020



                    CMS: the new component allows you to sign payloads and fields, on top of verifying signatures in the CMS cryptography standard. You can click here to understand the concept of Cryptographic Message Syntax. And to know more about the connector, click here and read our article.  



                    Kerberos: we’ve created a new type of account so that you can configure the principal and the keytab. 


                    The most recent versions of all the database connectors support the Kerberos-type authentication. If you want to use this type of authentication, get in touch with our support team. 


                    DOUBLE BRACES 

                    Accounts: now you can inform more than one account in REST V2 and in Soap Connector V2, bringing more flexibility and safety in the use permission through Double Braces. Click here to read our article about the subject. 


                    USERS MANAGEMENT

                    Improvements in the Platform allow you to reactivate removed users. Besides, the login can be integrated with your own Identity Provider (AD) through SAML V2, broadening the management capacity of the Platform. 





                    June 09, 2020


                    DB V2: improvements in the component allow you to make batch transactions through batch mode. To read our updated article about DB V2, click here.  

                    USERS MANAGEMENT 

                    We’ve made updates so that you can add new data related to the registered users, including name and timezone. Besides, we’ve added a security layer in the token to decrease the expiration time to 30 days only. 

                    We’ve also fixed a few bugs:

                    • Soap V2: we’ve expanded the capacity of the component for you to use accounts with a certificates chain. 

                    • Google Drive: we’ve corrected an issue that wouldn’t allow the removal of files when the DELETE function was selected. 

                    • JMS Trigger: now the consumers are returned to the pool when the connection with the broker is lost. 

                    • Login: we’ve corrected the presentation of messages that provide guidance about the password filling.

                    • Users Management: the user status isn’t hidden anymore and the “First Access” and “Forgot Your Password?” processes are free of errors.



                      May 12, 2020


                      • CSV To Excel: a new functionality in this component allows you to add multiple sheets inside a new or pre-existing Excel file. Would you like to know more about CSV To Excel? Click here to access our article. 

                      • REST V2: a new support added to this component allows calls to the Google API services, such as Translate, Vision, Machine Learning, among others, to be made through the use of a service account key of your Google Cloud project registered as an Digibee account. To know more about, click here.  


                      We’ve also fixed a bug:

                      • Choice: we’ve solved an issue in the labels validation that incorrectly considered a Choice paths repetition. 


                      ⚠ Existing pipelines using CSV To Excel

                      The Excel file name receiving has been changed (property: EXCEL FILE NAME) and it impacts the fileName property output of the component. Please, change the parameter to provide the Excel file full name with the fileName.xlsx extension before deploying the pipeline.



                      April 28, 2020


                      Google Drive: can be configured to list, upload and download, delete and move objects from Google Drive to the pipeline and vice-versa. To read the article about this component, click here



                      • Kafka: the message consumption is possible when we use triggers that make subscriptions on Kafka. Click here and know this specific trigger better. 

                      • Allow Redelivery: this advanced configuration can be applied to any trigger to determine if the pipeline must reprocess discarded or lost messages. 


                      DOUBLE BRACES

                      It’s possible to access particular details (metadata.execution.key, metadata.execution.timeout, metadata.execution.startTimestamp and metadata.execution.redelivery) from the pipelines execution through the Double Braces metadata context. 


                      PIPELINE ENGINE

                      We’ve improved some mechanisms of the pipelines execution engine:


                      • Messages processing: the message expiration time is no longer affected, since the Pipeline Engine doesn’t prematurely remove the messages to be processed. Click here and know more by reading our article. 

                      • Pipeline startup time: the infrastructure waits for the Pipeline Engine availability before enabling the triggers access for it.

                      • Pipeline crashes: the pipeline is automatically restarted when it’s out of memory (OOM). 



                      The status STARTING is applied in the Runtime screen to pipelines whose deployment is in progress. When the deployment is finished, the ACTIVE or ACTIVE BUT DEGRADED status indicate the pipelines are available. 



                      The color palette application in our buttons generates more familiarity between the pages of the system and eases the components identification. 


                      We’ve also fixed a few bugs:

                      • Rest / HTTP / HTTP-File Trigger: now it’s possible to build flows that receive custom tokens in the Authorization header when you don’t want to use the Digibee JWT mechanism. To do that, disable the JWT option in the trigger configuration. 
                      • Custom Scheduler Trigger: in rare situations, there could be duplications in the pipeline execution. A protection mechanism has been added to stop it from happening. Would you like to know more about his trigger? Click here to read our article. 



                        April 15, 2020


                        We’ve improved the usability of the components list, making the items visible for users who don’t have scroll mouse and also for the ones who prefer to use scroll. 


                        • Choice: our new error message indicates the path for the repeated items to be found. To read the article about this component, click here

                        • File Reader: we’ve added a consolidated reading capacity of all the lines in just one string to ease the files processing. 

                        • REST V2: it’s possible to inform the file type in the dispatch based on multipart/form-data. 


                        • JMS: pipelines built with this trigger add more resilience when parameterizing the consumption of messages/JMS topics. To read the article about this trigger, click here


                        The components palette is accessible even when test-mode is open. 

                        We’ve also fixed a few bugs:

                        • REST / HTTP / HTTP-File Triggers: the log message now shows the invalid payload that is presented to the pipeline. 

                        • Consumer: we’ve eliminated the error that wouldn’t allow the consumer to be edited when your related pipeline was erased. 
                        • Shortcuts: now the shortcut list has a scroll bar. 

                        • Breadcrumb: it became possible again to copy and paste the name of the pipeline/level. 



                          March 30, 2020


                          • JMS: now supports dynamic and static Double Braces. Click here to know more about this component. 
                          • SAP: we’ve updated the article about this component with iDoc information. Click here to read it. 
                          • Do While: we’ve created a new feature that allows the flow to continue even in case of errors. We’ve also updated the article about this component. Click here to read it. 



                          The shortcut modal with more spacing between the items and line lightening ease the data reading. 



                          The Shift + Delete shortcut can remove components during the pipeline edition, as well as Ctrl + Delete



                          The “more” menu shows all the links that don’t fit in the header. Besides, titles that exceed the space are fully shown through tooltips.


                          We’ve also fixed a few bugs:

                          • Login difficulties: the Realm can now be typed in lowercase, uppercase or both. 

                          • Error message: we’ve fixed a spelling mistake in a warning that would appear during the pipeline edition. 

                          • OAuth Authentication: we’ve solved the problem that wouldn’t allow the consecutive execution of pipelines when using the OAuth authentication. 

                          • OAuth: we’ve improved the tokens obtaining process through the OAuth mechanism by using specific resources from Google and Microsoft providers. 

                          • iDoc SAP: we’ve adjusted a limitation in the XML dispatch in this model. 

                          • Kafka: now the SASL_SSL and SSL security protocols are supported. 

                          • Trigger: we’ve solved the route problem that sometimes made some deployed pipelines inaccessible. 

                          • JWT: the requests are no longer barred in a specific scenario. 
                            Share This