Variable Substitution in Flowsana

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 can I use?

You can include any of the following phrases:

      {task.Custom field name}
      {task.Name}
      {task.StartDate}
      {task.DueDate}
      {task.CompletionDate}
      {task.CreationDate}
      {CurrentDate}

      {project.Name}       
      {section.Name}

      {task.ShortId}
      {task.ShortLink}

and Flowsana will replace the phrases with the value specified that's relevant for the current task being evaluated.

Additionally, for any of the {task. } phrases, you can specify {parent. } or {topParent. } to pull the value from a subtask's parent or topmost parent task. See below for details.


Where can I use these phrases in Flowsana Rules?

You can use these special phrases in the following places:
      The  If task contains the word or phrase ______  rule condition
      The  Set custom field ______ to the value ______  rule action
      The  Set task name to ______  rule action
      The  Create a project from a template  rule action, in the  Name for the new project  field
      The  Send an email notification  rule action, in the  Email Message Subject and/or Email Message Text fields (see the instructions for the equivalent fields in Forms Support for details)


Where can I use these phrases in Forms Support?

In Flowsana's Forms Support workflow, you can use variable substitution in the Send email confirmation to form submitter feature. You can include variables in the Email Message Subject and/or Email Message Text fields.


How can I make use of these phrases in Rules?

Here are some examples:

Say you want to prepend the name of the project to the front of every task in the project. Just create this rule:
      If task is newly created, set the task’s name to  {project.name} - {task.name}

Another example: say you want to add certain emojis to the start of a task’s name when the task enters into a particular state. Here are some examples of what you can do with this type of rule:
      If task is marked complete, set the task’s name to    {task.Name}
      If a task has custom field  Status  set to a value of  Waiting , set the task’s name to    {task.Name}

Let's say you're using the rule action  Create a new project from a template...  and you have a custom field called  Client Name  and you want that client's name to be part of the name of the new project you're creating. You can do that by using the text  {task.Client Name}  in the  Name for the new project  field; for example:
      {task.Client Name} Marketing Engagement


How can I make use of these phrases in Forms Support?

You can include variables in the Email Message Subject field. For example, you could define your subject like this:

That definition would yield an email message subject something like this:



You can also include variables in the Email Message Text field. For example, let's say in the form's Settings you set the title of the task to be the form's Name field:


Let's also say you have a drop-down list form field which is mapped to a drop-down list custom field named "Environment":


You can then use variables in the message text; for example:


That definition would yield an email message body something like this:



Using {task.ShortId} and {task.ShortLink}
For detailed instructions on these replacement values, please see this KB article: Creating Unique Task Short IDs and Short Links


Using {parent. } and {topParent. }
For subtasks, you can pull values from its immediate parent or topmost parent task, For example, you can specify phases like:

      {parent.Priority}
      Pull the Priority custom field from the task's parent task.

      {topParent.Name}
      Pull the name of the topmost parent task.

Using {topParent. } is only relevant where you have multiple level of subtasks and always want to pull a value from the top-level task, no matter how many levels there are. Note, though, that Asana only inherits custom fields for one subtask level down from a task attached to a project.


Date formatting
For the date phrases, Flowsana provides the ability to customize the format of the date.

By default, dates will be formatted into a format of mm/dd/yyyy, with a separator character of a slash (/) between the portions of the date. However, you can specify that you want a date in one of two alternate formats, dd/mm/yyyy and yyyy/mm/dd. In addition, you can specify the separator character that you'd like to use between the portions of the date (or no separator).

Tp specify an alternate format and/or alternate separator, format your date phrase like this:

      {[desiredDate],[format][separator]}

[desiredDate] is the name of the date field you want to replace with.

[format] is one of three allowable format letters:
      M for mm/dd/yyyy
      D for dd/mm/yyyy
      Y for yyyy/mm/dd

[separator] is the separator character you want to use. You can also omit this character for no separator.

Here are some examples:

      {task.dueDate, D/}
      Replace with the task's due date, using a format of dd/mm/yyyy

      {task.completionDate, M-}
      Replace with the task's completion date, using a format of mm-dd-yyyy

      {task.CreationDate, Y}
      Replace with the task's creation date, using a format of yyyymmdd

    • Related Articles

    • 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. ...
    • 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 ...