Create SharePoint workflow trigerred on a change in uploaded documents

Hello, SharePoint Experts,
I am having this challenge. I need to create a workflow in a Document Library that will be triggered by a certain field property (Document Purpose) that users choose after uploading a PDF file. I see that is not a simple task as the property is entered after the document is created (second step in the upload file sequence of events).
I found this link "Workflow not firing for new documents uploaded to a document library" ( that explains exactly my situation.
The solutions suggested there cannot work for me (I cannot enable versioning and cannot use content approval).
Are there any alternatives?
I kind of have a quick way around by creating an SharePoint alert that work on new files added to a view based on the property value (Document Purpose). In is not acceptable to users, in part, because they need to have a part of the Document Library path, a folder name, in the email, a folder but that is another story).
Any advice is appreciated!
Thank you!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Could you use a drop off library?  This would be the single source that documents are saved to, and then a document routing rule could be applied to move documents to the correct place one the correct metadata has been applied.  Once routed to the final location, a normal "fire on creation" workflow can be run.

The upsides of this are:
1) single point for users to save documents to/send documents from other sites
2) Encourages the use of SharePoint features such as routing and records management
3) Encourages use of meta-data driven navigation

The downsides are:
1) user acceptance
2) I've not seen this used outside of a record centre, which may not be what you want
3) I've struggled to route document to a library with more than one level of folders (although you can probably do this in code).
4) More configuration/development work to implement
IT-NYCAuthor Commented:
Thanks for your detailed post!
I am afraid that for the reasons you mentioned in the downsides section, it is not possible to implement  your suggestion in my situation. There have been a an established user procedure, multi-level folder structure, this is not within record center, and so on.
You could create an event handler that fires "on change", make this check for the column you need, and if the data is set, then start the workflow from the code.  This requires you to create a Visual Studio feature.
I believe commercial workflow solutions such as Nintex allow you to do this without code.

Alternative, if you are using SPD then this video from microsoft shows you how to set up an "infinate loop" that  waits for the field to be set:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.