PRS

Work Location Detail QDEs

The only reason there's a separate node, and a separate database table, is to account for Historical changes. Logically speaking, the user views the Details as merely attributes of the work location.

The ideal outcome is that the Work Location Detail QDE is abandoned completely, and the Work Location QDE used exclusively. Element-level checking is not currently required for Work Locations anyway, so there's no need to worry (at least, right now) about what the element names for the Work Location QDE should be (although there's no reason we can't just use the element names from the detail object).

So, I think, precisely, this is what I'd like us to do...

1. Abandon use of the WORK LOCATION DETAIL QDE
2. Use the WORK LOCATION QDE to control access to Work Locations AND THEIR DETAILS