HowardHoward PellSenior Technical EducatorLiaison, Special ProjectsOpen Text Corporationwww.opentext.com(519) 888-7111 Ext. 2203Education is for improving the lives of others and for leaving your community and world better than you found it.- Marian Wright Edelman
The addressbook module is usually on the second CD or the SDK cd.Inside you will find sdk,client lapi files this example and so on.I am a self taught oscripter and basically I did the addressbook sample many times to understand the livelink code architechture. Having understood module building the addanewmodule wizard attached here with is my copy,you should search for it or "Martin Scott".The script goes under the scripts directory of your opentext installation.Then it will show up as see screen shot...If you are are a beginner doing the addressbook module does not hurt.It has helped me tremendously having never a chance to attend a class by the likes of Howard Pell and so on…You get better and better doing it.I mentored under John Simon a huge oscripter and my guru….Donna is always there to help in times of crisis.
Regarding event script you basically get a stub of workflow information in it from OT.You will then basically have to write your code inside this script or any other utilty script passing parameters appropriately.The key to writing event scripts is understanding the events on which they get called.For eg it can get called on initiation,it can get called on a step entry exit like wise.
In your case the event script that OT stubs has been renamed to _ChangeAttributes that is all the difference to it.Put that in the context of a workflow(Paint a workflow,put that event script in the second step of the workflow.Put an echo statement inside the script something of an echo("Hello World") and see if you can compile etc.The evnt script executes before you can debug it hence the echo method...
<<MakeNewModule.lxe>>
-----Original Message-----From: eLink Discussion: Livelink Builder Discussion [mailto:componentbuilder@elinkkc.opentext.com] Sent: Thursday, December 14, 2006 9:25 PMTo: eLink RecipientSubject: Thanks for the help
Thanks for the helpPosted by Wan, Alvin on 12/14/2006 10:23 PM
Hi Nair,
Thanks for the screenshots. Inside the document you mentioned the AddressBook example by OT, sorry would you be able to direct me where I can find this? I can't seem to find this in the event scripts or workflow section of Builder. Also you mentioned the "AddANewModule" wizard, could you also please point me where I can find this? More for info really.
I've previously followed Builder documention to set up the module and callbackscript, but I guess my confusion was about whether the script would be able to work just by using the function inside the script. Would i need to add another "main" function to pass in arguments like prgCtx or Work into the ChangeAttributes function? Or would the system somehow pass these arguments to the ChangeAttributes automatically?
If i need to create another main function to pass arguments like prgCtx and work, how do I pull these values out for passing?
Thanks again for your help, its been useful .
Regards,
Jeremy
[To reply to this thread, use your normal E-mail reply function.]
============================================================
Topic: New to Livelink Builder - Help with event script for setting Workflow attributeshttps://knowledge.opentext.com/knowledge/llisapi.dll/open/9654729
Discussion: Livelink Builder Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/765419
Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dll
To Unsubscribe from this Discussion, send an e-mail to unsubscribe.componentbuilder@elinkkc.opentext.com.
Anadarko Confidentiality Notice: This electronic transmission and any attached documents or otherwritings are intended only for the person or entity to which it isaddressed and may contain information that is privileged,confidential or otherwise protected from disclosure. If you havereceived this communication in error, please immediately notifysender by return e-mail and destroy the communication. Anydisclosure, copying, distribution or the taking of any actionconcerning the contents of this communication or any attachments byanyone other than the named recipient is strictly prohibited.