Flowsana News

Hi all!

It’s been several months since I’ve posted any Flowsana updates, so it’s time!

Behind the Scenes

It’s been a pretty quiet couple of months from a features standpoint, as most of the work during this time has been “under the hood”:

  • Fixing bugs
  • Shoring up the infrastructure to allow for stability and future growth
  • Taking care of “special cases” that have come up (as an example, the “Copy subtasks from a template” rule action had to have special code added to support the copying of Sections, Milestones, and Approval tasks – it now supports all of the above)

New Features

I do have two new features to announce, though!

First, the If-Then rule actions of Add Task to Project and Move Task to Project now allow you to define a specific section with that target project where the task will be placed.

Second, in the Forms Support area, Flowsana has allowed you to set a Start and/or Due Date based on a date the user enters. Previously, dates entered were always interpreted as being in the mm/dd/yy format. Of course, if you’re basically anywhere in the world other than the USA (or according to Wikipedia, the Philippines, Palau, Canada, and Micronesia), that’s the wrong format. So now you can specify to have a Form’s user-entered dates interpreted as dd/mm/yy instead.

Coming Attraction

I’m pre-announcing an upcoming change to Flowsana’s billing model that will make it more accurate and more affordable to more users.

Currently organizations are charged for Flowsana based on the number of Asana users in teams that have workflow-enabled projects. The problem is that some of those team users may have nothing to do with those specific workflow-enabled projects. So Flowsana billing will soon be project-based instead of team-based; that is, it’ll be based on the number of users who are members of just those specific projects which are workflow-enabled.

This change should be implemented sometime in the next month; I’ll post more about it here when it happens.