Configuration Experiment #C3

Configuration Experiment #C3


Goal
The goal of this experiment is to help you understand how configuration changes impact crediting. For this challenge, you will use a demo workspace and alter the configuration. When asked to write down something, please copy the value to a document (along with the step #), as you will be using those values later on.

Difficulty
Easy.

Steps
  1. Create a demo workspace
  2. Go to Calculations > All Calculations
  3. Open the calculation
  4. Go to the Alerts tab
    1. How many warnings do you see?
  5. Go to the Credits tab
  6. Write down how many transactions were credited to "Daniel Martinez"
  7. Click on "Daniel Martinez" to view credited transactions
  8. Click on any transaction to edit it
  9. Write down the transaction's URL
  10. Change the "Sold By" from "danielmartinez@example.com" to "Hello"
    1. What do you think this will do?
  11. Save and select "Allow Overwrites"
  12. Go to Calculations > All Calculations
  13. Re-run the calculation (with delete)
  14. Open the calculation
  15. Go to the Alerts tab
    1. How many warnings do you see?
    2. What does the warning mean?
  16. Go to the Credits tab
  17. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  18. Go to Teams > All Teams
  19. Delete all teams
  20. Create a new team called "My Team"
  21. Set "Daniel Martinez" as the team manager
  22. Save the team
  23. Go to the Members tab
  24. Add "Eric Smith" as a team member
  25. Add "Veronica Haley" as another team member 
  26. Go to the Aliases tab
  27. Add an alias of "HELLO" to the team
  28. Go to Plans > All Plans
  29. Edit plan "One-Off Sales Contest"
  30. Go to the Targets tab
  31. Enter a crediting formula

  32. Check "First Check If Transactions Can Be Re-Assigned To a Team (advanced)?"
    1. What do you think this will do?
  33. Choose "Assign All Credit To Team's Manager"
    1. What do you think this will do?
  34. Save plan changes
  35. Go to Calculations > All Calculations
  36. Re-run the calculation (with delete)
  37. Open the calculation
  38. Go to the Alerts tab
    1. How many warnings do you see?
    2. Why is the warning gone?
  39. Go to the Credits tab
  40. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  41. Go to Plans > All Plans
  42. Edit plan "One-Off Sales Contest"
  43. Go to the Targets tab
  44. Choose "Assign Full Credit To All Team Members"
    1. What do you think this will do?
  45. Make sure "Include Team Managers" remains unchecked
  46. Save plan changes
  47. Go to Calculations > All Calculations
  48. Re-run the calculation (with delete)
  49. Go to the Alerts tab
  50. How many warnings do you see?
    1. Why is the warning gone?
  51. Go to the Credits tab
  52. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  53. Copy/paste the transaction URL into your browser
  54. Go to the Credits tab
    1. Did you expect to see the displayed value?

Key Learnings
  • You can achieve crediting of users via teams (level of indirection)
  • You can control if crediting goes to team managers, team members, or both
  • You have to specify a crediting formula to "force" the text value used for crediting 
    • Otherwise, the system will use the field mapped to the "Team / Territory" system category
    • We could also have specified which crediting field to use instead of a formula


    • Related Articles

    • Configuration Experiment #D1

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #V6

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the ...

    • Configuration Experiment #D2

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #D3

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #V5

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...