Configuration Experiment #V2
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 a document (along with the step #), as you will be using those values later on. 
Difficulty
Easy.
Steps
- Create a demo workspace
 - Go to Plans > All Plans
 - Edit plan "Sales Manager Compensation"
 - Go to the Incentives tab
 - In the dropdown, choose "As Percentages Of a Per-Target Dynamic Quota"
 - In the textbox next to it, enter "@@Quota"
 - Configure 2 attainment levels
- Set attainments to 0% and 100%
 - Make both attainment levels cumulative
 - Add a 5% of revenue reward to the 1st tier
 - Add a 10% of revenue reward to the 2nd tier
 
 - Save plan changes
 - Go to Calculations > All Calculations
 - Delete the calculation for "One-Off Sales Contest"
 - Start a calculation for "Sales Manager Compensation"
 - Open the calculation
 - Notice the alert (click for details)
-  Why did you receive this alert?
 - What does this alert mean?
 
 - Go to Settings > Tools > Bulk Set Team Quotas
 - Enter "Quota" as the property name
 - Click on "Load All"
 - Enter 1000 for some teams, 2000 for some teams, 3000 for some teams
 - Click on "Visualize"
 - Click on "Save"

 - Go to Teams > All Teams
 - Edit any team
 - Go to the Custom tab
- What do you see?
 
 - Go to Calculations > All Calculations
 - Re-run the calculation (with delete)
 - Open the calculation
- Notice there are no alerts
 - Why is the alert gone?
 
 - Go to the Rewards tab
- Can you tell which team(s) only attained the first attainment level?
 - Why was the criterion for getting to the second attainment level?
 - What was their assigned quota vs. other teams?
 
 - Click on "Reward Details"
- Can you tell each team's attainment to quota?
 
 
Key Learnings
- It's possible to configure plans whose attainment is based on a per-target custom variable
 - If the plan is team-based, custom variables should be set on teams, because we are measuring team performance
 - Using a tool, we can bulk-edit the same custom variables across many teams
 - We can also edit each team individually and see which custom variables are set
 
Related Articles
 
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 ...
 
Configuration Experiment #V3
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 ...
 
Configuration Experiment #V1
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 ...
 
Configuration Experiment #V4
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 ...
 
Configuration Experiment #T1
Goal The goal of this experiment is to help you understand the time dimension in calculation mechanics. 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 ...