Best Of
Re: How to retrieve sent emails
Update: Previously, a rule configured as explained in the previous post would not be triggered when the status changes from Draft to Sent.
A fix for this issue is expected to be delivered as part of release 21.1.
Re: OScript Orphaning an object
@Abir Saha Can you share either your code or your step list (ideally with screenshots) so that we can help you get there.
At the simplest level you should :
- In the OScript Explorer tab
- Right click on your OSpace object and select New -> Object
- Give it an Object Name e.g. "MyMenu"
- For Parent Package select "WEBLL::NavigationCallBack:LivelinkNavigationCallback"
- Now you have your new Object, double click on it so it opens in the editor
- Click into the editor, then select OScript -> Override Features from the main menu
- Click the checkboxes next to fEnabled, Execute methods
- Set the value of fEnabled to TRUE and put your code into the Execute method (see page 60 of https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551166/27085930/27085937/2120999/2120340/Livelink_Module_Development_Guide.pdf?nodeid=2122008&vernum=-2 for an example)
- Restart and see if it works.
As @Dave Carpeneto and @Appu Nair mentioned the best way to learn is via the course or working with our developers to help you grow.
If you are only adding a new Menu Item, you may find an ActiveView is a better way to go to start with, try looking at the "Add Item Menu Sample" predefined template.
Re: Best way to report an implementation error in the Content Server REST API?
From my past experience, the best way to report such issues is still going via the Support channel route so that all reported issues can be centralized and redirected to the right team for further investigation and updates.
Re: OScript Orphaning an object
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
