TaskACL - Claim a task

How does the user claim a task from another queue? I can't find a way to achieve this through Workspace.
Aditya

If you claim a task, you are basically taking it from the share queue and make it your own. If User A has already entered some information in the form, then User B will see that information.
Now if User A wants it back, they need to make sure they have access to User B's queue to claim it again and make it their own.
If you use consult, then you might not have to worry about sharing. When you consult, you ask someone else to look at the form, before it comes back to you. This is more sequential in the sense the form will go to User B, and you'll have to wait for him to complete the consult action before you get it back.
Jasmin

Similar Messages

Claim a task

Hi there,
I have the problem that I cannot claim a task via the following code:
var taskId = getValueOfURLParameter("taskId");
// Create ODataModel for BPM Task Data OData service
var taskDataSvcURL = "/bpmodata/taskdata.svc/" + taskId;
var oDataModel = new sap.ui.model.odata.ODataModel(
     taskDataSvcURL, true);
odataModel.create("/Claim?InstanceID='"+taskId+"'", null);
In the logs I get the following error:
[EXCEPTION]
com.sap.core.odata.api.exception.ODataApplicationException: Could not find an entity set or function import for 'Claim'.
The task gets only claimed, if I open it from the UWL.
Then I'm also able to complete it with my SAPUI5 application.
How can I fix this issue?
I tried to enter my user and password when creating the oData model, but that didn't work.
Do I have to add some header data to the model to make it work?
We're running a NW 7.40 SP07 system.
Thanks in advance!
Best regards,
Thorsten.

Hi Andre,
Thanks, it works now...
But I had first to add the X-XSRF-Token header data to the model, otherwise it didn't work:
claimTask : function(taskId) {
     var tasksSvcURL = "/bpmodata/tasks.svc";
     var tasksODataModel =
          new sap.ui.model.odata.ODataModel(tasksSvcURL, false);
     // Add header data to the model
     tasksODataModel.setHeaders(
          "X-CSRF-Token" : "Fetch"
     tasksODataModel.create("/Claim?InstanceID='"+taskId+"'", null);
But still I don't know how user authentification works for SAPUI5 applications.
If I'm logged in to the NW system (e.g. NWA), I can run my application using the URL
http://<host>:<port>/<app_name>/index.html.
But if I run the SAPUI5 app without being logged on to the NW system, it doesn't work.
How can I setup the system in a way that it automatically asks for user authentification when a SAPUI5 application is launched.
I just read about "UI5 productivity services", but I couldn't find more information about it.

Human Task: Claimed Group task not visible to others in group

We've recently upgraded from SOA Suite 10.1.3 to SOA Suite 11.1.1.3.
We're using the standard worklist application in both versions.
In 10.x, if we assigned a Task to a Group, all members of the group would always see the task in the worklist application.
If a group member claimed the task, the other group members would still see the task in the work list, and could see the task details (read-only) in the detail screen
All group members could also see all group tasks, regardless of status/outcome (completed, withdrawn, refused, etc.) and regardless of the group member that completed the task, if they chose the filter "Any".
In 11g, a group task that is claimed by another group member disappears from the worklist (on refresh), and users only see completed group tasks if they completed the task themselves.
We did grant "View Task" to all roles for the *.task in JDeveloper ("Actions" Tab)
and either "Read" or "Write" for all combinations in the "Content" Tab.
Is this is a "feature" ?
Is there some way to configure the old behaviour ?

Can anyone put some thoughts on this.
For normal report if I give u2018view instancesu2019 right over the folder for users, they can see instance ran by other user. However if I try to do the same thing with publication it doesnu2019t work this way.
Only publisher or recipients can see the instance created in the folder ,for rest it shows a blank page saying u2018No items to displayu2019 . I tried to add other users in u2018administratoru2019 group and with that access also they could not see instance there for publication. Is this the expected behavior of publication. If so we might have to look for another approach to meet the requirement.
Thanks.

Claim Task: User claiming the task gets an email that task was claimed

When a user claims a task from the group queue an email is sent that the task was claimed to the user that claimed the task...
This notification is only nessecary when a task if forwarded by a collegaue. The person that gets the task then knows he personally should take action.
In AdminUI the group task assignment notification setting is switched off as we use a generic email process to inform all group members about a new task. The regular Task Assignment notifiction is switched on and in the Workbench we configured the component to use a custom email template that contains more process variables than those that are availble in the AdminUI.
I want to get rid of the email that is sent to the user informing that the task was claimed when the user was the one that claimed the task themselves.
Any sugesstions?

Vu.Tuan.Anh has posted the solution on this link: http://forums.adobe.com/thread/514211?tstart=0
It works great for me, hope it works for you too.
Han

Auto claim a Task in the Worklist and limit the amount of assings per user

Hi, I have two questions:
1) Is there a way to implement "auto claim" in the worklist? I need to assign the task to the logged user as soon as the task is opened by the user.
2) Is there a way to limit the amount of tasks that the user claims? I need to avoid the situation of a user claiming more than one task. In other words, I need that "If a user claims a task, he MUST release or action it before claiming another task"
Thanks in advance,
Edited by: Neuquino2 on Apr 30, 2010 1:03 PM
I'm working with 11g

Ok, I understand your use case for question 1. I actually have this same problem I have been trying to solve for a couple of weeks and haven't found a solution. My use case is slightly different. I have to assign to a group, but in some cases, I know which user in the group the task should be assigned to. However, the requirement is that I assign to the group. So I am trying to figure out how to use the routeTask method of the task service to route the task to the user after the task has already been created and assigned to the group. Not sure yet if that works. I have an SR open with Oracle Support. In your case, it sounds like you want the first member of the assigneeGroup who looks at the task to become the acquiredBy user. I would assume you would need to use routeTask in the Workflow API (in my case, I am using routeTask from BPEL).
On the second question, I doubt that you will find any out-of-box mechanism to do this. There are the three workload balancing rules built into workflow API and available in the worklist application - round robin, least busy, and most productive. But none of those will fit your requirement. However, supposedly you should be able to create your own algorithm. I don't know how to do this, but there should be some place in the documentation that tells you how to do it.

Prevent an email being sent when claiming a task

Using the assign task component in WorkBench ES, we initially assign a task to a group rather than an individual. We would like to continue sending the initial email when entering in a task. We would like to stop the email being sent to the user that claims the item. This is because the user needs to click a single button to process the task. By the time they receive the email, they have already processed the item. Any suggestions would be appreciated. - Thank you

Hi,
We got the same issue of getting email when the user claim the task which is confusing the user.
I saw the issue is corrected/fixed or is helpful, can you please share on how you got it corrected.
We are still using ES with SP3. We have enabled the Group - Task Assignment and Task Assignment.
Thanks,
Han Dao

Claiming the task by double clicking the task in tasklist (SOA-11g)

Hi,
In the worklist application one can claim the task by clicking on Claim button in the taskdetails page, but can we change this behaviour to Claim the task moment the user clicks the task in the tasklist summary page in the top section

If BPEL don't timed out, you can have Human task in Synchronous BPEL process.
For this, you can have your synchronous reply before any Human task call back receive activities (this causes the timeout) or you can just create human task and no other call back receive activities.
Thanks
--Sreeny

"Claim and open this task" option not working

A task has been assigned to a group.
There are two option icons at the lower-left bottom corner named:
1. Claim this task and make it to your own
2. Claim and open this task
Problem with the first option
When I choose this option, the task is assigned to me; I could open this form and it renders properly; But if i choose the attachments tab and come back to Form, the display area is blank.
Problem with the second option
when I click on the second option, i am unable to see both attachments and the form.
This problem occurs only if I assign task to a Group.
Any help on this..
Thanks,
Nith

This happens occasionally. If I relogin to workspace, it works fine.
I think there is something wrong with the flex app.
Hence closing this issue now.
Nith

'Claim' a Human Task through Workflow API

There is no function to "Claim" a task that is assigned to a group, through Workflow API.
There is a function to "Acquire" the task but after acquiring, the task cannot be completed (it throws exception):
java.lang.NoClassDefFoundError: com/collaxa/common/util/NonSyncPrintWriter
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at com.evermind.io.ClassLoaderObjectInputStream.resolveClass(ClassLoaderObjectInputStream.java:33)
     at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1538)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
     at com.evermind.server.rmi.RMIClientConnection.handleMethodInvocationResponse(RMIClientConnection.java:856)
     at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:287)
     at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:242)
     at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:224)
     at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:152)
     at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:127)
     at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:107)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
     at java.lang.Thread.run(Thread.java:595)
and if viewed through the default worklist application, there is no action available to the task after "Acquiring" through API.
How can we create a custom worklist application and complete tasks which are assigned to a group of users ?

Can you post how you are acquiring it and how you are attempting to complete it?

BPEL automatically releases claimed tasks after three days

We have a BPEL process deployed on a BPEL Process Manager v 10.1.3.3. This process uses Human Tasks to assign tasks to groups of users.
Users have to claim a task and update the outcome of it.
We noticed that when a task remained claimed for more than 3 days, bpel automatically released it (using bpeladmin-the owner of the task as the actor).
We haven't set any expiration or escalation policies, so my question is:
- is this behaviour a feature of BPEL? is there a way to control it, for example to turn it off?

I answer my questions!!
Well, it is a feature of the product and you can control it's behavior by altering parameters in the file wf_config.xml:
<taskAutoReleaseConfigurations>
<taskAutoRelease priority="1" default="P1D" percentageOfExpiration="30"/>
<taskAutoRelease priority="2" default="P2D" percentageOfExpiration="40"/>
<taskAutoRelease priority="3" default="P3D" percentageOfExpiration="50"/>
<taskAutoRelease priority="4" default="P4D" percentageOfExpiration="60"/>
<taskAutoRelease priority="5" default="P5D" percentageOfExpiration="70"/>
</taskAutoReleaseConfigurations>
My tasks have normal priority and so they will be auto-released after 3 days or after passing 50% of the expiration time.

Bypass "Claim" action on a Human Task

We are going to start user testing of our first BPEL process. The human tasks are set up to have a single approver, but they are assigned to a group of users. The users want to know if there is a way to by-pass having to claim the task, so that just one user could select the outcome they want without first having to claim the task. Is that possible, or must a task first be claimed by one of the people in the group before the actual outcome can be selected?
Bonnie

To achieve this functionality I am afraid you must modify worklist application code. I faced the same requirement some time ago, I simply modified dropdown box so that it alway displayed actions and before update on task added code that claimed task for user performing update.
HTH,
Rad

BPEL Human Task Claim functionality Understanding

Hi all,
On a task with multiple assignees, it appears that each assignee has to claim the task before completing it. Some queries that I had on claim functionality -
1. Is there a way by which we can avoid the process of 'claiming' the task before completing?
2. Is there a way programmatically to release the claim? I saw releaseTask() API in TaskService class - but I observed that if a task has been claimed by an assignee - other assignees are unable to release this task. Any suggestions here?
Thanks,
Srini

Hi all,
On a task with multiple assignees, it appears that each assignee has to claim the task before completing it. Some queries that I had on claim functionality -
1. Is there a way by which we can avoid the process of 'claiming' the task before completing?
2. Is there a way programmatically to release the claim? I saw releaseTask() API in TaskService class - but I observed that if a task has been claimed by an assignee - other assignees are unable to release this task. Any suggestions here?
Thanks,
Srini

Task status after claimed by a user

Hello,
I assign task to a role on bpm server so users have the this particular role can see this task on their respective UWL list, with the task status 'New'. This is normal bpm procedure and works good.
However, when one of the user who has this role (for ex: user_a) clicks on the task link on the uwl this user claims the task and the status of the task changes into 'processing'. Therefore other users can not see the task on their own UWL.
(standart procedure for assigning the task to a role)
But customer requests that; other users who have this role could see the task on their own uwl even after one of them review the task (claimed the task but has not approved yet, just reviewed ). Is this possible ?
Regards,
Yasin

Yasin,
The user can review the task, then may be add some comments if any and put it back to the pool (i.e role to which the users are mapped) by using "Put Back" option available in the task UI available in the top right corner. This way multiple users who have access to the same task can review / add inputs.
Hope this helps.
My best,
Bala

Extra task instruction email sent when task is claimed from group que

Jasmin or whoever can help,
Task instruction and reminder emails are sent correctly to my group members but when someone claims a task from the group que they get another task instruction email as soon as it hits their personal que. Is this a bug or is there something I can do to keep it from happening?
Thanks for your help,
Brian

Hi Brian
This is not a bug.
When tasks are assigned to a group queue, members of the group receive an email notification if the administrator has turned on the Group - Task Assignment setting on the Task Notifications page.
Once the task is claimed, it is assigned to a individual user's queue.
That individual will also receive an email notification if the Administrator has turned on the Task Assignment setting on the Task Notifications page.
If you turn off the Task Assignment setting to stop the personal queue email, you will be turning off individual assignment notifications globally on the server.
Diana

BPEL Need help with Task Form's bindings' Claim

Hi,
I have a customer requirement, they want something like, if there is only one member in a group, when he views the task form from webcenter or from the worklist, the task should be automatically claimed, so he doesn't have to claim the task, and then ongo with what the task-form offers.
I have seen that Claim method comes from the bindings to the taskDetails.jspx, the code is below which auto-claims the task:
DCBindingContainer binding = (DCBindingContainer)getBindings();
DCIteratorBinding iter = binding.findIteratorBinding("taskIterator");
OperationBinding bind = bindings.getOperationBinding("Claim");
bind.execute();
However, there are two problems with this approach.
1) The Task Form isn't getting updated with the buttons that comes after claiming the task(yes-no-approve-reject-whatever).
2) If the task is allready claimed, there is an exception.
The second one, I can manage to overcome somehow, but the first one, I am asking you damn it :)
Any help would be most appreciated!

Can someone please help?

TaskACL - Claim a task

Similar Messages

Maybe you are looking for