Today, the Document node within a Runbook must be manually triggered each time to generate and save the resulting Word document, requiring user intervention at every execution. This enhancement would allow the Document node to automatically execute and save the generated document to a specified location as part of the Runbook run, without requiring a manual step. Customers running Runbooks on a recurring or scheduled basis would benefit from consistent, hands-free documentation generation, reducing manual effort and the risk of missed or delayed document creation.
Open
Automatic Execution and Save for Runbook Document Node
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain Universityor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
