Hexawise should allow users to constrain parameters, not just values

  • 8
  • Idea
  • Updated 8 years ago
  • Implemented
Hexawise should allow users to constrain an entire column (parameter), rather than having to select each individual value within that parameter.
Photo of Andrew Reagan

Andrew Reagan

  • 1 Post
  • 0 Reply Likes

Posted 10 years ago

  • 8
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
Andrew,

Thank you for your suggestion.

I can see how it would be useful to have the ability to constrain entire columns (e.g., selections of all the parameter values in a column) all at once. We are trying to balance "cool features" on the one hand against "a confusing number of choices" on the other. I'm not sure where we'll end up on this one. I'll mention this idea, along with other ones we receive, to clients and see how high a priority it is for them.

Thanks again for your idea. Please keep 'em coming. We really do appreciate it.

If anyone is reading this (and we still have not implemented it), please express your views with the "I like this idea!" button.

- Justin
Photo of julie.sheffield

julie.sheffield

  • 1 Post
  • 0 Reply Likes
I like this idea if what you mean is to create an invalid pair between a value for one parameter and an entire other parameter. My case is that I'm testing a rules engine. I have parameters for the field type of the left-hand side of a comparison and the right side. But if the comparison is Field A against a static value, the whole "Right Hand Side Field Type" parameter is moot.

That's just one simple example--this comes up all the time if you're testing any kind of use case with a decision tree--one choice early on invalidates an entire branch of the tree so it would be extremely useful to indicate which parameters are relevant given the values for earlier parameters.

Thanks!
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
Julie,

Thanks for your note and for your separate email offline. I look forward to talking tomorrow morning to discuss this in more detail.
Photo of Michael

Michael

  • 6 Posts
  • 0 Reply Likes
I would like to be able to do the above and also the ability to make and invalid pair that contains any combination of a identifier from a value expansion, a value, or a prarameter : )
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
Official Response
Thank you all for your feedback. We have implemented this idea now based on your feedback. The idea has been implemented in our "Married Pairs" feature.

Scenario:

You are testing a travel reservations site.
A customer may or may not rent a car (so parameter values for Car Rental could be: "Rent a Car" or "Do Not Rent a Car"
Values for Type of Car Transmission could be: "Manual" or "Automatic" or "N/A"

Simply hover over a Value name and then click on the green arrow that appears when you hover....

Select "Do Not Rent a Car" in this example. Next select "N/A." Confirm you're making a "bi-directional" married pair and you're done. There's no longer a need to create multiple separate invalid pairs.