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
  • @sikhivahans Thank you for you input. Today, we have seen a different issue in relation to this setup of the a gridLayout. The issue is that while testing the interface and using a dynamicLink to create a row in the gridLayout the row is being added property. However, when executing a process instance and working in that SAIL interface through Tempo, the dynamicLink is NOT adding rows to the gridLayout. Have you ever come across something like this?
Reply
  • @sikhivahans Thank you for you input. Today, we have seen a different issue in relation to this setup of the a gridLayout. The issue is that while testing the interface and using a dynamicLink to create a row in the gridLayout the row is being added property. However, when executing a process instance and working in that SAIL interface through Tempo, the dynamicLink is NOT adding rows to the gridLayout. Have you ever come across something like this?
Children
No Data