How to restrict an agent assigment task... and also restrictaworkitem for the Inbox for only one user.

Wed Apr 12 10:58:09 EDT 2006

Exactly,, that's what I tried first, but It didn't work... when I check the
value in the workitem container, it's empty...

On 4/12/06, Gavin Mooney <gavinmooney at gmail.com> wrote:
>
> Hang on... the container operation step was just so you could test
> whether your container element was defined correctly and that the
> binding from that to the work item was OK.
>
> If you have a step that's populating the container element with a user
> ID (in this case USUSER1) then you don't need the container operation
> - just bind in the container element as the expression for agent
> assignment on the work item (subsequent step I assume)
>
> 2006/4/12, Markkos <markkos at gmail.com>:
> > Well, In the workitem container of the step that obtains the userID, the
> > string 'USUSER1' is there, but then when I try a container operation,
> the
> > value doesn't appear.. it's empty.
> >
> >
> > On 4/12/06, Gavin Mooney <gavinmooney at gmail.com> wrote:
> > > Check the bindings into the WFSYST-AGENT container element and from
> > > that to the Agent for your work item.
> > >
> > > If they're ok then it sounds like a buffering problem, especially if
> > > you're seeing it in the task container in the log...
> > >
> > > 2006/4/12, Markkos <markkos at gmail.com>:
> > > > I tried hardcoding it right now, and it works...
> > > >
> > > >  I don't know why the element lose the value within the workflow...
> > > >
> > > >  Any comments?
> > > >
> > > >
> > > > On 4/12/06, Gavin Mooney < gavinmooney at gmail.com> wrote:
> > > > > Markkos,
> > > > >
> > > > > You're saying that even hard-coding (via Container Operation) a
> > > > > username into a container element and then routing the subsequent
> > > > > workflow step to that container element (as an Expression) doesn't
> > > > > make the work item go to the right person?
> > > > >
> > > > > Your container element is defined as like WFSYST-AGENT and you're
> > > > > hardcoding the agent as e.g. USMARKKOS where MARKKOS is the
> username?
> > > > >
> > > > > Maybe a binding problem then?
> > > > >
> > > > >
> > > > > 2006/4/11, Markkos < markkos at gmail.com>:
> > > > > > Yes Gavin , You understood, it's what you said...
> > > > > >
> > > > > >  And you were right, no value is passing through the container
> > > > operation...
> > > > > > the strange thing here, is that I've checked the container of
> the
> > task
> > > > that
> > > > > > determines the user, and there it is...
> > > > > >
> > > > > >  well, I tried to do several container operations without
> > succeeding.. I
> > > > > > don't know what's the problem now...
> > > > > >
> > > > > > at least thanks for your comments...
> > > > > >
> > > > > >
> > > > > > On 4/11/06, Gavin Mooney <gavinmooney at gmail.com > wrote:
> > > > > > > Markkos,
> > > > > > >
> > > > > > > You say that the user can be any user for each run of the
> > workflow,
> > > > > > > and that this user is determined in the preceding step. If the
> > agent
> > > > > > > can be literally anyone, then your task may well need to be a
> > general
> > > > > > > task.
> > > > > > >
> > > > > > > However the attribute "general task" belongs at the task
> level,
> > and if
> > > > > > > you want the work item to be sent to the user identified in
> the
> > > > > > > previous step then that will be assigned at the workflow step
> > level as
> > > > > > > an 'Expression' where you insert the name of your container
> > element
> > > > > > > that contains the user(s). I think that might be what you're
> doing
> > > > > > > already but I'm not sure I understood everything that you
> wrote.
> > > > > > >
> > > > > > > If the work item is going to everyone then it sounds like the
> > > > > > > container element with your agents in is empty. Are you sure
> the
> > > > > > > previous step is populating it correctly? To test this you
> could
> > put a
> > > > > > > 'Container Operation' before your work item step and hard code
> a
> > user
> > > > > > > ID into the container element then see if the work item is
> sent to
> > > > > > > that ID.
> > > > > > >
> > > > > > > HTH,
> > > > > > > Gavin
> > > > > > >
> > > > > > > 2006/4/11, Markkos <markkos at gmail.com>:
> > > > > > > > The question is:
> > > > > > > >
> > > > > > > >  How do I have an agent assigned task without having it as a
> > general
> > > > > > task?
> > > > > > > > (Using an expression as the element (that will contain the
> SAP
> > User
> > > > ID,
> > > > > > with
> > > > > > > > the US preceding...)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 4/11/06, Markkos < markkos at gmail.com > wrote:
> > > > > > > > >
> > > > > > > > > First, to Larry: No, I don't want to send it to myself.
> > > > > > > > >
> > > > > > > > > Second, Kjetil: is not the two points you wrote, it's "one
> and
> > > > only
> > > > > > one
> > > > > > > > user receives a task of this type, but this can be any user
> for
> > each
> > > > run
> > > > > > of
> > > > > > > > the workflow". Because I determine this user in a previous
> task.
> > > > > > > > >
> > > > > > > > > The problem is that when I put the element of the user
> agent I
> > > > > > determine,
> > > > > > > > It seems that it doesn't respect it, all users will receive
> a
> > > > workitem.
> > > > > > And
> > > > > > > > it should be only the one in the element (and it
> contanins...for
> > > > > > example,
> > > > > > > > USUTEST1).
> > > > > > > > >
> > > > > > > > > I mean, why if I specify the user in the element, only the
> > user
> > > > should
> > > > > > > > receive the workitem notification,,, why all the others
> users
> > > > receive
> > > > > > the
> > > > > > > > same workitem in their inbox... how come??
> > > > > > > > >
> > > > > > > > > Need some help with this issue.. I'll appreciate... thanks
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 4/11/06, lianghuan.x.hu at accenture.com <
> > > > > > lianghuan.x.hu at accenture.com >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Perhaps what Markkos wants is simply to send the work item
> to
> > > > himself.
> > > > > > If
> > > > > > > > this is the case, then instead of using "Expression" and the
> > > > container
> > > > > > > > element, try to use "US User", and  "RETZ10".
> > > > > > > > >
> > > > > > > > > Larry Hu
> > > > > > > > >
> > > > > > > > > ________________________________
> > > > > > > >  From: sap-wug-bounces at mit.edu [mailto:
> sap-wug-bounces at mit.edu
> > ] On
> > > > > > Behalf Of
> > > > > > > > Kjetil Kilhavn
> > > > > > > > > Sent: Monday, April 10, 2006 2:57 AM
> > > > > > > > >
> > > > > > > > > To: SAP Workflow Users' Group
> > > > > > > > >
> > > > > > > > > Subject: RE: How to restrict an agent assigment task...
> and
> > also
> > > > > > > > restrictaworkitem for the Inbox for only one user.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I am not quite sure if I understand what your requirement
> is.
> > > > > > > > >
> > > > > > > > > Is the requirement to ensure that
> > > > > > > > > a) you and only you (or any other user - but always the
> same)
> > > > receive
> > > > > > all
> > > > > > > > tasks of this type?
> > > > > > > > > b) one and only one user receives a task of this type, but
> > this
> > > > can be
> > > > > > any
> > > > > > > > user for each task?
> > > > > > > > >
> > > > > > > > > If your requirement is a) then the easiest solution would
> be
> > to
> > > > > > restrict
> > > > > > > > the possible agents of the task I imagine. In other words,
> don't
> > > > have a
> > > > > > > > general task.
> > > > > > > > >
> > > > > > > > > If your requirement is b) then one solution is to create a
> > role,
> > > > and
> > > > > > mark
> > > > > > > > the "Terminate if role resolution has no result" check box.
> The
> > role
> > > > > > would
> > > > > > > > e.g. take a user ID as input, check the validity of the user
> and
> > > > return
> > > > > > it
> > > > > > > > prefixed by US. Store the user ID that you pass in in a
> workflow
> > > > > > container
> > > > > > > > element so you can change it and restart the workflow if
> there
> > is a
> > > > > > problem.
> > > > > > > > > --
> > > > > > > > > Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ________________________________
> > > > > > > >  From: sap-wug-bounces at mit.edu [mailto:
> sap-wug-bounces at mit.edu]
> > On
> > > > > > Behalf Of
> > > > > > > > Markkos
> > > > > > > > > Sent: 7. april 2006 17:43
> > > > > > > > > To: SAP Workflow Users' Group
> > > > > > > > > Subject: How to restrict an agent assigment task... and
> also
> > > > restrict
> > > > > > > > aworkitem for the Inbox for only one user.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Hi, I have problems with workitems restrictions...
> > > > > > > > >
> > > > > > > > > I have a task that must to be review only by a user, so I
> have
> > > > created
> > > > > > a
> > > > > > > > WFSYST-AGENT type element for the agent, so in the Agents
> task
> > > > section
> > > > > > I've
> > > > > > > > selected the "Expression" option filled with my element
> > > > (UserId_Agent),.
> > > > > > In
> > > > > > > > the other hand, I've checked the "Agent Assignment" (in Task
> > > > Properties)
> > > > > > > > option so the user will received the workitem in his inbox.
> In
> > the
> > > > > > "Standard
> > > > > > > > task: Maintain Agent Assignment" I have selected
> the  General
> > Task
> > > > > > > > Attribute.
> > > > > > > > >
> > > > > > > > > The problem here, is that all the users are receiving this
> > > > workitem in
> > > > > > > > their inbox, and I just want it for the user I stated in the
> > Element
> > > > > > i've
> > > > > > > > created (that contains 'USRETZ10', where 'RETZ10' is my
> userID).
> > > > > > > > >
> > > > > > > > > How can I restrict the agent assignment for only and only
> one
> > > > user...
> > > > > > > > (I've tried to use the excluded field). And for getting
> things
> > > > worse,
> > > > > > any
> > > > > > > > user can proceed with the task, and that's not supposed to
> be.
> > > > > > > > >
> > > > > > > > > Maybe you can help me with this,,, I'll appreciate any
> > > > comments....
> > > > > > > > >
> > > > > > > > > thanks in advance.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> > -------------------------------------------------------------------
> > > > > > > > > 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.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > This message is for the designated recipient only and may
> > contain
> > > > > > > > privileged, proprietary, or otherwise private information.
> If
> > you
> > > > have
> > > > > > > > received it in error, please notify the sender immediately
> and
> > > > delete
> > > > > > the
> > > > > > > > original. Any other use of the email by you is prohibited.
> > > > > > > > >
> > > > > > > > >
> > _______________________________________________
> > > > > > > > > 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
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> >
> >
> >
>
> _______________________________________________
> 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/20060412/b43621e2/attachment.htm