What does draft mode enable you to do with a flow rule?

Draft mode allows you to work on a flow rule while some of its dependencies may still be in development or not yet fully defined. This feature is particularly useful during the design and testing phases of rule creation when you want to build and refine your flow without having all related components immediately available.

When you save a flow rule in draft mode, it enables you to continue iterating on the design, running simulations, or testing its behavior, even if certain elements it relies on are not yet in place. This flexibility supports an iterative development process, allowing teams to progress efficiently without waiting for all dependencies to be resolved.

In contrast, the other options do not align with the functionalities provided by draft mode. For instance, executing with complete dependencies suggests that everything must be perfectly configured, which is not the case in draft mode. Similarly, saving only a snapshot of the rule implies a lack of ongoing modifications, and making permanent modifications to existing rules contradicts the temporary, iterative nature of working in draft mode. Thus, the capability to save and run a flow rule while still allowing for incomplete dependencies is a defining characteristic of draft mode.