Calling an Child Interface from Parent Interface

RE: Calling an Child Interface from Parent Interface

Prasanta Paul — Mon, 25 Nov 2024 12:40:36 GMT

Keep the same parameters as rule inputs for parent and pass it to the child

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Fri, 22 Nov 2024 15:48:32 GMT

I got my issue resolved. Local variables are not passing the values correctly to Child Interface. I instead set up my process model on the Site and called the Child Interface from the Site page. This resolved the issue.

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Wed, 20 Nov 2024 14:54:00 GMT

Hi Magesh Waran G

Please see below 2 screenshots. excelData is the parameter I am passing.

RE: Calling an Child Interface from Parent Interface

Magesh Waran G — Wed, 20 Nov 2024 07:12:27 GMT

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?

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Tue, 19 Nov 2024 19:11:48 GMT

Hi Magesh Waran G

I have modified my Process model and removed the call to Child Interface. Also I have modified the Child Interface Submit button to use a!startProcess(), code provided below for reference.

Then I call the Parent Interface from the Site and click on Bulk Upload, select an excel to upload, and then click on Submit , In both the cases (Process Model calling the Child Interface or Child Interface calling the Process Model), Process Model seems to trigger end to end, but the data is not getting written to the database.

When I test the Child Interface or Process Model separately, they both load the data into database successfully.

{
  a!sectionLayout(
    label: "",
    contents: {
      a!fileUploadField(
        label: "",
        labelPosition: "ABOVE",
        target: cons!VWHIAP_BULK_LOAD_FOLDER,
        fileNames: "DD Review File " & now(),
        value: ri!excelData,
        saveInto: {ri!excelData},
        validations: {}
      ),
      a!buttonArrayLayout(
        buttons: {
          a!buttonWidget(
            label: "Cancel",
            value: true,
            saveInto: ri!Cancel,
            submit: true(),
            style: "OUTLINE"
          ),
          a!buttonWidget(
            label: "Submit",
            value: false,
            /*saveInto: ri!Cancel,*/
            saveInto:  a!startProcess
            (
              processModel: cons!VWHIAP_Bulk_Upload_Process_Model,
              processParameters: 
                {
                  cancel: false(),
                  excelData: ri!excelData
                },
              onSuccess: null(),
              onError: null()
            ),
            submit: true(),
            style: "OUTLINE"
          )
        },
        align: "START",
        marginBelow: "NONE"
      )
    }
  )
}

RE: Calling an Child Interface from Parent Interface

Magesh Waran G — Tue, 19 Nov 2024 15:58:47 GMT

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

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Tue, 19 Nov 2024 15:33:15 GMT

Thank you gayatria0439 , My parent interface is just a stand-alone Interface. Parent Interface has Navigation on the left side. Each Navigation link should open a new interface on the right hand side. I have attached screenshot for your reference. For example, upon click of Bulk Upload Navigation link it has to open Child Interface. In this case, Child Interface has File Upload utility and with Cancel/Submit button. Child Interface has 2 Rule Inputs which are Cancel (Boolean) and excelData (DocumentType). Child Interface has a process model to process the data from the File Upload.

I am now able to call the Child Interface successfully from parent interface by passing parent interface localVariables to them. But when I click Submit button on the Child Interface, nothing happens, I mean the file upload does not trigger.

It works fine when I test the Child Interfaced Process Model.

I am new to Appian, can you please advise if I am doing something wrong here?

RE: Calling an Child Interface from Parent Interface

gayatria0439 — Tue, 19 Nov 2024 07:20:09 GMT

Regarding interface layouts, we cannot use form layouts when calling an interface within another, as form layouts are top-level layouts and cannot be nested. Instead, we should use section layouts for such scenarios.

RE: Calling an Child Interface from Parent Interface

gayatria0439 — Tue, 19 Nov 2024 07:11:49 GMT

Hi maheshg821223 ,

Whenever we call an interface within another interface, we need to pass the necessary parameters to handle actions or transfer values between interfaces. We can use either local variables or rule inputs, depending on the specific requirements. Rule inputs function as global variables and can be managed through the process model. Alternatively, if you need to use the values within the interface itself, you can pass local variables.

For example:
rule!Interface(cancel: ri!cancel/local!cancel,fileUpload: ri!fileUpload/local!fileupload)

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Mon, 18 Nov 2024 20:25:19 GMT

Hi Mike,

Below are the parameters for my 2 buttons on the child Interface, please advise if you notice anything off here. Process Model for the child Interface works fine when I have tested it.

a!buttonWidget(
label: "Cancel",
value: true,
saveInto: ri!Cancel,
submit: true(),
style: "OUTLINE"
),
a!buttonWidget(
label: "Submit",
value: false,
saveInto: ri!Cancel,
submit: true(),
style: "OUTLINE"
)

RE: Calling an Child Interface from Parent Interface

Mike Schmitt — Mon, 18 Nov 2024 20:11:13 GMT

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

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Mon, 18 Nov 2024 20:10:40 GMT

Hi Aditya,

I have created 2 local variables on the parent stand-alone interface. I called the child interface by passing those 2 parameters. When I am testing the Site, the Submit/Cancel buttons are doing nothing. Below is how I am calling the Child Interface, both the local variables are defined on the parent interface.

{

rule!DD_Review_Bulk_Upload_Interface(local!Cancel, local!excelData)

}

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Mon, 18 Nov 2024 20:09:57 GMT

Hi Soma,

{

rule!DD_Review_Bulk_Upload_Interface(local!Cancel, local!excelData)

}

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Mon, 18 Nov 2024 20:05:58 GMT

Thank you Mike, I have created an interface with section layout instead of Form layout.

RE: Calling an Child Interface from Parent Interface

Mike Schmitt — Fri, 15 Nov 2024 16:37:24 GMT

[quote userid="291585" url="~/discussions/f/new-to-appian/37969/calling-an-child-interface-from-parent-interface/142814"]The contents field on a column layout cannot contain a form layout[/quote]

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).

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Fri, 15 Nov 2024 16:28:33 GMT

I have added Child Interface and Parent Interface screenshots. Child Interface is a Form that has File Upload, Cancel and Submit Button. It has 2 Rule Inputs Cancel (boolen) and excelData (Document).

Parent Interface has Navigation as shown in the screenshot, My expectation is when user clicks on Bulk Upload, it should show the Child Interface. So in the Parent Interface Bulk Upload Section Layout, I have added rule!Child Interface, when its asking for parameters, I have passed on 2 local variables and I was getting below error message:

The contents field on a column layout cannot contain a form layout. Received a form layout at index 1.

RE: Calling an Child Interface from Parent Interface

maheshg821223 — Fri, 15 Nov 2024 16:20:40 GMT

RE: Calling an Child Interface from Parent Interface

Soma — Fri, 15 Nov 2024 08:35:27 GMT

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

RE: Calling an Child Interface from Parent Interface

adityae736199 — Fri, 15 Nov 2024 06:22:10 GMT

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

RE: Calling an Child Interface from Parent Interface

Kumar Agniwesh — Fri, 15 Nov 2024 03:43:14 GMT

can you share the parent interface code. I am not sure on what do you mean by navigation link

RE: Calling an Child Interface from Parent Interface

kaushik12 — Fri, 15 Nov 2024 02:13:49 GMT

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