You'd think, but there was definitely no change to the environment nor any update to any of the applications or the OS nor anything but incremental changes to the FrameMaker source. One day it worked, the next day it didn't. If FrameMaker tech support covered ExtendScript maybe they could have sorted it out.
I experienced similar bit-rot in RoboHelp. On Fri, Oct 25, 2013 at 5:15 AM, Rick Quatro <rick at rickquatro.com> wrote: > FWIW, scripts don't generally just stop working. If it worked then stopped, > some condition must have changed.
