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
10 replies
Subscribers
9 subscribers
Views
3764 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi everyone, Is there a better way that allows end user to go back and edi
lins
over 9 years ago
Hi everyone,
Is there a better way that allows end user to go back and edit a process instance after it's completed? I tried with Quick Task but the problem is that the Quick Task will not be available after the process got terminated. In most of our cases, end user needed to go back and update a process instance after the form being submitted.
Or is there a way to keep a process instance active after an end user completing a form?
Any input would be much appreciated!
OriginalPostID-149807
OriginalPostID-149807
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 9 years ago
@lins AFAIK it isn't a good idea to perform operations upon a completed instance until we have a good reason for to do so. Given an option, I would rather keep the instance active as long as I know that I am going to perform some operations in it. Also when the instance ends/ terminates, the archival comes into picture which you should consider if you stick to carry out with modifying the completed instance.
Coming to the topic of keeping the instance live, there are various ways of doing so(for instance, we could have a timer process in order to make the instance wait for some time). It would be worth describing the usecase at a very high level(conditions for keeping the instance live, conditions to end the instance etc) so that the practitioners here could come up with better approaches considering the available options.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 9 years ago
@lins AFAIK it isn't a good idea to perform operations upon a completed instance until we have a good reason for to do so. Given an option, I would rather keep the instance active as long as I know that I am going to perform some operations in it. Also when the instance ends/ terminates, the archival comes into picture which you should consider if you stick to carry out with modifying the completed instance.
Coming to the topic of keeping the instance live, there are various ways of doing so(for instance, we could have a timer process in order to make the instance wait for some time). It would be worth describing the usecase at a very high level(conditions for keeping the instance live, conditions to end the instance etc) so that the practitioners here could come up with better approaches considering the available options.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data