Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
NSC | Trigger the Button created by Script
Script triggers when a button is clicked, but on some scenarios, customers need it to be always be clicked and customer likes to set a workflow to say for example when the status changes to closed click the button. The only way to do what you are describing is to use the DOM and get the button element and click it. I'm not sure if a client side workflow action script will do it but I know it will work with a client script. In either case it will require a script to click the button without user interaction. DOM is the browser's Document Object Model, i.e. get the button element in
Tagged:
0