Hi,
I'm in an interface A, and I'm calling a process from a!startProcess.Inside the process I have an Input task to display interface B.
Could you explain me why when I call the process, it works fine but the Interface B is never displayed ?
(all the nodes are linked with chaining)
Discussion posts and replies are publicly visible
startProcess starts a process async. This means it is started on the available engine and hence even if you have chained, it will not work. It is best when you have a set of tasks that you want to complete in the background.
But if I need to get process data information, how can I do ? with startProcessLink, I did not have "onSucess" anymore, so I cannot use fv!processInfo
cedric01 said:But if I need to get process data information
In this case you'll need to use the asynchronous call provided by a!startProcess().
The concept is that a!startProcess can be called from anywhere, run in the background, and come up with some results for you instantly/chained, that will then be fed back via fv!processInfo. With a!startProcessLink(), the concept is totally different, and there is no presumption that you will be returning any data to the original interface, and of course the original interface will presumably be reloaded from scratch. So you'll need to choose which of these concepts is the one you actually need, and build accordingly.
yes, I understandbut in this case I still have my problemwhatever the solution : using startProcess or startProcessLink, I will miss something...
They're for two totally separate use cases. That was my point. Can you give us more details as to your use case, so we can help you figure out what's more appropriate?