Different flowchart shapes using an extra field

I’m consulting for a company in the capacity of process planning and process documentation. Flowcharts is one of the first tools I am using. I decided to try out Airtable in hope for future flexibility instead of using the usual Visio, lucid, StarUML, etc.

I immediately ran into

  1. the problem of not being able to select different shapes for different records (Diamond=decision, rectangle=process, etc).
  2. General lack of flexibility for the view because it is either all vertical or all horizontal.
  3. ABC flowcharting is connecting processes using their predecessors not their successors. (it is more important to know that A needs to be done before B in order to begin B, rather than what comes after A. Well everything comes after A). I’m working around this right now, but would be nice to see the change.
    4)100 record limit.

I ordered the above in terms of importance for my case.

Thank you :slight_smile:

P.S. I reported a bug the other day when exporting the flowchart to SVG or PNG, when I use the ‘<’ sign in one of the attributes.

1 Like

Have you looked at Vega-Lite?

Yes. I don’t see how flowcharts can be built using Vega-Lite though, if at all possible.

Indeed, it’s not obvious and it’s certainly not easy. Furthermore, I’ve not actually tried to use the Vega0Lite block to build a flowchart. Telling others that it may be possible is really easy though. :wink:

However…

If something custom (like this) is possible in Vega-Lite, a very custom flowchart is a close cousin to this example. Bear in mind that while this example is shown in the Vega editor, I don’t think it uses any grammars beyond that which is supported by Vega-Lite.

There’s no doubt that the Vega block is likely less than a coin flip probability to solve your requirements. But the chart block is zero percent probability to address the requirements.

Airtable is not known for its state machine capabilities. Despite the claims as a workflow tool, there really isn’t much under the hood to address the rigors of business process automation; it all has to be built.

I’m unfamiliar with this limit. Please enlighten me.