Tuesday, June 4, 2013

BPM 11g Workspace - Initiator Task: No Applications Found

Of late, I have been seeing users getting this issue of not being able to initiate the BPM process due to non-availability of the process under the "Available Processes" panel in the BPM workspace.

This issue is not specific to Initiator tasks and can occur for any human task in a BPM process. Note that this issue is tough to reproduce and is very intermittent.

Not to worry. It is curable ;)

Check 1:

Ensure that the role mapping is done for the BPM application roles in the BPM workspace

Check 2:

1. Login to EM console as administrator
2. Choose your BPM application under soa-infra -> default
3. On the RHS, click on the appropriate human task under the "Component Metrics" section
4. On the resulting screen, go to Administration tab
5. Check if taskform URI information is available

More often, this information might be missing and you may have to manually configure this;

Sample information is provided below (Click on the "Add URI" button)

Application Name: worklist
Host Name: localhost (provide appropriate hostname information here)
HTTP Port: 8001 (SOA managed server port)
HTTPS Port: 0
URI: /workflow/ManageOrderUI/faces/adf.task-flow?_id=ManageOrderTask_TaskFlow&_document=WEB-INF/ManageOrderTask_TaskFlow.xml

URI information is just an example. Update it to match your ADF taskflow definition.

Hope this helps in the resolution of the issue.

13 comments:

  1. Thanks. Do you know if there is a place in EM to enter the localhost to be used for all future deployments of human tasks? I am changing "localhost" to my current server name, after every deployment. Thanks!

    ReplyDelete
    Replies
    1. Hi Matias,

      Please refer to my blog post here: http://sathyam-soa.blogspot.com/2013/07/solving-bpm-ps6-11117-webform-rendering.html

      Delete
  2. Hi,

    I verified both the steps above but still not able to see the Application that I created and deployed referring the tutorial : http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/obpm/11g/r1/firstProcess/firstprocess_obpm11g.htm

    Please help.

    Thanks and Regards,
    Vijay Inani

    ReplyDelete
    Replies
    1. Do you have an initiator task in your BPM process? If so, check whether you assigned it to a user/group.

      This post covers some scenarios which helps to resolve initiator task issue where despite normal process setting/configuration issue prevails.

      Delete
  3. worked for me BPM 12c release, thanks :)

    ReplyDelete
  4. hi
    I have a problem and searching for it a lot! but finding not.
    I have lots of process with initiator task. I want to change the name of this process the "Available Processes" panel in the BPM workspace. because the deployed name are not nice for my users! can you help me?!

    ReplyDelete
  5. Hi! I want to permanently solve this problem before deployment, as it happens to some of my ADF projects but not others, do you know what causes this in the first place?

    ReplyDelete
    Replies
    1. Rosi, what version of BPM are you on? I am aware that this issue is no longer a concern in 12c releases.

      Delete
  6. Hi BPM Experts,
    I am using BPM12c, I couldn't get link for open adf form from workspace. If I select assigned task, it gives ADF form in bottom of workspace only. But I need to open with separate form. Can you help me our this

    ReplyDelete
    Replies
    1. Just double click on your task instead of single click. The task form will pop out.

      Delete
  7. Hi Sathya,
    Thanks for your valuable post.

    I am using BPM12.2.1.0.0, I couldn't see the assigned task in approval form. I am submitting form in initiator task --> logout from initiator and login to approver. Here, the assigned task is to getting approver inbox. the same code is working fine in my local server, if I deployed into DEV environment, which is running as cluster, its not working.

    Appreciate your help

    ReplyDelete
    Replies
    1. You must check the organization and user assignment in your Dev server. That seems to be the issue. Users in your local may not be there in your Dev server.

      Delete