Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Drawio
simple0
zoom1
inComment0
custContentId1957891415
pageId903774217
diagramDisplayNameAccount map list.drawio
lbox1
contentVer1
revision8
baseUrlhttps://tspcinc.atlassian.net/wiki
diagramNameAccount map list.drawio
pCenter0
width700.1199999999999
links
tbstyle
height179.61

  1.  Access to Account and Opportunity level map list related to the Account 

  2. + Add - Creates a new Account level Relationship Map
  3. Access to Organigram
  4. Clears filters, toggles to full screen or exports list as XLS
  5. Refreshes the map list
  6. Click on the column header object (Name, Primary,..) to rearrange the data
  7. Applies Filters -  set, apply or clear filters
  8. Shows number of Stakeholders in the map
  9. Edits map name and sets map as Primary or Deployed
  10. Deletes the map

...

Drawio
simple0
zoom1
inComment0
custContentId1967915032
pageId903774217
diagramDisplayNameOpp list.drawio
lbox1
contentVer1
revision8
baseUrlhttps://tspcinc.atlassian.net/wiki
diagramNameOpp list.drawio
pCenter0
width709.9099999999999
links
tbstyle
height208.20000000000005

  1. + Add  Add a contact to the Opportunity Stakeholder List
  2. Display the map for drag and drop functionality
  3. Import Data or Delete All Records
  4. Shows % progress of Stakeholders Role Goals 
  5. # of Economic Buyers present / goal
  6. # of Procurement Stakeholders present / goal
  7. Click on the column header object (Name, Reports To, etc..) to rearrange the data
  8. Click on Name to open Stakeholder Overview
  9. Inline editing for key attributes
  10. Edit Stakeholder
  11. Delete Stakeholder

...

  • Click + Add button
  • Enter map Name, select Primary or Deployed and Save.
    • Primary: Makes the map the Account's primary map. Each account may have only one primary map.
         Note: Selecting Primary will override the current primary map. Primary map cannot be imported into other map or added as Submap.
    • Deployed: Makes the map generally available.
         Note:  Deployed maps can be imported into other map or added as a Submap to other maps.
  • Click the Save button. 
    • You will be redirected to the mapping tool once the record is saved.

...

Stakeholder Layout & Navigation 

The following describes the relevant components and related navigation. 

Drawio
simple0
zoom1
inComment0
custContentId1967620191
pageId903774217
diagramDisplayNameStakeholder layout.xml
lbox1
contentVer1
revision4
baseUrlhttps://tspcinc.atlassian.net/wiki
diagramNameStakeholder layout.xml
pCenter0
width599.65
links
tbstyle
height641

  1. Contact Photo - Upload/change/delete a photo or url link.
  2. Stakeholder Name - Opens a new window with contact information.
  3. Title - Title
  4. Company - Account Name / Company Name
  5. Address - Opens the location in google maps.
  6. Role - Indicates the Stakeholder's role in the buying process.
  7. Relationship - Indicates the depth of the relationship.
  8. Decision Status - Indicates the Stakeholder's status in the decision making process.
  9. Support Status - Indicates the depth of relationships between Stakeholders.
  10. Detail Tab - Display Stakeholder information.
  11. Actions Tab - Add tasks
  12. Notes Tab - Add relevant notes about the Stakeholder.
  13. Covered By - Indicates the person from your organization responsible for this stakeholder.
    Note: The 'Covered By' tab is only visible on Opportunity level Relationship Maps. If this field is not displayed, it has been disabled in the Admin Settings.
  14. Contacts - Key Stakeholder contact attributes.
  15. About Stakeholder - Provides an overview of the Stakeholder, including goals and background.
  16. Additional Contact Fields - Displays additional Stakeholder attributes provided by your organization.
  17. Edit - Edit Stakeholder information.
  18. Delete - Delete Stakeholder. 

...

  • Hide or discplay existing Lines and Flags

    • Hiding or displaying existing Lines and Flags is done from the main relationships map page.

    • Click the  icon on the right side of the Map surface

    • Toggle to display or hide lines or flags

      • Note: Deselecting individual flags from the Stakeholder node must be done from the ClosePlan admin tab > Environment > Relationships > Fields

...

When Control Opportunity Contact Roles in the ClosePlan Admin environment is enabled, and you select Role on the Stakeholder, it will propagate to Contact Role on the Opportunity


Merge Maps

Merging Maps is the process of joining two different Maps into one Map

The process begins with a ‘Target’ Map.

...

 

A ‘Source’ Map is then selected.

The contents of the Source Map are added to the Target Map.

This merging process may create conflicts or anomalies, and so some conditions will apply to this process.

Please read the following to get a better understanding of what will happen when you choose to Merge Maps.


Terms:

Target Map: The Target Map is the Map into which the Source Map is placed.  The Target Map can be an Account Map or an Opportunity Map

Source Map: The Source Map is the Map that will be merged into the Target Map. The Source Map can be an Account Map or an Opportunity Map

Contact: The individuals associated with your accounts.

Stakeholder: Stakeholders are the individual Contacts on the Account or Opportunity level. Stakeholders are bound to Salesforce contacts. Each Stakeholder contains relevant information related to the Account and to the Opportunity. 

Account Map: A ClosePlan Map that is associated with an Account. Accounts may have more than one Map.

Opportunity Map: A ClosePlan Opportunity Map that is associated with an Opportunity. Each Opportunity may have only one Map.

Node: Represents a Contact on the Map surface. The Node contains the basic Contact information and other specific features.


Map Merging Scenarios

General 

As a general example, the below shows a Source Opportunity Map merged to Target Opportunity Map

Steps:

  1. Target Map is open
  2. Click ‘Import Map Icon’
  3. Select Source Map
  4. Select ‘Marge Map’


Target Map: GenePoint Opp 2

Image Added


Source Map: GenePoint Opp 1

Image Added

Result:

Image Added

Scenario 1: Account Map to Account Map

A Source Account Map is merged into a Target Account Map.

  • If the Source Map contains nodes that are not present in the Target Map, those nodes will be added to the Target Map. 
  • If the Source Map nodes are the same as nodes on the Target Map, the merge will overwrite all the attributes of the node on the Target Map EXCEPT the Role

Scenario 2: Opportunity Map to Account Map

A Source Opportunity Map is merged into a Target Account Map. 

  • If the Source Map contains nodes that are not present in the Target Map, those nodes will be added to the Target Map. 
  • If the Source Map nodes are the same as nodes on the Target Map, the merge will overwrite all the attributes of the node on the Target Map EXCEPT the Role

Scenario 3: Account Map to Opportunity Map

In this scenario we are merging Account relationship Map (source) to Opportunity relationship Map (target). 

  • If the Source Map contains nodes that are not present in the Target Map, those nodes will be added to the Target Map. 
  • If the Source Map nodes are the same as nodes on the Target Map, the merge will overwrite all the attributes of the node on the Target Map EXCEPT the Role

Scenario 4: Opportunity Map to Opportunity Map 

In this scenario we are merging Opportunity relationship Map (source) to another Opportunity relationship Map (target). 

  • If the Source Map contains nodes that are not present in the Target Map, those nodes will be added to the Target Map. 
  • If the Source Map nodes are the same as nodes on the Target Map, the merge will overwrite all the attributes of the node on the Target Map EXCEPT the Role

Issues when Merging Maps:

Cyclic Relationship

Existing nodes in Maps are not deleted during the merging process. This may lead to a situation where node A reports to Node B in the Target Map, and Node B reports to Node A in Source Map (or vice-versa). 

The Merge process will not permit this looping ‘cyclic’ hierarchy. 

In this case,  the hierarchical relationship found in the Source Map will take precedence.

Be Careful

Merged mapping cannot be automatically undone.  When the User completes the command by clicking ‘Confirm’ the Target Map will be merged with the Source Map.

  • If you have any doubts about the correct course of action, consider your actions carefully.

Image Added

  • IF you merge a map and need to undo, it will be a manual process of deleting added Stakeholders and returning Stakeholder Attributes on the Target Map to their original settings. 
  • Difficult, but not impossible.

Please, merge responsibly.


Show Submap Stakeholders 

To show the submap´s Stakeholders, open the submap in another window, or view the map in Preview mode via the Preview icon

...