After Execution tab - all variables not enabled after upgrade to 5.8.3.12

This is a big problem, we upgraded from 5.8.3.0 to 5.8.3.12 and all of our packages and logic stopped working. we noticed that all of the variables in the "After Execution" tab are not enabled.

We attempted to fix some of our packages by enabling all of the default variables present and we got some success there.

But, This is a real pain to go about checking all variables of all of our components.

Guys, I need a workable solution or I have to not use 5.8.3.12. Is there any way to have all of the default variables enabled.

You can right click to enable all variables



We will have a look at how we can make it easier in the next release

Hi,

right click enable all is still a lot of work, we have many packages and many objects in every package.

anyways, i've noticed that, the disable all package variables by default was checked under file - options - interface

so i unchecked that option and the packages and objects that i did not "fix" manually are all now showing the default variables as checked under the after execution tab.
unfortunately the objects i fixed manually now have all the variables set to enabled. I will have to restore my backed up repository database and try again.

looks like the "disable all package variables by default' unchecked may save the day.

questions are
1. would the nested loops 3 levels deep still work
2. whats the downside of "disable all package variables by default" unchecked
3. does the "disable all package variables by default" checked affect the custom package variables that i created ? if so why?

Thanks,

This check box is used when you add new objects to the package.
It is also used when you open package first time and this package had no "After Execution Tab" before
once package is saved it has no impact on the existing package objects

Daniel

As promised we have added option to enable all variables in the package
v 5.8.3.14

Thanks for the fix.

We will look into this, but in the mean time we found if the unchecked the "disable all package variables' before we opened a "restored" respository database we were able to proceed. the enabled all will also help us.