Hi,I have a process model where I have a value in a pv! variable.
Now, I would like to send pv! variable value to the SAIL form from where I triggered the Process Model.
Can someone give me a clue to do this.
Thanks in advance.
Discussion posts and replies are publicly visible
You will need to configure this as a Rule Input on your SAIL Interface. If this is a Start Form, you can define the PV as the Rule Input value in the Process Model Properties -> Process Start Form tab, or on the User Input task's Forms tab for other interfaces.
To send any value to SAIL Form from the Outside you have to use the Rule input variable in the interface and while configuring the user input task of this interface send your PV as a value in the user input task.and if you want to save the value of the update field of the variable and use that variable as a Save into parameter as well
Hi,
I am using linkField and startProcessLink to call a process model. In the process model I am generating the document using docs from template. I am storing the filename in the pv! variable.
Now, can I get the pv! value into the ri! which is there in my SAIL form?
a!linkField( label: "", links: {a!startProcessLink()})
Rao2022 said:I would like to send pv! variable value to the SAIL form from where I triggered the Process Model.
I think I as well as some other folks here are mistaking your question for something else.
Do you mean you're calling a process model from an existing form, like using a!startProcess()?
In that case, you'll want to utilize the "onSuccess" parameter where you can grab PV data and save it back into local variables in your interface.
You can't do this with a!startProcessLink(), but you can do it with a!startProcess() (for an unattended process flow).
As far as I've ever seen, the data flow into "startProcessLink" is one-way only. That's primarily because the usage pattern is that the link takes you *away from* your original interface, and when the process is done, that interface is loaded again from scratch.
This is different from a!startProcess(), which starts an asynchronous process instance but allows you to stay on your present interface with all values and variables in-tact.
I am using "startProcessLink". I don't see any "onSuccess" parameter.Are you suggesting me to use startProcess instead of startProcessLink?
Rao2022 said:Are you suggesting me to use startProcess instead of startProcessLink?
If you want to generate a document in the background and get its ID back into your current interface without interruption, then yes, you have to use a!startProcess(). Note this only works if the generation process is 100% unattended and you activity-chain all the way up to where the new DocId is generated.
Thanks for the info. Let me give a try and update back soon.
Hey you can use StartProcess function. Make sure the process model will be activity chained to get the value back into the interface. In the given code, designation in my process variable which i am getting back into the interface from StartProcess function.
a!startProcess( processModel: cons!Test1, onSuccess: { a!save( local!a, fv!processInfo.pv.designation ) } )
a!startProcess() is not showing under a!linkField().
Can't I use a!startProcess() using a link in the form?