Alteryx Designer Desktop Ideas

Hi Team,

I understand there is no .dmg i.e. direct macOS installation package is available to install directly on Mac instead we have to use other third party apps to install WindowsOS and then use it.

However I would suggest that if Alteryx can have a web version or something called Alteryx Public (similarly that Tableau has for their users) which users can use and explore the tools with limited to basics functions and to understand the UI and experience the tool itself by having hand-on it.

Please find the below Tableau Public snapshot for reference purpose.

I am looking forward as I am keen on exploring Alteryx as a beginner and become expert one day :)

Thanks,

Sachin

To rename a workflow, usually we have to save and then name the workflow. Could you please consider adding a feature of renaming a workflow after "Close" & "Duplicate"?

Hello all,

As of today, the error message when trying to activate a license doesn't give any useful information :

I want to know :
-do I manage to access to the Alteryx Licensing? (so maybe a security/proxy issue.. so I have to contact my IT)
edit : for that there is another message usually

-is the key correct but not more seats? (so I have to contact the Alteryx License manager) Or another issue?
Here, I perfectly know the license key is correct so the error message is really misleading.
-also displaying the machine id as it appears on the License portal would help.
-and anything that can be helpful to debug.

Best regards,

Simon

I am using Alteryx as an ETL Tool and then QlikSense for data visualization.

Alteryx only gives QVX outputs which are the old version QlikView files. It works for QlikSense but it slows down the system. So, the QlikSense support suggested using QVD outputs. 

I want to suggest supporting QVD files as QlikSense is being used more widely instead of QlikView, most users are migrating to QlikSense.

It would be more useful and efficient if Alteryx supports latest file format.

When a workflow runs on the server and the server tells me there was an error with Tool ID 103, I'd like to be able to open that workflow in my designer and search for that Tool ID 103.  We have some really large workflows and it takes a long time to manually locate that tool.

It would be great if you could include a new Parse tool to process Business Glossary concepts formatted using the SKOS (W3C) standard in the next version of Alteryx.

SKOS is a widely used standard for the representation of concept and term relationships. It provides a consistent way to define and organize concepts (including versioning), which is essential for the interoperability of these data.

We believe that supporting SKOS in Alteryx would be a valuable addition to the product. It would allow us to:

• Improve the interoperability of our data sets with other systems (M2M)
• Make it easier to share and reuse our data sets
• Provide a more consistent way to describe our data sets
• Bring down the costs of describing and developing interfaces with other Government Entities
• Work on some parts of making our data Findable – Accessible – Interopable - Reusable (FAIR)

We understand that implementing support for this standards requires some development effort (eventually done in stages, building from a minimal viable support to a full-blown support). However, we believe that the benefits to the Alteryx Community worldwide and Alteryx as a top-quality data preparation tool outweigh the cost.

I also expect the effort to be manageable (perhaps a macro will do as a start) when you see the standard RDF syntax being used, which is similar to JSON.

SKOS, which stands for Simple Knowledge Organization System, is a W3C Recommendation for representing controlled vocabularies in RDF. It provides a set of classes and properties for describing concepts, their relationships, and their labels. This allows KOS to be shared and exchanged more easily, and it also makes it possible to use KOS data in Semantic Web applications.

SKOS is designed to be flexible and extensible, so they can be used to describe a wide variety. They are both also designed to be interoperable, so they can be used together to create rich and interconnected descriptions of data and knowledge.

Here are some of the benefits of using SKOS:

• Improved discoverability: SKOS makes it easier to discover and use KOS, as they provide a standard way of describing their attributes.
• Increased interoperability: SKOS allows KOS to be integrated with other Semantic Web applications, making it possible to create more powerful and interoperable applications.
• Enhanced semantic richness: SKOS provides a way to add semantic richness to KOS , making it possible to describe them in a more detailed and nuanced way.

Here are some examples of how SKOS and DCAT are being used:

• The Library of Congress uses SKOS to describe its controlled vocabularies.
• The Dutch Government made it a mandatory standard for all Dutch Government Agencies.

As the Semantic Web continues to grow, SKOS is likely to become even more widely used.

SKOS

• Reference Page: https://www.w3.org/TR/skos-reference/
• Dutch (NL) Standard: https://forumstandaardisatie.nl/open-standaarden/skos
• WIKI Pedia on SKOS: https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System
• Video: https://youtu.be/pbTRDDQ43Sw?si=RG3f-jPBsx2OK8IQ
• Tools: https://csiro-enviro-informatics.github.io/info-engineering/semantic-tools.html

RDF

• Reference Page: https://www.w3.org/TR/REC-rdf-syntax/
• Dutch (NL) Standard: https://forumstandaardisatie.nl/open-standaarden/rdf
• WIKI Pedia on DCAT: https://en.wikipedia.org/wiki/Resource_Description_Framework

This is a question which is somehow in between Designer and Gallery ideas.

When saving a workflow to the Gallery, the user can select the Assets (elements which are also copied to the Gallery). The point in time during the save process is a bit questionable from my perspective.

Often, I develop workflows locally until they reach a state in which I want to move them to the Gallery so that they can be included in Schedules or be made available to other users. I would like to be able to select which macros or datafiles are copied to the Gallery as well much earlier in the development process. From my perspective, it would be great if the user could set the Assets settings in the "Workflow Dependencies" window as well. I propose 3 possible values for each element (macro or data file):

• "Auto" → decide on asset when saving the workflow to the Gallery (current behaviour)
• "Yes" → Copy this element as asset in the Gallery
• "No" → Do not copy this element to the Gallery 
• "N/A" → The question does not apply to this row (e.g., directory)

It could look like this:

Hi, as a person with a mapping background, I love that Alteryx added zoom & pan abilities. The hold ctrl + mouse wheel zoom is great! Also, the hold space to pan is great as well. My only issue is this function should still work if the process is running, can you implement?

When I open I'd workflow, I'd like the option click on "something" to see content previous created for the workflow.  The content I'd use most frequently is:  How was the INPUT data obtained?  ALL of the Alteryx workflows I will be creating with my current employer will require some level of pre-build of the data sources.  I would like to document the pre-build requirements (could be pages of text, so "comments" aren't optimal) and be able to ask for them as needed.

Optimally, this feature would accept .docx, .pdf and other standard formats.  Another option would be to support a URL that would link me to the content.  For my purposes, this would be even more advantageous as all of our knowledge content is on-line.

One of things I like to do is select a bunch of tools and to see the collective performance of particular part of a workflow. It would be super cool if these stats were aggregated. 

I could imagine then you could run alternative solutions side by side and then just select the tools involved to compare.

Currently, Control Containers only report in case they are activated:

Info: Control Container (3): Control Container Activated.
...
Info: Control Container (3): Control Container Completed.

It would be very helpful to also get information on disabled Control Containers:

Info: Control Container (3): Control Container Deactivated.

Currently, Cache and Run Workflow cannot be used if there's a second branch of data which goes around the tool which you want to cache. This slows down intermediate runs especially in complex workflows with a lot of inter-dependencies.

For example:

If you want to cache at the formula "Do something", Alteryx will not allow this because a single temporary cache file at this tool will not be sufficient:

My suggestion is that Alteryx allows multiple cache files for one single cache event. In this case:

Proposed process:

1. Run the cache run from the initial source(s) of data (here the Text Input tool) via all tools needed to produce the output of the selected tool (here Formula "Do something"). In this case: Text Input, left Select, Formula.
2. Produce a cache file for every tool which has a connection towards outside of the direct tool chain. In this case: Cache file 2 (as Alteryx does it today), Cache file 1 (new behaviour)

This way, I could use Cache and Run Workflow much more often which would save me a lot of time. 

When the user has no internet connection or when the Help > Source setting is set to "Offline", clicking on a custom tool's help icon will always navigate to

• [AlteryxInstallDirectory]/bin/RuntimeData/HtmlAssets/help.alteryx.com/AlteryxCurrent/en/[helpURL]

which is practically never desirable for custom tools.

Specifying an offline help URL

Developers should have a way to (optionally) specify an offline help URL. This configuration could behave the same as `help_url` which already supports specifying both URLs and local files. If the offline help URL is not set, it would fallback to the `help_url` configuration.

{
  "tools": {
    "MyCustomTool": {
      "configuration": {
        "help_url": "https://mywebsite.com/help/my-custom-tool",
        "offline_help_url": "file://help/my-custom-tool.html"
      }
    }
  }
}

All built-in tools have their names, descriptions, help URLs, etc. localized to the currently selected locale. Custom tools should also be able to do this.

Specify localized configuration values

Developers should have a way to specify localized values for any locales they choose to support. Similar to the deprecated .yxlang files, this can be done with supplementary `ayx_workspace.[locale].json` files that redefine a subset of configurations which support internationalization.

/* ayx_workspace.jp.json */
{
  "tools": {
    "MyCustomTool": {
      "configuration": {
        "long_name": "カスタムツール",
        "description": "これは日本語です",
        "help_url": "https://mywebsite.com/help/jp/my-custom-tool"
      }
    }
  }
}

All built-in Designer tools have an associated example workflow that can be opened by right-clicking a tool and selecting Open Example. This feature is invaluable in helping users familiarize themselves with a tool and explore all of its features. Custom tools should be able to specify example workflows of their own.

It is currently possible to specify an example workflow, but

1. The workflow must be specified by modifying a tool's `Config.xml` file, where changes may be overwritten by the SDK.
2. All paths are relative to `[AlteryxInstallDirectory]\Samples\[locale]\02 Learn_one_tool_at_a_time`, and there is no easy way to install workflows into this directory.

Specifying an example workflow

Developers should have a way to specify the example workflow associated with any custom tool. This would likely be done in the `ayx_workspace.json` file.

{
  "tools": {
    "MyCustomTool": {
      "configuration": {
        "example_path": "configuration\\MyCustomTool_1_0\\example.yxmd"
      }
    }
  }
}

Note that a workflow may depend on some external files as well. It would be ideal if an `assets_path` could be defined to easily allow any arbitrary assets to be included with your tool. (This is currently possible, but must be done by manually modifying the .yxi archive; it isn't handled by the SDK). This would easily allow for example workflows to be specified as a path relative to `assets_path`, and if the workflow contains any relative paths to files within the assets folder, they can be resolved.

{
  "tools": {
    "MyCustomTool": {
      "configuration": {
        "assets_path": "configuration\\MyCustomTool_1_0\\assets",
        "example_path": "example\\example.yxmd"
      }
    }
  }
}

Localization of the example workflow would also be supported when localization of the plugin configuration is supported.

When a plugin is created, it can be labelled with any tool category, existent or non-existent. If the category does not exist, Designer will create it and give it a default icon. It would be nice if a category icon could also be specified, specifically for this case.

Specifying a tool category icon

Developers would have a way to (optionally) specify the tool category icon for their plugin. This would likely be part of `ayx_workspace.json`.

{
  "name": "My Plugin",
  "tool_category": "Custom Category",
  "tool_category_icon_path": "configuration\\tool_category_icon.png",
  "package_icon_path": "configuration\\package_icon.png",
  ...
}

Behavior when installing a plugin

If a plugin has a tool category icon specified, Designer should do the following when installing the plugin:

• If the tool category already exists and has an icon, no changes are made
• If the tool category already exists and does not have an icon set, the category is updated with the specified icon
• If the tool category does not exist, the category is made and its icon is set to the specified icon

This prevents changing the icons of existing categories (including built-in categories), but would prevent subsequent plugin versions from updating their tool category icons.

Use case

The company Acme Corporation develops a plugin for interfacing with Acme-related products, and would like all its tools to be grouped in a new category called "Acme" whose icon is the Acme icon.

It would be nice to create our own custom categories to be able to organize tools. It would be similar to how the Favorites category works, but any number of additional categories can be created.

Creating a new category

The user would have a way to create a new category and enter the following information:

• The category's name
• The category's icon
  • There could be a number of premade icons to select from

Adding and removing tools from custom categories

The user would have a way to add tools to or remove tools from the custom categories.

In many programming languages, errors can be thrown and caught so that the final program does not fail even if a procedure or function produces an error.

I would like to propose something similar for Alteryx, using the Control Containers. Already now, a Control Container outputs the log in the container to its output stream on the upper right corner:

Still, the workflow produces an error:

My idea is to optionally avoid the error output to the log but only report the error through the control container's output log. The error message in the output log should be "degraded" to a warning. The output log of the control container should stay unchanged. The configuration of the Control Container could look like this (addition in red):

This would help a lot if stuff produced by others is used (e.g., third party macros) which might fail while this might be normal behaviour for the workflow.

いつも大変お世話になっております。本日は、製品の動作環境についてご相談させていただきたく、ご連絡いたしました。

弊社のお客様の中には、Windowsのユーザー名やフォルダ名に日本語を使用している方々が多く存在します。

現状、こうした日本語環境でのAlteryx製品の動作保証が明確にされていないため、問題が発生した際の対応に困難を感じております。

したがって、Windowsの日本語ユーザー名、または日本語のフォルダ名を使用した環境における

Alteryx製品の動作保証について、再検討をお願いできますでしょうか？

これにより、お客様へのサポートがより円滑に行えると考えております。

お忙しいところ恐縮ですが、具体的な方針や計画についてご教示いただければ幸いです。何卒、よろしくお願い申し上げます。