Thanks for your details. However, I enquired about the license agreement/limitation for desktop version as the remote batch processing works is similar to InDesign server.
We need to know whether this is legally allowed for this automation using InDesign desktop version.
It depends who the client is.
If it's a web sevice, you need InDesign Server. If it's a local network service, you need either as many dsktop licenses as the number of clients or a server license.
I think I have not explained well for this clarification.
We are having single InDesign desktop version (CS5) and developed a script to do the following activities:
1. Open InDesign document
2. Import text into the document
3. Formating the layout
4. Create PostScript file
The above mentioned activities are need to do continuously without any manual intervention, meaning the active indesign script looking into the hot folder and initiate automatically whenever the XML placed in the hot folder.
We have done this development and need to confirm whether this remote batch processing script is legally allowed to run in InDesign desktop version as it seems to be server activity.
To answer this question,we'll need to know more about your needs.
Where is this XML coming from, and how?
What is the Postscript file being used for and how?
The XML will be processed in different team and after completion of the XML conversion the file will be copied in the Hot folder for InDesign process.
Also, after completing the page generation in InDesign, the script automatically triggered the export to PS option using pre-defined Preset.
I hope this answered your question.
You can use an automation tool from Enfocus: FullSwitch or PowerSwitch (www.enfocus.com).
But there is still question - if this is ok with License ...
It seems interesting, can you give me more details to do the automation thro' enfocus? I already know that we can create the watch folders to watch the folder for any PDF and then enfocus will generate the Pitstop report immediately, pl. correct me if I'm wrong.
Power Switch is a very interesting and great tool, but writing script for using in it's flow is quite a tricky business: it differs significantly from writing a conventional script for InDesign. Sample scripts I found on Enfocus site are quite primitive and description on writing scripts is scarce -- I had to spend several days experimenting with Switch to figure out how it works. Actually, Switch takes your script and adds some stuff of its own to it. Moreover you have to handle all possible problems since the script should run without user interaction.
But the result is worth of the spent time — a big step in automation. I wrote a version of my Resize Images script for Switch. You just drop a dozen of InDesign packages full of pictures into the "Input" folder and in a few minutes you get documents with resized pictures in the "Output" folder.
Unfortunately, not many scripters know about this potential.
Kasyan, as you are interested in all sorts of automation and do some AppleScript too… have you also looked at 'Folder Action Scripts'. You only need the item added event to kick a script into action. From there you could do script and process in either JS or AS. Enabling and attaching is very straight forward. All you need to get going is…
on adding folder items to This_Folder after receiving These_Items
set ESTKstuff to "alert('A file has been added to your folder…!');"
tell application "Adobe InDesign CS2"
end adding folder items to
You know the rest…
I know about Folder Actions, but what I want to say is that Power Switch allows to rise automation to much higher levels. I discovered this application by chance when I was asked to write a script to be attached to InDesign configurator. And this script is only one step of a complex multi-step flow.
I don't consider myself an expert of Power Switch — I don't use it in my workflow since we can't afford us to buy it. But during the trial period I found a lot of interesting things about it. For example, you can throw the whole package with fonts into the "In" folder, the PS temporarily attaches these fonts, processes the package by script and finally moves it to the "Out" folder. You can also build a fully automated flow (without human intervention) — e.g. open the package, resize "good" images in Photoshop and mark problematic images with red circles on a non-printed layer, then enhance images in another application, export to PDF, check PDFs in Pitstop, etc.
Kasyan, I had not heard of power switch before this. I will have to take the tour and may be give the trial a go if it works both platforms? (Im mac only). These things are always worth checking out. Budget is always the stumbling block for me… As a general rule most of what I try script is the preping of files before they get placed in ID. Folder action scripts are pretty basic but at least its a free option.
Power Switch is available for both platforms. Trial period is 30 days.
If you, or somebody else is interested, I can post the script I wrote.
Here are a few short tips to get you started:
You can add up to 5 arguments which are simple strings that can be passed from the Properties panel in PS to the script.
Attach the script to Command property. Don't use Open and Save in the script -- PS handles them on its own (Open and Save as parameters)
Use $doc in the script instead of activeDocument
If you had any questions, I would gladly answer them. Probably we could even start a new thread on the Power Switch topic.
I would be very interested in the script you wrote for PowerSwitch.
Please post it. Thanks
I just took a bit of time to check out Power Switch, but at $8400, you'll need to have some serious use of this to make it worthwhile...
Wow… I was going to look at that over the winter break… I think CS5 for all the studio is more likely and Im not holding my breath for that… I'll have to make up something else to do now…
Hi, I have an Indesign script, can anybody help me how to create a watched folder for this automation.
I will be dropping a file .indd to watched folder then it will process using the script I created.