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
11 replies
Subscribers
10 subscribers
Views
3557 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
hi all, i created a sub-process as quick task for process record.
eaglez
over 10 years ago
hi all,
i created a sub-process as quick task for process record.
i did delete the start form, but when i click the sub-process in the related action, it opened a new window and redirected to portal page and a start form.
btw, if i directly start the process for debugging in desin page, there is no start form.
is there a place to configure this?
many thanks....
OriginalPostID-135990
OriginalPostID-135990
Discussion posts and replies are publicly visible
0
Ray Croxon
Appian Employee
over 10 years ago
Hi Eagle, if you are calling this as a subprocess, then check that the node with the subprocess call is assigned to Run as whoever designed this process model. Otherwise you could be seeing the form for the subprocess call step.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
eaglez
over 10 years ago
hi Ray, but if a sub-process is configured as a quick task, the node(run as whoever designed) is disabled, please see the attached pic
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ray Croxon
Appian Employee
over 10 years ago
Thanks Eagle, I see your problem.
Rather than define this as a quick task in the process model, you'll need to set it up to call directly from the Record, in the Related Actions section. You can pass the process id in the context field e.g., {requestId: rp!id} , where pv!requestId is the field in the subprocess
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
eaglez
over 10 years ago
in this case, how can i update the process variables in parent process,
i know there are two types of related action
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ray Croxon
Appian Employee
over 10 years ago
Here's a screenshot of a similar example. It's the subprocess call which is causing the form to appear from what you describe, so this should remove that problem. This also allows you to use it as a button on the form (assuming) you're on 7.7 or later.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
eaglez
over 10 years ago
hi Ray, my purpose is to update the process variables through related actions,
if use independent model as related action, is it possible to update the variables in the parent process?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ray Croxon
Appian Employee
over 10 years ago
You can use a Send Message event to push any data back up. Use a receive message on the calling process to pick it up.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
eaglez
over 10 years ago
yes, i forgot that. thank you very much, Ray.
theoretically, sub-process should be able to be configured as a quick task.
don't know why it doesn't work. "start form" alwasy shows....
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Ray Croxon
Appian Employee
over 10 years ago
True. It's because it's a quick task, this means Appian is trying to start the subprocess as a user, and therefore wants input into it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ajinkyab277
Certified Lead Developer
over 10 years ago
Hi Eagle,
1. Though we can target specific process using send and receive message node, But messaging is not synchronous.If your parent process don't have any logic which require immediate modification of pv after execution of related action then you can prefer the messaging.
2. You can use 'Set external pv' smart service to modify the process variable in another process(Process variable updated by this smart service wont get logged in process history)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>