I have a V13 package that does some funky things with Forms in the backoffice. Admin's are able to "LOCK" a form once its been designed, so that additional changes can't be added. Part of this plugin also amended the Tree section and changed the icon / added [LOCKED] at the start of the node name (see attachment). After upgrading to V17, we've lost the TreeNodesRenderingNotification handler. What would be the best way of implementing this now? https://cdn.discordapp.com/attachments/882984798719729704/1498995251447074826/Screenshot_2026-04-29_at_11.27.21.png?ex=69f32f9d&is=69f1de1d&hm=dac589d611bdb52db855c8785d6d397a7e0da001cb907dba634b0b17edbbb291&

I would consider an Entity Sign to show its locked https://docs.umbraco.com/umbraco-cms/customizing/signs

your a star @Warren Buckley there's so much new stuff to learn with V17, the hardest part is finding it in the docs 🤣

No worries - but yeh loads of thiongs to think about. Need to try and think clientside first rather than the older approaches of being able to edit the UI easily from C# at runtime. The client needs to make a request to a MGMT API to know about this state of forms at some point

Cheers @Warren Buckley got there in the end, works a treat !! https://cdn.discordapp.com/attachments/1498995251736608768/1499320568720130109/Screenshot_2026-04-30_at_09.03.50.png?ex=69f45e97&is=69f30d17&hm=76d753f1e5fb2b9b39ded083a0ab29e8ea285fe33010fe7c9e5fb8eece72d4ac&

Nice how did you end up solving it?

I created: 1) entitysign to handle the icon switching, and updating of the node name 2) custom condition IsLocked to handle the check if the form is locked/published via an API 3) custom workspace for the Read Only view showing the locked symbol and text, and some code that adds the reverse of IsLocked to the default Design view to hide it

Future suggestion - perhaps disable/remove the save button for the form bottom right

that's a good idea 👍

Thanks for the mention @Warren Buckley ! did you end up using the tool in the end @Ian Houghton ?