Scheduled agents will not disable with design refresh

HCL Domino Domino Forum
1

Anyone seen this one? Try disabling a scheduled agent in a template and push the change to a database that inherits design from the template. The agent’s date/time stamp is updated in the target db but the agent remains enabled in the target db, even tho it was disabled in the template :frowning: Happening for several scheduled agents in multiple dbs that use the same template. Same results with convert -d. When issuing the design command at the server, the console shows date and time stamps but doesn’t disable the agent. See below. Is there a new way in 8.5 to enable/disable scheduled agents in dbs that inherit design from a template? The server is 8.5. One interesting note: If I do a manual design refresh of the target db using Notes instead of the server console, the agent updates fine (gets disabled). Please tell me I don’t have to manually update dbs or use a LotusScript agent. I can write a LotusScript agent to disable the agents, no problem, but there has to be a way to enable/disable agents in 8.5 via a template refresh or console command without having to resort to manual labor! :expressionless:

DestNonDataModifiedTime: 06/25/2009 10:24:42 PM

DatabaseDesignModifiedTime: 06/25/2009 10:24:42 PM

DestIconModifiedTime: 05/31/2007 05:19:06 PM

DestRefreshDesignModTime: 06/25/2009 10:24:42 PM

DatabaseTemplateTime: 06/25/2009 09:33:41 PM

Context.SrcDesignTime: 06/26/2009 01:15:16 AM

2

Subject: This is a feature. Details inside

Keeping agents enabled after design update has been a long standing feature request.It has been added in R8.

no ini variable, or DESIGN_AGENT_UPDATE = 0 means update the design of the agent, then reable it adding the previous signed on OnBehalf field. This allows the agent to run with the same authority as before the update. Before performing this operation, the agent signer of the template and the database are verifying so the agent cannot be spoofed.

You can override this behavior using an ini variable

DESIGN_AGENT_UPDATE = 1 → means do not keep the agent enabled, overwrite if the agent in the template has a newer design than the agent in the database

DESIGN_AGENT_UPDATE = 2 → means override even if the agent in the template has the same or older version than the one in the database