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
6 replies
Subscribers
6 subscribers
Views
2677 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Normally user should not been able to complete the task (of sub-process) after t
amitm
over 10 years ago
Normally user should not been able to complete the task (of sub-process) after the main process instance has been terminated. But I found it surprising that sometimes a user is able to accept and complete the task (but no further node) AFTER the termination of process instance. Can anyone help to understand the actual reason?
OriginalPostID-148583
OriginalPostID-148583
Discussion posts and replies are publicly visible
Parents
0
amitm
over 10 years ago
We have functionality where user can close the running case any-time via related action. This will 'Terminate' the process from back-end. If a task note is active that time (in a synchronous sub-process) should be aborted.
This is happening normally, but we noticed few times the user input task allow assigned user to accept and submit (surprising) but not moving next node further (which is expected).
Hope now you got the scenario.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
amitm
over 10 years ago
We have functionality where user can close the running case any-time via related action. This will 'Terminate' the process from back-end. If a task note is active that time (in a synchronous sub-process) should be aborted.
This is happening normally, but we noticed few times the user input task allow assigned user to accept and submit (surprising) but not moving next node further (which is expected).
Hope now you got the scenario.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data