how to override a method in builder

Tamer_Morsi

i am fairly new to ll builder, & need some pointers in overloading a method (9.7.1).In Module: Project -> MyProjects -> Projects-> the ManageSelect script is what i am trying to overload.We need to retrieve more columns from the dtree table versus the original code, which is:getInfo.ColumnsList = { 'DataID', 'Name', 'CreateDate', 'ModifyDate', 'SubType', 'Status' }My question is how do i override this file (ManageSelect) to replace it with additional column names?would i need to create a whole new module or can i use an existing custom module to do this ?what i did so far is, in an existing custom module i have orphaned the (project) object in the core module and made the code changes but the new code is not getting called instead of the old one ...

Iain_Halliwell

Hi Tamer, When I have carried customisation I have used a module called CustomizationRT, this enables you to manage your customisation after you have applied them for example when you have many overrides and you need to know where they all are there is a script that can be executed to find and list them all.In answer to your question you will require some extra script in your _init script to replace the orig code with your customisation.This is something that was written explaining the process sometime ago but I think it still holds true:are you changing a single feature of a single object ?if so, try this...1. create a Child object in the Root object of your OSpace2. call this Overrides3. create a script in this new object called '__Init' - NOTE THERE ARE 2 _ chars there !! This script will get called by livelink on startup, and we will use it in each object below to register an override.4. create a child of this new object, and call it the name of the OSpace you are overriding (WebWork)5. within this object, create another child with the name of the OBJECT you are overriding. It may seem like a lot of new objects, but it just makes it easier to maintain.6. you will now find it easier to open a 2nd OSpace browser window.7. Go find the object you want to change, and drag the feature you want to change into your new object - it should ask you if you want to copy it - say yes.8. Now drag the original object itself into your new object. You will be asked to name it, and by convention I normally stick an 'f' infront of the name, where the f stands for feature as opposed to script. This will create what is called an object reference feature, which allows us to point to the original object.9. in the __Init script, enter a line such as this....fWorkStatus._BrowseContents = this._BrowseContentssubstitute the names for your object and feature.10. Now we need to tell Livelink about your new object, so it will run this __Init script on startup.11. In your OSpace's Globals object is a script called BuildOSpace. Right mouse click on this script and select Run Script. This will register all objects with a script feature called __Init in the Global object's f__InitObjs feature. Just so you know, take a look in your OSpace's Root object's startup script. This is predefined to make a call to...$Kernel.OSpaceUtils.InitObjects( .f__InitObjs )which goes through running all these __Init scripts.What this script is saying, is... 'replace the feature called _BrowseContents in the object pointed to by fWorkStatus with the feature called _BrowseContents in object'. (this is not strictly required, but it makes it clearer).The reason I tend to use this method of overriding, is that the other way would involve creating an orphan of the original object. Livelink would then look at your copy of the object instead of the original. This is OK, except when more than one person/module needs to change the same object - you wouldn't be able to guarantee who's version would be used.I hope this is of help.Many Thanks Iain