AW: Changing GOS key within transaction?
Michael Pokraka
workflow at quirky.me.uk
Mon Apr 12 18:31:04 EDT 2004
Ah, that was one of the first options I ditched. Causes an annoying
delay and flicker as it is refreshed. This is what prompted me to go
digging and understand what it does in a bit more detail - which is to
look for existing instances and replace instead if found.
I doubt SAP will change it as it's already in use that way... but you
never know. It would be a bit confusing, but as it's a big custom
development the GOS change would probably be small fry in the grand
scale of an upgrade.
Cheers for the input,
Mike
On Sat, 2004-04-10 at 09:08, Kjetil Kilhavn wrote:
> You could destroy the object first, couldn't you? We are on 4.6C and I
> haven't needed to do what you are doing, but that would be my first
> thought. Destroy, (even Free maybe) and then Create again.
> Then it should work even if SAP decides the possibility of multiple GOS
> icons is a nice thing to have.
> --
> Kjetil Kilhavn
>
>
>
>
>
> Michael Pokraka
> <workflow at quirky.me. To: SAP-WUG at MITVMA.MIT.EDU
> uk> cc: (bcc: Kjetil Kilhavn)
> Sent by: SAP Subject: Re: AW: Changing GOS key within transaction?
> Workflow
> <Owner-SAP-WUG at MITVM
> A.MIT.EDU>
>
>
> 09.04.2004 15:30
> Please respond to
> "SAP Workflow Users'
> Group"
>
>
>
>
>
>
> Hi Simone,
> Thanks, that was closer to what I'm looking for and at least gave me
> something to go on. Looking through the code (it's obsolete on 620), I see
> it calls the GOS_MANAGER class methods in any case so I went digging around
> there for what is now a good half a day :-) Ah, what we don't do sitting at
> work over Easter.... I'll share my conclusions on three alternatives:
>
> call method gos_manager->set_id_of_published_object
> This seems to be the obvious choice based on the name but seems like it is
> used in callbacks only. Repeated calls only result in the message that one
> or other key is already in your object list, and doesn't affect the already
> instantiated GOS.
>
> The method used by SWU_OBJECT_PUBLISH adds the object into a table. Thus a
> user clicking on GOS is first presented with a choice of objects (s)he's
> already displayed. Nifty having GOS for multiple objects simultaneuosly,
> but
> I think it may confuse people in this particular case.
>
> Eventually I dug around the gos_manager constructor some more and found it
> had catered for already existing objects, so it seems the big hammer
> approach works just fine: just set a new key and 'create object
> gos_manager'
> to your hearts content.... duh. And I wasted half a day on that.
>
> Cheers
> Mike
>
> Falk, Simone wrote:
> > Hallo Michael,
> >
> > why dont you publish that other object ?
> >
> > You can use FM:
> >
> > 'SWU_OBjECT_Publish'
> >
> > Best regards
> > Simone
> >
> > -----Ursprüngliche 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.
> > Keep this in mind if you answer this message.
> >
> >
>
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.
More information about the SAP-WUG
mailing list