Which statements about draft flows are NOT correct?

In the context of Pega Rules Process Commander, it is important to understand the nature of draft flows and how they function in the development environment.

A draft flow serves as a working version where developers can make incremental changes without immediate verification against existing rules. When discussing the accuracy of the provided options, it's notable that the assertion regarding the restriction that a flow shape cannot reference a rule that does not exist is indeed not correct. In a draft flow scenario, there are no restrictions preventing the reference of non-existent rules. This flexibility allows developers to design and plan flows without being hindered by the need for every rule to be previously created or verified, making it easier to prototype workflows.

On the other hand, when saving a draft flow, the system allows for the absence of checks on rule existence, supporting the iterative development process. Additionally, draft flows can indeed create work items, as they serve as preliminary versions leading to actual cases and tasks within an application. It’s also important to note that a starting flow can be saved as a draft, providing further flexibility during the development phase.

Understanding these aspects emphasizes the nature of draft flows as tools for rapid development and experimentation, as opposed to finalized flows where such references might be strictly enforced.