{dialog.object}.argumentValue is no longer returning the correct value.
Using latest version of Alpha (3670_4684).
Steps to reproduce in UX Component:
1. Create new UX Component.
2. Create Argument from Properties -> Arguments. For the sake of testing, set argument name to "TestArg". Set argument value to "test"
3. Create a button control.
4. In Click Javascript event, set code type to Text Mode, and insert this code: alert({dialog.object}.argumentValue('TestArg').toLowerCase());
5. If you open the console, you will see the error that you can't call toLowerCase() on undefined.
If you remove toLowerCase() from the function, it should alert undefined.
This error is causing much of our code to break. We have a huge app built in alpha that uses argumentValue() in many locations, and many of those locations we use .toLowerCase() to ensure we check for the correct value regardless of case. We also have checks to see if the argument is blank by checking for either "" or "__notSet__", which is now evaluating incorrectly because the argument is always undefined. In the previous version of alpha that we were using (2999_4519), if we used argumentValue() it would return "__notSet__" if the argument has not yet been set.
Is there some easy way to fix this that would fix it everywhere without having to go through the entire application to look for every place we use argumentValue(), or will this require a patch from Alpha? The current part of the project that we are working on is time sensitive, so we really need a solution for this quickly.
While I'm on the topic, is there an "official" place to submit bug reports to Alpha, or is this forum the only place?
Thanks.
Using latest version of Alpha (3670_4684).
Steps to reproduce in UX Component:
1. Create new UX Component.
2. Create Argument from Properties -> Arguments. For the sake of testing, set argument name to "TestArg". Set argument value to "test"
3. Create a button control.
4. In Click Javascript event, set code type to Text Mode, and insert this code: alert({dialog.object}.argumentValue('TestArg').toLowerCase());
5. If you open the console, you will see the error that you can't call toLowerCase() on undefined.
If you remove toLowerCase() from the function, it should alert undefined.
This error is causing much of our code to break. We have a huge app built in alpha that uses argumentValue() in many locations, and many of those locations we use .toLowerCase() to ensure we check for the correct value regardless of case. We also have checks to see if the argument is blank by checking for either "" or "__notSet__", which is now evaluating incorrectly because the argument is always undefined. In the previous version of alpha that we were using (2999_4519), if we used argumentValue() it would return "__notSet__" if the argument has not yet been set.
Is there some easy way to fix this that would fix it everywhere without having to go through the entire application to look for every place we use argumentValue(), or will this require a patch from Alpha? The current part of the project that we are working on is time sensitive, so we really need a solution for this quickly.
While I'm on the topic, is there an "official" place to submit bug reports to Alpha, or is this forum the only place?
Thanks.
Comment