Hi Stefaan,<br>
<br>
I got the same problem I think.<br>
<br>
I used the standard text (SO10) put in the long text of the tasks.<br>
Also I built a table with the rule and its standard text.<br>
<br>
Hope this help you.<br>
<br>
Yves.<br>
<BR><BR><BR> <br>
<HR>
<br>
------=_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 <MARK.PYC@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@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@GMAIL.COM>:> > >> > > 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@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@mit.edu> > > > http://mailman.mit.edu/mailman/listinfo/sap-wug> > > >> > > >> > > >> > >> > > _______________________________________________> > > SAP-WUG mailing list> > > SAP-WUG@mit.edu> > > http://mailman.mit.edu/mailman/listinfo/sap-wug> > >> > >> > >> >> > _______________________________________________> > SAP-WUG mailing list> > SAP-WUG@mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >> >!
>
>>> _______________________________________________> SAP-WUG mailing list> SAP-WUG@mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug>>>------=_Part_13_25960703.1160553619132<br>
One task for multiple recipients, thats the case.<br>
I agree with you that I'm a bit stuck and will have to split the groups up in advance.<br>
<br>
thanks anyways,<br>
Stefaan. <BR><BR> <br>
<SPAN class=gmail_quote>2006/10/11, Mark Pyc <<A href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</A>>:</SPAN>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
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. <br>
<br>
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.<br>
<br>
You may be stuck.<br>
<br>
Good luck,<br><SPAN class=sg>
Mark<BR><BR> <br></SPAN>
<SPAN class=e id=q_10e3658b15350e11_2>
<SPAN class=gmail_quote>On 10/11/06, <B class=gmail_sendername>Stefaan Vermeulen</B> <<A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:stefaan.vermeulen@gmail.com" target=_blank>stefaan.vermeulen@gmail.com</A>> wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
Mark,<br>
<br>
Thanks for the reaction, but by reading trough my question I saw I wasn't clear or complete.<br>
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.<br>
<br>
Now some US-users in this table are Host, some are Deputies depending on an attribute at user level.<br>
<U>So the problem is</U> ;when wf dipatches the task to the specific user, you should be able to react dynamicly on this.<br>
<br>
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.<br>
<br>
This works , but has his consequences, therefore I wondered if there would be another way.<br>
<br>
thanks,<br>
Stefaan.<BR><BR> <br>
<SPAN class=gmail_quote>2006/10/10, Mark Pyc <<A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:mark.pyc@gmail.com" target=_blank>mark.pyc@gmail.com</A>>:</SPAN>
<SPAN>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
G'day Stefaan,<br>
<br>
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. <br>
<br>
Have fun,<br>
Mark.<BR><BR> <br>
<SPAN><SPAN class=gmail_quote>On 10/10/06, <B class=gmail_sendername>Stefaan Vermeulen</B> <<A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:stefaan.vermeulen@gmail.com" target=_blank> stefaan.vermeulen@gmail.com</A>> wrote:</SPAN> </SPAN><br>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<SPAN>
Hi all,<br>
<br>
In the past I used variables in different way in the UD task-description.<br>
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.<br>
I can easily solve this by splitting up in branches depending on user-type, but I would like to avoid this.<br>
<br>
The difficulty is that the information is depending on an item of the agent determination at sending time.<br>
<br>
kind regards,<br><SPAN>
Stefaan.<br></SPAN><BR></SPAN><br>_______________________________________________<BR>SAP-WUG mailing list<BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target=_blank>SAP-WUG@mit.edu</A><BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE><br><BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target=_blank>SAP-WUG@mit.edu</A><BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE></SPAN><br><br><BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A onclick="return
top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target=_blank>SAP-WUG@mit.edu</A><BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE><br><BR></SPAN><br><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE><br>
<BR>------=_Part_13_25960703.1160553619132----<BR><BR><br>