Hello, In what case the Task stays in Accepted status after you click

aksharc over 9 years ago

Hello,

In what case the Task stays in Accepted status after you click on the Return task to all assignee link?

Following is the scenario I am facing, and I am not sure why it is behaving that way:
There is a task assigned to the group I am member of. When I accept the task, it will show an option to return the task to all assignee. When I click on that link, the task stays assigned to me with Accepted task status. I was expecting that the task would assign back to the group it was originally assigned. Please help me understand why it behaves like that.

Let me know if there is any questions.

Thanks!

Discussion posts and replies are publicly visible

0 aksharc over 9 years ago

I couldn't find the path you mentioned. Will it be same for the cloud version too?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Otherwise, something like: <Appian home>/logs/application-server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Though you are right, for cloud the jboss1-stdOut.log will be the right one. There should be a complete stack trace in the log following the error you previously mentioned
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aksharc over 9 years ago

Tom, I am not getting anything under the error. I am attaching the screen shot of the error log. And that's the end of error.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Thats odd. Are you still seeing the issue? It may take some time for task assignment to propagate through the system - does waiting a short period and refreshing the page show the correct assignment?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 muthukumars over 9 years ago

Hi Tom, do we have any resolution for this issue? Even we are facing the same problem and we are getting the same error in the log file.
I waited for around an hour after returning the task back but the reassignment still doesnt happen.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

I assume you don't see any more details in the log file either? Would it be possible for you to create a small sample application that shows the issue, and attach it along with the steps we can take to reproduce the issue? If you prefer this not to be on Forum, then you can create a support ticket for this issue so that we can investigate further.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 muthukumars over 9 years ago

Unfortunately, I cannot provide any screenshots from my environment due to restrictions in my company. But I have tested this issue many times with many combinations with a simple process model with nothing but a User Input Task, user and groups. The problem seems to appear when we assign two or more users/groups to the User Input Task and if any one of them is set with Re-assignment previleges as "No Previlege". Let me know if you need any other details.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Thanks for the update. I will continue to look into this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

I can confirm that this is an issue with the product. Thanks all for alerting us to this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel