You’re offline. This is a read only version of the page.
150
I have a document editing workflow that's pretty simple. Somebody submits text, it goes to an editor for copy editing, it goes to a proofreader/final read, and then it gets pushed to the web site.
I suspect I'm missing something about how Business Process Flows work, though. I would imagine that something gets to the editing stage, but is "Ready to get picked up by an editor". The document can be long, and so it might take an hour or two get edited. So when an editor starts to work on it, it would be "Being edited". The same is true for the rest of the flow. For each stage, there's a "Waiting in the Queue" and "Being Actively Worked" component. Should these be separate Stages in the flow? That seems kinda clunky. Should I be using the "Status Reason" field? But that doesn't appear to be Stage dependent. Should I create my own "Status" field with "In Queue" and "In Process" values?
Then a View for an idle editing would be "Items that are in the Editing Stage and are In Queue Status".
I've looked everywhere for examples of this but have not found any. There must be some best practice with BPFs that I'm missing, since I can't imagine that my situation is unique or even unusual.
Any pointers, tutorials, documentation, or sample apps would be greatly appreciated.
P.S. If I'm posting in the wrong forum, please direct me to the right place.
Thanks for the thoughtful answer, Mario. There is no 'right way'. There are lots of tools, and I can build what I want.
Still, always looking for examples and best practices so I'm not reinventing things. Or maybe I will BE the best practice!
It is up to you how you solve this. There are no universal recipes for that. Sketch, design, and analyze all the possibilities. Consider usability, reporting requirements, development complexity, and weak points.
The Business Process Flows generally help users remember to do all required steps of the process or gather mandatory data, before they advance to the next stage. I always think about it as "something that guides users, what they have to do". I don't apply BPFs to all my business processes.
Even though the stages of the process in the BPF are beautifully highlighted on the flow diagram you are not obliged to use them just to track the progress. You can do this just by using the Status Reason field. If you would like to see the diagram you may use an external PCF control (see: Picklist Progressbar PCF or Progress Bar With Stage).
Think about using the additional functionality of the PowerApps - Queues and Queue Items, which allows the creation of containers for records, from where the workers can distribute them freely among other queues and users.
You don't have to rely on the BPF time tracking features, you can create your own mechanisms that fit your needs.
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
17
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
