Questions Tagged With additional-property

TaskQuery with additional property

dolong — Tue, 06 Jun 2017 06:25:16 -0400

Hi everyone,

I have the issue related to additional property in TaskQuery: Task A doesn't have any additional property and Task B has the "DISPLAY" additional property.

TaskQuery stateQuery = TaskQuery.create().where().state().isEqual(TaskState.SUSPENDED).or().state().isEqual(TaskState.RESUMED).or().state().isEqual(TaskState.PARKED);
TaskQuery additionalPropertyQuery = TaskQuery.create().where().additionalProperty("HIDE").isNull();
TaskQuery query = TaskQuery.create().where().and(stateQuery).and(additionalPropertyQuery);

==> The result of this query is only Task A. I expect that the result is A and B.

Do you have any suggestions?

Why does Axon.ivy persist an ICase when `setAdditionalProperty` is invoked even if there is no TaskSwitch element?

Genzer Hawker — Fri, 29 Apr 2016 05:40:29 -0400

There written in the public document:

Normally, a case is started non persistent. This means it is stored in memory only. As soon as the process hits a task switch the case and its tasks will be made persistent by storing them to the system database.

I just found out that you can make an ICase persisted without any TaskSwitch element in the process by setting an additionalProperty.

As soon as the line of code is evaluated:

ivy.case.setAdditionalProperty("anything-will-do", "some-value");

The ICase will be persisted immediately.

Is this a non-public behaviour or a bug in the API?

P.S: there is a demo project to demonstrate this behaviour at https://www.mediafire.com/?hxi3z0v27dhjxh4

`TaskQuery.and(TaskQuery)` and `CaseQuery.and(CaseQuery)` doesn't work with `additionalProperty()`.

Genzer Hawker — Wed, 27 May 2015 09:04:31 -0400

On our project, we extensively uses the API TaskQuery and CaseQuery in order to find ITask and ICase respectively. We also make use of the additionalProperty of both ITask and ICase in order to store custom fields.

However, we later found out that the method and(TaskQuery and or(TaskQuery) doesn't work with the criteria additionalProperty.

Consider the below snippet of code:

public List<ITask> findTask() {
    Ivy.wf().getTaskQueryExecutor()
            .getResults(TaskQuery.create().where()
                    .state().isEqual(SUSPENDED)
                    .and(hasCustomField()));
}

private static TaskQuery hasCustomField() {
    return TaskQuery.create().where().additionalProperty("custom").isLike("customized_value");
}

Runing the code will result as an exception:

java.sql.SQLException: Column not found: ADDITIONALPROPERTYFORTASK.NAME in statement [SELECT IWA_TASKQUERY.TASKID ....... FROM IWA_TaskQuery WHERE (IWA_TASKQUERY.APPLICATIONID = ? AND (IWA_TASKQUERY."STATE" = ? AND ((ADDITIONALPROPERTYFORTASK.NAME = ? OR ADDITIONALPROPERTYFORTASK.NAME IS NULL) AND ADDITIONALPROPERTYFORTASK."VALUE" LIKE ?))) ORDER BY IWA_TASKQUERY.TASKID ASC]

While this works:

public List<ITask> findTask() {
    Ivy.wf().getTaskQueryExecutor()
            .getResults(TaskQuery.create().where()
                    .state().isEqual(SUSPENDED)
                    .and().additionalProperty("custom").isLike("customized_value");
}

Please note that only the criterion additionalPropety() has this problem, the other criteria don't.

Digging a little deeper, I found that the queries produced are different:

The former (the problematic one) produces:

SELECT * FROM IWA_Task WHERE
 (Column(IWA_TaskQuery.State) = 4 &amp;&amp;
 ((Column(AdditionalPropertyForTask.Name) = custom || Column(AdditionalPropertyForTask.Name) IS NULL)
    &amp;&amp; Column(AdditionalPropertyForTask.Value) LIKE customized_value))

...whereas the latter produces (correctly):

SELECT *  FROM IWA_Task 
LEFT JOIN IWA_TaskAdditionalProperty ON Column(IWA_TaskQuery.TaskId) = Column(IWA_TaskAdditionalProperty.TaskId)
LEFT JOIN IWA_AdditionalProperty ON Column(IWA_TaskAdditionalProperty.AdditionalPropertyId) = Column(IWA_AdditionalProperty.AdditionalPropertyId)
WHERE (Column(IWA_TaskQuery.State) = 4 && (Column(AdditionalPropertyForTask.Name) = custom || Column(AdditionalPropertyForTask.Name) IS NULL) && Column(AdditionalPropertyForTask.Value) LIKE customized_value)

This problem occurs both on TaskQuery and CaseQuery and on Axon.ivy 5.1.x (additionalProperty() has been introduced since 5.1.x).

I think this is probrably a bug in Axon.ivy query API. While there is a work-around (don't use and(TaskQuery with additionalProperty()), I think it is not good to have inconsistency in the API. I hope this would be fixed soon.

I have created a demo project which can reproduce the problem on Axon.ivy. Download it at box.net.