In many cases you need some kind of a script to install an application, not fore the installation itself but for customize behaviour or configuration. This scripts are often customized for the specific application and very seldom in need of parameters or switches, but for those special occasions where you just want to use a command with parameters you should know how to follow best practice.
setup.exe /quit /log=debug /endpoint=upkeeper.se
If you have made application packages in upKeeper you know the routine and the best practice using script files for installation command. You may even made some packages using application installation command with a few parameters directly entered into the command field in upKeeper, with success. But when you try to make an application installation command with multiple or complex parameters adding them to the command field it will fail.
The command field in upKeeper is built to contain application installation commands and nothing else, but it can handle a few parameters as long as the text length don't exceed the field limit of 64 chars or the complexity affects how upKeeper interpret the content.
Best way to handle parameters in combination with commands is to enter the parameters into the parameters field and separate them from the command. The parameters field is handled as parameters at the execution which increase quality and interpret success dramatically. Parameters field can contain up to 512 chars and are there for more suitable for long strings of parameters or switches.
Hope your next application package have parameters in the parameters field.