Release notes 2021
2021 updates on any recent changes, feature enhancements, or bug fixes for the Digibee iPaaS.
Was this helpful?
2021 updates on any recent changes, feature enhancements, or bug fixes for the Digibee iPaaS.
Was this helpful?
Email V2: we’ve added a new parameter to the component: FORCE TLS V1.2. It allows users to set the use of the protocol TLS V1.2 as mandatory for connections with email servers. Important: we recommend the use of this parameter with Microsoft Exchange email servers. Click here to read the full article on the component.
We’ve also fixed a few bugs:
Scheduler Trigger: we’ve fixed an error that, on rare occasions, prevented the execution of consecutive scheduled tasks.
We’ve developed a new access control model. It’s practical and robust. The access management now allows grouping and reusing the profiles with similar accesses for a better experience when accessing the realm.\
Example of the new access grant:
The new access control model includes the concepts of Groups, Roles and Users that are related to one another just like on the model below:
Now, updates in a user’s access will be in real time. There’s no need to logout for the update.
To learn more about the new access control, read the following articles:
Basic Concepts About Users
Just so no users lose their permissions, we planned a transition period in which both access models will coexist. All users must be migrated to the new access until March 31, 2022. To learn more about the transition process, read the full article here.
Thinking about improving our users’ experience and giving them more clarity and accuracy on the use of a few terms, we’ve updated the Consumers screen under the Settings menu. Its new name is API Keys. The functionalities have not changed and the settings flow is still the same as well.
We’ve made some improvements on the audit experience. Now, the audit logs contain new information:
Service - identification of the Digibee Integration Platform’s features that have been audited. E.G.: Pipelines, Globals, Accounts.
Action - the action taken that created the register. E.G.: created, updated, deleted, viewed.
Reference - it’s the friendly name of the audited object.
IMPORTANT: During this delivery phase, the only objects with the reference are: Pipeline, Account and Globals.
Status: shows if the action has been successful or if it contains any error.
This delivery is part of a larger improvement process that will include the possibility of navigating up until the audited object.
XML Schema Validator: the client is now able to validate a XML file against XSD files. Click here to read the full article.
We’ve also fixed a few bugs:
Component CSV to Excee’ve fixed the error that prevented the ability of reading files with charsets different from UTF-8.
Pipelines Metrics: we’ve fixed the error that prevented the correct exhibition of information when filtered with the 15 minutes period option.
Email Trigger V2: we’ve fixed the error that prevented new emails from being read, moved and deleted correctly after they had been processed.
We have developed a new experience for your pipelines’ deployment.
The new deployment screen offers more autonomy and ease, bringing more data to help the decision making process at the moment of the pipelines’ deployment, such as the indication of who has deployed them. Click here to read the full article about the new interface.
IMPORTANT: During the period of the Beta program, the functionality will be offered parallel to the current one - this way you will see two buttons on the screen.
To read more about the Beta program, access our document here.
We added a new functionality to the history of pipelines’ versions. Now it’s possible to see any minor version of a pipeline, its components and the settings of each of them. Click here to read the full article about the pipeline history .
To read more about the Beta program, access our document here.
We added an improvement to the Projects management. When a pipeline is moved to a new project, it’s necessary to deploy it again because the execution environment of pipelines (Test and Prod) are unchangeable. This way, there will be an alert on the deployments in need of this action.
IMPORTANT: this functionality doesn’t support multi-instance deployments yet.
Aiming to improve security when accessing the Platform, your login’s password will expire every 15 days.
From now on it will be necessary to create a new password every 15 days and login again to reestablish your session.
In case there is any need to change the password’s expiration period, get in touch with our support team through the chat. Only the realm’s administrator can make the request.\
We updated the documentation of the article on Accounts and we added the expiration period of the tokens given by the following providers:
Microsoft - 3 months Google - 6 months Mercado Livre - 6 months
Click here to read the full article.
Rest V2: we updated the documentation of the component. Click here to read the full article.
In order to always offer you support, we built an alternative messaging feature. Now, it’s possible to send questions and requests to our support team even if our online chat is unavailable. The answers will be sent by email.
Due to updates in the OAuth server from Mercado Livre, we have modified the OAuth provider from Mercado Livre so that it authenticates through the endpoint of accounts from Brazil (www.mercadolivre.com.br/authorization). IMPORTANT: the current tokens registered in Accounts won’t be affected. New tokens will be obtained through the new endpoint.
The new component enables you to generate OpenID-type tokens for IAP (Identity Aware Proxy) proxies authentication. Click here to read the full article.
The new SQS component enables you to send messages to FIFO-type queues in AWS SQS service. Click here to read the full article.
The function allows a cardinality of n:1 to be applied to any informed structure, where regardless of the number of elements in the input, the output will always be 1 element. Click here to read the full article on JSON Functions.
The function allows an output to be standardized by a multiple cardinality. That means, when an input of an array has n elements, its output will be an array of n elements, and when an input has a sole object, its output will be an array of this same object. Click here to read the full article on JSON Functions.
We’ve also fixed a few bugs:
LDAP Component: We fixed a bug that blocked pipelines from executing when using the LDAP component.
Chat: We removed the requirement of the USER:READ permission for a user to access the chat.
Pipeline history: We fixed the bug that resulted in a white screen when all versions of a pipeline were archived, and when one of the versions was restored.
NFS: The component manipulates files. It lists files, and enables downloading, uploading, and deleting. Click here to read the full article.
IMPORTANT: due to the characteristics of the NFS protocol, only Dedicated SaaS platforms are supported.
We’ve also fixed a bug:
Environment selector in Monitor: we fixed a bug that did not save the last environment selected after switching screens.
PUSH: now it’s possible to use the PUSH(array, element) function to insert new elements at the end of an array in order to implement a stack structure. Click here to read the article about PUSH and the other JSON functions. \
POP: now it’s possible to use the POP(array) function to remove the last element of an array in order to implement a stack structure. Click here to read the article about POP and the other JSON functions.\
Trigger HTTP/REST: now the Triggers REST, HTTP, and HTTP File add the invoked path as part of the request information from a pipeline. You can read the articles about each trigger in the following links: REST Trigger HTTP Trigger HTTP File Trigger
digibeectl is an application that not only exposes commands for your pipelines management, but also enables interactions with its respective deployments at each stage in the Digibee Integration Platform. Click here to know more about digibeectl. IMPORTANT: You can request access to the restricted beta program of digibeectl through our chat or with the Customer Success team. If you want to know more about the Beta program click here.
digibeectl is an application that not only exposes commands for your pipelines management, but also enables interactions with its respective deployments at each stage in the Digibee Integration Platform. Click here to know more about digibeectl. IMPORTANT: You can request access to the restricted beta program of digibeectl through our chat or with the Customer Success team. If you want to know more about the Beta program click here.
Trigger HTTP/REST: now the Triggers REST, HTTP, and HTTP File add the invoked path as part of the request information from a pipeline. You can read the articles about each trigger in the following links: REST Trigger HTTP Trigger HTTP File Trigger
PUSH: now it’s possible to use the PUSH(array, element) function to insert new elements at the end of an array in order to implement a stack structure. Click here to read the article about PUSH and the other JSON functions.