Contextual decision text in user decision step

Thu Aug 18 20:26:03 EDT 2011

Hi Edward,

Yes, in this case I will keep the same path. Here is one of my scenarios

One of the user decision steps in my workflow has these four options

User decision header text
"Enter company code data for the vendor request"

Decision options (Buttons)

1.       Edit company code data

2.       View general vendor data

3.       View pOrg data

4.       Task Completed

Idea is to embed this user decision within until loop so that agent can keep working on this WI until they explicitly choose "Task completed". This obviously gives them full control over the WI completion which is our requirement.

Now the first time a user gets this WI, there is obviously no company code data - which has multiple fields and is stored in a structure container element - attached to the request.
So until the key fields within the company code data structure are filled in, I want to keep displaying "Add company code data" on the 1st button. But once the key fields have been entered and the user has not yet marked the WI completed, I want to start displaying "Edit company code data" on the 1st Button.

You are right, if I wanted a different path I will have to have multiple decision steps. This is more like a "Dynamic decision options" while the above scenario is like "Dynamic decision option texts"

Regards
Inder

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Edward Diehl
Sent: Thursday, 18 August 2011 10:18 PM
To: sap-wug at mit.edu
Subject: RE: Contextual decision text in user decision step

Question:  If you changed the text would you keep the same outcome path?  I'm having a hard time coming up with an application where that would be true.  And if you would want a different path why would you not have multiple decision tasks?
> Date: Thu, 18 Aug 2011 12:43:46 +0100
> Subject: Re: Contextual decision text in user decision step
> From: wug at workflowconnections.com
> To: sap-wug at mit.edu
>
> 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
> >
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug

________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110819/6f53166d/attachment.htm