Discussion
Originator: BenAllums
Created on: 2010-09-14 15:32:02
Mike,
AutoMap does currently allow you to rescan all files in the job when you switch over to the Target configuration panel and hit the "Scan" button for conditions and variables. Is this not doing what you need?
No, it does not seem to work that way. (Lauren and I investigated this last week.) You can only scan the object selected in the Documents tree. This is different from ePublisher Pro which allows you to "scan all" the documents in the project. Selecting the group does not seem to scan all documents within the group.
Further, when the selected document is a Framemaker .book, the scan does not go into the child documents (the .fm docs in the .book); rather, it only looks at the .book file. This is different from ePublisher Pro.
I jut want to be able to "Scan All" and go through all documents in the project to find out what changed since the stationary or job was created.
Mike,
Thanks for clarifying.
Just to be sure, I have an Automap job with 1 group that contains FM books.
+Help - Book1 - Book2
Variables were defined in the job when the job was created. They appear to have been sourced from the stationary.
If you now add a variable "FooVar" to ALL of the .fm and .book files, there is no way to get that variable to appear in the Automap Job editor. None of the scan techniques in Automap can find it.
If on the other hand, the job contains a single .fm file, you can "scan" that file in Automap and the variable will appear. So maybe there is a bug hidden in this feature request.