Add Universal Processing Notation (UPN) Shape Library

[ehsky]

• I agree to follow the [Code of Conduct](https://github.com/jgraph/drawio/blob/dev/CODE_OF_CONDUCT.md) that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.

draw.io supports many diagramming standards (UML, BPMN, flowcharts, etc.) but lacks support for Universal Process Notation (UPN). UPN is an open, nonproprietary process mapping standard originally developed in the early 2000s and released as an open standard in 2008. It is designed to be simple enough for anyone to use, not just process analysts, and is today supported by and embedded in many enterprise software programs. Teams that use UPN currently have no native shape library in draw.io and must manually construct activity boxes from grouped shapes, which is tedious and produces inconsistent results.

This was previously requested in #1031 but was declined, in part due to the lack of a suitable licensed icon set. This proposal addresses that concern directly: the implementation uses no external icons or image assets. All shapes are rendered programmatically using canvas drawing operations (rectangles, lines, circles, text), so there are no licensing dependencies. Everything is Apache 2.0 compatible.

Describe the solution you'd like

A UPN shape library in the sidebar palette containing:

• Activity Box - A single shape divided into three sections: WHAT (activity description), WHO (responsible resources), and SYSTEM (tools used)
• Flow Lines - Labeled connectors between activities describing WHY the next step occurs
• RASCI role badges - Programmatically rendered visual indicators on resources showing their role (Responsible, Accountable, Supportive, Consulted, Informed)
• Drill-down support - UPN's hierarchical process decomposition can be achieved by using draw.io's built-in link feature on activities to navigate to sub-process pages within the same document

Describe alternatives you've considered

• Using BPMN shapes as a substitute, but BPMN is significantly more complex and doesn't map well to UPN's simplicity
• Building UPN diagrams manually from basic shapes, which works but is slow, inconsistent, and loses semantic meaning
• Distributing a custom library via Extras > Configuration (similar to [drawIo-Salesforce](https://github.com/ehsky/drawIo-Salesforce)), which covers basic shapes but cannot support programmatic features like RASCI badge rendering

Additional context

I have a working implementation ready in my fork that i will link in a bit: https://github.com/ehsky/drawio

All rendering is done programmatically. No external icons, fonts, or image assets are required. Happy to open a PR if there is interest.

UPN references:

• [Universal Process Notation - TechTarget](https://www.techtarget.com/searchcio/definition/Universal-Process-Notation-UPN)
• [What is UPN - Netcall](https://www.netcall.com/blog/what-is-upn/)
• [UPN Quick Start Guide (PDF) - Imperial College London](https://www.imperial.ac.uk/media/imperial-college/administration-and-support-services/operational-excellence/public/Quick-Start-Guide-to-Universal-Process-Notation.pdf)
• [Understanding UPN - Salesforce Trailhead](https://trailhead.salesforce.com/content/learn/modules/business-process-mapping/understand-universal-process-notation)

[draw-io-triage-bot]

👋 Thank you for opening this issue!

---

Summary: The user is requesting the addition of a Universal Process Notation (UPN) shape library to draw.io's sidebar, including activity boxes, flow lines, and RASCI role badges, all rendered programmatically with no external assets. They have a working implementation in a fork and are offering to submit a PR.

---

📝 Additional Information Needed

To help us investigate this more effectively, could you please provide:

• The issue mentions a previous request in Universal Process Notation (UPN) Shapes #1031 that was declined partly due to licensing concerns. Has there been any updated guidance from maintainers on whether a fully programmatic (no external assets) implementation would now be considered acceptable?
• Could you share details on the scope of the implementation in your fork — specifically how many custom stencils/shapes are involved and whether the sidebar integration follows the existing pattern used by other shape libraries (e.g., BPMN, UML)?

---

---

_{🤖 This is an automated response to help with initial triage. A human maintainer will review this issue. If you've provided all the requested information, no further action is needed - we'll get back to you soon!}

[ehsky]

Could not open a PR, but this branch holds the UPN solution. ehsky/drawio (universal-processing-notation)

Thank you for looking into this! 💯