Not exactly.
When I add this rule to the properties, I don't receive the error anymore. So that is solved 🙂
But, when I modify the values in the iLogic window that pops up, then the parts of my library are modified. And this can't be correct.
In 2016, when I insert this specific iLogic component, then it generates copies of the adapted part into my project folder.
See below how this works in 2016.
Step 1: insert iLogic component
Step 2: automatically generating copys of the modified part into the project folder.

To make things more complex again. With another, more simplistic model, it does the job correctly = copy the modified parts into the library.
I know, it's perhaps not easy to follow exactly what I mean because our library and way of working is customized for our purpose.
I just want to mention this because: in 2016 this works fine and in 2018 not for all components.
I will also try to figure this out by deleting all the rules and adding them step by step again.