I have an interesting observation that lead to a difficult bug detection dealing with hidden form data vs other components. This might be a variation on the "passing parameters and interesting difference" discussion.

In the attached protocol, the parameter order in presence of the table is hidden form data first, then the checkbox even though the nested element is Run to Completion.

Output:

Parameters

• Original_index : 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• split_parameter : 2, 4, 6, 8, 10, 1, 3, 5, 7, 9
• button : Crash

If the table is disabled then the Output is what I would expect:

Parameters

• Original_index : 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• split_parameter : 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• button : Crash

This has the unfortunate effect of sorting the hidden form data to the top of the parameter arrays while not changing any other parameter.

Two questions:

Why does this happen?

Can I avoid it and still retain the text(no change allowed) vs operating box (change allowed to user)? I want to maintain the table with a column of flags. Right now I give the user a checkbox and just ignore their input when they are not allowed to make changes.

I am running PP 7.5.2 in Windows XP SP3

Thank you,

Warren