Tom,
Not only what Jim Cobane warns but at least prior to the Master Site concept, when doing an upgrade the root tclprocs directory gets rebuilt so anything you place there (wheterh links to another dirctory or your code itself) goes away.
We always had a ‘Master’ site and used soft links. We did not use the root tclprocs directory because of issues in using it. Once the Master site concept was imbedded in the engine we went to that.
It works fine with one exception, you cannot see Master site objects from the local site. You can reference them but cannot see them in the GUI.
Healthvisions explanation is their best practices dictate you should have to go to the master site to change any master site object.
A position some of us have (and have requested as an enhancement) is either to allow read only from local sites and making the object appear in the local ‘Sirte Manager’ container – or – allow the customer to set a setting with each local site if read/write should be allowed from the local site but all objects should be readable.
The second gives the control back to the customer of what they consider to be ‘best practices’ and give granularity of control at the site level.
So our position is if we have a global object it goes in the Master Site – and that has been our position before Cloverleaf inherently embraced the Master site concept.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
.
.