-
Bug
-
Resolution: Done
-
Major
-
7.12.0.GA
-
False
-
-
False
-
-
-
-
-
-
CR1
-
-
-
2022 Week 14-16 (from Apr 4), 2022 Week 17-19 (from Apr 25), 2022 Week 20-22 (from May 16), 2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27), 2022 Week 29-31 (from Jul 18)
The custom query response does not return the "SLAdueDate" with UserTasksWithCustomVariables mapper. If different mapper like UserTasks is used, then SLAdueDate is returned correctly.
It seems like the "QueryMapper" for "UserTaskInstanceWithCustomVarsQueryMapper" only has below values in the build instance. It doesn't have "COLUMN_TASK_SLA_DUE_DATE" mapped.
protected UserTaskInstanceWithVarsDesc buildInstance(DataSet dataSetResult, int index) {
UserTaskInstanceWithVarsDesc userTask = new org.jbpm.kie.services.impl.model.UserTaskInstanceWithVarsDesc(
getColumnLongValue(dataSetResult, COLUMN_TASKID, index),//taskId,
getColumnStringValue(dataSetResult, COLUMN_TASK_STATUS, index),//status,
getColumnDateValue(dataSetResult, COLUMN_ACTIVATIONTIME, index),//activationTime,
getColumnStringValue(dataSetResult, COLUMN_NAME, index),//name,
getColumnStringValue(dataSetResult, COLUMN_DESCRIPTION, index),//description,
getColumnIntValue(dataSetResult, COLUMN_PRIORITY, index),//priority,
getColumnStringValue(dataSetResult, COLUMN_ACTUALOWNER, index),//actualOwner,
getColumnStringValue(dataSetResult, COLUMN_CREATEDBY, index),//createdBy,
getColumnStringValue(dataSetResult, COLUMN_DEPLOYMENTID, index),//deploymentId,
getColumnStringValue(dataSetResult, COLUMN_TASK_PROCESSID, index),//processId,
getColumnLongValue(dataSetResult, COLUMN_TASK_PROCESSINSTANCEID, index),//processInstanceId,
getColumnDateValue(dataSetResult, COLUMN_CREATEDON, index),//createdOn,
getColumnDateValue(dataSetResult, COLUMN_DUEDATE, index)//dueDate
);
return userTask;
}
Whereas "UserTaskInstanceQueryMapper" has additional parameters like "COLUMN_TASK_SLA_DUE_DATE" in the build instance.
protected UserTaskInstanceDesc buildInstance(DataSet dataSetResult, int index) { UserTaskInstanceDesc userTask = new org.jbpm.kie.services.impl.model.UserTaskInstanceDesc( getColumnLongValue(dataSetResult, COLUMN_TASKID, index),//taskId, getColumnStringValue(dataSetResult, COLUMN_TASK_STATUS, index),//status, getColumnDateValue(dataSetResult, COLUMN_ACTIVATIONTIME, index),//activationTime, getColumnStringValue(dataSetResult, COLUMN_NAME, index),//name, getColumnStringValue(dataSetResult, COLUMN_DESCRIPTION, index),//description, getColumnIntValue(dataSetResult, COLUMN_PRIORITY, index),//priority, getColumnStringValue(dataSetResult, COLUMN_ACTUALOWNER, index),//actualOwner, getColumnStringValue(dataSetResult, COLUMN_CREATEDBY, index),//createdBy, getColumnStringValue(dataSetResult, COLUMN_DEPLOYMENTID, index),//deploymentId, getColumnStringValue(dataSetResult, COLUMN_TASK_PROCESSID, index),//processId, getColumnLongValue(dataSetResult, COLUMN_TASK_PROCESSINSTANCEID, index),//processInstanceId, getColumnDateValue(dataSetResult, COLUMN_CREATEDON, index),//createdOn, getColumnDateValue(dataSetResult, COLUMN_DUEDATE, index),//dueDate getColumnLongValue(dataSetResult, COLUMN_WORKITEMID, index), //workItemId getColumnStringValue(dataSetResult, COLUMN_FORM_NAME, index), getColumnStringValue(dataSetResult, COLUMN_SUBJECT, index), getColumnStringValue(dataSetResult, COLUMN_CORRELATIONKEY, index), getColumnIntValue(dataSetResult, COLUMN_PROCESSTYPE, index), getColumnDateValue(dataSetResult, COLUMN_TASK_SLA_DUE_DATE, index), getColumnIntValue(dataSetResult, COLUMN_TASK_SLA_COMPLIANCE, index) ); return userTask; }
These additional variables seem to be added as part of this commit .
Not sure why these new variable were not added to other mappers.
