Hello, Today we have seen something particularly odd in the a!gridLay

Hello,

Today we have seen something particularly odd in the a!gridLayout SAIL component.

Referencing the SAIL recipes we built a a!gridLayout Component and in a second rule the a!gridRowLayout Component.
The problem we were having is that the values we were entering in the a!gridRowLayout Component were not being saved to array of values that is being passed into the a!gridRowLayout Component.

After a lot of attempts, we have found that the Rule Input of the array of values, in the SAIL Interface that displays the a!gridRowLayout Component, must have the SAME name as the local variable in the parent SAIL Interface that calls the gridRowLayout SAIL Interface through the applyComponents function. If the names are different then the values we were entering in the gridRowLayout were not being saved.

Is this behavior normal? And if so, why is that?

OriginalPostID-150252

OriginalPostID-150252

  Discussion posts and replies are publicly visible

Parents
  • @thanosm The code looks pretty straight forward. I could definitely say that the behavior being observed by you while testing interface won't be seen when you execute the same SAIL interface from process because we do have many editable grid rules which have their input's names different from the names of parent's variables.

    As said by conorc or as observed you in case of interface designer, this is some thing that Appian should explain if it isn't the product behavior. AFAIK, this behavior isn't mentioned in the documentation as well.
Reply
  • @thanosm The code looks pretty straight forward. I could definitely say that the behavior being observed by you while testing interface won't be seen when you execute the same SAIL interface from process because we do have many editable grid rules which have their input's names different from the names of parent's variables.

    As said by conorc or as observed you in case of interface designer, this is some thing that Appian should explain if it isn't the product behavior. AFAIK, this behavior isn't mentioned in the documentation as well.
Children
No Data