FM2019 event-driven scripts do not run automatically while in Autorun

Hi Klaus, I haven't tested Roman's code, but I checked some of my past scripts and in one I actually used PreSave events to do this. Roman, try modifying the code below and testing it. Thanks. -Rick

#target framemaker

Notification (Constants.FA_Note_PreSaveDoc, true);
Notification (Constants.FA_Note_PreSaveBook, true);

function Notify (note, object, sparam, iparam) {
 
    switch (note) {
        case Constants.FA_Note_PreSaveDoc :
        case Constants.FA_Note_PreSaveBook :
            if (app.VersionMajor > 12) { 
                // Cancel the built-in save.
                ReturnValue (Constants.FR_CancelOperation);
                saveAsFm12 (object, sparam);
            }
            break;
    }
}
 
function saveAsFm12 (doc, name) {
	
    var params, returnParams, i;
    
	// Get required parameters for the save function.
    params = GetSaveDefaultParams ();
    returnParams = new PropVals ();
    
    // Get the FileType save parameter and set it to FrameMaker 12.
    i = GetPropIndex (params, Constants.FS_FileType);
    params[i].propVal.ival = Constants.FV_SaveFmtBinary120;
    // Add the name to the recently opened list.
    i = GetPropIndex (params, Constants.FS_UpdateFRVList);
    params[i].propVal.ival = true;

    // Save the document as FrameMaker 12.
    doc.Save (name, params, returnParams);
    PrintSaveStatus (returnParams);
}

Hi Rick,

I appreciate your quick response!

I have a script that saves an active doc or book as FM13 while hitting Save or Ctrl+S. I moved it to Autorun. 

When I run FM19, open a book or book component, make changes and save them, the file is not saved as FM13, until I go to the Scripts pod, select the event script and hit Run. I experienced the same problem with event scripts in FM13. I don't see this was impoved in FM19.

Best Regards,

Roman