Adding Exceptions to Object Methods

[Stephan Becker]

I wouldn't do anything if you don't want to change the workflow definition.
If you add the exceptions in the method definition, nothing will happen -
apart from error messages that might change because you're now creating a
different error than before, ie. exceptions not modelled in definition
instead of exceptions not defined in method. However, the next time you
enter the activity details in your workflow definition, you will see the
exception in the appropriate tab. If you put any text in the event field
behind the newly defined exceptions, the graphical overview will pick them
up and you can model them.
Because you wouldn't actually enhance anything in my view, I'd just leave it
until you really have to change the workflow, and then do it in one swoop..
Stephan
 
 
 -----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Schroeter, Brad
Sent: 18 January 2000 21:05
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Adding Exceptions to Object Methods
 
 
    I've found some "exit_return" statements in our methods which don't have
a corresponding object method exception.  My plan is to go add the
appropriate exceptions to the object methods.  My question is this: will
doing this require any changes to the actual workflows (we're in
production)?  From I can see, it won't.  However I'd like to make sure.
I've attached the sections from OSS note 125400 (Modifying a Productive
Workflow) which pertain to Business Objects.  Thanks...
 
    "Modifying a Business Object Method
    Usually an incompatible change.
    When in doubt, create a new method, encapsulate it in a new task which
    is called from a new workflow version.
    If the method's implementation has changed (ABAP code), but neither the
    method's interface nor the properties  have changed, the workflow and
    task do not need to be changed.
 
    Modifying a Business Object Attribute
    Sometimes this is an incompatible change. Read on.
    Changing the algorithm behind an attribute will not affect the workflow
    definition.
    Changing the attribute's data repository reference could affect the task
    container and consequently the workflow container and binding. Create a
    new workflow.
    Changing the multi-line flag of the attribute will have consequences for
    the workflow and its container, so you need to create a new workflow."
 
 
 
    Brad Schroeter
    E-mail: BSchroeter at ti.com
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20000119/a7510012/attachment.htm