RE: template management Kevin Pettitt 11.Nov.02 12:45 PM a Web browser Domino Designer -- Other 5.0.11Windows NT
You can leave the agents enabled in the development environment, just be sure the "server" that they are set to run on is the production server.
The production template is another matter, since it of course sits on the production server. I'm not sure if there is a blanket way to turn off agents in any *.ntf databases, but that would solve the problem.
Another way, which is a little more innovative but not that hard, is to include as a standard piece of code in all scheduled agents that checks a configuration document before running. The config doc is a convenient way to turn on/off and control the time of execution for agents at the user, not the admin level.
For example, you might have a "daily" agent that in fact is configured to run hourly, but every hour it looks to this new config doc to find out if it can keep running FOR THAT HOUR. If the config doc has a field with a "17" in it, then the agent will run during the 5PM timeframe. The other 23 times it starts running during the day, it aborts before anything actually happens.
Using this approach will allow a fine degree of control over agent execution. In this context, the production templates, lacking any config doc, can have their agents "enabled" without any adverse consequences.