AW: Changing GOS key within transaction?

Falk, Simone SIMONE.FALK at airbus.com
Thu Apr 8 06:20:46 EDT 2004


Hallo Michael,
 
why dont you publish that other object ?
 
You can use FM:
 
'SWU_OBjECT_Publish'
 
Best regards
Simone
 
-----Urspr=FCngliche Nachricht-----
Von: Michael Pokraka [mailto:workflow at quirky.me.uk]
Gesendet: Donnerstag, 8. April 2004 12:03
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Changing GOS key within transaction?
 
 
Hmmmm, good thought. Showing the log was the most important requirement =
at
present - so I guess it would be possible to link that FM to a button =
on
the
screen and remove GOS alltogether to keep from confusing any users.
 
My first choice obviously remains GOS for consistency and openness, but
that's definitely the best alternative I can't get GOS to play nicely.
Thanks for the input.
Cheers
Mike
 
rvmarut at earthlink.net wrote:
> Mike,
>
> Take a look at function module SWI_WF_CONNECTIONS_DISPLAY. This is =
used
in
> GOS. I've used it to return both a single workflow and a list.
>
> RIchard...
>
> -----Original Message-----
>> From: Michael Pokraka <workflow at quirky.me.uk>
> Sent: Apr 7, 2004 11:02 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Changing GOS key within transaction?
>
> Hi all,
> I have a transaction which uses Generic Object Services. This custom
> transaction however includes functionality to skip to a different =
object
via
> buttons.
> I'd like to know what the best way is to update the GOS object key. =
In
other
> words I'm looking at object 123 and would like to see it's workflows,
then
> skip to 124 and GOS should then show me 124's workflows. (The =
transaction
> was designed before workflow and major changes are out....).
> I've gone through the class, and looked at the docs (surprisingly =
good
> documentation I might add), but everything seems to relate to a =
single
> instantiation. The section on dynamic instantiation using a a =
callback
> function is really a delayed instantiation of an otherwise static =
object,
> which doesn't help my cause much.
> This is one of those where one can spend a fair bit of time testing
> alternatives, but this one is in a bit of a hurry, so I thought I'd =
ask
here
> first.
>
> Any input appreciated.
> Cheers
> Mike
>
>
 
This mail has originated outside your organization,
either from an external partner or the Global Internet.=20
Keep this in mind if you answer this message.
 


More information about the SAP-WUG mailing list