Skip to Content
author's profile photo Former Member
Former Member

Problems with terminating event

Hi all,

I defined a terminating event for a task.

I want all instances of this task to be completed when raising the event.

I made the binding of the object.

I defined the event as a instance linkage(is this correct?)

Does a terminating event works for a dialog task?

When I start the event, I get only the following message in the event trace

'no receiver entered' but I have the impression that with the instance linkage, you cannot enter receiver data.

I tried also the type linkages but this gives me this error

' task not defined as start/end event'

Thanks for any help,

Hans

I

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 12:47 PM

    First of all Terminating event works only if the that particular task is in Process state. Unless it is in process state this terminating event will not be cached. Terminating event is generally used in Asynchronos task. You can take a look of WS20000075.

    Thanks

    Arghadip

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 30, 2007 at 03:13 PM

    Hello Hans,

    I don't think this is that straightforward, because instance linkage is always use a key. If I understand your question correctly, you have several different tasks with different objects and you want all of them to terminate when a single event is raised. Unfortunately a terminating events will wait for an event using an object instance.

    One workaround would be to use the task as the object whose events you're waiting for. In other words an instance of a subtype of TASK with the key corresponding to your workflow template ID. So now your task is waiting for an event TASK.ZCOMPLETE. The downside to this is that you have to code the task number that you are trying to terminate into wherever you are raising the event.

    Hope that helps.

    Cheers,

    Mike

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Hans,

      When you say 'one by one', this is not how events work: if an event is published then anyone listening will react, and this is asynchronous and kindof all happens at once.

      If you want to kill them one by one (why?) then use the event queue to limit the rate, or if it has to bve in sequence then you'll have to resort to a custom solution. Not too difficult, use one of the SAP_WAPIs to dig out all the open workflows, read their container and publish an event for each. Note that even this way your sequence will not be guaranteed as they can overtake each other.

      Cheers,

      Mike

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 03:19 PM

    Hi Mike,

    'One by one' would be a workaround but offcourse it would be nice to

    terminate all tasks of a certain type with one event.

    But I didn' t succeded yet.

    Best regards,

    hans

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.