When the ODX Server originally came out, there was a really nice documentation feature in the portal that allowed you to define and add tags to ODX Sources based on:
- source
- schema
- table
- field
You could also upload the metadata from your repository into the TX cloud and generate simplified documentation for your whole implementation including the impact of GDPR/confidential data. Having this feature in the new release is becoming more and more important due to larger customers needing to be compliant with internal and external policies. In 20.10.x you can at least tag BU → DWH → SSL or DWH → SSL if you use the ODX, but in the new release this is more fragmented.
The main advantage of the prioroption was being able to grant access to a DPO who could then input all the tagging without needing to understand how TimeXtender itself works. While there may not have been much use back then, I think having all of this within the scope of TimeXtender makes for a unique selling point. You can technically do this in Purview (and this is what I am doing in a few situations) but that is not a viable solution across the board.
In the current situation you can add tags to DWH instances but there is no end-to-end documentation. The tagging is also only field-based and mostly hidden from sight.
