We are trying to build short-lived processes, and looking at building one proces

lesli.cowan over 8 years ago

We are trying to build short-lived processes, and looking at building one process per task, where the process ends when the task is complete and starts a new process for the next action. What is the most efficient method for Appian to start a process from the end of the previous process? We have looked at starting an asynchronous (sub)process as the last step in the current process, using JMS Messaging, or Web APIs, which of these is the most efficient for starting the next Appian process, or is there another way that is recommended over these options?

Discussion posts and replies are publicly visible

Parents

0 David Williams over 8 years ago

If you have a sequential style process you could hold a task ID in a database, when the process is generated, lock the task in the database, then generate the task.

On the form you can then submit or cancel, cancel would unlock the task from the database and terminate the process. Submit would mark the task as completed and then loop back on to the task to re-generate it.

I don't think you necessarily need to launch a new process, you could handle it all in one process maybe?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 David Williams over 8 years ago

If you have a sequential style process you could hold a task ID in a database, when the process is generated, lock the task in the database, then generate the task.

On the form you can then submit or cancel, cancel would unlock the task from the database and terminate the process. Submit would mark the task as completed and then loop back on to the task to re-generate it.

I don't think you necessarily need to launch a new process, you could handle it all in one process maybe?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data