• State Not Answered
  • Replies 23 replies
  • Subscribers 8 subscribers
  • Views 5358 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

Question on expected behavior when mapping rule parameters while calling sub-interface

Sidhant Behura

#UserInterface
Hi All, I was designing a form where I came across this new or different behavior which I suspect to be a bug. This is related to the mapping of the rule parameters while calling a sub-interface.

I have 2 interfaces, one parent interface(TEST_Interface1) and one sub-interface(TEST_Interface2).
TEST_Interface1 contains two rule inputs : varA (Text) and varB (Text).
TEST_Interface2 contains two rule inputs : varA (Text) and varB (Text).

TEST_Interface2 contains 2 text fields using which I initialize the rule inputs varA and varB.
In TEST_Interface1, I am calling TEST_Interface2 and below goes the code snippet:
rule!TEST_Interface2(
varA: ri!varB,           /* Mapping varA in TEST_Interface2 to varB TEST_Interface1 */
varB: ri!varA                    /* Mapping varB in TEST_Interface2 to varA TEST_Interface1 */
),
          a!textField(          /* Displaying the changed variable value */
label: "Variable A",
labelPosition: "ADJ...

Additional Info.zip

OriginalPostID-208471

OriginalPostID-208471

  Discussion posts and replies are publicly visible

Parents
  • 0
    @stefanh791 and @mschmitt :
    Here are some additional information:
    If you observe there are 2 interfaces main and sub interface.
    The rule input names in the parent and child interfaces are same i.e varA and varB.
    So when i call the sub-interface(contains text fields to initialize the variables) and map the rule inputs there is an anomaly.
    My mapping is:
    varA(Main Interface) --> varB(Sub Interface),
    varB(Main Interface) --> varA(Sub Interface)

    In this case whatever changes you might perform on the variables, those wont persist.
    Reason being appian is not considering my mapping instead it is mapping
    varA(Main Interface) --> varA(Sub Interface),
    varB(Main Interface) --> varB(Sub Interface)

    If the above explaination is not clear then I will create a small application with the same interfaces and attach it so that it can be imported and checked.
Reply
  • 0
    @stefanh791 and @mschmitt :
    Here are some additional information:
    If you observe there are 2 interfaces main and sub interface.
    The rule input names in the parent and child interfaces are same i.e varA and varB.
    So when i call the sub-interface(contains text fields to initialize the variables) and map the rule inputs there is an anomaly.
    My mapping is:
    varA(Main Interface) --> varB(Sub Interface),
    varB(Main Interface) --> varA(Sub Interface)

    In this case whatever changes you might perform on the variables, those wont persist.
    Reason being appian is not considering my mapping instead it is mapping
    varA(Main Interface) --> varA(Sub Interface),
    varB(Main Interface) --> varB(Sub Interface)

    If the above explaination is not clear then I will create a small application with the same interfaces and attach it so that it can be imported and checked.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.