A workflow definition describes when a record needs a decision and which role can make it. Its record type and amount threshold matter. A purchase-order rule doesn't automatically govern sales orders, and an inactive definition can't route the request.
The local model uses a simple amount threshold and configured approver role. Matching active rules mark a newly created order Pending Approval. An existing eligible order can be explicitly submitted after a rule is installed. This is a narrow teaching model of workflow state, not the complete SuiteFlow designer, identity system or notification engine. Saving a definition is different from approving an individual order. Test the rule with an eligible transaction and inspect its approval state before interpreting a visible action as authority to post.