Enabling agents with Editor access

Hi All,

I’m currently writing a web based application. All of the backend stuff is done with Java via an agent which is set to run as the web user.

As part of the admin for this application, I need to be able to enable or disable a scheduled agent. I’d set the security on this agent to “Allow editor level user activation” but it was just throwing errors each time I tried to call save on the other agent.

Eventually I tracked it down to the fact that I’d set the agent to run on server with the option “Choose server when agent is enabled” checked. Although you can enable or disable the agent as an Editor, this agent needed the server name set and that requires higher access privileges.

My way round it is going to be to test the current access level and only enable the agent if the user has designer or above access, or the agent doesn’t need it’s server name changing.

I couldn’t find anything when I searched on this so hopefully this will help anyone else having trouble with this.

Emily.

Subject: editor level activation

This feature is meant for enabling and disabling scheduled agents in the mail file.

There are very strict rules about the use of this feature

  1. the agent has to be in a mail (if you use AdminP to enable it)

  2. if don’t use AdminP to enable it, the OnBehalf field has to be set at design time (as well as server to run on and every other parameter of the agent). The editor user cannot change anything but enabled status

  3. the agent has to be signed by someone who has rights to sign agents that run onbehalf of someone else

This level is very high level of privilege, tightly control which people in your organization have this right.