Business Process Mapping12% of the exam
Governing process maps in a versioned repository
Why approved process maps belong in one version-controlled, web-published repository with diagram-level history, view and edit rights, named owners and a sign-off cycle, and how that repository controls scope, links implementation and operational assets, and supports regulated processes.
Document business processes in a version controlled repository to manage scope.
~7 min read · 8 practice questions ·
What the exam expects
- Replace emailed or locally stored diagrams with one version-controlled, web-published repository that keeps change history at the diagram level.
- Set access rights so that viewing and editing are controlled separately.
- Put governance on an agreed future-state process: versioning, sign-off, named content ownership and a defined change mechanism.
- Route a new request against the approved version through the change mechanism instead of editing, refusing or bypassing the map.
- Link implementation and operational assets to diagrams, make regulated processes specific and versioned, and align maps with company terminology and brand for adoption.
Key terms:
- Version control (diagram level): each diagram keeps its own versions and history of changes.
- Access rights: settings that determine who can view and who can edit a diagram.
- Governance: the release cycle, sign-off, ownership and change mechanism around a map.
- Baseline: the approved version of a process that new requests are compared against.
- Implementation and operational assets: project material (requirements, stories, metadata) and run-the-business material (SOPs, help, metrics) linked to steps.
Key facts
Version control level
- Detail
- Process maps are version controlled at a diagram level
Change cadence
- Detail
- Lower-level diagrams change more often; major innovation is top down
View and edit
- Detail
- Access rights determine who can view and edit a diagram
Tool features for scope
- Detail
- Security and versioning; publishing and sharing
Best for publishing
- Detail
- A web-based tool is ideal for sharing and publishing
Governance
- Detail
- Release cycle with versioning; someone signs off each diagram
Governance questions
- Detail
- Change mechanism, content owner, business champion
Linked assets
- Detail
- Implementation (requirements, stories, metadata, ERDs) and operational (SOPs, help, metrics)
Regulated processes
- Detail
- Very specific and version controlled to prove consistent use
Adoption
- Detail
- Match brand standards and existing terminology
Sources for this section (5)
- Mapping Languagetrailhead.salesforce.com (opens in a new tab)
- Understand UPNtrailhead.salesforce.com (opens in a new tab)
- Mapping Toolstrailhead.salesforce.com (opens in a new tab)
- Create a Process Maptrailhead.salesforce.com (opens in a new tab)
- Mapping in Practicetrailhead.salesforce.com (opens in a new tab)
- Why is change history kept at the diagram level rather than for the whole map?
- Which two tool capabilities protect a process asset and help it reach the business?
- What three governance questions should be answered for a process map?
- When must a process map be very specific and version controlled?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams