User Decision Task Description.

Fri Oct 13 07:06:00 EDT 2006

Txs, for the idea,

I used standard text also as a dynamic solutions in some cases, but in this
case I don't see where and in which moment I can intercept the user who
receives the UD and use this as dependencie for a variabele or standard
text.

kind regards,
Stefaan.

2006/10/12, yves.lebacq at skynet.be <yves.lebacq at skynet.be>:
>
> Hi Stefaan,
>
> I got the same problem I think.
>
> I used the standard text (SO10) put in the long text of the tasks.
> Also I built a table with the rule and its standard text.
>
> Hope this help you.
>
> Yves.
>
>
>
>
> ------------------------------
>
> ------=_Part_13_25960703.1160553619132One task for multiple recipients,
> thats the case.I agree with you that I'm a bit stuck and will have to
> split the groups upin advance.thanks anyways,Stefaan.2006/10/11, Mark Pyc
> :>> Are you actually creating a decision per user or is there one decision>
> Workitem with multiple recipients? If there is only one Workitem there can>
> only be one Workitem short-text. If there are multiple Workitems I'm not
> not> sure what the other consequences would be.>> If you have only one
> Workitem you can still have dynamic long-text, but I> don't think you could
> be dynamic enought to change the text depending on who> was looking at the
> Workitem.>> You may be stuck.>> Good luck,> Mark>>> On 10/11/06, Stefaan
> Vermeulen wrote:> >> > Mark,> >> > Thanks for the reaction, but by reading
> trough my question I saw I> > wasn't clear or complete.> > The thing is dat
> my agent determination already done and resultated in a> > agents table,
> this table gives via the expression the agents for this UD.> >> > Now some
> US-users in this table are Host, some are Deputies depending on> > an
> attribute at user level.> > *So the problem is* ;when wf dipatches the task
> to the specific user,> > you should be able to react dynamicly on this.> >>
> > What I did is I split up the hosts and the deputies by previous agent> >
> determination and use the same task with the different host- or> >
> deputies-table.> >> > This works , but has his consequences, therefore I
> wondered if there> > would be another way.> >> > thanks,> > Stefaan.> >> >>
> > 2006/10/10, Mark Pyc :> > >> > > G'day Stefaan,> > >> > > You would need
> to perform your agent determination in a backgr! ound> > > step beforehand.
> In this you could also return your 'title' variable at the> > > same time to
> keep everything nice and tidy. You would then use an Expression> > > for
> your agent on the decision and your title variable would be ready to go.> >
> >> > >> > > Have fun,> > > Mark.> > >> > >> > > On 10/10/06, Stefaan
> Vermeulen < stefaan.vermeulen at gmail.com> wrote:> > >> > > > Hi all,> > >
> >> > > > In the past I used variables in different way in the UD> > > >
> task-description.> > > > This question differs somehow ; depending on the
> agent determination> > > > by expression (in this case a table of US-user
> objects) I would like to> > > > specify the type of approver in the title.>
> > > > I can easily solve this by splitting up in branches depending on> > >
> > user-type, but I! would like to avoid this.> > > >> > > > The difficulty
> is that the information is depending on an item of> > > > the agent
> determination at sending time.> > > >> > > > kind regards,> > > > Stefaan.>
> > > >> > > > _______________________________________________> > > > 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> >> >!
> > >>> _______________________________________________> SAP-WUG mailing list>
> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug>>>------=_Part_13_25960703.1160553619132
>
> One task for multiple recipients, thats the case.
> I agree with you that I'm a bit stuck and will have to split the groups up
> in advance.
>
> thanks anyways,
> Stefaan.
>
>
> 2006/10/11, Mark Pyc <mark.pyc at gmail.com>:
> >
> > Are you actually creating a decision per user or is there one decision
> > Workitem with multiple recipients? If there is only one Workitem there can
> > only be one Workitem short-text. If there are multiple Workitems I'm not not
> > sure what the other consequences would be.
> >
> > If you have only one Workitem you can still have dynamic long-text, but
> > I don't think you could be dynamic enought to change the text depending on
> > who was looking at the Workitem.
> >
> > You may be stuck.
> >
> > Good luck,
> > Mark
> >
> >
> > On 10/11/06, Stefaan Vermeulen <stefaan.vermeulen at gmail.com> wrote:
> > >
> > > Mark,
> > >
> > > Thanks for the reaction, but by reading trough my question I saw I
> > > wasn't clear or complete.
> > > The thing is dat my agent determination already done and resultated in
> > > a agents table, this table gives via the expression the agents for this UD.
> > >
> > > Now some US-users in this table are Host, some are Deputies depending
> > > on an attribute at user level.
> > > *So the problem is* ;when wf dipatches the task to the specific user,
> > > you should be able to react dynamicly on this.
> > >
> > > What I did is I split up the hosts and the deputies by previous agent
> > > determination and use the same task with the different host- or
> > > deputies-table.
> > >
> > > This works , but has his consequences, therefore I wondered if there
> > > would be another way.
> > >
> > > thanks,
> > > Stefaan.
> > >
> > >
> > > 2006/10/10, Mark Pyc <mark.pyc at gmail.com>:
> > > >
> > > > G'day Stefaan,
> > > >
> > > > You would need to perform your agent determination in a background
> > > > step beforehand. In this you could also return your 'title' variable at the
> > > > same time to keep everything nice and tidy. You would then use an Expression
> > > > for your agent on the decision and your title variable would be ready to go.
> > > >
> > > >
> > > > Have fun,
> > > > Mark.
> > > >
> > > >
> > > > On 10/10/06, Stefaan Vermeulen < stefaan.vermeulen at gmail.com> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > In the past I used variables in different way in the UD
> > > > > task-description.
> > > > > This question differs somehow ; depending on the agent
> > > > > determination by expression (in this case a table of US-user objects) I
> > > > > would like to specify the type of approver in the title.
> > > > > I can easily solve this by splitting up in branches depending on
> > > > > user-type, but I would like to avoid this.
> > > > >
> > > > > The difficulty is that the information is depending on an item of
> > > > > the agent determination at sending time.
> > > > >
> > > > > kind regards,
> > > > > Stefaan.
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > >
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
> >
>
> ------=_Part_13_25960703.1160553619132----
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061013/44b4a402/attachment.htm