Dependencies of (custom) flow parts

When opening a (custom) flow part, it would be ideal if you can see the user flows in which the flow part is used.

Bonus feat: you can’t delete a custom flow part when the number of dependencies > 0

Hi @ronald,

Thanks for your feature request. We have a slightly different idea how to get the same result; let me explain a little bit about our design philosophy, to make it clear.

Allowing the deletion of items
First of all, allowing the deletion of any used item (data item property, flow part, user flow, etc) that is used in the design is actually a very conscious decision. It is much easier to not allow the deletion, from a technical perspective. So why don’t we do that?

When you are making changes to a design, you are working with a certain mental model of what you want to change. If you then are forced to go from, for example, the flow part to the user flow to remove it, it is easier to lose your train of thought. This is why we decided to build the harder solution and allow you to delete it, and show that missing item as a “red dot” indication.

We believe this is actually one of the killer features when it comes to making Triggre easy to use.

Tracing items
What you are asking, if I understand correctly, is that you want to know where an item is used. This falls into 2 categories: items that are not used, and items that are used (somewhere, or in multiple places).

Items that are not used
We are contemplating marking items that are not used anywhere in the design. Much like we now highlight items that have an inconsistency/error. This feature is on our backlog in this way.

Items that are used in one or multiple places
One of our main design philosophies is that we want to minimize the number of buttons at all times, so it is easier to choose the right option. This means that showing a lot more extra info, such as where a flow part is used for example, will create a lot of distraction. Distraction that you don’t use 99% of the time.

Also, we tend to want to limit the number of concepts in Triggre, and re-use the same concept for multiple goals. A good example is the rule editor, which looks and works the same whether it is to look up data, make a decision or show data on a page.

So how do we then intend to handle your idea?

Tracing the Triggre way
We have an idea to build a ‘trace’ function, which will actually use the same concept as the inconsistency functionality (the red dots). The idea is that you can select an item (a data item, data item property, flow part, etc) and ‘trace’ it. This will mark all occurrences of the item in your design, for example with the color purple.

You can then easily follow the purple dots to find the occurrence of the item that you are tracing. We feel that this is a much simpler solution in terms of visually distraction, since it will only take a single button to enable/disable tracing of an item.

Hope this sheds a bit of light into how we think about Triggre, adding features and how we keep the designer as simple to use as we possibly can, while at the same time extending the capabilities.

1 Like

Hi @Jesse ,

Thanks for this thorough response! It certainly sheds a lot of light on the philosophy behind Triggre.

Looking forward to the tracing feature!

1 Like