Passing a new container or struct to / from WF template.

[Michael Pokraka]

Ahhhhh  yes, those things are far too easily forgotten! I think the 'click on
the little arrow' bit is a little obscure - as I often overlook this as a
possibility myself. (Design hint for SAP :-)
Looks like 'Transfer all Data' would be a handy option for what you're after. 

Cheers
Mike

--- Workflow <nathanfox at swissinfo.org> wrote:

> Hi guys
> 
> Working in a 4,7 system I found this help on the binding options between
> template and task : It looks like a "Programmed binding" is in the works.  I
> haven't used it yet however.  Here an excerpt from the online help.
> 
> Binding Operations
> Operation from source element to target element of binding.
> 
> Use
> The following binding operations are supported:
> 
> Assign : The content of the target element until now is replaced.
> 
> Append : The content is written in the next empty line of the multiline
> target element.
> 
> Programmed binding : The binding is executed using a separate function
> module or its own ABAP
> class. Here, either the BOR container or the new container interface is
> used.
> 
> Transfer all data : Elements of the target container with the same name are
> overwritten with elements of the soure container.
> 
> -----Ursprungliche Nachricht-----
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]Im Auftrag
> von Rick Sample
> Gesendet: Donnerstag, 10. Februar 2005 16:07
> An: sap-wug at mit.edu
> Betreff: Re: AW: AW: Passing a new container or struct to / from WF
> template.
> 
> 
> I re-read my own post. It sounded negative and I hope it did not rub
> anyone the wrong way.
> But if we do not ask, suggest, or complain we will not move forward.
> 
> It would just be so wonderful l if we could just do a "getSomeAttribute
> / setSomeAttribute" from the
> WF Template without having to create containers everywhere, define them
> in
> Task, bind them from Template to Task, do work pass back to Task to
> Template if changed, etc.
> A lot of work just to get / set data. Just my opinion.
> 
> Work-arounds are par for the course in SAP as far as I am concerned.
> With so many developers under the same hood sometimes we are forced
> to do work-arounds until we get everyone on the same page with existing
> objects
> and designs. Most times in the real world I just don't have the luxuary
> of waiting to create
> the "perfect app" and need to create a solution. I am sure you know
> what I mean.
> 
> When we get to the newer versions of SAP (NetWeaver) are we not
> going to have to know OO? Since NetWeaver is based on Java and all.
> I have an OO backgoound pre SAP so it won't be a huge learning curve
> for myself.
> So while we are waiting for the future I am trying to design with OO in
> mind.
> Just me thinking out loud...
> 
> Mike,
> I looked at the note. I understand what it is saying about the "WF
> Template" versions.
> But, this does not solve the issue of Tasks - BO Methods.
> >From my experience, if you change a BO Method code it _will_ be picked
> up in old / new
> WF Templates regardless of template versions. From my experience
> anyway.
> So there is no reall way to "version" the entire flow, tasks, BO
> methods, attributes, etc.
> Yes?
> 
> 
> 
> >>> nathanfox at swissinfo.org 2/10/2005 4:05:14 >>>
> Hi Rick and Mike
> 
> Well I appreciate the compliment and am glad you got through my
> lengthy
> suggestions, I sense from your contributions to this forum that you two
> know
> what you're doing.
> I sense, however, from a lot of other contributions to this forum that
> many
> "workflowers" need some pretty basic training not only in workflow as
> such
> but in basic OO design concepts. It makes me cringe sometimes to think
> of
> the work-arounds that are implemented to rectify a flawed concept.
> 
> keep up the good work
> contributors like you make this forum interesting and worthwhile
> Nate
> 
> -----Ursprungliche Nachricht-----
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]Im
> Auftrag
> von Michael Pokraka
> Gesendet: Donnerstag, 10. Februar 2005 10:44
> An: SAP Workflow Users' Group
> Betreff: Re: AW: Passing a new container or struct to / from WF
> template.
> 
> 
> Hi Rick,
> I totally agree with the 'least amount of moving parts' theory, a
> rather
> nice
> way to put it.
> To answer your question, a container is just a table. So you can create
> a
> multiline element 'Container' and pass this around to your heart's
> content.
> I've a feeling this is too simple an answer - am I missing the
> question?
> 
> To add another completely inexpert 2p's worth, I still don't agree that
> this
> is
> really necessary (in most cases). Have a look at note 125400. It's a
> small
> matter of thinking before each change and copying into a new flow if
> appropriate - or if in doubt :-)  After a while it becomes automatic,
> and
> I'm
> quite happy for most part with the way versioning works.
> 
> Our biggest flows at my current site have 10-15 elements, most of them
> flags
> used internally. The real data lives in attributes. Bindings are
> generally
> in
> the order of 1-3 elements and rarely change once set. All a matter of
> design
> really :-) And there are a lot of flows throughout many areas. One
> notable
> exception I've already mentioned is HTML forms - ESS Leave request!!!
> (Oh,
> and
> a SAP standard QM rule with over 200 elements). I've thought about
> modding
> leave requests, but it's a very finnicky beast with umpteen notes and
> best
> left
> as close to the original as possible (got burnt here).
> 
> Cheers
> Mike
> 
> --- Rick Sample <Rick.Sample at gbe.com> wrote:
> 
> > >>If that wasn't an 'expert' answer, I don't know what is :-) Not
> > because of the amount of suggestion...
> > Mike,
> > Just too funny!
> >
> > All,
> > Any way, If SAP Business Objects were truly OO I would not be having
> > this conversation.
> > But I am not going there. SAP 4.6C. It is what it is...
> >
> > So, with that said, all I need to know is how (if possible) to pass
> a
> > container to a container.
> > Example: Create a container inside a BO method and pass to the Task
> to
> > the WF Template.
> > Possible? If so, what is the object name? Any SAP given generic
> objects
> > / structs so I don't
> > have to develop from scratch? I can't seem to find what I need.
> >
> > If I can pass custom structures or containers around I can leave my
> WF
> > Template alone
> > and won't have to create new containers in a dozen places, deal the
> > bindings,
> > re-test the entire WF Process, and then clean up in isle 9 for all
> the
> > old WFs that do
> > not have the same containers and bindings.
> >
> > I could always modify my BO or create yet another one but I will
> still
> > have the
> > issue of data persistence. (Or the lack there of).
> > I would still have to create yet another table(s) just to hold temp
> > data. Not what I want.
> >
> > The approach I am looking for is to "touch" the least amount of
> moving
> > parts and
> > shorten the testing time. It would be a beautiful thing... eh Mike?
> >
> >
> >
> > >> Have you thought of the implications :  workflow definitions have
> > versions,
> 
=== message truncated ===