![]() Often when we are in flow, there is a goal we’re working towards but in creative forms of flow, the end goal is often unknown, and there isn’t always a sense of control. I have a ton more research to do, but I did find this article super interesting - especially the part about having an objective or clear goal. What I’m most interested in is creative flow. There are clear indicators for when it’s happening, and also ‘rules’ for what needs to be in place for a flow state to take hold. ( My words! From experience!) Most of us have felt this - we slip so deep in-the-zone that we forget to eat, time disappears, and the process unfolds seamlessly as if the task were solving itself. Hari begins with the background of Mihaly Csikszentmihalyi who coined the term ‘Flow State’ after witnessing painters (and later adults who took part in other activities - rock climbing, music, chess) become so entranced in the process - so immersed that they almost became the task. The book is unsettling and relatable, and the second chapter really hit home for me as an artist: The Crippling of Our Flow States. You can now find the State Machine template in Microsoft Flow.This pause is timely as I’m currently reading Stolen Focus by Johann Hari (thanks Matt!) The book shares 12 causes behind our inability to focus, due largely to tech companies, but also surprising ones like our degradation of sustained reading. By creating a separate branch for each of the approvals you can see in the flow run history what happened with the invoice throughout its life within your organisation. Traditionally this could end up in a spaghetti alike process where you don’t know how many times each person will review the invoice. After my post earlier this week about invoices handling I might as well take that as an example.Īn invoice is approved by multiple people.Īs the process is approved or rejected by the different people you might have to switch between people. Each approval stage could have its own branch within the state machine. Imagine if you had a process that requires multiple people to review and approve a document. You can see the different phases of each process simply by stepping through the do until. So you would likely have some conditions around the setting of the status variable. Imagine if the next phase depends on the value of a variable or the status of the process or maybe if a document was approved or rejected. In real processes you might have to make slight adjustments here. Each scope box is followed by a state change. this is where you can add the actions that are needed in the process. Within each phase of the process I’ve added a scope box. If at any time you want to terminate the flow you could simply set the status variable to Completed or Completing and the flow will end. Anything that needs to be done before the end of the flow needs to be done within the Completing phase. The completed status will not do anything. In my case I’m using the following 4 status values:ĭid I make a mistake? Only 3 status values in the switch. Then the switch includes a value for the status field for each phase of the process. Do you remember the status fields on your libraries? You could also create a document with a status field but why would you want to pollute your document libraries with status fields. This is controlled by a variable called status. ![]() ![]() The flow is going to run until it is completed. Feel free to extend the flow once you used this template by added more status values. In business processes you might need more phases, but for simplicity reasons I’ve only created 3 phases. Once uploaded the document will go through 3 phases. I only want to run one process for each document that is uploaded to a SharePoint library. In this post I will explain how the new template works. In this post however I will move the process control inside the flow and I will only start my flow process once. My previous posts about state machines focused on running a flow multiple times and handling the multiple runs of the process. There is actually a second template that is useful when you create a new flow. Last week I was wrong when I said You only need one template to get started. By Pieter Veenstra State Machines in Microsoft Flow
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |