Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1656

Incorrect correlation key shown in the Task list (RHPAM UI)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.2.0.GA
    • 7.0.2.GA
    • Business Central
    • None
    • RHPAM 7.0.2

    • 1
    • CR1
    • ?
    • Workaround Exists
    • Hide

      Workaround exist:

      1. Stop the server;
      2. Delete the query - jbpmHumanTasksWithUser - from the database (querydefinitionstore table);
      3. Change the query manually inside the git - by changing the following dataset:

      *****************************

      RHPAM_HOME//bin/.niogit/system/datasets/definitions/jbpmHumanTasksWithUser.dset

      *****************************

      4. Start the server;

      Show
      Workaround exist: 1. Stop the server; 2. Delete the query - jbpmHumanTasksWithUser - from the database (querydefinitionstore table); 3. Change the query manually inside the git - by changing the following dataset: ***************************** RHPAM_HOME//bin/.niogit/system/datasets/definitions/jbpmHumanTasksWithUser.dset ***************************** 4. Start the server;
    • Hide

      1. Create process instance with task;
      2. Assign correlation key;
      3. Start the process;
      4. Navigate to the process instance and confirm that correct correlation key is shown;
      5. Navigate to the task page in the business central for above process instance and confirm that correlation key is not correct.

      Show
      1. Create process instance with task; 2. Assign correlation key; 3. Start the process; 4. Navigate to the process instance and confirm that correct correlation key is shown; 5. Navigate to the task page in the business central for above process instance and confirm that correlation key is not correct.
    • 2018 Week 42-44

      The correlation key shown for the task (in the task list page in RHPAM UI) differs from the correlation key of the process instance (where the task is running).

      It seems that the following query - jbpmHumanTasksWithUser [1] - is incorrect:

      *****************************
      {
      "query-name" : "jbpmHumanTasksWithUser",
      "query-source" : "${org.kie.server.persistence.ds}",
      "query-expression" : "select t.activationTime, t.actualOwner, t.createdBy, t.createdOn, t.deploymentId, t.description, t.dueDate, t.name, t.parentId, t.priority, t.processId, t.processInstanceId, t.processSessionId, t.status, t.taskId, t.workItemId, t.lastModificationDate, pil.correlationKey, pil.processInstanceDescription , oe.id from AuditTaskImpl t left join PeopleAssignments_PotOwners po on t.taskId=po.task_id left join OrganizationalEntity oe on po.entity_id=oe.id left join ProcessInstanceLog pil on pil.id=t.processInstanceId",
      "query-target" : "FILTERED_PO_TASK"
      }
      *****************************

      as it is doing:

      *****************************

      left join processinstancelog pil on pil.id=t.processinstanceid

      *****************************

      and it should be:

      *****************************

      left join processinstancelog pil on pil.processinstanceid=t.processinstanceid

      *****************************

              cnicolai@redhat.com Cristiano Nicolai (Inactive)
              rhn-support-bkramer1 Biljana Kramer
              Tomas David Tomas David
              Tomas David Tomas David
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: