Hi everyone, Is there a better way that allows end user to go back and edi

@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.

Only users with access to designer and appropriate privileges are able to edit the process instances. It may be better to have something like a process backed record that the end users are able to view and modify.

To keep a process instance active for a period of time you could consider adding a delay -
forum.appian.com/.../Scheduling_the_Start_of_an_Activity.html

In such scenario, you should NOT terminate the process. I suggest end the process for end users but in process model you can put some logic or timer (as @sikhivahans suggested above) and once it's actually completed, mark it terminated.

For example, see the attach screen

@sikhivahans & @amitm
thanks for your comments. I can put a timer to delay the termination of the process but the problem is that we have a bunch of user input tasks for that process. In order to give end user the option of editing the process instance, I have to create a quick task for each user input task. I don't think this is a good practice. Do you have any other suggestions?

Thanks a lot in advance!

@lins It will be worth if you could elaborate the business use case in brief.

@sikhivahans It's a process that our employees use to record incidents. For some of the incident types, they need to do a root cause analysis. For some of the cases, they need to go back and update the root cause part or some other info regarding that incident. I know a quick task could solve this but the process would like really messy (please see my attachment). Thank you very much for your time!

@lins If you make use of records, you can have a related action (not a quick task) against the record, and this should solve the issue as per my knowledge:

Related action:
1. Create a related action which performs the desired functionality and save the data in the database.
2. After the completion of step - 1, send a message to the main process (as attached in the post).

Main process:
1. Configure a receive message which will be triggered by related action.
2. Upon receiving a message, you can make queries in a subsequent script task and save the new values into process variables in the main process.

@sikhivahans thanks! is there any documentation regarding how to set up a related action?

Please go through the forum.appian.com/.../Records_Tutorial.html. AFAIK, the process backed records allow you to configure related actions (stand alone process models) and process quick tasks to appear automatically in the 'Related actions' on a record. But I guess this goes hand in hand with Appian version you are using. Hope this helps you to some extent.