Contextual decision text in user decision step

[Mike Pokraka]

One of the new functionality ideas currently under discussion at SAP
towers is dynamic decision options, which would help here.

It's semi-public knowledge within the customer connection programme, which
is a glorified term for SAP using ASUG and other customers as guineapigs
for small updates without the heavy NDA stuff. So far no decision has been
taken whether this will be implemented, but if it happens then it could
possibly be made available as an OSS note or else included in the next EhP
update.

I have no official capacity nor do I work for SAP, so take everything as a
rumour with large pinch of salt.

Regards,
Mike

On Thu, August 18, 2011 10:33 am, Rick Bakker wrote:
> Hello,
>
> Welcome to SAP-WUG!
>
> When you say "Decision texts" do you mean the text that is displayed
> in a workitem of a User Decision step?
> Or do you mean the header text - i.e. what the user will see as one
> line in the UWL?
>
> If the former then yes, you can do what you want. You can build in
> conditions in the SapScript of the task description.
>
> If the latter then you'll just have to make use of a container element
> that you fill beforehand in a previous step.
>
> Let me know if I've misunderstood.
>
> regards
> Rick Bakker
> hanabi technology
>
> On Thu, Aug 18, 2011 at 6:07 PM, Chabbra, Inderpreet
> <inderpreet.chabbra at effem.com> wrote:
>> Hello SAP-WUG
>>
>>
>>
>> I am new to this great forum and this is my first question to the group.
>> Please excuse me if I unwittingly break any protocol.
>>
>> I am a rookie when it comes to SAP workflow technology and I have been
>> busy
>> reading Practical workflow for SAP (2nd Edition). An awesome resource,
>> by
>> the way.
>>
>>
>>
>>
>>
>> Anyway, my question for today is related to decision texts in user
>> decision
>> step.
>>
>>
>>
>> Is it possible to display a string stored within a container element as
>> decision text?
>>
>>
>>
>> Driver behind my question
>>
>> --------------------------------
>>
>> I have a user decision step with 5 outcomes and is embedded within an
>> until
>> loop. Decision text on a couple of these outcomes can be better named
>> based
>> on the context, if this at all possible. For instance: “Add company code
>> data” when no company code data exists and “Edit company code data” when
>> company code data exists as opposed to a catch all name like “Maintain
>> company code data” etc
>>
>>
>>
>> I tried using &1 (parameters) which I quickly found  does not work with
>> decision texts L
>>
>>
>>
>> The only option I can think of is to create a condition step within the
>> loop
>> execution branch and have a copy of user decision step within each
>> branch of
>> the condition step.  This is obviously very messy especially given the
>> number of steps I have in each of the 5 outcomes of my user
>> decision
horrible
>>
>>
>>
>> Any clue and/or advice would be greatly appreciated
>>
>>
>>
>> regards
>>
>> IP
>>
>>
>>
>> ________________________________
>> CONFIDENTIALITY. This email and any attachments are confidential and may
>> also be privileged. If received in error, please do not disclose the
>> contents to anyone, but notify the sender by return email and delete
>> this
>> email and any attachments from your system.
>>
>> _______________________________________________
>> 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
>