WI text annoyingly short!

[Dr. Ulrich Mende]

Hi Michael-
 
why not use a dynamic inbox column (attribute1 .. attribute6)  instead of
or beside the static WI_TEXT?
What I know, the WI_TEXT is evaluated at creation time of the WI and the
result is copied
into the field SWWWIHEAD-WI_TEXT. After that it will be difficult to change
it.
In contrast to that the dynamic columns of the WIs in an inbox are evaluated
every time
that inbox is opened. (unfortunately not at every refresh)
For changeable object types I myself prefere to create virtuell
attributes attribute1..attribute6 and link them to the corresponding dynamic
columns.
(SWLD-->Administration-->Settings-->dynamic columns)
In the implementation of the column-attributes I can do what ever I want,
select data from database,
concatenate lots of fields into one string ...
 
Best regards Ulrich
 
----- Original Message -----
From: Michael Pokraka <MPokraka at samsungsemi.co.uk>
To: <SAP-WUG at MITVMA.MIT.EDU>
Sent: Friday, December 15, 2000 11:55 AM
Subject: Re: WI text annoyingly short!
 
 
> Thanks all for your input so far, there's still one minor hitch in this:
> One of the texts (the main one I'm interested in) is actually the main WF
> template text. So, assigning container elements once the WF has already
> started doesn't work.
> Or is there a way to make the WI text dynamic - i.e. if the container
> changes, can the WF text also be made to change accordingly? The only way
I
> can see (aside from direct modification via ABAP) is to create a custom
> method CHANGETEXT for FLOWITEM and a task which will do just that. This
> seems a bit lengthy, or am I missing something with container operations -
> it would seem that you cannot assign e.g. _Workitem.ShortText, only the
> whole object.
>
> The end goal / why am I after all this: to be able to pull up a WI report
> (SWI1) on the top level WF and see what the status is on that screen
without
> having to drill down to the individual WF's.
>
> Thanks again.
> Michael
>
> -----Original Message-----
>> From: Kjetil Kilhavn [mailto:KJETILK at statoil.com]
> Sent: 15 December 2000 08:31
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: WI text annoyingly short!
>
>
> Not that I have tested this, but I would think it is possible to create
> *one*
> additional container item, concatenate whatever variables you need into
that
> through container operation steps, and use it in the WI text. That sounds
> better
> to me than creating one extra container item for every variable you need.
> --
> KjetilK
>
>
>
>
>
>> From:  Michael Pokraka <MPokraka at samsungsemi.co.uk>@MITVMA.MIT.EDU> on
>        14.12.2000 19:13
>
> Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
>
> Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
>
>
> To:    SAP-WUG at MITVMA.MIT.EDU
> cc:     (bcc: Kjetil Kilhavn)
>
> Subject:  Re: WI text annoyingly short!
>
>
>
> Hmm, yup, not quite there, but it's one better than creating short object
> attributes :-)
> Thanks
>
> -----Original Message-----
>> From: Griffiths, Mark [mailto:mark.griffiths at sap.com]
> Sent: 14 December 2000 17:47
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: WI text annoyingly short!
>
>
> You could create a load of additional Task container elements with short
> names and bind the attributes of the object you are using into these when
> you call it from the workflow task.
>
> Hope this helps,
>
> Mark
>
> SAP UK
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:MPokraka at samsungsemi.co.uk]
> Sent: 14 December 2000 17:14
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: WI text annoyingly short!
>
>
> Hi folks,
> A really simple one (and I've searched through OSS on this):
>
> Because of the lengthy variable definitions for work item texts, I keep
> running into
> "WI text for assigning text variables is too long, please shorten!"
>
> I'm talking about stuff like &SALESORDER.DELIVERYSTATUS& which returns a
> single character. Or a customer number
> (&ZSALESORDER.ORDERINGPARTY.CUSTOMERNO&)...
>
> As text is limited (4.0B here) to 120 characters, I can't fit all these
> fields in - even though at runtime they would result in a short bit of
text.
>
> Any ways around this?
> Thanks
> Michael
>
>
> -----------------------------------------------------------------------
>
> The information contained in this email may be privileged, confidential
> and protected from disclosure. The opinions expressed are those of the
> individual and not Samsung Semiconductor Europe Ltd or Samsung
> Electromechanics Ltd. Internet communications are not secure and
> therefore Samsung Semiconductor Europe Ltd and Samsung
> Electromechanics Ltd do not accept legal responsibility for the contents
> of this message. If you think you have received this email in error please
> notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
> copies of the mail.
>
>
> -----------------------------------------------------------------------
>
> The information contained in this email may be privileged, confidential
> and protected from disclosure. The opinions expressed are those of the
> individual and not Samsung Semiconductor Europe Ltd or Samsung
> Electromechanics Ltd. Internet communications are not secure and
> therefore Samsung Semiconductor Europe Ltd and Samsung
> Electromechanics Ltd do not accept legal responsibility for the contents
> of this message. If you think you have received this email in error please
> notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
> copies of the mail.
>
>
>
> -------------------------------------------------------------------
> Statoil: 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.
>
>
> -----------------------------------------------------------------------
>
> The information contained in this email may be privileged, confidential
> and protected from disclosure. The opinions expressed are those of the
> individual and not Samsung Semiconductor Europe Ltd or Samsung
> Electromechanics Ltd. Internet communications are not secure and
> therefore Samsung Semiconductor Europe Ltd and Samsung
> Electromechanics Ltd do not accept legal responsibility for the contents
> of this message. If you think you have received this email in error please
> notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
> copies of the mail.