This content has been marked as final. Show 1 reply
It seems to be a bug of versione 11.0, fixed in next version. We got some files from support which solved this problem, even if we are facing in these days with some collateral undesired effects under support investigation.
Hope this helps.