Basically, I want to write one workflow to cover both situations. I; however, want to change some wording based on whether the workflow is coming from a create or a modification.
I don't want to stick another column in the list called "new item" and update it.
I think there's a way to do this--but I can't find it.
Hmm.. well, I suppose that would depend. If you were requiring a major version update each time, you could look at the version column -- if 1.0, then this branch; if larger than 1.0, a different branch.
Would that work for you?
It's a thought.
Thanks,
Stephan
The particular library I'm using isn't being versioned. I probably could turn it on--but I'd like to find another way.
have a look whether this idea suits you
This looks like a good alternative but it does recommend adding another column, which I think Stephan doesn't want to do.
That would have been my initial suggestion as well... but surely there must be something unique, by default, that a newly initiated form displays... hmm. I still can only think of ...
OH WAIT. What about Modified Date? If Modified Date is equal to Created Date? It would have to include time and be identical, but ... the only time that'd ever be true is on creation.
Rhia Wieclawek, do you refer to the post marked as correct?
my suggestion there doesn't need any additional column in the list...
the link I provided should point directly to my post there, but sometimes browsers do not recognize/find an anchor within the page and end up at the top of page
I'm not aware of any OOTB reliable way to identify within workflow on what event it was started.
problem with modified/created dates are that
- they are just in minute-level precision. within a minute several changes can be be made.
- if items are created/updated from a program code, there are ways to do it so that version number and timestamps do not change
Ah yes, I see now - sorry, browser took me directly to the top post.
thanks 
Where's the Created Date? All you have is modified date.
Looks harder than creating 2 workflows.
So if you create 2 extra workflows, one that runs on start and one that runs on modify, and both those workflows start your main workflow, you'll know what action started the workflow. You can even pass a variable from your first mini workflows to your main workflow, if that helps.
My experience with workflows starting other workflows is not good. I've seen humongous delays. I'd rather use a column.
hm, I don't think so.
if you create two full-functional workflow, likely you will duplicate plenty of functionality.
as well, if you already have the workflow (partly) developed, I see it as easiest approach without touching existing logic/functionality.
then I would maybe focus on resolving these delays. I use it regularly and haven't experienced such issues.
I would rather say I have minimum workflows that do not start other workflows.
This would work. However, in my case the list is preexisting and versioning wasn't enabled. So the older items are now version 1 and they are not really new.
I'm biting the bullet and adding a NewItem column. I'm setting the default to "Yes" and immediately updating to "No". I'm also updating the ones with a null value to "No" when they been worked on.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.