I have started a<appian-record-view> that starts a related action via process model but it doesn't allow me to have a secondary input or parameters
<appian-record-view>
docs.appian.com/.../Embedded_Interfaces.html
Discussion posts and replies are publicly visible
Can you tell us a bit more about your use case? Is this specifically for an external embedded interface? What parameters would you need to pass in?
yes, I am calling my interface via my process model via my related actionhttps://docs.appian.com/suite/help/21.2/Embedded_Interfaces.html#related-actionso far I am sending the recordId and that seems to be working but I also need a number from 0-9 as a parameter and that doesn't seem to be working. Is there another way to start a process model from outside Appian and get an interface to pop up?
You can try calling API and in that API you can use a!startProcess() , and pass parameter which u receive in http!request.
would this allow me to start an Interface?
https://community.appian.com/discussions/f/integrations/8774/parameters-to-embedded-sail/38948#38948 Can follow this
sergiog0002 said:start an Interface
What do you mean "start an interface"? The process you kick off would be able to start a task that gets assigned to an Appian user.
no, there is not Appian users as per our business model I just want to display a value and update a database
If you are trying to call a related action process model, you can only pass the recordId as parameter. If you need to pass more parameters, then you should use the startprocess smart services which will give you the ability to pass as many parameters as needed.
Case1,
if the record contain the respective parameters then it can be passed in the record while adding related action itself but not when related actions are called in UIs as its only supporting Identifiers
case 2
a. Create a dummy record as expression backed record with dummy data as {Id:1 and data:null} and add your process model in it as a related action .
b. This will require to query your recordId in the process rather than sending it from interface while calling related actions and perform all your requirement in the process model.
c. In this way you can have the pop up UI functionality through any UI