Alteryx Server Ideas

Hi everyone,

Since the Home page has been replaced by the My Workspace page as the main page on the Gallery, end-users are getting confused or at least uncomfortable with this transition.

It would be amazing to change the default main page to the Public tab or even remove/deactivate the My Files tab for these users. 

Removing /deactivating the My Files tab will also correct an issue generated when an Artisan is downgraded to an end-user. Currently, these users can see their workflows in the My Files tab but can't access them.

Idea based on @phottovy 's question: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Change-quot-Public-quot-to-default-view-...

At some point we would like Alteryx Gallery to support SSO via SAML and Authorization via AD groups. The way I want is to have Authentication via SAML and Authorization via AD groups. For instance one of our apps Tableau: It does authentication via SAML (SSO) and for authorization, we import AD groups into Tableau thrice a day(stores the groups in a .xml file), once the groups are in the Tableau, we secure the objects within Tableau using that LDAP groups (which kind of become local groups after import). Basically the userid after the successful authentication step is used by the app for authorization.

I just stated Tableau as one of the ways to implement Authentication and Authorization for an enterprise app. If Alteryx Gallery needs to be an enterprise app, you will need to look into this idea. 

Thanks
Raj

Currently Alteryx has a timeout setting at a worker level which applies to all of the workflows/schedules that run on that node. 

It'd be great and very useful is that setting is made available at a granular level like at the Collection/User Group or workflow level. 

I've been told by Alteryx support that this is not a feature that is currently available. Hence proposing an Idea on the community requesting for such an ability!

Good Day.

We would like a built-in process that would search or, and resolve, workflows that are stuck in the "initializing" state. These seem to happen for various reasons but communication problems between the controller and workers .. usually a socket timeout.. which appears  to be most problematic. It seems  that these type of errors should be expected in all but the most stable environments,

Currently, the only tool that we have to solve this problem is to restart the Alteryx Service on the controller and while this works there tendency to cause some collateral damage in workflows ...erroring or restarting from their beginning.

There may be a way to solve this without restarting the service by editing Mongo using a tool like Robo 3T but that is unproven and has its own risk.

After dealing with this issue and struggling for quiet some time we think that the best option is to implement a "clean up" DB process that will run every 5 min or so, capture a list of workflows in the "initializing" state , then compare that list to one in the next 5 min cycle and fix any workflows that appear in both lists. We think that returning  any stuck workflows to the queued state would be the best Fix  option.

We just don't want to continue to use Restart the Service process to solve this issue and accept the collateral damage.

Thank you for your consideration

Tom D  

The workflow result window shows the Name/workflow, AMP, Priority, Assigned worker, Run as, Completed at, Runlenght, and Runtyp of the workflow. The following feature would also be useful on the page.

1. Showing the creation date of the workflow without taking queue time into consideration
2. The option to change the time zone would make it easier to analyze the logs
3. Detailed insight about the particular workflow results, such as average execution time, failure count, and success count with date filtering. 

Hello!
I found a weird bug in my travels today.

The TL:DR is that when a date input tool within the interface tool is used within a collapsing radio button, it defaults to "dd/mm/yyyy", breaking any app when this is not filled out: 

Both values are default - i have not edited these values. The weirdest part is, this is Server/Private Gallery specific. When this workflow is downloaded and run within Designer:

And the workflow runs fine.

I have not tested this with any of the other interface tools, however I suspect this to not be the only tool this issue resides within.

I have attached the workflow I used (not that it would take long to recreate) for testing.

Hello Alteryx Developers,

It would be great if you develop a way to connect the Alteryx Designer to AWS Redshift by SSO. When i try to set this type of connection at the Simba ODBC Driver it opens the connection several times with AWS at the browser and that ruin the customer experience.

Best Regards

Danilo Benjamin

It would be nice to have workflow version information on the Workflow Results page for every running status.
The reason for that is after workflow was scheduled and then the published version has been changed, there is no way to follow versions.

Can we make API function available to assign specific worker node while submitting job request using api.

The job timeout function is a perinate issue on the the Alteryx server because scheduling workflows on the server that overlap with another workflow can cause bottleneck issues. Depending on the number of workers and the other workflows, the workflow in question could fail to run or not complete running at the desired date and time. I recommend a view option of the Schedule Forecast feature for all users, so as to allow all users to effectively schedule workflows on the Alteryx server that do no conflict with other workflows. 

Can we add an ability to manually adjust the order of workflows in a collection? I don't think we should have to go and click the column to sort each time if we want them in alphabetical order. It looks better for the end user to have everything nice an arranged when you have multiple processes in each collection.

When rerunning a failed manual job, the same Priority is used, but the Optional Job Name is not and cannot be re-entered on submit.  User has to go to Workflow results page and Edit to add the Optional Job Name for a rerun.

I suggest the Optional Job Name text box be added to the rerun submit page.

Prefill using the original job's value if one exists.

Thanks,

MJ

As we look at upgrading Alteryx Server - one of the challenges is that it's an all-or-nothing approach; and there doesn't seem to be a guided wizard approach to upgrading.

The upgrade process would be much less intimidating if we could create a Migration tool which can work across versions - similar to Microsoft SQL Server which has the.    This would allow us to:
- Migrate a subset of assets up or down versions

- Migrate across servers to do consolidation or to split loads into different servers for the purpose of segregation

- Progressively migrate over time to limit the risk.

cc: @JohnPelletier 

Hello, Alteryx users,

My idea is simple but would make things way easier for the analytical app users on the Gallery.

Currently, the order is ascending and we can see all the files from all the applications we have run before.

It would help a million to see the most recent files first and only see the files related to this workflow.

Thank you,

Fernando Vizcaino

Some of our artisans are unable to publish straight from designer and it would be great if there was an "Upload workflow" button in the private studio just like there is for curators in the admin panel.

Currently, DCM credentials appear to only be used in combination with a DCM Data Source.  

For ease of use for my end users (non-Designers), I would like my end users to be able to save a user ID and password as a standalone DCM credential.  Then, I want the user to have the option to select that credential for use in two places:

1.  Run-As - when running a workflow on demand, the user should be able to choose their saved DCM credential.
2. Credential injection into Input Data or other relevant tools in Analytic Apps - I want to use the DCM Connection tool to build Analytic Apps that prompt my users to select their DCM Credential (NOT a full DCM Connection with data source - I don't want my users to have to set that up.)  When the user selects their Credential, their user ID and password should be securely encrypted and inserted into the existing connection set up by the App designer.

Having this functionality would remove administrative burden from both our Designers and the end users they support.

Currently when we need to disable/enable schedule on API,we need to update all the schedule info,could you provide only one attribute to disable.

Can we just update on parameter

"enabled": true, --> "enabled": false

current update example,we need update all

{
"workflowId": "string",
"ownerId": "string",
"iteration": {
"iterationType": "Once",
"startTime": "2022-09-06T08:01:52.717Z",
"endTime": "2022-09-06T08:01:52.717Z",
"hourlyContract": {
"hours": 0,
"minutes": 0
},
"dailyContract": {
"runOnlyWorkWeek": true
},
"weeklyContract": {
"daysOfWeek": [
"Sunday"
]
},
"monthlyContract": {
"simpleDayOfMonth": true,
"dayOfMonth": 0,
"occurrence": 0,
"dayOfWeek": "Sunday"
},
"customContract": {
"daysOfMonth": [
0
],
"months": [
0
]
}
},
"name": "string",
"comment": "string",
"priority": "Default",
"workerTag": "string",
"enabled": true,
"credentialId": "string"
}

We have the Local License Server installed.  Right now, if a Designer user changes roles, or leaves the company, they have to release their license from their client-side machine.  If they don't release it properly, and IT can't get us into their machines, then we have to wait 7 days for that license to roll off the server.  There should be a way for a system admin to forcefully revoke someone's license.

We have situations where some workflows that are scheduled end up having intermittent connection issues to other databases that result in the workflow running to timeout. The timeout settings are set in the server, but it would be nice if you could set an override value for a lesser timeout in the runtime settings for individual workflows and basically use the server setting as a not to exceed value. We have a multi-node environment with multiple worker nodes and about 250 artisans. We have some regularly scheduled workflows taking the full amount of time in the timeout setting and obviously if a couple of normally quick running workflows ran to timeout that causes issues with the queue.