-
-
Implement a payment form in Podio using Globiflow and Jotform
-
Trigger Workflows when tasks are completed
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Triggering Workflows when Tasks are completed in Podio
Although a dedicated tasks app in Podio is a good thing, there are still situations where Podio’s native tasks are preferable because they’re quick and centrally located.
In this example, we’ll look at the process after a website project goes live. When a project is complete, we generally have 4 tasks that need to completed:
- Manager to approve the completion of the project.
- Accounting to invoice for the remaining project cost.
- Design to add the project to our portfolio.
- Marketing to submit a press release.
BUT: Tasks 2, 3 and 4 can only be done AFTER task 1 is completed, and task 4 can only be done after task 3 is completed.
Task Completion Flows
Our first Flow will trigger on a status change in the project when it’s marked as complete, and assign the first task.
Our second Flow will trigger on Task Completion and will check the name of the task that got completed. We can actually use this one Flow to assign all remaining tasks depending on the task that just got completed.
To summarize the above logic, the Flow states:
- If a Task was completed and had approve in the title, assign the invoicing and portfolio tasks.
- If a Task was completed and had portfolio in the title, assign the press task.
And that’s it. Tasks will now be created conditionally in sequence. Here’s a simple screenshot animation to show this:
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.