Ongoing Development of Mega Ultimate Power Galactic Kanban

The main objective with the Kanban I am creating is that it will be VERY GENERIC… being able to use anywhere.

So in the first screen you only see it after first placing the code in the Custom Widget Builder.

when clicking CONFIG you have access to configurations, done in two tabs. This first tab you choose what column you will use to map the Kanban columns

it’s important to notice the Kanban gets the column colors FROM the Options Column you mapped

now let’s customize our cards

No Card (In the Card) means that column will appear in the card.
Usar Formatação means the Widget will access the formatting options of the column (header formatting, cell formatting, options formatting and even conditional formatting)
Card Pos# regulates the order of the fields that will appear in the card… in the card.
Mostrar Label Card means Show Label Card. Disabling it means that instead of Country: Brazil, it will show only “Brazil”

Now for something cool… the configurations are done BY column. But you can replicate the configurations to the next column or to all other columns.

so, continuing… as you can see here, I configured only the first column to use the fields in the card.

but clicking on “Replicar p/ Todas” (Replicate to All), now all columns show the same fields in the cards

now… when clicking on a card, you go to the card editing screen

Oops, there are fields I don´t want shown there, like gristHelper_Display

so… I select first Column of the Kanban (in this case could be any column… order the fields by name and at “Visible Drawer” column I disable the 3. THey are not visible anymore. But first, I will replicate to all Kanban columns.

Now… when the process starts, the first user must insert name, company and group of the employee. But at second column, the task is to add other details. Nobody can change those fields anymore.

SOOOO… they will be visible but blocked to edit.

and… see, Nome Funcionário is blocked to edition

I am still working on this. Several features will be added:
ToDo List
1 - set maximum cards viewed per column
2 - set maximum number of cards per column (indicating an employee or department can´t do more than X of that tasks at the same time)
3 - set responsible PER column. Only someone belonging to group or user itself may move FROM that column to others
4 - option to not allow moving a card more than one column
5 - rules to create new card in another Kanban when moving to a certain column, and make that a child Kanban (a sub process)

6 Likes

here, changed column colors and some field colors too, just to show the Widget is able to get those data

1 Like

added configuration to sort cards by up to 3 different columns

added configuration to show a maximum of cards per column (more cards can be shown by clicking an expand arrow at the bottom of the column)

added a configuration to add MAX number of cards per row, so user can simulate maximum workload.

That means a specific task upon reaching a max workload doesn´t accept new tasks until cards are removed from it

added a configuration to only allow cards to be moved to neighbor columns. Meaning a card can´t jump from TO DO to DONE without passing through the “IN PROGRESS” column (in a 3 columns Kanban)

That is even more important if we are dealing with processes Kanban and workload restrictions.

1 Like

Wow, great! Looking forward to try this out!

Adding table relationships and RULES

you can select a column of the Kanban and create multiple rules for it.

For example, if X field is (operator) Y value, that card is not allow

another rule:
If card enters the column, it creates a new card in X table (you select table and field of relationship)

So for example if a card enters the Column Employee Registered, you can automatically create cards in the column IT Onboarding (with several predefined tasks of creating users on different systems) , cards in the Training Kanban (to be sure employee will have all needed training)

Adding a rule that when selected field is a certain value, a card from that field will move to X field.

So for example, Card is stuck on Employee Registered column until a Grist field that becomes YES when both related “Kanbans” (IT Onboarding and Training) reach their DONE status. When That Grist column becomes YES, the Card automatically moves to next column.

also added options to change column color and card color.

also, I create special ordering based on Priority and Due Date

and changed the REPLICATE configuration. Now you can select to what columns you want to replicate the configurations

I must inform that I am not setting ALL the rules on the Kanban engine. The Kanban engine requires some types of rules to be created on Grist itself for more complex behavior.

Example… showing the data from related Kanbans… you will need to create a column showing that data and set the Kanban to show that date, non editable, either in the Card or Card Editing Drawer.

Or the example I gave… I am creating a rule to create cards on other tables. But the rules that check for data only work with the connected table. So you must BRING the related data to the connected table for the Kanban rule to check it for the rules.

several rules working. For example, moved a card to a specific Kanban column, it creates a card in a specified column of another Kanban (actually, a record in a table with a Status column set to a specific option)
also, now we can set colors of background (including color gradients, in radial and linear format) as well as change font colors.

all fields capture the colors set in Grist

one problem I have and that may require extensive programing is Reference Fields and Choice Fields.

In the screenshot we see the fields Acessórios and Sistemas, which are Choice Fields.

You press Control and Select more than one of the options.

I would prefer something more like Grist.

is your repo on github and can we try it out ?

thank you very much

as mentioned on Discord, I am developing it on the Widget Builder yet. So it’s not online.

I also faced some problems to show attachments… because the attachments are on our internal http server… but the Grist Widgets are on Github. WHich is https.

Trying to show our attachments on our http going through the widget on Github returns error of mixed content

This is neither a restriction of Grist or the widget, but of the insecure way how you host assets internally. GitHub will have very strict XSS and CSRF settings.

You might get better results with hosting the widget yourself, on HTTPS to be able to run on your secure instance but also able to configure insecure XSS/CSRF settings for it and the place that hosts your widget, or to upgrade your internal CDN with a self-signed certificate, eventually from a CA managed with mkcert or step-ca, which could be installed into browsers and systems.