WF_BWP_DYN_COLUMN & Virtual Attributes

[Mike Pokraka]

As good a summary as I've ever seen. :-)

On Thu, July 22, 2010 12:41 pm, Madgambler wrote:
> Evil? No. Inspired yet inefficient and hazardous at high volumes would
> be more accurate.
>
> Mike GT
>
> Sent from my iPhone
>
> On 22 Jul 2010, at 11:34, "Mike Pokraka" <wug at workflowconnections.com>
> wrote:
>
>> Mike GT will be along shortly explaining why dynamic columns are
>> evil, but
>> in the meantime I would point out that you have already answered
>> your own
>> question with: "virtual attributes with some extensive coding behind
>> them"
>>
>> Dynamic columns are not too bad if used sparingly, and virtual
>> attributes
>> performance depends on the coding. I would like to see an ability to
>> ban
>> dynamic columns from the main inbox but allow them in the 'Group by
>> tasks'
>> view. Try suggesting your users do this - i.e. only configure the
>> specific
>> task views that need dynamic columns so at least it doesn't drag the
>> whole
>> inbox into the gutter.
>>
>> Cheers,
>> Mike
>>
>>
>>
>> On Wed, July 21, 2010 9:44 pm, Neumann, Marcia wrote:
>>> Hello,
>>>
>>> I'm trying to implement BAdI WF_BWP_DYN_COLUMN to improve our inbox
>>> performance.  Several of our dynamic columns are virtual attributes
>>> with
>>> some extensive coding behind them.  Some tasks have dynamic columns
>>> defined from a mix of database fields and virtual attributes.  I have
>>> searched but couldn't find any information on the use of virtual
>>> attributes in this BAdI.  Is there any performance gain in adding
>>> virtual attributes or will it perhaps actually have the opposite
>>> affect?
>>> If a task has 3 dynamic columns, two of which are database fields and
>>> one is a virtual attribute, would it still be beneficial to implement
>>> the BAdI for the 2 database fields?
>>>
>>> I would appreciate any insight anyone has on this topic.  We are
>>> running
>>> ECC 6.0 Enhancement Pack 4.
>>>
>>> Marcia Neumann
>>> Cincinnati Insurance Companies
>>> IT Claims/CSU Development & Support
>>> Ext 4461
>>>
>>> Confidentiality notice: The information included in this e-mail,
>>> including any attachments, is for the sole use of the intended
>>> recipient
>>> and may contain information that is confidential and protected. Any
>>> unauthorized review, use, disclosure, distribution or similar
>>> action is
>>> prohibited. If you are not the intended recipient, please contact the
>>> sender and delete all copies of the original message immediately.
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>