This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
>>But, in case of any deletion initiated from web(iNotes), I find the agent's code being executed twice. Unable to figure out the cause.
I don't know why that would be the case, but it's possible that iNotes is calling NSFNoteDelete twice for the same document.
>I wish to know if below requirements can also be met:
>1. How to differentiate whether an action is performed from Notes client or from web?
Modify TriggerHappy to call different agents depending on what task triggers the event. You'll have to do some C coding and rebuild TriggerHappy for that. Code to figure out what task you are running in will probably be platform-specific.
>2. How to identify a document being deleted during archival?
Are you configuring triggerHappy to catch the delete event before, or after it occurs? If you configure it to catch the event before it occurs, then I believe you should have full access to all the data in the document. If you catch the event after it occurs, the data is already gone.
>3. How to track the IP of the machine causing this action?
>I'm sure there will be a way to do that.
I'm not sure of that at all. TriggerHappy is working at a very low level. It traps events at the API level, and all it gets is the event and the arguements to that API call. The arguments to NSFDocumentDelete will not include any information about the client that generated the call. TriggerHappy may not be the right solution for you if you need this. If you mentioned this requirement earlier, I'm sorry that I missed it. (On the other hand, all other methods are going to have some drawbacks as well.)
-rich
Feedback response number WEBB9CASYE created by ~Ned Nimfanakonyoopsi on 10/08/2013