When you fire up a child workflow in classic workflow, it’s always asynchronous. Fire and forget. Sometimes it’s what you need, sometimes you want to insist on child finishing their greens before the dessert, so to speak. Power Automate, on the other hand, always wants the result when you call a child flow and nags […]
Tip #1252: Creating a Planner task with Flow: wait a minute
If you use Microsoft Planner to plan your project tasks, you may want to automate creation of tasks. You can do this with Microsoft Flow. You will notice that you can’t update fields like the task description when you create a task–this is actually a separate step, called update task details. But if you try […]
Tip #1251: Run workflow when something did not happen
Flow is all the rage these days but there are some scenarios where classic workflow still rules. Classic workflow has the uncanny ability to readjust itself when underlying data you’re waiting for, changes. This dialog took place not so long ago: Steve “Reads his own blog” Mordue: I want to trigger a workflow to update […]
Tip #124: But wait, there is more
Despite of what we said earlier this week, wait can be a very powerful instrument. My fellow tipster Joel suggested in his last tip some fine tuning when it comes to wait: Combine waits and check condition. So you have a process that emails a customer service representative three days after the case is open. […]
Tip #123: Waiting for Godo in CRM workflows
This week’s tips all seem to be about workflows and here is an old favorite of mine. I always found it interesting how non-intuitive wording around Timeout condition pushed majority of developers to use rather convoluted but easier to read and understand Wait conditions when a workflow needs to be paused for a fixed duration. […]
Tip #122: If you must use waiting workflows
In yesterday’s tip we suggested to avoid wait conditions altogether; but if you must use them: Combine waits and check condition. So you have a process that emails a customer service representative three days after the case is open. No need to email them if the case has been closed, right? After the wait, have […]
Tip #121: Don’t use wait conditions
Workflow wait conditions can be very useful. Say you need to have an email go to a customer 30 days prior to their contract renewal, it can be tempting to use a wait condition. However, excessive use of wait conditions has a downside. Performance: each waiting workflow instance carries performance overhead. The more waiting workflow […]