Regd. work items of same object type instance

[Mike Pokraka]

Yep, a fork will do the trick.
Cheers,
Mike

vijay srikanth wrote:
> Hi Mike,
>
> Should it be a fork with a wait for event in one branch, or I just add a
> wait for event step in my workflow, after the step that I want to execute,
> and the workflow ends if either the step gets executed or the event is
> fired. Thanks fr the help in advance.
>
>
> Regards,
> Vijay
>
>>From: "Mike Pokraka" <wug.replies at workflowconnections.com>
>>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>>Subject: RE: Regd. work items of same object type instance
>>Date: Mon, 9 Jan 2006 08:51:10 -0000 (GMT)
>>
>>Hi,
>>You can have as many items for an object as you like.
>>If you want a new workflow to replace a previous one, then you need to
>> add
>>a wait for event step which will terminate an existing workflow when the
>>event is triggered.
>>In other words, the event is both a trigger and a terminator for your
>>workflow.
>>
>>Cheers
>>Mike
>>
>>akshay.bhagwat at wipro.com wrote:
>> >
>> > Hi Vijay ,
>> >
>> > I think I differ in this opinion of getting it handled automatically..
>> > I am not sure, but I think, we will manually need to handle this
>> > situation.
>> > Because, I think, there will be another work item with latest data
>> along
>> > with previous work item.
>> >
>> > It made me think like this because, every time we change any data,
>> this
>> > work item data will be different than previous work item's data.
>> >
>> > Would like to have comments on my opinion, by other members in our
>> > workflow group....
>> >
>> >
>> > Regards,
>> > Akshay
>> >
>> > -----Original Message-----
>> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>> Behalf
>> > Of vijay srikanth
>> > Sent: Monday, January 09, 2006 12:39 PM
>> > To: sap-wug at mit.edu
>> > Subject: RE: Regd. work items of same object type instance
>> >
>> > Hi Yogesh,
>> >
>> > That makes me wonder, how will it do it. Is there some internal
>> > technique, for it to identify if a previous workitem exists with the
>> > same object key and then overwrite it. This is amazing, and we won't
>> > have to handle it separately in our program or workflow.
>> >
>> >
>> > Regards,
>> > Vijay
>> >
>> >
>> >>From: "Yogesh Chopra" <Yogesh.Chopra at axonglobal.com>
>> >>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>> >>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>> >>Subject: RE: Regd. work items of same object type instance
>> >>Date: Mon, 9 Jan 2006 14:59:14 +0800
>> >>
>> >>It will overwrite the previous workitem.
>> >>
>> >>Thanks and Best Regards
>> >>    Yogesh Chopra
>> >>Yogesh.Chopra at axonglobal.com
>> >>
>> >>
>> >>-----Original Message-----
>> >>From: vijay srikanth [mailto:vijay_d15 at hotmail.com]
>> >>Sent: Monday, January 09, 2006 2:52 PM
>> >>To: sap-wug at mit.edu
>> >>Subject: Regd. work items of same object type instance
>> >>
>> >>Hi,
>> >>
>> >>I just have this doubt, about workitems of a particular object type
>> for
>> >
>> >>the same instance.
>> >>For eg. if I already have a work item in a users inbox say for the
>> >>business object BUS2034, event - changed, and again if I raise the
>> same
>> >
>> >>object event for the same key(in this case the contract number), does
>> >>it raise another work item or does it overwrite the previous work
>> item.
>> >
>> >>Will it result in
>> >>
>> >>concurrent work items in the users inbox for the same object-instance,
>> >>if yes, then how do I avoid that situation, wherein I have two work
>> >>items referring to the same object instance in a person's user id.
>> >>Thanks for the help in advance.
>> >>
>> >>Regards,
>> >>Vijay
>> >>
>> >>
>> >>_______________________________________________
>> >>SAP-WUG mailing list
>> >>SAP-WUG at mit.edu
>> >>http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >>
>> >>
>> >>
>> >>The content of this email is confidential and for the addressee only.
>> >>If you are not the addressee of this email (or responsible for the
>> >>delivery of this message to such person) you may not copy, forward,
>> >>disclose or otherwise use it or any part of it in any form whatsoever.
>> >>If you have received this email in error please email the sender by
>> >>replying to this message and delete this message thereafter.
>> >>
>> >>Opinions, conclusions and other information in this message that do
>> not
>> >
>> >>relate to the official business of our Company shall be understood as
>> >>neither given nor endorsed by it.
>> >>
>> >>
>> >>
>> >>_______________________________________________
>> >>SAP-WUG mailing list
>> >>SAP-WUG at mit.edu
>> >>http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >
>> >
>> > _______________________________________________
>> > SAP-WUG mailing list
>> > SAP-WUG at mit.edu
>> > http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >
>> >
>> > The information contained in this electronic message and any
>> attachments
>> > to this message are intended for the exclusive use of the addressee(s)
>>and
>> > may contain proprietary, confidential or privileged information. If
>> you
>> > are not the intended recipient, you should not disseminate, distribute
>>or
>> > copy this e-mail. Please notify the sender immediately and destroy all
>> > copies of this message and any attachments.
>> >
>> > WARNING: Computer viruses can be transmitted via email. The recipient
>> > should check this email and any attachments for the presence of
>> viruses.
>> > The company accepts no liability for any damage caused by any virus
>> > transmitted by this email.
>> >
>> > www.wipro.com
>> >
>> > _______________________________________________
>> > SAP-WUG mailing list
>> > SAP-WUG at mit.edu
>> > http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >
>>
>>_______________________________________________
>>SAP-WUG mailing list
>>SAP-WUG at mit.edu
>>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>