Generate process diagrams

Plans in Power Apps helps teams create and refine diagrams as part of the plan to clarify user interactions and build effective solutions. Process diagrams make workflows clearer, improve communication, and help teams work more efficiently, especially on complex projects.

Optionally, include images of existing process diagrams as additional resources during the creation experience to enhance clarity. But if you add predefined processes, Copilot might just replicate what you provide, which can limit creativity and cause duplication or misinterpretation.

The process diagram appears on the right as you create a plan. The diagram generates after you create user requirements. If you prefer to see a plan overview instead, you can toggle off the process diagram.

Processes use a two level hierarchy.

• Process stages: An overview of the processes needed to address the business problem and user stories.

  

• Process maps: Select View process on a process tile to see detailed steps, events, and decision points for developing a process. Each activity shows the user role responsible for the action.

  

Understand a process

A process has these types of nodes.

1. Events

   • Start: Event that starts the process.
   • Intermediate: Event that happens during the process before it continues.
   • End: Event that signals the process is finished.

2. Gateways

   • Exclusive: At a decision point, the process takes only one path from the gateway.

3. Activities

   • Task: The main action a user or system takes to finish a user story.

Edit a process

The process is an AI-first experience and might not always produce the results you expect. Use natural language to describe the changes you want, or manually edit the process. The AI then reassesses your changes and the overall process to generate a new process map.

Legend:

1. Add step: Add a new step.
2. Add event: Add a new event.
3. Add decision: Add a yes/no decision, run multiple branches at once, or run all matching conditions.
4. Delete: Delete a node. Remove connecting lines by selecting the backspace key.
5. Connect nodes: Add connecting edges between nodes by selecting a node anchor and dragging it to another node.
6. Validate changes: Confirm your changes. Changes aren't finalized or saved with the plan until you validate them. The process experience in plans is an AI-first experience, even when you make manual edits. When you validate changes, the AI reviews and merges them with the existing process. As a best practice, batch three to five manual changes at a time, then validate them. If you want to make more than five changes, try the natural language update first to save time and improve the accuracy of the AI-generated content.

Known limitations

• You can't add events manually.

• The process doesn't directly affect technology proposals.

• You can validate only one set of changes at a time.

• You can't change node types. You can only delete and re-add them.