Examples of FrameMaker Automations with Several Practical ExtendScripts
In April 2015, Adobe Partner Rick Quatro of Carmen Publishing was a special guest in a webinar that focused on how repetitious tasks can be economically automated through ExtendScripts for FrameMaker.
Register here to get access to the “FrameMaker Automation Ideas with Example ExtendScripts” webinar recording:
Note: When you follow this link, you will come to our event page. There you will need to click on [REGISTER] to obtain access to the recording. You will receive a confirmation webpage that has a link with the webinar name. Click on this link and you will see title and description, and the [REGISTER] button will have changed to [VIEW NOW].
Minute Markers to Key Concepts in Recording
Why would I want to use ExtendScript? Despite computer power, we find ourselves doing too many repetitive, manual tasks.
DEMO of 1st Script. One of Rick’s client wanted entire project inside one doc, not within a book. Client wished to have the BLANK page at end of Sections to say “THIS PAGE INTENTIONALY LEFT BLANK” … Demo of running the script to auto-apply master page.
DEMO: a view of the script code that was just used for “Intentional Blank” pages
Script that makes impractical tasks more practical … an eExample with tables that behave like “sub-head rows” and need to look different …
Using the Script [ApplySubheadRows.jsx] … (a) the subhead row is placed at top of each page under HEADING ROW … and the most recent instance of a subhead row will appear at top of next page.
How to use a RESTORE script. Exploring the role of markers in this type of script
A marker that is used to note a “Repeat Row” so this row can be deleted in the “Restore” Script which puts table back to its original state.
A script that creates a floating dialog box with all headings, hyperlinked, to allow “one click” navigation
Unusual Script requested by the client, who wished to have a warning before any ELEMENT is deleted from a structured FrameMaker document. This is an EVENT SCRIPT: “waits” for something to happen in FrameMaker before it is invoked. Main purpose was that nothing would be accidentally deleted.
Viewing the above Script to see how “Notification” is set up on line 17. – The “Notify” function on line 21. Line 27 has query to determine that action must be invoked.
Understanding the “Registered” panel of the Script Library menu
Another event script … which will invoke saving an FM doc as MIF … this can be useful for mixed environments where users have more than one version of FrameMaker and you have to “save down” to MIF, so older version of FM will open the file.
Script for saving variable definitions … method is to save variable definitions into a table, with name in column 1, and definition in column 2 (more visual method for managing variables.)
View the script … example, it is even possible to add variables in the FM doc table, and the script will add new variables into the target FM document
Comment/Observation: some of these scripts are not “powerhouse” with dramatic results, but they can save you a tremendous amount of time.
Alternate method in which document data definitions are saved in an XML file, and a script will prompt you to accept values in displayed window – the method shown with this script would work well with machine generated data
Script for structured FrameMaker, to give you an easier way to edit attributes, with ability to TAB from one value to another … This script pops up a dialog box for editing Attributes, which you can easily tab through
Example of Powerhouse Script: BooksToPDF.jsx … does an entire workflow … viewing the “Settings.xml” file for this script. Notice that same book is specified 3x, because different conditions are going to be set for the book. An <outpath> is set for each iteration of PDF output.
DEMO of this book workflow script … start by selecting the Settings.xml file …
Offer scripts in exchange for a charity donation … you can obtain scripts from Rick if you wish to support his charity of choice before late June 2015.