How to Pass Parameters from Parent to Child Interface in a Tab-Based Navigation

Certified Associate Developer

Hi,

I have a Child Interface with a Submit button and a File Upload functionality. It has two Rule Inputs:

  • cancelInput (Type: Boolean)
  • uploadedFile (Type: Document)

Now, I’m using a Parent Interface that has a Tab-based Navigation layout, and I want one of the tabs to display this Child Interface. However, the system prompts me to pass the two parameters (cancelInput and uploadedFile) when I call the Child Interface using rule!ChildInterface().

How can I effectively pass these parameters from the Parent Interface to the Child Interface while keeping the setup simple? I’d appreciate any tips or examples!

Thanks in advance for your help!

Naveen k Rajakumar

  Discussion posts and replies are publicly visible

Parents
  • +1
    Certified Associate Developer

    Hi  ,

    To effectively pass the parameters from the Parent Interface to the Child Interface we need to create the rule inputs with the same type, generally When 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 requirements, Rule inputs are like global variables and it can be managed through the process model. Or if you need to use the values within the interface itself, you can pass local variables.

    Example of passing variables:
    rule!Interface(cancelInput: ri!cancelInput/local!cancelInput, uploadFile: ri!uploadFile/local!uploadFile)

  • 0
    Certified Associate Developer
    in reply to gayatria0439

    hello  

    Thanks for sharing your insights! That’s a great explanation of how to use rule inputs and local variables to handle parameter passing. Your example is really helpful, especially for anyone trying to figure out how to structure their parent-child interface relationships.

    I agree that defining rule inputs with matching types in the parent and child interfaces is a clean approach. Using local variables to manage intermediate values also adds flexibility.

    Out of curiosity, have you come across any specific challenges when managing such setups in more complex scenarios, like nested tab-based interfaces or when multiple child interfaces need to sync with the same parent variable?
    It would be great to hear how you’ve handled those situations!

Reply
  • 0
    Certified Associate Developer
    in reply to gayatria0439

    hello  

    Thanks for sharing your insights! That’s a great explanation of how to use rule inputs and local variables to handle parameter passing. Your example is really helpful, especially for anyone trying to figure out how to structure their parent-child interface relationships.

    I agree that defining rule inputs with matching types in the parent and child interfaces is a clean approach. Using local variables to manage intermediate values also adds flexibility.

    Out of curiosity, have you come across any specific challenges when managing such setups in more complex scenarios, like nested tab-based interfaces or when multiple child interfaces need to sync with the same parent variable?
    It would be great to hear how you’ve handled those situations!

Children
No Data