Database

The Board component is a powerful tool for organizing and visualizing workflows in a Kanban-style format, allowing you to move cards between different stages. This component is ideal for task management, project management, process workflows, or even CRM. It provides a clear and organized view of the status of items in each phase of the process.

2. How to Configure

Drag to Screen: Drag the Board component to the screen where you want to display the Kanban.

Configure the View: Set up the View using SQL or Table View to populate the cards and stages of the Board.

3. Personalize (if you are using a SQL View)

In the Personalize configuration, if you chose to use a SQL View, follow these steps:

Cards Table: Specify the table used to generate the cards, such as "Negotiations" in a CRM.
ID Column: Select the View column containing the card IDs, essential for uniquely identifying each card within the Board.
Description Column: Define which View column will provide the card description. This description will be the primary text displayed on the component.
Stages Table: Specify the table defining the Kanban stages. For example, in a CRM, the stages might include "Lead," "Demo," "Proof of Concept," "Negotiation," "Forecast," "Closed Won." For task management, the stages could be "Pending," "To Do," "Done," etc.
Stage Column: Select the View column containing the FK ID representing the stages. Your View must return at least the table ID generating the cards, the card description, and the FK ID defining the stages.
Visible Stages:
- Fixed: Manually select the stages you want to display on the Board.
- SQL: Use SQL to return the ID and description of the stages, allowing the card phases to be dynamically constructed.

4. Personalize (if you are using a Table View)

If you set up the Board using a Table View, Mitra already recognizes the table and its relationship with the column holding the stages. In this case, you only need to define:

Stages Table: Select the table that will define the Kanban stages, as in the SQL configuration.
Visible Stages:
- Fixed: Manually select the stages you want to display on the Board.
- SQL: Use SQL to determine which stages will be visible, allowing the card phases to be defined dynamically.
Use First Data as Title: If you prefer the card title to be based on a column from your View instead of the axis description, activate this option. For example, in a CRM, you might use the prospect's name instead of the negotiation number.

Additional General Settings:

Card Movement: Enable or disable moving cards between stages.
Search: Enable the search option to allow users to quickly locate specific cards.

Design: Customize the Board design by adjusting font color and size, column width, and other aesthetic options.

5. Tags

You can add tags to your cards to categorize or visually mark them. To do this, concatenate the attribute name with the hex color hash (Hot#FF5733 for "Hot" in red). These tags will be displayed in color, facilitating visual identification.

Note: If you have questions about the algorithms used or the View configuration, consult the "Table View" documentation, which details the process of building and personalizing table views.

6. Movement Control

You can control which stages cards are allowed to move to and from. This configuration is made within the settings of each stage. By clicking the three dots on a stage, you can define these movement rules.

7. Interactions

The Board supports various interactions, including:

Action: Define a specific action to execute when interacting with a card.
Database Action: Perform data manipulation operations such as INSERT, UPDATE, DELETE, or calling PROCEDURES.
Form: Open a form when interacting with a card.
Details Modal: Open a details modal when interacting with a card.

Different Detail Modals by Phase: Enter the configuration of each phase to define a specific detail modal for that phase. For example, Phase 1 can have Detail Modal 1, while Phase 2 can have Detail Modal 2.