Automap 9.0 FAQ
Looking For Answers?
Last Modified: November 22, 2005
WebWorks Automap
The purpose of this article is to outline key information necessary for you to start using WebWorks Automap efficiently. You may expect full documentation to be provided with the product in the future.
Scripting
Which script variables are available at the various stages?
Variable |
Project
|
Target
|
Group
|
Not available when scanning documents in Job Wizard
How does the document retrieval script work when assigned to a group?
The text that is entered into the script editor is saved into a batch file and executed. If the script returns successfully, WebWorks AutoMap will look for a text file at the location specified by the variable “FileListPath” which should contain a line delimited list of documents the user would like to add to the group.
Why are certain variables not available when scanning documents in the Job Wizard or Job Editor?
During the job creation process, the “JobDir” and “JobFile” are not available because the job has not been saved yet., and the “ProjectDir” and “ProjectFile” variables are not available because a WebWorks ePublisher Pro project does not exist yet. They are only available during generation.
What is the current working directory when a script executes?
During generation the current working directory is set to the location of the job file’s directory.
When scanning documents in the Job Editor, the current working directory is the job file’s directory.
When scanning documents in the JobWizard, the current working directory is the location of the temporary script file.
Why does the hierarchy under a group get ignored, when a script is assigned to it?
WebWorks AutoMap will ignore the hierarchy because there currently is no way to specify the location of the documents retrieved by the script. A workaround is to create adjacent groups and place them before or after the group that has a script assigned to it.
Command-Line
Which command-line switches are valid when processing a WebWorks AutoMap job file versus a WebWorks ePublisher Pro project?
|
|
WebWorks AutoMap job (.waj) |
WebWorks ePublisher Pro Project (.wep) |
Deployment
Why does WebWorks AutoMap report “Deployment failed. Can not find the deploy setting in preferences” even though it exists in WebWorks ePublisher Pro preferences?
Currently WebWorks AutoMap does not share preferences with WebWorks ePublisher Pro, so it is necessary to create deploy settings in WebWorks AutoMap that have the same names.
Formats
Why does WebWorks AutoMap reports that it can not load the custom user format when it is trying to generate?
By default WebWorks AutoMap and WebWorks ePublisher Pro both look in the same location for user formats. Verify that in the WebWorks AutoMap application preferences that the “User Format Directory” is pointing to the directory that contains the user format. If the command line interface is being used, the user format directory can be specified by using the “-u” or “--userformats” switches.
Administrator
Why does the job fail to generate when the job is run directly from the Administrator?
The Administrator uses the Windows Task Scheduler to schedule the job. It is recommended that the user specifies the username and password of their account when the “User Information” dialog is displayed.
Preferences
Why are the “File Mapping” and “Deploy Locations” preferences not shared between WebWorks AutoMap and WebWorks ePublisher Pro?
At this time, the preferences between both products are separate, however the user can copy the preferences if they wish to do so.
For file mappings, copy the file at:
C:\Documents and Settings\<username>\Local Settings\Application Data\WebWorks\ePublisherPro\9.0\filemapping.prefs
C:\Documents and Settings\<username>\Local Settings\Application Data\WebWorks\Automap\9.0\filemapping.prefs
For deployment locations, copy the file at:
C:\Documents and Settings\<username>\Local Settings\Application Data\WebWorks\ePublisherPro\9.0\deploy.prefs
C:\Documents and Settings\<username>\Local Settings\Application Data\WebWorks\Automap\9.0\deploy.prefs
