Local Variables in Reusable Interface

Question

Hi! 
 
 I created an interface with cardChoiceField, which allows me to choose one of multiple subinterfaces (via rule!), which I created before. These subinterfaces have a dropdown which value is assigned to a local (to subinterface) variable. 
 The problem is that when I choose a value in the dropdown it doesn't change the local variable simultaneously - to see the "refreshed" interface, I have to switch to other subinterface, and then turn back to the original. In that case I obtain the subinterface I want, with refreshed variables. Is there any way to do this without switching to other subinterfaces? 
 I understand that it could be solved using rule inputs, but I would like to know how the interaction with local variables in reusable interfaces work

Mike Schmitt · Accepted Answer

IMHO you're way over-complicating this. Your parent need only save a marker / pointer of whichever child you currently want to show, instead of trying to save the child itself into some sort of local variable. 
 a!localVariables(
 /*local!link: null,*/
 local!selection: null(),

 {
 a!cardChoiceField(
 label: "Select A Version",
 data: {
 a!map(
 /*id: rule!IM_Child1,*/
 id: 1,
 icon: "globe-alt",
 primaryText: "Text"
 ),
 a!map(
 /*id: rule!IM_Child2,*/
 id: 2,
 icon: "globe-europe",
 primaryText: "Num"
 )
 },
 cardTemplate: a!cardTemplateBarTextStacked(
 id: fv!data.id,
 primaryText: fv!data.primaryText,
 icon: fv!data.icon,
 iconColor: "POSITIVE"
 ),
 saveInto: 
 /*{*/
 /*local!link*/
 local!selection,
 /*},*/
 value: local!selection,
 maxSelections: 1,
 validations: {}
 ),
 a!sectionLayout(
 label: "Selected...",
 contents: {
 a!match(
 value: index(local!selection, 1, null()),
 equals: 1,
 then: a!boxLayout(label: "rule!IM_child1 would go here"),
 equals: 2,
 then: a!boxLayout(label: "rule!IM_child2 would go here"),
 
 default: {}
 )
 }
 )
 }
)

Mike Schmitt · Answer

Your child interfaces need to actually save their values up into the parent interface. I'm not altogether clear what you're doing in this example exactly, but it's pretty clear to me that no value ever gets saved from the child to the parent. In both of your child interface examples here the local variables are scoped such that they'd only be accessible locally. 
 There's not some sort of "magic" that makes data in a child interface automatically promote up to a parent interface, you actually have to build that into your structure.

Local Variables in Reusable Interface

Top Replies