Best Of

Sorry, I go back between my heydays of builder and then CSIDE. I haven't been keeping in touch with Oscript until I needed to do something. However, the starter document on CSIDE explains the art of Orphaning in great detail.

If what you wrote looks like what OT programmers did then I would say it is correct Essentially the .fEnabled tells the Oscript compiler to include your object

An orphan just means that the parent object lives in another Space.I think for e.g if you right-click WebDoc::DocNode you will see the RED that means the original code is in WEBNODE ospace In this graphic one understands this info DocNode is the Parent for Folder, Document and such like and depending on the inheritance you can see that the Action-Create7 Action-Create2 has been overridden so at this main level its .fenabled is false but its children with node type registrations have been enabled

It is a fantastic object system with myriad subsystems and all but nowadays not many attempts to do anything oscriptish...

will invite Oscript stalwarts like @Chris Meyer @John Simon @Ossie_Moore @Hugh Ferguson

@Greg Griffiths are like the go-to guys who seem to help people(I also try) (there are tonnes of OT people who help as well like Chris webster, Howard Pell(retired,Donna Nalla ), and so on). If you can afford it take the script training

I would advise that

You are not supposed to Orphan from the module side you always do it from the Oscript (Project explorer) side. what you are doing is old Builder technology they sometimes work but it will not many times reflect in the code you are building. Did you come from the old builder style?

As Appu said: orphaning is the same as overriding, but the parent is from a different OSpace. That's really all there is to it from a functional standpoint. Orphan objects show up as 'red' in the various CSIDE views. They also show up directly under the OSpace where they live.

Is this still the problem you are facing? If so: can you post the top few lines of your .os file (in the OScript Explorer, not the Module Explorer as Appu flagged) so that I can see how you define the package & object? Also: could I see how you are trying to reference said object in the code that's complaining that the object doesn't exist?

Note that OScript & the framework that Content Server provided is fairly different to most other software development experiences; as Appu flagged training (https://www.opentext.com/TrainingRegistry/course/details/2807) will help very much, should the option presents itself.