Contents:
The following settings can be customized for the user experience in your workspace. When you modify a setting, the change is immediately applied to the workspace. To access the page, select User menu > Admin console > Workspace settings.
NOTE: Users may not experience the changed environment until each user refreshes the application page or logs out and in again.
Enablement Options:
NOTE: Any values specified in the Workspace Settings page applies exclusively to the specific workspace and override any system-level defaults.
| Option | Description |
|---|---|
Default | The default value is applied. This value may be inherited from higher level configuration. Tip: You can review the default value as part of the help text. |
Enabled | The setting is enabled. NOTE: If the setting applies to a feature, the feature is enabled. Additional configuration may be required. See below. |
Disabled | The setting is disabled. |
Edit | Click Edit to enter a specific value for the setting. |
API Access Token
When accessing the REST APIs, you can optionally use a token for simpler use and enhanced security.
NOTE: This feature may not be available in all environments.
NOTE: API access tokens must be enabled to use the API reference documentation available through the User menu.
Avro output format
When enabled, members can generate outputs in Avro format.
CSV output format
When enabled, members can generate outputs in CSV format.
Collaborative suggestions
If desired, you can enable the inclusion of suggestion cards that are generated from recent use of the Designer Cloud application. As the application gathers more information about how you or members of your workspace apply transformations to your data, the suggestions become more meaningful for the data that you are processing.
NOTE: No data is shared with Alteryx Inc. or any system outside of the Designer Cloud Powered by Trifacta platform.
These collaborative suggestion cards can be generated from individual usage or from workspace level usage. These suggestions appear under the Recently Used heading in the side panel.
NOTE: This feature requires the machine learning service, which is enabled by default. For more information, see Miscellaneous Configuration.
When this feature is enabled, individual users can still choose to opt-out of sharing their usage data with this feature. See User Profile Page.
| Option | Description |
|---|---|
disabled | Collaborative suggestions are not surfaced in the application. |
personal | Collaborative suggestions are based on the individual user's previous transformations. |
workspace | Collaborative suggestions are based on the transformations from all users in the workspace. |
Default | The default setting for the workspace is applied. |
For more information, see Overview of Predictive Transformation.
Column from examples
When enabled, users can access a tool through the column menus that enables creation of new columns based on example mappings from the selected column. For more information, see Overview of TBE.
Combine Spark Transform and Profile jobs into one.
When enabled, the transform and profiling tasks of a job executed on the Spark running environment are combined. The profiling task is executed as a part of the transform task, which eliminates any time spent orchestrating the profiling task and accessing the profiler input file on storage.
NOTE: When these two tasks are combined, publishing actions are not undertaken if the profiling task fails.
For more information on these actions, see Configure for Spark.
In the Job Details page, combined jobs appear in a Transform with profile card. See Job Details Page.
Connectivity feature
When enabled, workspace users can create connections to relational datasources.
NOTE: Disabling this feature hides existing relational connections.
Custom Spark Options Feature
When enabled, users can override Spark configuration options for output objects before running Spark jobs.
Tip: When enabled, a default set of Spark configuration options is available for users. Additional properties can be specified through the Spark Whitelist Properties setting.
Email notifications
When enabled, Designer Cloud Enterprise Edition can send email notifications to users based on the success or failure of jobs.
NOTE: This feature requires access to an SMTP server to send emails. For more information, see Enable SMTP Email Server Integration.
Email notifications: on job failure
When email notifications are enabled, you can configure the default setting for the types of failed jobs that generate an email to interested stakeholders. The value set here is the default value for each flow in the workspace.
Settings:
| Setting | Description |
|---|---|
Never | Email notifications are never sent for job failures. |
Scheduled | Notifications are sent only when scheduled jobs fail. |
Ad hoc | Notifications are sent only when ad-hoc (manually executed) jobs fail. Tip: Jobs executed via API are |
All | Notifications are sent for all job failures. |
Default | Notifications are sent based on the default settings for the product. |
Default setting for job failures is scheduled.
Individual users can opt out of receiving notifications or configure a different email address. See Email Notifications Page.
Emailed stakeholders are configured by individual flow. For more information, see Manage Flow Notifications Dialog.
Email notifications: on job success
When email notifications are enabled, you can configure the default setting for the types of successful jobs that generate an email to interested stakeholders. The value set here is the default value for each flow in the workspace.
For more information on the settings, see the previous section. Default setting is never.
Individual users can opt out of receiving notifications or configure a different email address. See Email Notifications Page.
Emailed stakeholders are configured by individual flow. For more information, see Manage Flow Notifications Dialog.
Enable S3 connectivity
When enabled, base connectivity to S3 is enabled for workspace users.
NOTE: Additional platform configuration is required. See Enable S3 Access.
Flow export
When enabled, workspace users are permitted to export their flow definitions into a ZIP file. Exported flows can be imported into other workspaces or product editions. See Export Flow.
Flow import
When enabled, workspace users are permitted to import exported flows from a ZIP file. See Import Flow.
Flow sharing
When enabled, workspace users are permitted to share flows with other users in the workspace. See Share a Flow.
Forbid users to add non-default publishing actions
When enabled, workspace users are not permitted to specify publishing actions, which can be used to control export of results to unexpected locations or systems.
Hide underlying file system to users
When enabled, workspace users cannot see locations in the default storage layer.
Hyper output format
When enabled, members can generate outputs in Hyper format for publication and use on Tableau Server.
JSON output format
When enabled, members can generate outputs in JSON format.
Locale
Set the locale to use for inferring or validating data in the application, such as numeric values or dates. The default is United States.
NOTE: After saving changes to your locale, refresh your page. Subsequent executions of the data inference service use the new locale settings.
For more information, see Locale Settings.
Logical and physical optimization of jobs
When enabled, the Designer Cloud application attempts to optimize job execution through logical optimizations of your recipe and physical optimizations of your recipes interactions with data.
NOTE: This feature requires the optimizer service, which is enabled by default, and the optimizer service database, which is installed by default. For more information on installing the database, see Install Databases.
This workspace setting can be overridden for individual flows. For more information, see Manage Flow Advanced Settings Dialog.
Parameterization
When enabled, users can create parameters, which can be applied to import, creating sample, and outputs. For more information, see Overview of Parameterization.
Parquet output format
When enabled, members can generate outputs in Parquet format.
Plan feature
When enabled, users can create plans to execute sequences of recipes across one or more flows. For more information, see Plans Page.
For more information on plans and orchestration, see Overview of Operationalization.
Product walkthroughs
When enabled, new members are led through a tour of the product. After the tour is dismissed, it does not re-appear again to the member.
NOTE: This feature may need to be enabled in your environment by an administrator. For more information, see Enable Onboarding Tour.
Publish actions
When enabled, users are permitted to create custom publishing actions for their jobs.
When disabled, users must accept the default publishing actions.
For more information, see Run Job Page.
Publish job results
When enabled, workspace users are permitted to publish results through the Output Destinations tab in the Job Details page to external datastores.
NOTE: These external datastores must be enabled and configured. See Connection Types.
For more information, see Job Details Page.
Sample downloads
When enabled, members can download the contents of the Transformer page at any time. For an individual step, a member can download the current sample, as modified by the current recipe up to the point of the current step. For more information, see Recipe Panel.
Schedule list
When enabled, administrators and workspace administrators can see a list of all schedules in the workspace.
Scheduling feature
When enabled, workspace users can schedule the execution of flows. See Add Schedule Dialog.
Schematized output
When enabled, all output columns are typecast to their annotated types. This feature is enabled by default.
Self service password reset
When enabled, workspace users can reset their own passwords via link on the login page.
Session duration
Specify the length of time in minutes before a session expires. Default is 10080 (one week).
Session Tags: Enable the use of session tags when assuming an IAM role
If you are using IAM roles to request temporary credentials for access to AWS resources, you can enable the use of session tags to make those requests. When a session tag is submitted, the Alteryx user is provided access to AWS resources based on the user's corresponding permissions within AWS, instead of having to specify those permissions in Designer Cloud Enterprise Edition. This method leverages the existing permission infrastructure in your enterprise and simplifies the use of IAM roles in the Designer Cloud application.
NOTE: After enabling the use of session tags, you must spin up a new EMR cluster, which forces EMR to use the newly deployed credential provider JAR file.
NOTE: Additional configuration is required. For more information, see Configure AWS Per-User Auth for Temporary Credentials.
Session Tags: The name of the session tag that holds the username as its value
When Session Tags: Enable the use of session tags when assuming an IAM role is enabled, you must specify the name of the session tag to be submitted to AWS containing the username of the Alteryx user requesting resources. Default value is trifacta-user.
For more information, see Configure AWS Per-User Auth for Temporary Credentials.
Show file location
When enabled, workspace users can see the locations of source and output files within the application.
Spark Whitelist Properties
Comma-separated list of additional Spark properties to be whitelisted for configuration of output objects while running Spark jobs.
NOTE: The Custom Spark Options feature must be enabled.
Storage directories
Allow members of the workspace to change paths to their upload and output results locations through their user profile. See Storage Config Page.
TDE output format
When enabled, members can generate outputs in TDE format for publication and use on Tableau Server format.
NOTE: TDE has been superseded by Hyper format. Please switch to using Hyper format instead. Support for TDE format will be deprecated in a future release.
Tableau Server output format
Sets the default format used for publishing to Tableau Server. Options:
AUTO- When set to auto:- Tableau Server version earlier than 10.5: publish format is TDE.
- Tableau Server version 10.5 and later: publish format is Hyper.
TDENOTE: TDE format has been superseded by the Hyper format. Please switch to using Hyper format. Support for TDE will be deprecated in a future release.
HYPERNOTE: Support for Hyper output format must be enabled.
UI for range join
When enabled, workspace users can specify join key matching across a range of values.
Upgrade to connectivity
When enabled, workspace users are presented with the option to upgrade to a plan that supports connection to external data sources, if the feature is current disabled.
Upgrade to flow sharing
When enabled, workspace users are presented with the option to upgrade to a plan that enables flow sharing, if the feature is current disabled.
Upgrade to scheduling
When enabled, workspace users are presented with the option to upgrade to a plan that enables scheduling the execution of flows, if the feature is current disabled.
Upgrade to upload large files
When enabled, workspace users are presented with the option to upgrade to a plan that supports uploading large files, if the feature is current disabled.
Webhooks
When enabled, webhook notification tasks can be configured on a per-flow basis in Flow View page. Webhook notifications allow you to deliver messages to third-party applications based on the success or failure of your job executions. For more information, see Create Flow Webhook Task.
NOTE: Additional configuration may be required. See Configure Webhooks.
This page has no comments.