Release Notes

COMPONENTS

DB

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.

SUPPORT

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.

COMPONENTS

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.

TRIGGERS

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.

COMPONENTS

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.

DB 

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.

FUNCTIONS

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.

GRAPHIC INTERFACE

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.

​​ACCOUNTS CONFIGURATION SCREEN

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

DASHBOARD

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. 

COMPONENTS

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

USERS REGISTER AND EDITING

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.

FUNCTIONS

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. 

COMPONENTS

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.

FUNCTIONS

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. 

COMPONENTS

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

DESIGN

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

DOCUMENTATION

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

• JSON to XML
• FTP
• SFTP 
• Stream DB V3
• Event Publisher 
• Event Trigger
• S3 Storage 
• Hash 
• Template Transformer

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.

COMPONENTS

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

INTEGRATED IDENTITY PROVIDER 

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. 

COMPONENTS

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.  

ACCOUNTS

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

KERBEROS 

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. 

COMPONENTS

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.

COMPONENTS

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

COMPONENTS

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. 

TRIGGERS

• 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). 

RUNTIME

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. 

DESIGN

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. 

COMPONENTS

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. 

TRIGGERS

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

CANVAS

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. 

COMPONENTS

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

DESIGN

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

CANVAS

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

BREADCRUMB

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.