Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
8 subscribers
Views
1788 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hello, I have my scenario in below steps: > I am member
tapans
over 8 years ago
Hello,
I have my scenario in below steps:
> I am member of one group let say "TaskRun" user group
> Now One task is assigned to "TaskRun" group
> I am picking that task and accepting it
> My aim is to complete that task within 2 days
> In the meantime, someone removes me from "TaskRun" group
> Next time when I am trying to access the task, I am getting "You are not the owner of this task" or similar kind of error
When I am accepting the task, assignee should be my group in place of "TaskRun". So if anyone have any suggestion or faced similar issue before, can you please guide me from here? Let me know for any followup questions.
Thanks in advance!
OriginalPostID-212924
OriginalPostID-212924
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 8 years ago
@tapans An enhancement Goutham's idea here: we could build a reusable component that captures the acceptance and this should be integrated into each and every user input task. This reusable component can consist of acceptance in any format (such as a boolean question with Submit button) and upon interaction, you can trigger a process in the back ground which will modify the task assignees with the current task as context. Here we need to check how the current task behaves if we changes its assignees when we are working on the same task, and if it's okay then there might not be a need to build a separate task. Further it simplifies the job as per my knowledge.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 8 years ago
@tapans An enhancement Goutham's idea here: we could build a reusable component that captures the acceptance and this should be integrated into each and every user input task. This reusable component can consist of acceptance in any format (such as a boolean question with Submit button) and upon interaction, you can trigger a process in the back ground which will modify the task assignees with the current task as context. Here we need to check how the current task behaves if we changes its assignees when we are working on the same task, and if it's okay then there might not be a need to build a separate task. Further it simplifies the job as per my knowledge.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data