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
5 replies
Subscribers
6 subscribers
Views
2094 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
#ProcessModeling #Security I have a process model that calls a subprocess (
johnj550
over 9 years ago
#ProcessModeling #Security
I have a process model that calls a subprocess (synchonously) to monitor the SLA for the task. The subprocess starts a timer that waits for the SLA to elapse.
In the mean time, the parent process is completed by the user and terminates.
When I run this using my account (System Administrator user type) the subprocess is cancelled when the parent terminates.
When I run this as an end user (granted Viewer permissions through group membership) the subprocess continues running and is not cancelled.
How can I configure the model so it cancels the subprocess when the parent terminates?
(I would prefer not to pass a boolean to the subprocess and check it when the timer expires.)
OriginalPostID-178681
OriginalPostID-178681
Discussion posts and replies are publicly visible
0
Chris
over 9 years ago
For most of these situations, I pass a boolean variable to the sub process by reference (must be by reference). Just before the parent terminates, this value is set to true(), which is used in the sub process as an exception flag. If the sub process is complicated (many nodes), you can create one new path between the start event and a terminate end event with a rule node which only flows on true(), this will cause the sub to end when the value is set to true() in the parent.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vikask146
over 9 years ago
You can add an exception on Sub-process node and connect to end node but make sure this exception ends first before main process terminates.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 9 years ago
Also to note, I'm not sure if this has been resolved yet but per AN-41986 sub processes configured as MNI and set to skip based on exception will only terminate the first instance, the rest will incorrectly remain active.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
johnj550
over 9 years ago
Thanks. We now believe this is related to chaining. If the path taken in the parent process was fully chained, the subprocesses don't realize the parent terminated and subprocesses stay alive. If any of the flows taken were not chained, the subprocesses get cancelled. We are opening a support request and in the meantime I have implemented csteward's solution.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mahesh Sanga
over 9 years ago
Similar issue
forum.appian.com/.../e-179376
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel