Summary (Custom) Field Mappings function like CE when creating/editing tasks

When summary field mappings are imported from CE to BOE Pro (via the "Import CE Estimates" or "Add Proposal from CE" features) and new tasks are created, the structure field drop downs (i.e BOE ID, CLIN, Option, WBS, etc) should function the same way as they do in CE. Each summary field (custom field) in the mapping is linked to a specific value, the drop down lists should be dependent lists, filtering the available options based on the previous tier's value in the mapping that is selected.

Currently when a mapping exists, while adding a new task, all summary (custom) field values are available to choose from in the drop downs, these lists are not filtered. Once the user hits the create button, if the selected combination of summary (custom) fields is not allowable per the mapping, user will receive a message at that point. User should not have to guess at the mapping only to find out its not valid. The drop downs should function the same way they do in CE, filtering the options and guiding the user to a valid combination.

The same thing should happen when editing an existing task that originally has a valid mapping. Currently, if a user edits the summary (custom) fields of an existing task and chooses a value not allowable per the mapping, there will be an error symbol next to the field flagging that there is an invalid selection. Drop down lists still reflect all values.