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
7 replies
Subscribers
8 subscribers
Views
2247 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
We have a process where people need to process requests in bulk. What we'd
Richard
over 10 years ago
We have a process where people need to process requests in bulk. What we'd like to do is generate an implementation task per item, but also provide an interface to the implementation teams that would allow them to indicate completion. Ideally this would allow the individual task if affects to be completed. Has anyone done this in Appian?
...
OriginalPostID-80780
OriginalPostID-80780
Discussion posts and replies are publicly visible
Parents
0
David Williams
over 10 years ago
Perhaps if you think of each of these tasks in a process it might be easier.
You could have the process have the option of creating X number of processes via a quick task going in to a subprocess that then replicates the parent process X times (held in a variable).
The child process then has a receive message event that takes a key from the parent process, which is the condition on the recieve message event leading to an end event or terminate on the child process. The alternative and probably recommended way is to pass a value byreference to the child process on input of the subprocess.
This way another quick task on the parent process, call it "terminate child processes" which then passes perhaps a boolean value byreference to the child processes. Instead of a receive message process you could have a rule event that leads to the terminate whenever that boolean value is activated. You can then also set data within the child processes such as a status variable which is changed when the rule event fires, you can use this to display on reports etc.
Hope I understood this right??
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
David Williams
over 10 years ago
Perhaps if you think of each of these tasks in a process it might be easier.
You could have the process have the option of creating X number of processes via a quick task going in to a subprocess that then replicates the parent process X times (held in a variable).
The child process then has a receive message event that takes a key from the parent process, which is the condition on the recieve message event leading to an end event or terminate on the child process. The alternative and probably recommended way is to pass a value byreference to the child process on input of the subprocess.
This way another quick task on the parent process, call it "terminate child processes" which then passes perhaps a boolean value byreference to the child processes. Instead of a receive message process you could have a rule event that leads to the terminate whenever that boolean value is activated. You can then also set data within the child processes such as a status variable which is changed when the rule event fires, you can use this to display on reports etc.
Hope I understood this right??
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data