Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Design Refresh handling of Agent (Scheduling) Properties option to only update program logic-leave server and schedule untouched.
We distribute our application and code changes to multiple customers with various topologies via standard . NTF templates.
For scheduled agents in particular the behavior of Design Refresh creates a challenge since server names, enabled/disabled ,frequency and schedule properties vary per site. Current behavior of Design Refresh is an "All or Nothing" proposition. Under default settings each night, when designer runs, the agent is aligned completely with the Template definition which will reset schedules and other runtime settings (in addition to the code changes).
The other option is to set the Design Property "Prohibit design refresh or replace to modify". Since this option shuts off all updates, it become impossible to transmit code changes to a customer without manual intervention at each site.
While in practice, to minimize the impact of this situation, we attempt to keep the agent design as simple as possible , typically a single simple call into a script library ... it is inevitable a change will be needed at some point in time. Distribution of even a small code change to a schedule agent creates a lot of manual intervention at customer sites that should be unnecessary.
We either need designer task behavior to change when dealing with Agents or add a design property option to disable design refresh of Only the agent's runtime properties (server, schedule, enable/disabled). This would allow updates to the underlying program code as needed as part of the automated Designer task
Option when refresing databases to not overwrite, Agent Signer, Schedule and Enabled/Disabled state of Agents
One of the biggest hassles for me administrating Domino servers is that every time we have new design changes I have to open the template, set the correct agents to be enabled/disabled, set the correct schedule for when the agent runs and set the ...