Yes. I see that now. That is great. It really is. You really might want to
promote your tool a bit. I will do it as much as I can. I am sure that it can
answer a lot of questions for a lot of people. FYI, this newsgroup
http://www.SharePointU.com is also pretty well travelled.
Now, I have another issue. I can now persist the old-value and new-value for
a given field in a given List by using a hidden field for the old-value. That
is fine. Unfortunately, to update the old-value as needed, the item needs to
be checked out. And, it seems, a checkout causes my Workflow to trigger
again, because it is set to start whenever an item changes. Therefore, my
Workflow runs 2x. Ug. Not good. I may have to use an Event Handler after all,
unless I find a better way.
Back to the drawing board. The problem that I am trying to solve is as
follows.
When a new item is created and whenever an existing item is changed in any
way, run the following simple logic...
Start the Workflow.
If ((OldStatus DoesNotEqual ReadyForReview) And (NewStatus DoesEqual
ReadyForReview)) Then
Send an email to A and B.
Else
Do nothing.
End If
Stop the Workflow.
In plain English, we have: If the Status changes from
SomethingOtherThanReadyForReview to ReadyForReview, then send an email;
otherwise, do nothing. There should be email sent only when the Status
changes to ReadyForReview. Unfortunately, the business processing is
non-linear; for example, it could go as: Status=NotSet, Status=Draft,
Status=ReadyForReview, Status=ReadyForPublish, Status=Draft,
Status=ReadyForPublish, Status=ReadyForReview, and so on. It can go from any
state to any state at any time.
If you, or anyone, has any hints on how to solve this, then please let me
know.
Thank you.
-- Mark Kamoski