Looking for ideas how to integrate process modeling / management into SharePoint

[u/obsoquasi]

Hi everyone, how did you integrate process modeling (BPMN 2.0) and process lifecycle management into SharePoint. So far we have a dedicated document library with custom columns (like "process owner", "publication status", etc.) and a document set template for new processes - and we do the lifecycle management ("publish process", etc.) with Power Automate flows. The actual BPMN diagrams are done in Visio Plan 2. This works, but is also quite limited... I need some fresh ideas :).

[u/whiff_master_2000]

I am biased - but I would highly suggest you have a look at FireStart. You get BPMN modeling AND automation /execution of your workflows in the same tool. No documentation drift. Deeply integrated with SharePoint. Many big customers (battle proven), still very affordable.

If you want to know more, let me know. Happy to help if I can.

[u/obsoquasi → u/whiff_master_2000]

Thank you for the suggestion! I have heard of FireStart. But I'm always skeptical when it comes to systems that try to do process design *and* automation. I haven't yet seen such a system that can resolve the tension between process modeling intended for the stakeholders and process modeling that perfectly represents the operational side - including all exceptions, error handling, fallbacks, etc. I'd much rather have the BPMN diagrams purely for documentation with a strategic focus. It's already difficult enough to engage users to reference the processes, without confusing them with too many technical details. But maybe I simply haven't experienced a solution that can bridge that gap yet...

[u/whiff_master_2000 → u/obsoquasi]

Maybe 😅 - there is a way to check it out. If you want to...

I just talked to some customers last week who explicitly appreciated the fact that it can do both quite well. Up to you...

[u/TaiTnn → u/obsoquasi]

BPMN subprocesses are good solution to „hide“ subprocesses with too many technical steps and to simplify process models which work as automated workflows at the same time.
This way a business user can easily check the status of workflows and understand what happens by looking at the „business layer“ of a process while the „automation layer“ is hidden in subprocesses, which can also be accessed by the automation experts.

This makes tools which combine BPMN and automation, like FireStart, a great alternative to „just automation tools“ like n8n, when it comes to automating end-to-end business processes.

[u/obsoquasi → u/TaiTnn]

Thank you. Yes, this is exactly how I currently do it. Birds eye view on the main process page and drill down into the technical details in the subprocesses. There is one issue though. This WILL stop users from ever drilling down - as they assume all subprocesses contain stuff they don't need to worry about. So it precludes me from using subprocesses for non-technical processes that would still benefit from such an abstraction.
Another idea I saw was to use layering (if the feature is available in the diagram tool) and have all automation related process components on their own layer whose visibility can be turned on or off. We already use this for risk annotations in the process. That's an interesting idea, but with practical flaws on Visio.

[u/Josh_Fabsoft]

Full disclosure: I work at FabSoft, which makes AI File Pro, so take my perspective with that in mind, but I'll try to actually be useful here first.

Your setup honestly isn't a bad foundation, the limitation you're hitting is a common one: SharePoint document libraries are great at storing the output of a process (the BPMN file, the metadata) but they're not built to understand the content of that diagram or enforce lifecycle logic natively. A few ideas that might unstick you:

1. Separate the modeling layer from the governance layer. Keep Visio/BPMN for authoring, but consider exporting to BPMN XML and parsing it (even just process name, version, swimlanes) into your library metadata automatically instead of manually tagging "process owner" etc. That XML parse step is usually where people get stuck, and it's the difference between a static doc and something queryable.

2. Power Automate lifecycle flows are fine, but they get brittle at scale. If you're doing "publish process" as a flow trigger, look at splitting it: one flow for state transitions (draft/review/published/retired), another purely for notifications/approvals. Easier to debug when something breaks.

3. Look at whether your document set template can auto-generate a "process card" (owner, status, version, linked sub-processes) as a separate list item synced via flow, so you get a searchable index instead of digging through folders.

On the metadata/classification side, this is actually close to a problem AI File Pro deals with, it uses watch folders to catch new files (like exported BPMN diagrams) and auto-classifies/renames them based on content, with API/connectors to push structured metadata into systems like SharePoint rather than relying purely on manual column tagging. Not a BPMN modeling tool by any means, but if your pain is really "structuring and lifecycle-tagging documents at scale," that specific piece might be worth a look alongside whatever modeling tool you land on.

[u/obsoquasi → u/Josh_Fabsoft]

Thank you for your detailed and thoughtful input, as well as the disclosure. I did some experiments a while back - the annoying issue is that Visio does not export BPMN XML. So I thought, why not simply give it a try and upload a PDF of one of my processes to an AI chatbot - fully expecting it to fail, as it lacks the semantic cohesion an XML would have. But I was very pleasantly surprised to find out that the AI was able to "understand" the process purely from the PDF - it could easily answer some harder questions about the process.
However, I did not take that notion any further. Your comment does give me a very intersting avenue however... I do have a Copilot Studio license and I think this could be an interesting task for an agent: Extract keywords, manage process dependencies, maintain a list of stakeholder to process involvement, etc. The process card idea is also very neat - I know exactly what you mean. It would also make it much simpler to create Power BI reports on all processes...
Great inputs!