Calling an Child Interface from Parent Interface

Question

My Child Interface has Submit and Cancel Button. It has File Upload functionality. Below are the 2 Rule Inputs it has: 
 
 Cancel Rule Input (Type Boolean) 
 excelData Rule Input (Type Document) 
 
 I have a Parent Interface which uses Navigation, in one of the Navigation link I need to have this Child Interface appear. I was using rule!Child Interface, but its asking me to pass 2 parameters. Can you please help me on how I can pass those 2 parameters from Parent Interface? 
 
 Regards, 
 Mahesh

kaushik12 · Answer

maheshg821223 You need to pass the parameters like this, let me know if you still have any confusion.

adityae736199 · Answer

If your parent interface is being used in a process model as either Start Form/User Input task and you need those two rule input data to be passed to the PM from child interface, then create two new rule inputs in the parent interface and map them to the child rule wherever you are calling in the parent. 
 If that's not the case, then you can create two new local variables in the parent interface and pass them as parameters where you are calling the child. 
 Approach may change based on how you want to utilize the data in those rule inputs

Soma · Answer

There are multiple ways of doing it. 
 1. If your parent interface needs to get and pass values to process model, then 
 a. Create two rule inputs in child interface and pass it to child interface. The data flow will be as below 
 process variable >> parent interface rule input >> child interface rule input 
 2. If your parent interface is standalone, then you can use localvariables to initialise the two rule inputs 
 local!cancel >> ri!cancel 
 local!excelData >> ri!excelData

Mike Schmitt · Answer

maheshg821223 said: The contents field on a column layout cannot contain a form layout 
 This error message is pretty self-explanatory. A child interface cannot contain "a!formLayout()", since a!formLayout() cannot be nested at all. You really don't need it though, you can do almost everything you need with a!sectionLayout; the Form Layout component only needs to be used in the top-most form in any case (and even then, it's not 100% required, just makes certain configuration aspects easier for a user input task interface).

Mike Schmitt · Answer

make sure your button widgets have the correct setting for the "submit" parameter.

Magesh Waran G · Answer

maheshg821223 hope you configured the child interface either as a start form or user input task in the process model and that is why it was working when you test it from the child interface. Instead try removing the form from the process model and call the process model using a!startProcess() in the saveInto parameter of the submit button to start the process model

Magesh Waran G · Answer

maheshg821223 can you try checking the value of output parameters of Import Excel to Database node by saving into PVs to check whether any error occurred during the import?