Creation Context of Copy&Pasted URCap stays as Loaded

Just noticed that the creation context of copy & pasted URCap nodes stays the same as the original node.
I feel a fleshly copied and pasted URCap node should have a NEW creation context. This would allows developers to know if a node was copy and paste during the programming (context set to new & not empty data model) to i.e rename nodes automatically.

Wondering if any one else would see a use for this ?

1 Like

Yep. Had to scrap ideas for making my CAP more user friendly as a result of this. The API documentation is wrong as well, since it doesn’t explain this detail. I believe this has been pointed out to UR, though it’s been this way since at least 5.9 soooooo