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

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
  • @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.
Reply
  • @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.
Children
No Data