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
7 subscribers
Views
2554 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
My process is triggered by external applications. Can I define the maximum numbe
Marcio Rosa
over 12 years ago
My process is triggered by external applications. Can I define the maximum number of Instances allowed to run in parallel?
I've found two properties to define node limits (MAX_SPAWN_INSTANCES and MAX_NODE_INSTANCES=1000) but nothing related to the main process.
...
OriginalPostID-62182
OriginalPostID-62182
Discussion posts and replies are publicly visible
0
shelzle
over 12 years ago
Try to create a report that shows the number of running instances and check this when starting the process. If the number is too high, go to an end node.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Marcio Rosa
over 12 years ago
Thanks Shelzie, but this solution doesn't work for us.
Because it is an external request I must execute the process, I can’t skip to the end node. I wish, if limit was reached, the solicitation stay on standby.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
shelzle
over 12 years ago
OK. You want to block your external application. Right ?
You could use a SQL DB to save the number of running instances and use this value from the external application. Or you can build a queue in the external application and call a webservice (in external app) at the end of the process that tells the external application to trigger the next process.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Marcio Rosa
over 12 years ago
I was looking something out of the box. Thanks
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Owen Parrish
Appian Employee
over 12 years ago
The process triggered by the external application could simply update a queue table in a database. Then you could have another process that would periodically check that table for new records and only start if there are new records.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
shelzle
over 12 years ago
As far as I can say there no OOTB solution for this case. But building some process models to solve this is kind of OOTB as this is the way to build things in Appian.
I had to build a message queuing mechanism to ensure that messages are processes by the target process in the same order as they were created. A small model "queue item" checks periodically whether it is the first item in the queue and sends the message to the target process. The target process sends a confirmation message back as soon as it processed it and the queue item completes.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel