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.
We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.
I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.
The basic concept behind this idea is to allow us (users) to have:
Repetitive patterns to be reusable.
Select after and Input tool
Get not matching records from join
Tell Alteryx to execute some logic if something happens.
Any other condition
Order of execution
Need to tell Alteryx what to run first, what to run next, and so on…
Run this first
Execute this portion after previous finished
Wait until “X” finishes to execute “Y”
Putting all together
This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:
The approach is to extend Tool Container’s attributes.
This proposition uses actual functionalities we already have in Designer.
So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:
Refers to the actual interface of the Tool Container.
Provides the ability to disable a Container (and all tools within) once it runs.
Idea based on actual behavior: When we enable or disable a Tool Container from an interface Tool.
Input and output data to the container’s logic, will allow to pickup and/or save files from a particular container, to be used in later containers or persist data as a partial result from the entire workflow’s logic (for example updating a dimensions table)
Based on actual behavior: Input & Output Data, Cache, Run Command Tools, and some macros like Prepare Attachment.
Order of Execution: Can be Absolute or Relative. In case of Absolute run, we take the containers in order, executing their contents. If Relative, we have the options to configure which container should run before and after, block until previous container finishes or wait until this container finishes prior to execute next container in list.
Based on actual behavior: Block until done, Cache, Find Replace, some interface Designer capabilities (for chained apps for example), macros’ basic behaviors.
Conditional Execution: In order to be able to conditionally execute other containers, conditions must be evaluated. In this case, the idea is to evaluate conditions within the data, interface tools or Error/Warnings occurrence.
Based on actual behavior: Filter tool, some Interface Tools, test Tool, Cache, Select.
Notes: Documentation text that will appear automatically inside the container, with options to place it on top or below the tools, or hide it.
This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:
This has probably been mentioned before, but in case it hasn't....
Right now, if the dynamic input tool skips a file (which it often does!) it just appears as a warning and continues processing. Whilst this is still useful to continue processing, could it be built as an option in the tool to select a 'error if files are skipped'?
Right now it is either easy to miss this is happening, or in production / on server you may want this process to be stopped.
I often need to create a record ID that automatically increments but grouped by a specific field. I currently do it using the Multi-Row Formula tool doing [Field-1:ID]+1 because there is no group by option in the Record ID tool.
Also, sometimes I need to start at 0 but the Multi-Row Formula tool doesn't allow this so I have to use a Formula tool right after to subtract 1.
So adding a group by option to the Record ID tool would allow the user not to use the multi-row formula to do this and to start at any value wanted.
Love the new updates to the Browse tool in 2019.2! However, if you choose the option Open results in new window, which I do often so I can see my whole dataset, the search/filter/sort functionality goes away. Would be great if that new functionality also worked in the new window. Thanks!
I would like to suggest that the licensing process is enhanced to work more effectively within a Citrix environment that has many servers in the farm.
When using a citrix environment it is not possible to register muliple users on a single citrix server with unique email addresses as the license is removed from an existing registered user when another user registers on the same citrix server. The License Server however does not reflect this and each user retains an allocated license on the license server even though they cannot use Alteryx Designer on the citrix desktop.
Alteryx have provided a workaround which is to use a generic email address to register each user and in this way the licenses are not removed as each new user registers.
Unfortunatley when a user unregisters a License the license is removed from the whole machine therefore no users on the machine are then able to use Alteryx Designer. In order to work around this we have had to schedule a daily job to run the license delete command from each server in our citrix farm.
This is not an ideal solution.
What we would like to see is user license seperation so that we can register the license to the users own email address at login and then remove the license for just that user at logout. This would ensure that the licenses are allocated to the user and machine as needed and we would not run the risk of running out of licenses if users log on and off different sessions over the course of a day logging on to different servers as the licenses are only revoked at the end of each day.