Programmatic checks for canvases before allowing push to production

[Deeksha]

We uncovered a possibility  in which the user  may potentially output a huge file into the Alteryx database  without specifying an external system to house it - which could  possibly take up a lot of space in the  database we use for running Alteryx (store schedules, user and run data to name a few), this  may even bring down the environment  and sure doesn't seem like a good practice.

Can you please   include  a  check  to ensure that  this  can be disabled or capped ( specify a limit on the size) ?

[SeanAdams]

Tremendous idea @Deeksha - this seems like a good run-time cap, where the admins could specify something like "no job can store more than 10Mb of data" - as well as an option to store the job-related blob data (like temporary outputs or input files) in a different database so that we can segment this for info security reasons.

Very good idea!

[Community_Admin]

The status of this idea has been changed to 'Inactive'. This status indicates that:

1. The idea has not had activity in the form of likes or comments in over a year.

2. The idea has not reached ten likes.

3. The idea is still in the 'New Idea' status. 

However, this doesn't mean your idea won't be implemented! The Community can still like and comment on this idea. With enough renewed interest, this idea can be brought back into the 'New Idea' status. 

Thank you for contributing to the Alteryx Community and the Alteryx Product Idea Boards!