Linter - Pipeline building validation (Beta)
Know more about the functionality to validate pipeline building.
IMPORTANT: Currently, this functionality is only available in Beta phase. To learn more about this, read the article Beta program.
The New Canvas displays alerts during pipeline building, helping developers identify and fix common issues faster.
For each component that encounters a problem during pipeline building, Canvas displays an alert with details and information. Many of the checks serve as warnings and do not require corrections or interfere with the building of your pipeline.
Issues validated during pipeline building are divided into Errors and Warnings. This division of alerts helps the developer understand the extent of the problem indicated by Canvas.
Error alerts indicate serious failures in pipeline building. They must be corrected or it will not be possible to save the project.
Today, Canvas has errors in the following category:
- Structure: structural errors that prevent the integration flow to be processed.
Warning alerts indicate improvement points in pipeline construction.
Today, Canvas displays warnings in the following category:
- Best practices: Construction habits that can make your pipeline function better and facilitate future maintenance and improvements.
For each issue encountered during pipeline building, an issue is displayed in a list. It displays the issues divided according to the categories listed above. It also contains the name of the component that presents the issue and a description of the issue.
From the issues list, it is also possible to temporarily hide pipeline alerts, easily navigate to the problem on Canvas by clicking on the issue, and edit components’ configuration forms.
To open the list, click the 
button on the left toolbar on Canvas.
All New Canvas checks contain information that will help you fix the problem. Hover over the ⚠ icon to view the information. This way, you can read them and evaluate each suggestion in your pipeline.
This page lists all possible alerts developed so far. They contain details and information on how to fix and improve your pipeline.
Choice allows conditional branching within a pipeline. To use this component correctly, you must configure its 'when' conditions. Each 'when' condition branches the flow into a specific path. You must have at least 1 when condition configured.
Therefore, define at least one when condition to avoid interrupting the pipeline flow.
Choice allows conditional branching within a pipeline. To use this component correctly, it is necessary to configure its 'otherwise' condition rule. The otherwise condition is executed when none of the when conditions are met. You must have 1 otherwise condition configured.
Therefore, define the otherwise condition to be executed if none of the when conditions are true.
The following issues refer to the components that allow structuring subpipelines, i.e., subflows of the pipeline. Subpipelines are structured around the following components:
The onProcess defines one of the subflows of the pipeline. Structure and connect the onProcess subpipeline so that the pipeline flow is not interrupted.
The onException is the subpipeline whose job is to handle an exception in the onProcess execution. Structure and wire the onException subflow so that the flow of the pipeline is not interrupted.
The onProcess defines one of the subflows of the pipeline. Review the onProcess subpipeline issues to continue creating your pipeline.
The onException is the subpipeline whose job is to handle an exception in the onProcess execution. Review the onException subflow issues to continue creating your pipeline.
Parallel allows you to configure parallel executions within the pipeline flow. Connect Parallel to another component to prevent the flow from stopping.
Note: Parallel must always be followed by another component for the flow to run.
Parallel allows you to configure parallel executions within the pipeline flow. As a best practice, we recommend that you use Parallel only when you need to make two or more executions at the same time.
The trigger defines how to start the execution of the pipeline. To configure the trigger, select one of the options from those offered by the Digibee Integration Platform. Next, connect it to the beginning of the flow to deploy the pipeline later. For more information, access the triggers documentation.
Note: You can save the pipeline without configuring the trigger. However, you will not be able to deploy it.
The version of the component you are trying to use has been deprecated. This means that a new, improved version is available to be used.
Note: The deprecated version of the component can still be used. However, it is important to note that increments and improvements are made only in its latest version.
The Capsule you are trying to use does not exist on the realm you are working on. You must delete it or replace it with another connector, flow, or a Capsule that is available in this realm.
The field cannot be used (GET operation) because it was not previously declared (PUT operation).
The field was previously declared (PUT operation) but is not being used.
Configure a new Session Management component to use (GET operation) or delete (DELETE operation) the previously declared field.
Last modified 1mo ago