Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
How can I replace LLNotify.LLNotifyRoot.MessageHanders?
Robert_Davies_(unlondonadmin_-_(deleted))
Hi folks.I want to customize the messages generated by the Change Agents to include (for things being added) who made the change and when.This means modifying the FormatMessageBody() and FormatMessageHTML() methods of the appropriate MessageHandler class (e.g. in the NodeAdded message handler) and using the miscData.Data.DATAID field to lookup the node's CREATEDBY & CREATEDDATE fields.I could modify the existing source, but would prefer to remain compatible with future versions by using an installable module.I've traced the NotifyRequestHandler.RunAgent.Execute() method and found it creating a cache of the message handlers . However I have the sneaking suspicion it is walking the object tree of the LLNOTIFY module to build the cache.Can anyone tell me how I can safely insert my Handler as a replacement for the existing handler?Best regards/matt.
Find more posts tagged with
Comments
Robert_Davies_(unlondonadmin_-_(deleted))
Ok now it looks like I need to replace both the EventHandler and the MessageHandler. Here's my reasoning.:In order to find the CREATEDBY and CREATEDDATE information that I want I will need a .fPrgCtx so that I can call$LLIAPI.NodeUtil.ListNodes()with a query like'(dataid=:A1)', { miscData.Data.DATAID }to get the node information.However the MessageHandler doesn't have a .fPrgCtx and it doesn't appear to be passed into the FormatMessageBody() function.So the question is now, how do I hook both the EventHandler and the MessageHandler to change the Change Agent report when a document is added?Best regards/matt.
Thomas_Feike_(UBISBE01Admin_(Delete)_2433807)
Hi Anne,Seems, that your question has been queued for a long time. Are you still alive or should I tell something to Jim for a second time?Well, if you're still there: have you ever heard about the facility of patching?This is what you need, because the Livelink-Developer who made this Agent-Implementation has created requesthandlers without a fEnabled-Feature. You only will get it by orphaning your requesthandlers from the llrequesthandler in WebLL. I often found things like that in Livelink.So you must patch it.How to patch?I'm sure there is a guide about that issue at the knowledgebase. Otherwise reply for helpGreetingsAlf (Berlin, UBIS AG)
Hans_Stoop_(hstoop_(Delete)_1579932)
In the customizationsRT module it is described how you can create a patch that is compatible with future releases of Livelink as long as the parameters don't change. I don't know if you can accomplish what you want with that that patching mechanism. It merely allows you to do your own code before and after the original call.The module can be found at:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2456823&objAction=browse&sort=nameIt
also contains some other handy development functions as compiling all the oscript, removing breakpoints, ...
eLink User
Message from Dylan Wright via eLinkLLPATCH.Utils.Dump( ospacename )> -----Original Message-----> From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of> eLink Discussion: Development Discussion> Sent: Friday, June 15, 2001 6:57 AM> To: eLink Recipient> Subject: Patching Livelink> > > Patching Livelink> Posted by hstoop on 06/15/2001 09:55 AM> > In the customizationsRT module it is described how you can create > a patch that is compatible with future releases of Livelink as > long as the parameters don't change. I don't know if you can > accomplish what you want with that that patching mechanism. It > merely allows you to do your own code before and after the original call.> The module can be found at: >
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objI>
; d=2456823&objAction=browse&sort=name> > It also contains some other handy development functions as > compiling all the oscript, removing breakpoints, ... > > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Topic: How can I replace LLNotify.LLNotifyRoot.MessageHanders?>
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objI>
; d=1696465&objAction=view> > Discussion: Development Discussion>
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objI>
; d=786303&objAction=view> > Livelink Server:>
https://knowledge.opentext.com/knowledge/livelink.exe>
; > >