Personally, I'd strongly recommend just jumping over this and using UML's activity diagrams instead to get all the goodies (most notably an actual language). Even if you won't produce anything other than an activity diagram you at least have a solid starting base and you can extend as you wish down the road.
When it comes to UML: I'm doing that pretty much every day. The single most important thing I can recommend is to use a proper modeller rather than a diagramming software. The spectrum there is pretty wide. On the low-end you have something like StarUML, mid-field is your typical EnterpriseArchitect and on the high end you'll find tools that are outside the reach of most of us such as Rhapsody.
I am not aware of any serious, real-life usable open-source UML modeller.