Automator workflow install locations in Leopards

We have several Automator scripts we created for Finder in Leopard. Where do these go? I expect they should go:
/Library/Application\ Support/Apple/Automator/Workflows/Applications/Finder/
But I noticed this directory:
/Library/Automator/
And this one:
~/Library/Automator
We want these Automator scripts to show up in users' Finder contextual menu. More importantly, we want to manage these Automator scripts in one place (so they should NOT go into the home directory).
Thanks,
Don

red_menace wrote:
The Application Support directories are just that - places for an application to put additional support files for it's use. The contextual workflows look like they would be similar to the Scripts menu, in that the items are defined and only work from the user's library. For a shared library of workflows, you would need to store them in an accessible place, such as Shared (or Library, but an admin will need to create the folder there), and then have each user copy or make an alias and place it in their ~Library/Workflows/Applications/Finder/ folder.
Users should no have to do anything if we push the *.workflow files to the correct locations. OSX is designed to be manageable at the local level, user level, etc. We have several *.workflow files that we need to push out to several dozen workstations. Each workstation can potentially have several dozen home directories. It's not possible (or desirable) to manage this deployment in a way that requires user intervention. I'm pretty sure a previous poster was right, that they *.workflow files belong here:
/Library/Application\ Support/Apple/Automator/Workflows/Finder/
We'll do some more testing (I'll keep monitoring this forum). I'll also post to the admin lists to see how other enterprise management folk are handling distribution of *.workflow files in managed environments (where users are non-admin, on workstations bound to AD/OD). Once this is all done I'll follow up with this thread and mark it as closed.
Thanks,
Don

Similar Messages

I want to write a script or Automator workflow/app that emails a random shortcut of the day to three recipients. The source is from an Excel spreadsheet. One column is the shortcut, and the second column is the definition. Anyone have experience?

I want to write a script or Automator workflow/app that automatically emails a random shortcut of the day to three recipients. The source is from an Excel spreadsheet. One column is the shortcut, and the second column is the definition. Anyone have similar experience and know that this would work?

I have had a first stab at the script, below. It uses a file to store the shortcuts and command [descriptions]. You should be able to see from the script annotations how to add a new one. (I populated 1-4 with real data, but got lazy after that, so you have a few placeholders to work with first.
As I have noted, once you are happy that you have all the data in the file, you can comment out part of the script for ongoing use. (BTW, my reluctance to use Excel is that I don't currently have it installed and I don't want to offer wrong advice. If you have Numbers, I do have that and could probably modify to work with a spreadsheet from there. This might be especially useful if you have the data already sitting in Excel.)
A few things came-up whilist I was writing the script:
1.     Currently, all recipients will not only get the same tip at the same time, but they will see the names and email addresses of the others who receive them. It is possible to modify this.
2.     I have added a property gRandomCheck which keeps track of which shortcut has already been used (since the last time the script was compiled. This will prevent the same tip being sent more than once.    When all tips have been sent once, the script will alert you and not send anything until reset. It does not check on a per-addressee basis (which would be a refinement). (If you add a new addressee at this stage, the whole process will start again, and you may not really want this to be the behaviour.)
3.     The way that I have built the list, commandList, is deliberately cumbersome - it's for the sake of clarity. If you prefer, you can construct the whole list as {{shortcut:"X", command:"X"}, {shortcut:"Y", command:"Y"}}
Have a look - I am sure you will have questions!
SCRIPT STARTS HERE Paste the following lines (thru the end) into a new AppleScript Editor document and press RUN
--The property gRandomCheck persists between runs and is used to stop sending the same hint twice.
property gRandomCheck : {}
--I am defining a file on the desktop. It doesn't have to be in this location
set theFolder to path to desktop
set commandFile to (theFolder as text) & "CommandFile.csv"
--(* Unless you need to change the file contents you do not need to write to it each time. Remove the "--" on this line and before the asterisk about 18 lines below
--Follow this format and enter as many records as you like on a new line - each with a unique name
set record1 to {shortcut:"Z", command:"Undo"}
set record2 to {shortcut:"R", command:"Record"}
set record3 to {shortcut:"⇧R", command:"Record Toggle"}
set record4 to {shortcut:"⌘.", command:"Discard Recording & Return to Last Play Position"}
set record5 to {shortcut:"X", command:"x"}
set record6 to {shortcut:"X", command:"x"}
set record7 to {shortcut:"X", command:"x"}
set record8 to {shortcut:"X", command:"x"}
set record9 to {shortcut:"X", command:"x"}
set record10 to {shortcut:"X", command:"x"}
set record11 to {shortcut:"X", command:"x"}
set record12 to {shortcut:"X", command:"x"}
set record13 to {shortcut:"X", command:"x"}
--Make sure you add the record name before randomCheck:
set commandList to {record1, record2, record3, record4, record5, record6, record7, record8, record9, record10, record11, record12, record13}
--This part writes the above records to the file each time.
set fileRef to open for access commandFile with write permission
set eof of fileRef to 0
write commandList to fileRef starting at eof as list
close access fileRef
--remove "--" here to stop writing (see above)*)
--This reads from the file
set fileRef to open for access commandFile with write permission
set commandList to read fileRef as list
close access fileRef
--Here's where the random record is chosen
set selected to 0
if (count of gRandomCheck) is not (count of commandList) then
          repeat
                    set selected to (random number from 1 to (count of commandList))
                    if selected is not in gRandomCheck then
                              set gRandomCheck to gRandomCheck & selected
                              exit repeat
                    end if
          end repeat
else
          display dialog "You have sent all shortcuts to all recipients once. Recompile to reset"
          return
end if
--This is setting-up the format of the mail contents
set messageText to ("Shortcut: " & shortcut of record selected of commandList & return & "Command: " & command of record selected of commandList)
tell application "Mail"
--When you're ready to use, you probably will not want Mail popping to the front, so add "--" before activate
activate
--You can change the subject of the message here. You can also set visible:true to visible:false when you are happy all is working OK
          set theMessage to (make new outgoing message with properties {visible:true, subject:"Today's Logic Pro Shortcut", content:messageText})
          tell theMessage
--You can add new recipients here. Just add a new line. Modify the names and addresses here to real ones
                    make new to recipient with properties {name:"Fred Smith", address:"[email protected]"}
                    make new to recipient with properties {name:"John Smith", address:"[email protected]"}
--When you are ready to start sending, remove the dashes before "send" below
--send
          end tell
end tell

How to apply multiple automator workflows to one file

Hi everyone,
I've set up a few workflow applications to automate the process of making packshots from PDF files. The way those roughly work is they create a temporary copy in a folder, open a Photoshop droplet that executes all the actions on the file, and then save the finished product in a "finished" folder.
However, we frequently need to deliver multiple packshots made from the same file. I was asked to make one automator app that allowed us to drop the PDF version on it, resulting in the multiple types of packshots in the "finished" folder, together with the original PDF.
The way I have this set up right now is as follows:
1) Copy the original PDF file to the "finished" folder
2) Execute the first automator app
3) Execute the second automator app
This seems simple enough, and does work in 10.6.8. When I try it on a different computer in our studio though, with 10.7 installed, I get various errors:
- Sometimes it says an error occured within one of the automator apps, while the app works fine when running it seperately (on all computers).
- Sometimes it says something like "An error occurred while converting the data" when moving on from the first application to the second application
- Sometimes I'll get an error message in the log, saying:
*** -[_NSArrayl objectAtIndex:]: index 0 beyond bounds for empty array
What I got from this is that it's actually not getting the right input it requires (or not getting any input, since it's an empty array). However, the previous task is set to "return the task input" (our systems are Dutch so excuse me for any discrepancies in translations please), and the resulting output that I get seems to be what I want the next automator application to use. Below is a screenshot of the error message:
What I've tried:
- I read somewhere that the newer versions of Automator require the action "Retrieve selected finder items" between them. I've tried using this in various ways (between all other actions/tasks, only before the second application to be run and before both applications to be run), but with no success. The problem I have with these is that, during the applications, it moves the files around, thus apparently selecting those folders as well.
- Building an entirely new workflow on the newer system
- Using "Start application" instead of "Execute Automator workflow". This results in Automator saying that it did execute the workflow while nothing happened.
- Using "Ignore input" for the second application. This also results in Automator saying that it executed the workflow while nothing happened.
So right now, I'm pretty stumped as to how to get this combination of apps to work in 10.7. Any solutions or workarounds are most welcome.
Thanks in advance!

Yes, angelanna. You can merge or split your video file via FCP sequence.
ahaah, maybe I think angelanna would like to get the resulting file with MTS format because he mentioned “No need to be compressed”. Are you asking for this, angelanna?
If so, a simple MTS files managing and editing tool is needed. Maybe you can have a try the Mac version of Aunsoft Final Mate for managing HD camcorder footages. I just downloaded its free trial version and it offers a simple way of garping footages directly from camcorder. And also it provides a attractive feature to join flawlessly and split accurately native MTS files for video file output with original MTS format.
Maybe this is the tool cwhich an help you out, angelanna.
Enjoy your video.

I am trying to do a clean install of Snow Leopard on an Intel Macbook Pro. (Need to partition for Boot Camp) I have done it in the past so I know it works but whenever I select the install disk as the boot device it gets stuck on the Apple logo/pinwheel.

Prety much what the question says. HELP!

stephenfromlynchburg wrote:
No the mac had come with Leopard. Then I bought the snow leopard DVD and did a clean install of snow leopard.
If you just stuck the disk into the Leopard Mac and run the upgrader, you didn't do a "fresh install" you basically upgraded from 10.5 to 10.6 leaving all the programs and files intact.
The white Snow Leopard disk was the right one for that machine as it had Leopard (10.5) on it previously.
So you already have Snow Leopard installed, if you want to erase the entire drive (along with all your programs, files and OS X) and want to install Snow Leopard again, you hold the c or option/alt key down and boot the machine off the disk. Then use Disk Utiltiy to erase the entire drive, then quit and install Snow Leopard.
How to erase and install Snow Leopard 10.6
Once Snow Leopard is installed you log in and use Apple Menu > Software Update until clear to get to 10.6.8 and fix security issues.
Now I can't get it to do the install again.
To install Windows into BootCamp, you read and run the BootCamp Assistant located in the Applications > Utiltiies folder
It's important to change the drive format from FAT32 to NTFS before installing Windows using the Windows disk.
Windows is rather complicated to install, if you boot to a blinking line with "press any key to continue" you need to press and hold the power button down and reboot holding the Option/Alt key down to get back into OS X.
https://www.apple.com/support/bootcamp/
If your Windows programs are not going to be as CPU/GPU demanding, you may rather prefer to use a virtual machine instead
Windows in BootCamp or Virtual Machine?

Getting File Name in Automator workflow - combine PDF

I am using Automator to combine 2 PDF files.
I would like to inherit one of the file names in the new PDF and append a standard text to the front of the file name.
I am not sure how to do this. I can combine the PDFs the way I would like, but I am not sure how to plick the file name.
my workflow is as follows.
Folder Action targets folder where 1st PDF is added(I want this FILE NAME).
Ger Specified finder item selects 2nd PDF to be combined.
Sort Finder Items makes sure the new PDF pages are ordered properly.
Combine PDF Pages combines the pages.
Move Finder Items saves the files where i want it.
Name single item is whre i thought to add my standard text plus the variable of FILE NAME.
Open File in mail to set up my email.
Anyone can help with this?
thanks,
Aaron

Here is an automator workflow that does something similar so I believe you can adapt to your needs. This workflow is setup as a service workflow. It will combine PDFs in the order in which they are selected/clicked via the Shift key. The default name of the combined output file will be the name of the first file clicked. Automator can be activated by CTRL clicking any of the selected PDFs.
1. Service receives PDF files in Finder
2. Automator Action: Run AppleScript
on run {input, parameters}
          display dialog "Files will be combined in the order selected via the Shift key" as text
          return input
end run
3.. Automator Action: Trim input items
keep the first one
you will need to download and install this autotmator action from here:
http://www.menace-enterprises.com/Files/Automator/Actions/Trim%20Input%20Items.d mg
4. Automator Action: Run AppleScript
(* Note & Definitions
This Applescript extracts the basename of the first selected file without its .pdf extension
"path_basename_ext" is full path and name, e.g. User/desktop/file.pdf
"NmExt" is filename with extension, e.g. file.pdf
"baseName" is the base filename without extension, e.g. file
"Ext" is the file's extension, e.g. pdf
on run {input, parameters}
          set path_basename_ext to input
          tell (info for path_basename_ext) to set {NmExt, Ext} to {name, name extension}
          set baseName to text 1 thru ((get offset of "." & Ext in NmExt) - 1) of NmExt
baseName
          return baseName
end run
5. Automator Action: Set Value of Variable
define baseName as the variable
6. Automator Action: Get selected finder items
Options: check ignore input
7. Automator Action: Combine PDF pages
choose Combine by appending
8. Automator Action: Move Finder Items
choose To: Desktop
Options: check show this action when workflow runs
9. Name Single Items
choose Basename only to: baseName
Options: check show this action when workflow runs
10. Open Finder Items

Old Toad's automator workflow to backup Library6.iPhoto database

Dear Old Toad,
I just today downloaded your workflow to backup the iPhoto database file, and am having problems making it work.
When I run it, either from the dock or the script menu, it launches Automator but then closes without doing anything. I don't get a confirmation screen, and no copy of the database is created.
So I opened it in Automator to see if editing it would help, even though my library is already named iPhoto Library and stored in user/pictures. When I dragged it onto the Automator window, there was only 1 action (Get Specified Finder Items) instead of the 4 that show up in the ReadMe. When I dragged it onto the Automator app to open it, I got nothing.
I downloaded it via Firefox 3.0.1 and got a 1.1MB zip, and I tried downloading it twice in case it had corrupted in the download, but no change with the second try. Downloaded from here:
http://web.mac.com/toad.hall/ToadsCellar/ToadsCellar.html
Running OS 10.4.11, iPhoto 7.1.5, on a G4.
Something else I can try?
Thanks,
Daiya
Message was edited by: Daiya

Yes. Run the application like you would use the Save command in other applications, often. Running it again will overwrite the current backup copy with a new backup that will include all changes you've made to your library, new pictures, deletions, slideshows, books, etc.
I suggested keeping it in the dock so you can quickly run it after any changes you've made to the library. Being in the Dock makes it more convenient than having to go into the Application folder and launching it from there.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Every time I sign into my Macbook, I get an error message from Automator; "The data couldn't be read because it has been corrupted.". I have never created an Automator workflow. How do I find out what Automator is trying to run and stop it?

Every time I sign into my Macbook, I get an error message from Automator; "The data couldn't be read because it has been corrupted.". I have never created an Automator workflow. How do I find out what Automator is trying to run and stop it?

Maybe it's set as a login item:
- System Preferences: Users and Groups:
- Highlight your user account in the left pane/list
- Click "Login" tab at the top.
See if you have an Automater action on the list
- Note, you can select it, then right-click, and can then select "Reveal in Finder". That way you might have an idea what installed it.

Automator Workflow to export Numbers documents in PDF format

Does anyone know of any automator workflow to export Numbers documents in PDF format? I tried this program: Convert to PDF 1.2
http://www.apple.com/downloads/macosx/automator/converttopdf_mauriziominelli.htm l
But it gives an error.

Reading carefully is often useful.
The description of the tool which you tried clearly states :
*About Convert to PDF*
*_Convert all of your text files to PDF_. This action uses the underlying cups printing system ability to convert files, it’s a simple front end to the command line tool cupsfilter.*
As far as I know, but maybe you don't, *_a Numbers document isn't a text file._*
I already posted a script exporting Numbers documents as PDF.
Here is an enhanced version which apply only to Numbers '09 (or maybe higher) :
--[SCRIPT save2Numbers&PDF.app]
Enregistrer le script en tant que Script : save2Numbers&PDF.scpt
déplacer le fichier créé dans le dossier
<VolumeDeDémarrage>:Users:<votreCompte>:Library:Scripts:Applications:Numbers:
Il vous faudra peut-être créer le dossier Numbers et peut-être même le dossier Applications.
aller au menu Scripts , choisir Numbers puis choisir save2Numbers&PDF
Le script enregistre le document au format natif de Numbers
et l'enregistre dans un fichier PDF.
S'il existe déjà un PDF homonyme, il est renommé en lui ajoutant une chaîne
construite sur sa date de modification.
--=====
L'aide du Finder explique:
L'Utilitaire AppleScript permet d'activer le Menu des scripts :
Ouvrez l'Utilitaire AppleScript situé dans le dossier Applications/AppleScript.
Cochez la case "Afficher le menu des scripts dans la barre de menus".
+++++++
Save the script
as a Script: save2Numbers&PDF.scpt
Move the newly created file into the folder:
<startup Volume>:Users:<yourAccount>:Library:Scripts:Applications:Numbers:
Maybe you would have to create the folder Numbers and even the folder Applications by yourself.
go to the Scripts Menu, choose Numbers, then choose save2Numbers&PDF
The script saves the document in the native Numbers format and saves it in a .pdf file
If such a .pdf already exists, it is renamed with a stamp matching its modification date.
--=====
The Finder's Help explains:
To make the Script menu appear:
Open the AppleScript utility located in Applications/AppleScript.
Select the "Show Script Menu in menu bar" checkbox
--=====
Yvan KOENIG (VALLAURIS, France)
modifié 2010/08/17
property closeIt : true
(* true = closes the saved document
false = doesn't close it *)
property theApp : "Numbers"
property theExt : "numbers"
--=====
on run
tell application theApp
activate
set le_document to front document
if modified of le_document then save le_document
delay 0.2
set thePath to path of document 1
end tell -- theapp
set {xPath, xExt} to my saveAs(thePath)
if closeIt then tell application theApp to close document 1 saving no
end run
--=====
on saveAs(p)
local extension_export, type_export, nomde_loriginal, dossierde_loriginal, nomde_lexport, cheminde_lexport
set {extension_export, type_export} to {"pdf", "LSDocumentTypePDF"}
set {nomde_loriginal, dossierde_loriginal} to my quelNomEtDossier(p)
if nomde_loriginal ends with theExt then
• replace the original extension by the xExt one *)
set nomde_lexport to (text 1 thru -(1 + (length of theExt)) of nomde_loriginal) & extension_export
else
• add the xExt extension name *)
set nomde_lexport to nomde_loriginal & "." & extension_export
end if
set cheminde_lexport to dossierde_loriginal & nomde_lexport
• CAUTION, When saving, Numbers doesn't take care of an existing document.
It replaces it by the new one. *)
tell application "System Events"
if exists (file cheminde_lexport) then
Playing safety, we rename the existing file by inserting a modificationdatetime stamp *)
set name of file cheminde_lexport to (text 1 thru -(2 + (length of extension_export)) of nomde_lexport) & my horoDateur(modification date of file cheminde_lexport) & "." & extension_export
end if
end tell -- System Events
• save as type_export document *)
tell application "Numbers" to save document nomde_loriginal as type_export in cheminde_lexport
return {cheminde_lexport, extension_export}
end saveAs
-- =====
on quelNomEtDossier(f)
local nom, dossier
tell application "System Events" to tell file (f as Unicode text)
set nom to name (* Unicode text *)
set dossier to path of container (* Unicode HFS path *)
end tell -- to System Events
return {nom, dossier}
end quelNomEtDossier
--=====
• Build a stamp from the modification date_time
on horoDateur(datedemodification)
local les_secondes
set les_secondes to time of datedemodification
return ("_" & year of datedemodification & text -2 thru -1 of ("0" & (month of datedemodification as integer)) & text -2 thru -1 of ("0" & day of datedemodification) & "_" & text -2 thru -1 of ("0" & les_secondes div 3600) & text -2 thru -1 of ("0" & (les_secondes mod 3600) div 60) & text -2 thru -1 of ("0" & les_secondes mod 60))
(* Here, the stamp is "YYYYMMDDhhmmss" *)
end horoDateur
--=====
--[/SCRIPT]
Yvan KOENIG (VALLAURIS, France) mardi 17 août 2010 18:16:27

Automator Workflow

Hi
I have created a workflow for automator to send me an email for birthdays coming up in the next 2 weeks, if i save this as an app it runs fine
But when is put an event into iCal to alarm and open either the automator workflow or application, it doesnt work
I am at a loss as to why ?
Any clues ! (Its on OSX Snow Leopard 10.6 and iWork 09)
Regards
Dave

Unless I am mistaken that first action is actually Find Address Book Items in disguise. Once dropped in place the name changes to either Find People or Find Groups depending upon whether it is set to groups or people. That seems to be the step that is causing problems for me. When I remove it the new workflow sends.
Here's what I have right now although it does not give me the option of searching two months ahead like one of my previous workflows did. I added a blank line after Stop If iInput is Empty just to make it easier to read.
Find People with Birthdays
Send Birthday Greetings
Send Outgoing Messages
Stop If Input Is Empty
Find People With Birthdays
Get Contact Information
New Mail Message
Send Outgoing Messages
The block of steps that includes Stop If Input Is Empty sends a birthday greeting to people having a birthday. The second block sends me a confirmation email with the contact information of the people who were sent greetings. If you want to see what the original workflow looks like check out http://www.atpm.com/12.08/automator.shtml

Automator/Workflow actions are in "slow-motion" under Mac OS X 10.6.x

Hi,
after the update to SL some of my Automator Workflows dont work properly.
I do things like copy some part of sentence from a .rtf document and insert it into a input box of a website in firefox.
In 10.5.8 everything worked like a charm. But in 10.6.x the same workflow (also new created) works some times and the other time it slows down and the cursor moves like a slow-motion. Pixel for pixel and i cannot stop the workflow. I only can wait until the workflow is finished (takes in "slow-down" mode 30 minutes) or i do a hardreset. I wonder if anyone else such of this problems with automator under 10.6
I tested the same things with my mac mini that i didnt upgraded and it works like expected.
I think you can reproduce the behaviour, if you create a new .rtf document with numbers from one to twelve and make a workflow where you mark 4 letters, cut, bring firefox to front, paste into form, go to .rtf, mark next 4 letters, cut, go to firefox, paste into form, doing that until there are no more letters.
very curious...

the whole automator and in particular the record action was substantially rewritten in snow leopard. and the record action is slow, unreliable and you can't trouble-shoot it. it's a wonder it works at all. the only advice i can give is to use it as little as possible. if at all possible avoid it altogether. if you do need to use it try using keyboard strokes instead of the mouse movement. for example. use command+c and command+v for copying and pasting and use tabbing to choose the correct box on the page.

AppleScript error -609 in Automator workflow

I created an AppleScript on one computer and incorporated it in an Automator workflow. The script works perfectly well stand-alone or as part of the workflow.
Then I copied both files to a headless computer via VNC. I adjusted the workflow to look at the new location of the script, and the script itself to look at the new location of the file it's processing. Now, on that second computer, the script works perfectly well by itself, but I get AppleScript error -609 Connection Is Invalid if it's run from the workflow.
For testing purposes I reduced the script to its simplest expression:
tell application "Finder"
end tell
and it's still generating the error.
Strangely, from the workflow the full script does what's it's supposed to, but the workflow stops because of the error. The error appears even if this script is alone in the workflow. Does anybody know what it means?

That error means that the script wasn't able to communicate with the targeted application properly, which can happen if the application crashes while the script is running. If that error doesn't cause any problems, it's appearance can be suppressed:
try
(your code)
on error number -609
end try
This construct will not execute any code on or after the line which produces the error.
(32099)

Mountain Lion installer will not let me choose my Lion Partition as an install location

Mountain Lion installer will not let me choose my Lion Partition as an install location.
Any ideas why?

Again, why will the Mountain Lion installer not allow me to select my Lion partition as the location for the install?
Good question. That's the main way it's supposed to be installed. You shouldn't even need to choose a partition. You purchase Mountain Lion through the App Store, it downloads to the Applications folder and automatically begins the installation on the drive where Lion or Snow Leopard resides as soon as the download is complete.

Automator Workflow for Mail Printing?????

How can I print out all all mail (250 emails) in a single mailbox into a single file, which I can save as a PDF?
I looked even for an Automator workflow that would
Print; Preview: Save As
so that I would then have a serires of PDFs that I could then import all the individual PDF pages in to Acrobat to create a single document, but Automator does not have these options.
Any thougt would be very helpful. Thanks!!
Mac OS X (10.4.2)

I don't believe you can do it the first way.
However there are at least three ways to do it the second way.
1) Use System Events GUI scripting exclusively to drive the user interface i.e., selecting menu items and pushing buttons;
2) Use some of 1) along with Mail's AppleScripting capabilities. GUI scripting would still be needed for Preview as it does not have AppleScript capabilities;
3) Install the cups-pdf solution called "Virtual Printer" (http://www.macupdate.com/info.php/id/20219) that allows one to create pdf files from anything that can be printed using the print dialog. This would also have to be driven using one or both of GUI scripting and Applescript.
If you do a lot of PDF printing then I would recommend 3) and generally 1) is less robust than 2). Myself or others on this forum should be able to help with whichever solution you prefer.

How to install Lion over Leopard if I already have the InstallESD.dmg file?

How can I install Lion over Leopard? I know everyone keeps saying you have to have Snow Leopard, but it seems that you only need it to actually download the file. I have the file and I've created a back-up disk and drive (using a 4gb card) and nothing worked. I don't understand why I can't install even if I have the file. The computer doesn't even recognize the disk when I press option at start up but it recoginizes it as Lion when fully logged in. I can't install using the .pkg file because it says it can't be installed on the running system. I have tried to use the drive and it gives me a EFI Boot when I press option at start up and so I click on it and It goes to the apple grey screen with the circle circling below it. But after a while, that apple turns into a No sign basically. So what else do I need to change or edit to install Lion over Leopard. The startup disk nor the drive are working.

The Lion installer is not a bootable device. You must run the installer like any other application. Since the installer will only upgrade Snow Leopard it may refuse to run. What you might try is putting a bootable Snow Leopard system onto a 16 GB USB flash drive, drag the Lion installer application into the Applications folder, boot the computer from the flash drive then run the Lion installer.
As for creating your own bootable flash drive you will need an 8 GB flash drive for that:
Make Your Own Lion Installer
1. After downloading Lion you must first save the Install Mac OS X Lion application. After Lion downloads DO NOT click on the Install button. Go to your Applications folder and make a copy of the Lion installer. Move the copy into your Downloads folder. Now you can click on the Install button. You must do this because the installer deletes itself automatically when it finishes installing Lion.
2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
Open Disk Utility in your Utilities folder.
After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
Click on the Erase button. The format process can take up to several hours depending upon the drive size.
3. Locate the saved Lion installer in your Downloads folder. CTRL- or RIGHT-click on the installer and select Show Package Contents from the contextual menu. Double-click on the Contents folder to open it. Double-click on the SharedSupport folder. In this folder you will see a disc image named InstallESD.dmg.
4. Plug in your freshly prepared USB flash drive. You are going to clone the InstallESD.dmg disc image to the flash drive as follows:
Open Disk Utility.
Select the USB flash drive from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the USB flash drive volume from the left side list and drag it to the Destination entry field.
Drag the InstallESD.dmg disc image file into the Source entry field.
Double-check you got it right, then click on the Restore button.
When the clone is completed you have a fully bootable Lion installer that you can use without having to re-download Lion.

Automator Workflow as Finder Plug In Doesn't Seem to Work Correctly

Has anyone noticed that if you create an Automator Workflow as a Finder Plug-in in Leopard it does not seem to work correctly or at all?
I have a two action Workflow.
1. Get Selected Finder Items
2. Import Files into iPhoto
When run inside Automator, it works fine. If I save as Finder Plug-in and use it in the Finder, it gets to the second action and dies.
I've seen other posts about Finder Plug-in weirdness and was wondering if this was another symptom.

Yes, I found this out today. Any Finder Workflow that I start with "Get Selected Finder Items" does not work. Hope they fix this soon ...that's an important one to work.

Automator workflow install locations in Leopards

Similar Messages

Maybe you are looking for