ABAP OO problem

[Mike Pokraka]

Update: I just did a quick test whilst I was buiding workflows, and you
can simply define an importing element of type Undefined, bind a class
instance, and it becomes a clickable object link.


On Mon, June 25, 2007 4:43 pm, Mike Pokraka wrote:
> Correct, that's not available. To be honest, I don't use Adhoc Objects
> much, most of the time the object types are known and you can just as well
> create container elements for it.
> I haven't played much with the ploymorphic capabilities of OO in WF, but
> it may well be something as simple as creating your own 'Adhoc' object to
> which you can bind whatever you like.
>
>
> On Mon, June 25, 2007 3:35 pm, Edward Diehl wrote:
>>
>> Well, I found one big drawback to using classes.  You cannot assign a
>> created instance to _Adhoc_Objects.  The error message is CL and BO are
>> incompatible.
>>
>> Is there a way around this?  The CL has a default method to display
>> certain info and is essential to meet the functional requirements.
>>
>> Thanks,
>> Ed_______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> --
> Mike Pokraka
> Senior Consultant
> Workflow Connections
> Mobile: +44(0)7786 910855
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


--