jdfwarrior

Which "Shared" folder are you referring to? By default, Alfred should be saving all his preferences in ~/Library/Application Support/Alfred 2/. That is assuming you were using Alfred 2 before. Check that location for the Alfred.alfredpreferences file. If it exists, copy it, go to that location on the new user account, delete the existing preferences file and replace it with the copy of the old file. Be sure to take ownership of the file to ensure you have permissions to it.

If you use Dropbox or something else to sync preferences you could use that tool to undelete the files that stores them. If not, heres a link to download a folder of all the default web searches. Drop it in ~/Library/Application Support/Alfred 2/Alfred.alfredpreferences/preferences/features/

Try using full path rather than relative paths or paths beginning with ~. See if that fixes it.

To expand a little on Vitor's response, in an effort to remain as lean and fast as possible alfred doesn't include any sort of monitoring capability to let you perform things like this. You could potentially do such things with workflows depending on your knowledge with programming/scripting or with using cron jobs

You didn't include the actual automator workflow with the alfred workflow. I haven't messed with csh before but from the looks of it, it seems like its just building onto the mailto and then opening that url with IBM Notes. I'm not a big csh guy but could knock this out really quickly with PHP.
 
Try the workflow attached here and let me know if this works please.
 
It does just as I mentioned above. It builds a custom mailto url that is opened with IBM Notes.

I created a quick workflow for you to quickly jump back to Finder. Download it here.
 
I left the keyword blank because I wasn't sure if you wanted one. The hotkey will also need to be set for this action.
 
I'll consult with Andrew but right this second I'm unaware of a way to perform the other action (returning to the previous app). Simulating the hotkey through AppleScript doesn't seem to want to work well. Perhaps he has an idea of a way that we can get this accomplished.

To get the best experience from this (where you can see what values are being used in what places) your best bet would be to use a script filter and to parse the input from the user (you) and then create fields based on that. Based on your example, you would have to read the user input, split the input using a / as a delimiter, then count the number of items then assign each piece from the split to a field, e.g. field 1 = to, field 2 = cc, etc.. and then build the URL from that. With the script filter, as you enter the individual fields, you could have it list them as results in Alfred so you could see how the input was being parsed.
 
Some of the examples here may be a start if you want to try to learn/tackle this yourself. If not, myself or some of the other guys around here I'm sure could help you.

The Format
 
** This will be an evolving document. Check here for updates and new documentation. **
 
There is also an XML format example available in Alfred 2 preferences. To see it, open Alfred Preferences, navigate to Workflows. Click the + i nthe bottom right corner of the installed workflows list, select Examples->Script Filter XML format.
 
Result feedback is generated by returning an XML string back to Alfred from a Script Filter item in your Workflow. Script Filters are the only way to pass feedback to Alfred. The following is an example XML string that would be returned to Alfred.
<?xml version="1.0"?> <items> <item uid="rdioartist" arg="r96664" valid="yes" autocomplete="Incubus"> <title>Incubus</title> <subtitle>Artist</subtitle> <icon>rdio-artist.png</icon> </item> <item uid="albumart" arg="/Users/user/Documents/album.jpg" type="file"> <title>Incubus Album Art</title> <subtitle>Album Art for Science</subtitle> <icon type="filetype">public.jpeg</icon> </item> </items> Results will be returned as a list of "items", with each one being an "item" inside. Each item has several arguments and pieces of information associated with it.
 
Item Attributes
 
uid (optional in Alfred 2.0.3+)
The uid attribute is a value that is used to help Alfred learn about your results. You know that Alfred learns based on the items you use the most. That same mechanism can be used in feedback results. Give your results a unique identifier and Alfred will learn which ones you use the most and prioritize them by moving them up in the result list.
 
As of Alfred 2.0.3, this attribute is now optional. If no uid is provided, Alfred will simply generate a UUID. This will allow you to maintain a specific order of generated feedback. Previously, the uid (if not unique for each result) would be added to Alfred's knowledge and would be prioritized in later executions.
 
arg
The arg attribute is the value that is passed to the next portion of the workflow when the result item is selected in the Alfred results list. So if you pressed enter on the sample item above, the value 'r96664' would be passed to a shell script, applescript, or any of the other Action items.
 
type
The type attribute allows you to specify what type of result you are generating. Currently, the only value available for this attribute is file. This will allow you to specify that the feedback item is a file and allows you to use Result Actions on the feedback item.
 
 
valid ( optional - Defaults to 'yes' )
The valid attribute allows you to specify whether or not the result item is a "valid", actionable item. Valid values for this attribute are 'yes' or 'no'. By setting a result's valid attribute to 'no', the item won't be actioned when this item is selected and you press Return. This allows you to provide result items that are only for information or for help in auto completing information (See autocomplete flag below).
 
autocomplete ( optional - Only available when valid = no )
The autocomplete attribute is only used when the valid attribute has been set to 'no'. When attempting to action an item that has the valid attribute set to 'no' and an autocomplete value is specified, the autocomplete value is inserted into the Alfred window. When using this attribute, the arg attribute is ignored.
 
Elements
 
title
The title element is the value that is shown in large text as the title for the result item. This is the main text/title shown in the results list.
 
subtitle
The subtitle element is the value shown under the title in the results list. When performing normal searches within Alfred, this is the area where you would normally see the file path.
 
icon ( optional - If not icon value is available, the icon will be blank. If the icon element is not present, a folder icon will be used )
The icon element allows you to specify the icon to use for your result item. This can be a file located in your workflow directory, an icon of a file type on your local machine, or the icon of a specific file on your system. To use the icons of a specific file type or another folder/file, you must provide a type attribute to the icon item. 
Example: <icon type="fileicon">/Applications</icon> - Use the icon associated to /Applications
Example: <icon type="filetype">public.folder</icon> - Use the public.folder (default folder) icon

You could accomplish this by creating a workflow and adding a hotkey and a Run Script item. Set your hotkey and for the Run Script, set your language to /usr/bin/osascript.
In the script area, use this code..
tell application "Finder" to make new Finder window That should get what you are looking for

Yup, to launch an app or just show a window, "activate" is the way. Glad you got it figured out.

Could be that the hotkey that you are attempting to assign to this feature is one that is already in use somewhere else? Have you tried any other hotkey combinations to see if it allows you to set it to another combination?

Pop open Alfred's preferences and go to Features->Default Results. There is a button at the bottom labeled "Setup fallback results". That should allow you to setup DDG or any of the other search engines as the default fallback.

I need to go back and take a look at it again. Everything seemed to work perfectly on my machines at home (iMac and Macbook Air) but when I distributed to others, it broke. I'm not sure what the issue was unless it was a difference in Plex config somewhere (not sure what it would have been) or a difference in server version or what.
 
I may just put what I have up on Github and let others fork it and tinker with it as well and see what they can come up with.

So, you use the ISBN number to reference a file. How are the files organized on the server? Are they all located in one large folder? Organized into some kind of structure? If they are all in one large folder that could be referenced, it would GREATLY simplify things and make it so much fast. I am however talking about alternate scripts similar to what Vitor was referencing. As he mentioned, AppleScript has its place, but I think there are better ways to accomplish this. The reason if would be so much easier if they are lumped into one folder is because, if they aren't.. it being a network resource, I doubt Spotlight indexes the location. That being said, Alfred isn't going to easily find them. Searching a directory structure would be a manual process in the script to incrementally dive deeper into the file structure searching for the file. This process does work but can be VERY slow deepening on the the depth of the file structure and network connection speed.

Recommendations for Sharing Workflows
 
The forums have really been running well and you guys (and gals) have been creating some amazing workflows so far. I wanted to throw out a few suggestions though to make sure things stay organized, are easy to read, and easy to find.
 
This will be an evolving document. Check back for questions regarding questions on posting your workflows. If you have a question that isn't answered within the contents of this thread, feel free to contact any of the moderators (Myself, Andrew, or Vero). 
 
Post Titles
Be specific. Don't be overly descriptive about every little feature the workflow provides. Titles are best kept to the workflow name, and potentially a few words on the overall gist of what it does.
 
Tags
Be sure to set topic tags for your workflow post. This will make it easier for users searching on the forums to find your post/workflow easily based off of a few key words.
 
Dependencies
Please include a listing of all dependencies for your workflow. This will hopefully alleviate potential problems that users run into from attempting to run an installed workflow without an installed package being present. Examples of this would be Ruby gems or Python modules or even Python versions that are required for using the workflow. If a specific application is required for your workflow to function, be sure to include a link to that applications website, or a link to it in the App Store as well. Also include, if necessary, required versions of OS X.
 
System Modifications
If your workflow creates or modifies any supporting files that would alter the users environment, this should be noted. This will make it known up front that your workflow modifies system file X to achieve its functionality. Also, if the user uninstalls the workflow, how to remove these files or restore the originals.
 
Screenshots
They aren't required, but providing a screenshot or two for your workflow helps provide users with a good idea of what it is they are about to download. Descriptions help, but many users are wanting to pop in, get a quick visual, and download.
 
Posting
When sharing a new workflow, please be sure to create your own thread for it. By posting it in another workflows thread, your workflow may never reach the masses. Create your own thread so that it stands out and everyone will be able to find it easily. This helps remove confusion on which workflow to download if there are multiple workflows, or modified workflows posted within the same thread. It also helps ensure that the develop that spent their time and put in the hard work to create the workflow get credit for their work. Posting a patch/update/fix/modified version of a workflow in another authors thread may steal attention from their original work. So let's try to be considerate.
 
Sharing Multiple Workflows
Try to limit a new thread to a single workflow. The reason for this follows the situation mentioned above. Unless you have an abnormally long title, users casually browsing the forums may not realize how many workflows are available in the post, or what they are. Creating a separate post for workflows also creates an individual area for you to provide support or answer questions for that workflow alone.
 
Modifying Existing Workflows
Most developers are very open to feature requests for their published workflows. So before modifying someone else's workflows, check with the developer and see if they would add the feature first. If the requested feature is something that the developer doesn't plan on adding, of course you could add the feature yourself. If you think it's a feature that others would also find greatly useful and you decide that you would like to share your modified version, please be respectful of the original developer give them a heads up before hand. Also, be courteous and give credit to the original author and/or a link back to their original thread so that they receive some credit for their work. Nobody enjoys having their work stolen.
 
Updating You Workflows
When sharing an update to an already posted workflow, rather than creating another post in the existing thread, update the initial post to include desired information and updated download links (if necessary). This makes it easier for users to find the most up to date version of your workflows, along with information what is included in the update. You could also modify the thread title to indicate the date that the workflow was last updated.
 
 
Notice: I'm also going to try to monitor this thread and keep it clean. If you post suggestions for other things to be added to the document, if they are merged in, I will probably remove your original post. Questions will also be treated the same way. If answers are later added into the original post, I may remove the original question. This will hopefully keep it so that all documentation remains in the original post so someone doesn't potentially have to search through several pages of questions for find a simple answer.

I'm not sure if it will affect anything or not. I'm willing to try it tomorrow afternoon/night and report back though. I would think that there wouldn't be an issue.

Quick little Contact Action workflow that will allow you to select a contact's address in the Alfred Contact Viewer and see that address in the Apple Maps app.
 
Download
 
You will have to add the custom action. Use the screenshots below to guide you through setting up the contact action..
 


After the action is set up.. when viewing a contact in the Alfred Contact Viewer, you should be able to select the Contact's address and view it in the Apple Maps application.

https://www.youtube.com/watch?v=OIaGdN-NUmg
 
A little preview of what I have so far (watch in HD if you can)
 
I had the artwork showing for the results but since Alfred can't use urls as icons for results yet, I would have to download the icon for all of them in order to show them. It can be done but slows things down a good bit (especially on a library the size of mine). One query downloaded over 10mb of artwork

here ya go.. link

Awesome AriX, thanks for the info!
 
Well, Yeraze, thanks to AriX, this should be extremely easy
 
Try this.
 
Import it, then go to Preferences->Features->Contacts. Click the + in the bottom right, set the Contact Field to "Phone" then for action, select "Call via DeskConnect". Enjoy. 

Alfred already has an option to make him show on whatever screen the cursor is currently on which is typically where you would be doing your work.
 

If you use Dropbox or something else to sync preferences you could use that tool to undelete the files that stores them. If not, heres a link to download a folder of all the default web searches. Drop it in ~/Library/Application Support/Alfred 2/Alfred.alfredpreferences/preferences/features/

Another quick update. Got the ability to browse the library working
 
http://cloud.dferg.us/G4yr

Another quick update. Got the ability to browse the library working
 
http://cloud.dferg.us/G4yr

https://www.youtube.com/watch?v=OIaGdN-NUmg
 
A little preview of what I have so far (watch in HD if you can)
 
I had the artwork showing for the results but since Alfred can't use urls as icons for results yet, I would have to download the icon for all of them in order to show them. It can be done but slows things down a good bit (especially on a library the size of mine). One query downloaded over 10mb of artwork