Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

Setting up default values in Configuration Variables #733

puneetg ·
Hi,

Is there a way to setup default values/selections in Configuration variables?

I have a "prompt as text input" UI element, where I would like to read a file and present it to user for alteration.

In another case, I have a "prompt as selection box" and would like to have first element selected. This shows empty now.

thanks
-Puneet
  • replies 14
  • views 4268
  • stars 0
robinshen ADMIN ·
The value specified when define the variable will be used as default value for the first time when an user triggers the build, however subsequent build will remember the value selected last time. If you want to use default value for subsequent builds, just specify the variable as "allowed to be empty" when define its prompt setting. And if the variable is left empty when build is triggered, the default value will be used. Taking Windows for example, if you have a "prompt as text input" variable with "allowed to be empty" set to true, and if the value is set to ${util.readOutput("cmd /c cat d:\temp\file")}, the variable value will be read from the file "d:\temp\file" if it is left empty at build time.
This default behavior also applies when variable is set to "prompt as selection box".
puneetg ·
Thank you Robin

I understand the defaults will be read and triggered once the step is executed.

Is there any way to populate the UI elements with default value first time?

In my workflow, I would like the users to see the build config spec as default but would have ability to alter.

thanks again
-Puneet
robinshen ADMIN ·
Do you mean that instead of using last specified value, the default value should be prompted each time the build is manually triggered? If so, QuickBuild does not provide this option, and you may submit an enhancement request at http://track.pmease.com
puneetg ·
Robin

Yes this is what I am looking for.

thanks
-Puneet
roger ·
Sounds like this feature request... http://track.pmease.com/browse/QB-461

-r
boeyeb ·
[quote="robinshine"]The value specified when define the variable will be used as default value for the first time when an user triggers the build, however subsequent build will remember the value selected last time. If you want to use default value for subsequent builds, just specify the variable as "allowed to be empty" when define its prompt setting. And if the variable is left empty when build is triggered, the default value will be used. Taking Windows for example, if you have a "prompt as text input" variable with "allowed to be empty" set to true, and if the value is set to ${util.readOutput("cmd /c cat d:\temp\file")}, the variable value will be read from the file "d:\temp\file" if it is left empty at build time.
This default behavior also applies when variable is set to "prompt as selection box".[/quote]

Is it possible that value is calculated every time "run" is hit instead of first time? That will serve our (puneetg) purpose.
robinshen ADMIN ·
Once the issue mentioned in this thread is implemented, QB2 will be able to re-calculate the variable value every time instead of just the first time.

Regards
Robin
puneetg ·
Hi Robin

QB461 or parameters evaluation everytime run is executed is very important for our workflow. Is this a feature request or a bug?

thanks
-Puneet
robinshen ADMIN ·
This is an improvement request rather than a bug, we will try to get it addressed in version 2.1

Thanks
Robin
puneetg ·
Thanks very much Robin

-Puneet
boeyeb ·
Thanks Robin. What is ETA for 2.1?
robinshen ADMIN ·
We plan to get it released at Jan, 2010.

Thanks
Robin
robinshen ADMIN ·
Yes, this is done in 2.1. Just uncheck the "remember" option when define prompt setting of the variable.
ShawnGriffin ·

Hello, I am new to your forum as of today.. I am from Alberta, Canada. I am really happy to be a member of this forum. thanks.