New notification developement and Agents within builder

Janusz_Frydecki

I'm trying to develop a new notification for the task object: inform owner of the task (not assignee) when the task is modified.1- Anyone has done this yet?2- Is it normal that the agents don't run while I'm in builder3- What are the steps of creating a notification?From what I figured out so far, I could create a new Trigger in my Oracle database to write an event to the NotifyEvents table and orphan LLNotify Objects/EventHandlers but I can't test this in builder and most of all, I don'T know if it's the "recommended way" of doing it.I called OT support but they told me that I don't have the right level of SDK support for this question. Do you think it is normal for a company providing an SDK no neither document nor explain the objects available to development? Do you think it is acceptable, as developpers using SDK/builder to have our application break on almost every new version because of methods' signature changing or simply objects disappearing? I would appreciate your comments on this too. Maybe I'm only too new to LL development! ;)Thank you!

eLink User

Message from Nair, Krishnankutty N. via eLinkIn Old livelink to test your agent with builder you would do thisTo test with builder... - In opentext.ini set/add the following:[options]RunWithoutLogin=TRUE - In the browser type the following URL:http://......./livelink.exe?func=notify.runagent http://localhost/livelink/livelink.exe?func=notify.runagent&agent_list={'9883'}The second argument is the way to tell livelink not to run alloutstanding agents and just your agent in this case I had an agent withan id 9883In new livelink you would do the same but do - In the browser type the following URL:http://......./livelink.exe?func=agent.runagent http://localhost/livelink/livelink.exe?func=agent.runagent&agent_list={'9883'}Theoretically if you look a the the notification process PPT we postedsometime back that will tell you how agents and notify work.I have notdone new notifications but have done a few agents here and there andhence I know this works in builder.In fact the next time plays animportant role in that too.I always have problems with my agents itworks in builder and not in llserver.Most of the times I set afuturistic time on the next run and it seemed to fix it. -----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Wednesday, December 14, 2005 3:27 PMTo: eLink RecipientSubject: New notification developement and Agents within builderNew notification developement and Agents within builderPosted by Paradis, Diane on 12/14/2005 04:23 PMI'm trying to develop a new notification for the task object: informowner of the task (not assignee) when the task is modified.1- Anyone has done this yet?2- Is it normal that the agents don't run while I'm in builder3- What are the steps of creating a notification?>From what I figured out so far, I could create a new Trigger in myOracle database to write an event to the NotifyEvents table and orphanLLNotify Objects/EventHandlers but I can't test this in builder and mostof all, I don'T know if it's the "recommended way" of doing it.I called OT support but they told me that I don't have the right levelof SDK support for this question. Do you think it is normal for acompany providing an SDK no neither document nor explain the objectsavailable to development? Do you think it is acceptable, as developpersusing SDK/builder to have our application break on almost every newversion because of methods' signature changing or simply objectsdisappearing? I would appreciate your comments on this too. Maybe I'monly too new to LL development! ;)Thank you![To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe/open/786303Livelink Server:https://knowledge.opentext.com/knowledge/livelink.exeTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.development@elinkkc.opentext.com.