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
5 subscribers
Views
3441 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
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?
OriginalPostID-217133
OriginalPostID-217133
Discussion posts and replies are publicly visible
0
David Williams
over 8 years ago
Will there be more than one task generated concurrently? So for example, a user could have 5 tasks to choose from at any point in time?
Or, a user will have a task and then you are looking to "feed" the next task each time they complete a new one?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
lesli.cowan
over 8 years ago
Usually it's just one next task but sometimes there are several concurrent tasks in a single step
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
lesli.cowan
over 8 years ago
We are building a general-use template, so we're trying to set it up the most efficient way possible.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jonathan Katora
Appian Employee
over 8 years ago
If you are on 16.2 you can also use the start process smart service. This would be the preferred option:
forum.appian.com/.../Start_Process_Smart_Service.html
You can use the send message event or configure the end event to start a process:
forum.appian.com/.../Send_Message_Event.html
I would not recommend using the sub-process because they will all execute on the same execution engine.
This page in the documentation shows a nice breakdown of all of your options:
forum.appian.com/.../Ways_to_Start_a_Process_From_a_Process.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
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
0
Stefan Helzle
A Score Level 3
over 8 years ago
I just discussed this with my new colleagues in our Appian training. Having a model for each task does not feel like a good practice. We try to find natural "cuts" or logical units in the functional process to create models. This can be time like the process has to wait for something. This can be organizational, meaning the process flow leaves or enters another department or company.
On the technical implementation, we normally use a scheduled sub-process node to delay the start of the next process.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel