Notes db has web page with WebQuerySave event coded in one of the following ways:- @Command([ToolsRunMacro]; “(ESEPWebQuerySave)”)
@Command([ToolsRunMacro]; “WebQuerySave”).
The agent’s name is “(ESEPWebQuerySave)|WebQuerySave”.
Submitting the web page returns “Form Processed”, as the agent is apparently not called. I don’t think the @Command is the problem, because I get the same response if I code “123456” as the agent name.
The agent is shared, with an event trigger of 'Agent List Selection, with a Target of “None”. The db ACL has ‘-Default-’ with Author access and “create documents” checked. But none of that would appear to matter, as it creates the document, it just doesn’t call the agent.
However, if I run a local copy of the database, not the server copy, the agent is successfully called. So all of the above is fluff, as the environment is the deciding factor. I have another database of very similar design on the same server and I’ve checked all the attributes and don’t see any differences.
Also, I can add an action button to one of the views which just runs ToolsRunMacro, and it executes the agent just fine.
Subject: agent doesn’t run… and IBM should really pre-fill the subject line in this forum and show original text when composing the answer.
You should be able to see the reason on the problem in the log.nsf on server.
Check that the signer of the agent has rights to run the agents on the server.
If agent uses restricted operations (disk read/write, SQL, Win API), make sure that agent’s security setting (second tab in agent’s properties) is set to “2. Allow restricted operations”.
Try to trigger agent manually with ?OpenAgent using web browser and see the log.
If it doesn’t help create a new agent with another name and try it. If still doesn’t help, try the same solution in a new database to eliminate possible problems with access and caching.
Those were useful suggestions. I hadn’t thought of directly calling the agent from the browser.
I am the agent signer, and it doesn’t perform any restricted operations. It did execute successfully using ?OpenAgent. I had asked the server admin to check the log, but it didn’t show any related entries.
Keep in mind that it didn’t matter what I actually coded in the WebQuerySave event. It’s as if that event is being ignored, not that some sort of error occurs when it’s called.
For now, I’ve admitted defeat and am using $$Return since I didn’t need to do anything operational anyway.
Those were useful suggestions. I hadn’t thought of directly calling the agent from the browser.
I am the agent signer, and it doesn’t perform any restricted operations. It did execute successfully using ?OpenAgent. I had asked the server admin to check the log, but it didn’t show any related entries.
Keep in mind that it didn’t matter what I actually coded in the WebQuerySave event. It’s as if that event is being ignored, not that some sort of error occurs when it’s called.
For now, I’ve admitted defeat and am using $$Return since I didn’t need to do anything operational anyway.