Typically in a PB process, we would setup area scopes and assign each budget one area. The scopes structure we would have is e.g.:
If you assign the Area scope from the above list to the budgets component and then for each budget the sub-scopes (North, South, West and East), you are no longer able to select any scope when under that budget. This applies e.g. to the "import proposals" view as well as "new project" / "edit project" view.
In this situation, and only when the sub-scopes list is empty, the user should be able to select the top level scope from the list.
Note that it is done on purpose that when there are sub-scopes, the top-level scope is not visible in the list. This makes sense when submitting proposals but it is problematic for the further steps, such as budgets.
Typically in a PB process, we would setup area scopes and assign each budget one area. The scopes structure we would have is e.g.:
If you assign the
Areascope from the above list to thebudgetscomponent and then for each budget the sub-scopes (North,South,WestandEast), you are no longer able to select any scope when under that budget. This applies e.g. to the "import proposals" view as well as "new project" / "edit project" view.In this situation, and only when the sub-scopes list is empty, the user should be able to select the top level scope from the list.
Note that it is done on purpose that when there are sub-scopes, the top-level scope is not visible in the list. This makes sense when submitting proposals but it is problematic for the further steps, such as budgets.