Introduction to Flowsana

Introduction to Flowsana

Flowsana consists of five different types of workflows that you can apply to any of your projects.

Each type of workflow has its own section here in the Knowledgebase with information on how it operates.  Please see those sections for more details.


Auto-Adjust DueDate-Based Workflow

This type of workflow is simple: If you change the Due Date of a task in the project, and that task has dependent tasks, the Start and Due Dates of all of those dependent tasks will be automatically shifted the same number of days that you moved the initial task.


Dynamic Duration-Based Workflow

This type of workflow lets you have projects where rather than setting specific Due Dates on tasks, you instead set a duration for each task, defining how long it will take to complete each task.  You can optionally also set a lag time for a task; this indicates there should be a delay between the end of a previous dependency task and the start of the task which depends on the previous task.

You then set a Start Date for the overall project.  When you do, Flowsana automatically sets the Start Dates and Due Dates for all tasks in the project.  You can also set or change a Start Date for a particular task, and Flowsana will adjust the Start and Due Dates for all of its dependent tasks.


Rule Workflow

This type of workflow is comprised of a Condition and an Action, otherwise known as an IF-THEN RULE.  This allows you to automate a large number of behaviors on your Asana tasks, such as moving them, associating tags, setting custom fields, assigning to users, etc.


Forms Support

This type of workflow adds additional capabilities to your Asana forms. You can set the start and/or due date of the task resulting from the form submission, and you can make these dates relative to the form submission date or a date the user enters on the form. You can also set the task's assignee, either to a specific user or based on a field on the form. You can have the form's submitter be automatically added as a Collaborator. Finally, you can have an email confirmation be sent to the form's submitter, and you can customize the subject and body of that email.


Hashtag Automation

This type of workflow allows you to specify a due date, an assignee, a section, tags, and additional projects just by typing the appropriate hashtag anywhere in the body of the task's description.


NOTE:
A given project can be put under either an Auto-Adjust DueDate-Based Workflow or a Dynamic Duration-Based Workflow, but not both. Any project can have any number of Rule Workflows and can have Hashtag Automation and/or Forms Support active on it, regardless of whether or not it has an Auto-Adjust DueDate-Based Workflow or a Dynamic Duration-Based Workflow.

    • Related Articles

    • Variable Substitution in Flowsana

      In certain rule conditions and actions, and in Forms Support, Flowsana lets you insert values from custom fields, as well as task, project, and section names. To do this, you include a special phrase, surrounded by curly braces, What special phrases ...
    • How does Flowsana's pricing work?

      Flowsana's pricing works based on the concept of Billable Users. A Billable User is an Asana user who's a member of a team having workflow-enabled projects. Flowsana charges at $2.99/month USD per Billable User. Say you have a Marketing team which ...
    • My recurring tasks are not being handled properly by Flowsana

      Unfortunately Flowsana is not able to support recurring tasks, because the Asana programming interface does not provide any data about task recurrences to external integrations. So Flowsana has no way of knowing that a task is a recurring task and ...
    • How do we handle multiple Flowsana users in an organization?

      Multiple users can be handled in two ways; choose the best fit for your scenario. One option is to create one Flowsana account and share the login among multiple users. In this case, you'll have one list of workflows among the multiple Flowsana ...
    • What happens if an organization or workspace is shared among multiple Flowsana user accounts?

      The basic rule is that only one Flowsana account is ever charged for a given Asana team or workspace. By default, the account that gets charged is the first user that signs up for Flowsana which includes that team or workspace.  However, this default ...