Introducing enhanced dependency management in Kissflow

We are pleased to announce a redesigned dependency experience across Kissflow. Whenever you delete, archive, or move something that other parts of your account rely on, Kissflow now shows you exactly what is connected and only stops you when it truly has to.

What are dependency checks?

When you attempt to delete a field, dataset, workflow step, or archive a flow, Kissflow checks everything that references it and lists the results in a Dependencies dialog, so nothing breaks without you knowing.

What’s new

Blocking and non-blocking dependencies

Dependencies are now separated into two groups, so you can tell at a glance what actually stands in your way:

• Blocking dependencies must be removed before you can proceed.

• Non-blocking dependencies no longer stop you. You can review them and continue with a Permanent data loss warning when you are deleting.

Each entry shows where it is used, what is dependent, and who created it, grouped by the integration, notification, report, analytics table, or flow it belongs to.

Dependencies on process steps

Deleting a workflow step now tells you everything tied to it before anything changes — connected flows and integrations, reports built on the step, Goto branches pointing at it, sequence number fields, and Send back buttons configured on other steps. Items already in the step are never deleted.

Moving a step now runs the same check. Previously, a step could be relocated without any warning about what depended on its position; now you see the same dialog before the move goes through.

 

Check dependencies without deleting anything

You no longer have to attempt a deletion just to find out what a field is connected to. Click a field in the form builder and click the Dependencies button to inspect the full list at any time. This is useful when you plan a change, audit a form, or hand a flow over to someone else.

Your feedback is important to us. Try the new dependency experience and let us know what you think in the comments below.