As a user....
I expect to have a cohesive experience and an understanding of how the configuration works. 

General description of the problem
With new configurations and some incompatible ones, we must develop rules for interactions and their effects so that we can refer to these when making decisions and create a coherent experience. 
**We must make these decisions explicit. 

Value proposition
• Enable us to make decisions quicker by referring to a thought out framework
• Enable us to discuss these decisions with transparency and ensure we are making the Right decisions
• Can extend to other Camunda offerings where configuration is key ie. Operate

Additional information

https://confluence.camunda.com/display/CO/2021-03-04+Multi-Measure+Reports+-+Next+Steps

Why are we doing this now
• Complexity of Report builder requires action on this topic
• Transparency of current state makes this possible 

Dependencies and related topics
See parent ticket

** Note - this ticket relates to future improvements - post multi process topic

Outcome and documentation WIP

Rules
—

**

1. Prioritise the latest selection.
Within a view: 

• If multiple measures exist, selecting an incompatible group by, removes one measure and disables the add measure button for that group by.
  (If another group is set, we do not revert to the multi measure state) 
• If a distribution was set, that is incompatible, it is reverted to none. 

Meaning: Group by options are not disabled for that view - they simply affect the other selections. 

Multi measures: 
If multi measure is selected, a grpu by variable can still be selected, the measure is removed. 
(2. Multi measures are always removed in favour of group by or view selections where they are incompatible) 

2. Group By: Only available if the option exists. 

From a start state: Only options which are availble appear for selection.
Ie. no group by in variable views.