OIM-SOA: Populating wftask table with custom attributes

Many a times, for reporting or other purposes, we need to populate the data the wftask table(directly mapped to human task in composite) with some custom data.

This custom data can be data from the payload or any other data that is present in the composite.

Updating the wftask table with the composite data can avoid writing bpel apis and a query suffices in this case.

How to do it, is probability what you are interested in. This is done by a simple assignment in the human task.

1. Expand your human task in the composite. You should see a construct like 'taskName_AssignTAskAttributes'

    2. This is where you need to assign the variables. You can do it in design editor, or can copy the following lines in BPEL file.

<copy> 

      <from variable="inputVariable" part="payload" 

        query="/client:process/client:EntityKey"/> 

      <to variable="initiateTaskInput" part="payload" 

       query="/taskservice:initiateTask/task:task/task:customAttributes/task:customAttributeString1"/> 

</copy> 

<copy> 

  <from variable="inputVariable" part="payload" 

   query="/client:process/client:BeneficiaryLogin"/> 

  <to variable="initiateTaskInput" part="payload" 

   query="/taskservice:initiateTask/task:task/task:customAttributes/task:customAttributeString2"/> 

</copy>

You might want to edit the data in from and to depending on your exact requirement.

3. Now, once you deploy and test the composite. You will see the two columns 'customAttributeString1' and 'customAttributeString2' populated in your wftask table.

OIM: Task Assignee not visible in track request

Sometimes, after you deploy your composite and raise a request which in turn invokes your custom composite, the following situation is encountered:
1. Request status shows 'Request Awaiting Approval'.
2. Task is assigned to the correct assignee and the assignee can see it in his/her inbox.
3. When anyone tracks the request, the request assignee are not visible.

This is because, the task was not correctly associated with the request.
To associate the task,
1. Open your .bpel file in jdeveloper.
2. Double click on the human task that was invoked.
3. In the 'Initiator' field in 'General' tab, give the login of the requester:
<%bpws:getVariableData('inputVariable','payload','/ns3:process/ns4:RequesterDetails/ns4:Login')%>

4. Now, navigate to 'Advanced' tab and give requestID in the 'Identification Key' field.

5. Redeploy the composite and test.

OIM: Release a claimed task

Detailed Steps:

1. Login into BPM worklist URL (http://hostname:port_number/integration/worklistapp).

a. Please note that ‘port_number‘ is soa server’s port(8001).

2. In the left hand navigation tree, click on ‘Administrative Tasks’

3. Click on the ‘pencil icon’ on the top of the navigation tree to edit the inbox settings. Specifically, we are adding more column in the main window.

4. Click on  the down arrow next to the ‘magnifying glass’ icon on top of the main window and select ‘Advanced’

a. This is used to specify the search filter. This is a one-time activity, search filter can be saved as a view.

5. Specify the search condition

6. As per the search conditions, this will give you all the tasks which satisfy all the following conditions:

a. Are raised for disconnected provisioning.

b. Are acquired by a user with user login as ‘RAGNI’

c. Are in ‘assigned’ status.

7. All tasks will be displayed, satisfying the search criterion.

8. You can select the claimed task and, and from the ‘Actions’ dropdown select ‘Release’ to un-

claim

SOA: JBO-29000: Unexpected exception caught: oracle.bpel.services.workflow.client.WorkflowServiceClientException, msg=javax.naming.NameNotFoundException: Unable to resolve 'TaskQueryService'.

Check soa-infra.war's status from admin console. Restart the same.

OIM SOA - Callback Server URL location

1. Login into EM console.
2. Right click on SOA -> SOA_INFRA -> SOA Administration -> Common Properties
3. The callback server url will be inside Server URLs section

Callback server URL location

SOA: Enable auto claim in SOA human task

Add the following line in the .task file in your composite.

<enableAutoClaim>true</enableAutoClaim> inside <workflowConditions> </workflowConditions> tag