nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Changed GROUP_ID_ column value in ACTIVITI_RU_IDENTITYLINK

samratrcs

I changed the GROUP_ID_ column value in ACTIVITI_RU_IDENTITYLINK value from PLCM to PLCM1 for tweaking a busimess logic. Now again when I am changing the group to PLCM the following error is coming while claiming a task.

Caused by: org.activiti.engine.ActivitiException: Cannot assign a groupId to a task assignment that already has a userId
        at org.activiti.engine.impl.persistence.entity.IdentityLinkEntity.setGroupId(IdentityLinkEntity.java:132)
        at sun.reflect.GeneratedMethodAccessor36945.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.ibatis.reflection.invoker.MethodInvoker.invoke(MethodInvoker.java:37)
        at org.apache.ibatis.reflection.wrapper.BeanWrapper.setBeanProperty(Bean                                                                            Wrapper.java:169)
        … 445 more

Can you please help me with tjis. The system is live in production.

Find more posts tagged with

Comments

martin_grofcik

Hi,

you are referring to the following case
org.activiti.engine.test.api.task.TaskServiceTest#testClaimAlreadyClaimedTaskByOtherUser

(in activiti source)

regards
Martin

samratrcs

Hello Martin,

Thanks for the reply.
Can you please explain me the problem.
What can be the solution now?

Regards
Samrat

martin_grofcik

Hi,
use claim/unclaim. Already claimed task can not be claimed again

<br>&nbsp; /**<br>&nbsp;&nbsp; * Claim responsibility for a task: the given user is made assignee for the task.<br>&nbsp;&nbsp; * The difference with {@link #setAssignee(String, String)} is that here <br>&nbsp;&nbsp; * a check is done if the task already has a user assigned to it.<br>&nbsp;&nbsp; * No check is done whether the user is known by the identity component.<br>&nbsp;&nbsp; * @param taskId task to claim, cannot be null.<br>&nbsp;&nbsp; * @param userId user that claims the task. When userId is null the task is unclaimed,<br>&nbsp;&nbsp; * assigned to no one.<br>&nbsp;&nbsp; * @throws ActivitiObjectNotFoundException when the task doesn't exist.<br>&nbsp;&nbsp; * @throws ActivitiTaskAlreadyClaimedException when the task is already claimed by another user.<br>&nbsp;&nbsp; */<br>&nbsp; void claim(String taskId, String userId);<br>&nbsp; <br>&nbsp; /**<br>&nbsp;&nbsp; * A shortcut to {@link #claim} with null user in order to unclaim the task<br>&nbsp;&nbsp; * @param taskId task to unclaim, cannot be null.<br>&nbsp;&nbsp; * @throws ActivitiObjectNotFoundException when the task doesn't exist. <br>&nbsp;&nbsp; */<br>&nbsp; void unclaim(String taskId);<br>

samratrcs

Hi Martin,

The task is not claimed. The Assignee_ column of the ACT_RU_TASK table is null.

Regards
Samrat

martin_grofcik

Can you create jUnit test?
http://forums.activiti.org/content/sticky-how-write-unit-test

Regards
Martin

samratrcs

Hello Martin,

A detailed log

Caused by: org.apache.ibatis.reflection.ReflectionException: Could not set property 'groupId' of 'class org.activiti.engine.impl.persistence.entity.IdentityLinkEntity' with value 'PLCM1' Cause: org.activiti.engine.ActivitiException: Cannot assign a groupId to a task assignment that already has a userId

The source of error is the following method.

public void completeTask(String taskId, Map<String, Object> decision) {
taskService.complete(taskId, decision);
}

Regards
Samrat

samratrcs

The bpm file is attached
ACtiviti version : 5.13

process_1.txt.zip

jbarrez

Does the error still happen on the latest release? 5.13 is very old. Chances are it's already fixed in newer versions.