Action conditions in GUI vs CMD mode behave differently!

FinalBuilder Discussion
1

Hi,

I'm trying to run the same build from the GUI and sometimes from FBCMD. I see some behavioral differences when it comes to evaluating action conditions.

For example if I have in one action group condition:
BUILDSORTER = True

if I click it in the Multiquestion dialog in the GUI it is set to true and everything's ok.
if I pass /VBUILDSORTER=True to FBCMD it will be skipped
if I pass /VBUILDSORTER=1 to FBCMD it is skipped

When I write BUILDSORTER in the action condition (my usual way)
if I pass /VBUILDSORTER=True to FBCMD it will work ok BUT if I don't pass anything (if I don't want to build sorter) then the condition fails and all the project with it
------------------------------------------------------
Error In Execute Condition (VBScript)
Sorter : Invalid argument
This Action did not execute.
------------------------------------------------------
(Sorter is the name of the action group on which the condition works)

So basically, I can't find a way in which both the GUI and CMD builds evaluates the condition in the same way.


Please help
Thanks,

NirS

2

Hi Nir,

It may be that you need to set the default value of the variable to False (rather than blank), but at the moment a blank value works fine for us here. VBScript is pretty forgiving about types.

Which FinalBuilder version are you using? Would it be possible for you to please send the project file to support@finalbuilder.com?

Regards,

Angus

3

OK I set all the variables to false by default, and it works fine now.

Thanks,
NirS