I am still creating my somewhat complex instantiation form and have almost got it working. There are several configurable variables defined as workflow variables to gather the user selections of various checkboxes on my instantiation form. One problem I ran into is if I have too many items showing, it creates pages of forms rather than one single page with a scroll bar, which was undesirable. I found a solution on DevNet to wrap a container around the items, which worked. No more pagination - all my items appear on a single page with a scroll bar.
However...
Adding the container is somehow mucking with my configurable variables, and I can't figure out how to fix it. I now have a new container named controlScrolling that I wrapped around all my items. While this works to prevent pagination on the instantiation form, I now cannot read the values of my configurable variables that are mapped to the items in my externaltask. Something about adding the container is changing the signature/name of the workflow variables - or maybe the reference from the instantiation form is whacked. I think the container is somehow changing the reference from the workflow configurable variable name, but I don't know how. I am attaching my custom_instantiation.cfg and my default_config.xml files as well as the workflow model that contains the workflow variables that reference the configurable variables. If I run the workflow with the container and select the DevDing item, when I look at the DEV_DING_SILOS variable in my externaltask, I would expect to see a value of "ding/web", but the value is null. If I remove the container from the custom_instantiation.cfg and execute the same test, I see the value "ding/web" in the DEV_DING_SILOS workflow variable. I need to understand how the container affects the configurable variable and what I need to change to still use the container but be able to read the correct value in my externaltask.
Has anyone run into something like this?
