This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Oh no! The Community appears to be haunted! Help us find all the spooky specters here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email firstname.lastname@example.org for assistance.
on 11-11-201512:49 PM - edited on 07-27-202111:45 PM by APIUserOpsDM
Alteryx Analytic Applications (Apps) are very useful. They let us take a process, parameterize parts of it, and add an interface so that end users don't need to know all of the inner workings of the process in order to make it work for their specific scenario. We can even take an app and publish it to an Alteryx Gallery so the process can be shared with someone who doesn't even have Alteryx installed on their machine.
A common question we hear from app builders is, "how do I make the choices presented for one interface question depend on a previously answered interface question?". This is primarily accomplished by chaining multiple apps together such that the results from App #1 dynamically provide the options for a drop down or listbox question in App #2. Step 1 and Step 2 in the attached package provide an example.
What if the question you want to update is not a drop down or listbox? You can actually use App #1 to dynamically update the raw XML controlling the question (or any tool) in App #2 prior to presenting the questions of App #2 to the user. Step 2 and Step 3 in the attached package provide an example.
Less often, we are asked how we can create what I like to call a "feedback loop" in the interface. This involves the user of the app filling out a set of questions, seeing some result from those questions, and deciding whether to continue forward or go back to modify their initial selections. This can be accomplished using the same idea of modifying the XML to dynamically decide which app becomes the next link of the chain in a process. Step 3 in the attached package is an example that will either move on to a real step 4 if the user is happy with the results from Steps 1-3 or will loop back to Step 2 so the user can modify their initial selections. They can continue in the loop, modifying their selections in Step 2 over and over until they are satisfied with the results and choose to move on to step 4.
The attached package contains an example for each of these options with a few notes calling out the different examples.
Please note that both options involving modification of an app's XML will not work in an Alteryx Gallery because any app run by the gallery must be verified by the server ahead of time and there is no way to build this verification step into the app.