Creating a Task based on a Calculated Field Value

Follow

Carson Young - Red Cliff Labs

• June 12, 2016 23:27

I thought this would be simple, but I can't seem to make it work without using GlobiFlow...

I want to use advanced workflows to create a task if my calculated field returns a value of < 2

I know it can be done with Globiflow, but the organization I'm helping with this doesn't have and doesn't want Globiflow right now. 

 

Does anyone have another way to make this happen?

0

• 

  Rainer Grabowski

  • June 14, 2016 05:22
  • Edited

  Hi Carson,

  you can achieve this with a workaround: 
  
  Create a second calculation field and enter:

  @first calculation field < 2 ? "Trigger task" : null

  Instead of "Trigger Task" you can also write "Hello beautiful day" or "abc" or whatever you want  :)  - the idea is, that something should happen in the second calculation field if the first is > 2 so that the second one changes. This change fires a trigger that can be used in Advanced Workflows.

  Then in Advanced Workflows create a flow: 

  When an item is updated
  and field Second calculation field changes
  create a task.

  Btw: You can't do that with Globiflow directly cause Globiflow can't recognize it when a calculation field changes. You would also need a workaround, e.g.: If calc field changes, Podio Advanced flows create a comment, this comment triggers Gfobiflow to check the item if the value is > 2 and to do something.

  Rainer

   

  2

  Comment actions Permalink
• 

  Carson Young - Red Cliff Labs

  • June 14, 2016 08:33

  Thank you Rainer, 
  
  I figured that was most likely going to be the case, but didn't know exactly how to write the syntax after "@first calculation field < 2"

  You are always very helpful on the forums, thanks!

  Interesting to know that even Globiflow would require a sort of workaround here also.

  Now if only Zapier was compatible with piping info from calculation fields I'd be set....it seems however that I will still be in the position of needing to break in and buy the Globiflow level license soon. Just so unfortunate that it is a 5 seat minimum still!

  I am one of many that knows we want the Globiflow solutions, but too stubborn to pay for that license level when we only need 1 or 2 seats. 

  0

  Comment actions Permalink
• 

  Marcus M. Ubani

  • January 07, 2017 06:40

  Hi Carson,

  you could create a task using webhooks.

  Let me know if this still an issue.

  0

  Comment actions Permalink
• 

  Rainer Grabowski

  • January 07, 2017 10:16

  FWIW: Since several weeks Globiflow is available for Premium licences < 5 seats too.

  0

  Comment actions Permalink
• 

  Priscilla Farran

  • November 13, 2018 00:06

  Hi Rainer, 

  Since Globiflow doesn't recognize when a calculation field changes, any suggestions on how I can get globiflow to copy the number from my calculation field into a regular number field? 

  I am trying to create a view based on this number field in Podio. 

  0

  Comment actions Permalink
• 

  Rainer Grabowski

  • November 14, 2018 11:24

  Hi Priscilla,
  
  you can create a view based on the calculation field too if the calculation field is number type.
  Click the little triangle on the left side of the template brick, if you see a selection for decimals it is number type. 
  
  Also you can trigger Globiflow on calculation field updates with a workaround by using the Podio internal workflows.
  Add a (always hidden) category field with categoriy "Check". Then in Podio Workflows: When item changes -> select the calculation field, then "Update Item here", category field to "Check". 
  Then a flow triggered by a change of the category field (if equal to "Check") - do something. Last action in the flow should be: Update item - category field = Unset.
  The Podio Workflow you find in the app menu (click the wrench in app view).

  Rainer

  0

  Comment actions Permalink

Please sign in to leave a comment.