Important Update: Archer Community Scheduled Maintenance on November 23–24 - New Community Launching Soon! Learn More..
2023-12-28 04:19 PM
Hi all!
I have a few different custom javascript buttons that are causing Archer's unsaved changes message to appear when I don't expect it to. Below are a couple of examples:
In the first scenario, if I change the onclick to "javascript:transitionNode(10);$('#master_btnApply').click();return false;" I don't see the unsaved changes message any more.
In the second scenario, I'm already calling $('#master_btnApply').click(); at the very end of my custom function.
Is there a better or more elegant way to force Archer to know the form is not dirty? I don't technically have a solution for the second scenario at this point. Any suggestions would be helpful. Thanks!