At the moment, we are aware of this issue and we are planning to address this in one of our Feature Upgrades. There is no committed time yet to get this fixed since we are collaborating with a 3rd party about this issue. We apologize for the inconvenience.
I have logged your feedback as a feature request and we will make sure you are the first to know as soon as we have any updates. If you want to request an update on your own time frame, please reference ticket CR-161258.