ABAP OO application exception and passing parameters back to workflow container

[Florin Wach]

Hi Dave,

the data flow is aborted on an exception. Only the message variables (sy-msgv1,..v4) and the exception number is passed back.


---> follow-up:

If you want to have a workflow activity with more outcoming threads (like you have it in the generic user decision steps), you could use the following:
- Double click on the object's method
- Choose tab "Result type"
- Give a reference to a field here, that again refers to a domain with fixed values, e.g.
  SE Step executed
  X1 Exception 1
  ....
  (I think there's a restriction to 4 characters as the key)
- In the object's method implementation use the macros to set the result
  swc_set_element container RESULT 'SE'. 
  swc_set_element container RESULT 'X1'. 

This way you'll have a dataflow.

Best wishes,
Florin

-------- Original-Nachricht --------
> Datum: Wed, 20 Feb 2008 20:04:15 -0500
> Von: "Dave Weston" <Dave.Weston at clockwork.ca>
> An: sap-wug at mit.edu
> Betreff: ABAP OO application exception and passing parameters back to workflow	container

> Hi folks,
> 
> I am raising an application error in an OO method in my workflow and
> filling some export parameters (which would normally get passed back to the wf
> container when no exception is raised). When the class exception is raised
> the filled parameters are not passed back to the wf container.
> 
> Has anybody implemented an application exception that when raised passes
> export parameters back to the task and wf container ?
> Was wondering if creating an attribute on the exception class was the way
> to do it.
> 
> Any guidance would be great.
> 
> Thanks
> Dave