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

thanosm over 9 years ago

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?

Discussion posts and replies are publicly visible

0 sikhivahans over 9 years ago

@thanosm Out of interest, may I know if you are using rule input (ri!) variables or local (local!) variables while saving the values (in 'saveInto') of components in a!gridRowLayout Component? Seems like you are making use of local variables, if so, it could be a reason.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thanosm over 9 years ago

@sikhivahans We are using only rule input (ri!) for the array of values in the gridLayout SAIL interface and in the gridRowLayout SAIL interface. We do not use local! variables to hold the values for the grid.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Schmitt
Certified Lead Developer
over 9 years ago

Can you post code (or at least samples)? In the chance that there's an error it'll be impossible for anyone to tell without seeing some represenation of what you're actually trying.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 9 years ago

@thanosm The behavior you have seen is not normal as per my knowledge, because there isn't any such constraint with respect to the names of inputs and the names of the variables that were passed as values to the rule inputs. Anyhow, as said by mschmitt, attaching the code snippet at high level allows other practitioners to make comments on the problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Conor Cahill
Certified Lead Developer
over 9 years ago

I've heard of this occurring when testing in the interface designer, but when you actually use it in process it'll save properly even if the name doesn't match.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thanosm over 9 years ago

I am attaching (as text files) the two interfaces involved.

If you see in the MA_TestGridLayout interface the ri!gridItems is what is passed into the MA_TestGridRowLayout interface. IF, the rule input (gridItems) in the MA_TestGridRowLayout interface has a different name than the ri!gridItems in the MA_TestGridLayout interface, then the values are not saved.

@conorc Yes, we are seeing this behavior in the Interface Designer as we have not yet moved into creating the process models that will execute these interfaces.
MA_TestGridLayout.txt
MA_TestGridRowLayout.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 9 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thanosm over 9 years ago

@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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 9 years ago

@thanosm As already discussed, there might be behavioral variations in interface execution, but there shouldn't be any such in the process. So far I haven't experienced any such issue nor have heard of such issue. It would be probably worth posting your code so that some one can take a look at it and decide whether it's a problem with code or any other thing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel