After changing this field you will need to restart the browser or reload the application (User → Reload Application) to see the new value in the banner.

The default version of Excel to be used when exporting data from PhixFlow to Excel. This is only used if a non-valid excel extension, such as "csv", is used in the file name extension specified in the exporter. Otherwise PhixFlow will determine the correct format from the extension specified in the file name. See file exporters for details.

• "T" - By default, all users will be allowed access to the stream data.
• "F" - By default, no users will be allowed access to the stream data unless they are a member of a user group which is explicitly added to the stream.

• "T" - By default, all users will be allowed access to export functionality.
• "F" - By default, no users will be allowed access to export functionality unless they are specifically configured against the datasource.

The Url to open when the user requests online support through PhixFlow. Under normal circumstances you should not need to update this setting. If you have problem with PhixFlow help, please contact the PhixFlow support team (see the welcome page for contact details).

After changing this field you will need to restart the browser or reload the application (User → Reload Application) to start using the new help location.

The root location of all uploaded files and received email messages.

Uploaded files/processed emails are saved in standard sub-directories as follows:

.../tag/in/yyyymmdd/uid/

where

tag is the File Collector tag or the #tag extracted from an email subject line, or default

yyyymmdd is the date the files were uploaded / received

uid is a 32 character unique identifier

For each email message received, the folder will contain a file called body.txt representing the main body content of the email and also any corresponding email attachments.

Defines the default number of rows to be loaded into to a grid when displayed in PhixFlow. This is an advanced option which should not be updated without advice from the PhixFlow support team.

After changing this field you will need to restart the browser or reload the application (User → Reload Application) to apply the new default page size.

Specifies whether or not PhixFlow should check that an attribute exists when a model attempts to read the value of an attribute from a stream record or a record supplied by a collector. If not ticked, if no attribute could be found with the given name a null value is return. If ticked, PhixFlow will raise an error. 

It is strongly recommended that this flag is ticked.

Outgoing emails will only attach files (zipped or unzipped) that do not exceed this configuration limit. An extra message will appear in the email's message subject/body indicating to the recipient that a file attachment has been removed due to this size restriction.

PhixFlow will not impose any upper limit to the size of the attached files if this field is left blank, hence in this case the underlying email servers will determine if the message is sent/received correctly or not.

If required, you can set the maximum number of errors found, before exporters will stop attempting to export records.

This is useful where you process large number of records and do not want to wait until all records are processed in case of errors occurred. This value can be overridden in Exporters.

See Tasks and Task Plans for how to set up and run a System Task.

If not ticked, exceeding the cache size on a pipe will result in a warning message.

If ticked, cache sizes for in memory streams are strictly enforced; an in memory stream which tries to cache too many records will fail and an error will be reported.

If not ticked, exceeding the cache size on an in memory stream will result in a warning message.

The Data Storage Group to use when creating tables to store Stream data. This field is interpreted differently depending on the underlying database:

• On Oracle, a Data Storage Group is equivalent to a Tablespace.
• On SQL Server, a Data Storage Group is equivalent to a Filegroup.
• If no Data Storage Group is specified, the database user's default setting will be used.

• Database: Store the data in a regular table within the PhixFlow database. This is the most common option
• Database (Partitioned): Store the data in a partitioned table within the PhixFlow database. This option provides improved performance for rollback and archiving of very large Streamsets. The option is only available if "partitioning" is available within your database installation.
• In Memory: Data for the Stream will not be written to the database. This option can be used (for example) when you want to aggregate large amounts of unsorted data which can then be written to a stored Stream.

A Licence key issued with an expiry date. If the licence has expired an additional field will show the expiry date. After a licence has expired PhixFlow will generate warning messages in the analysis logs for 28 days beyond the expiry date. After this time analysis tasks will cease to run.

If this field is set, a System Task, when run, deletes Log Messages and Managed Files for Log Files older than this number of days. Temporary files created by File Exporters to send by email will also be deleted when the Managed File entry is deleted.

See Tasks and Task Plans for how to set up and run a System Task.

Whether to archive Log Messages to file before deletion. Archived Log Messages are written to archive files in the Archive Directory (see above).

There is no option to archive Managed File entries to file before deleting them.

If this field is set, a System Task, when run, deletes Emails older than this number of days.

There is no option to archive Email entries to file before deleting them.

Before performing a 'Reset Configuration' the administrator must tick this checkbox to allow access to reset the configuration.

WARNING: Resetting the configuration will delete all configuration data in the PhixFlow Instance.

See Configuration Reset for how to reset the configuration

Names can be separated by a semicolon but spaces around the semi-colon are considered part of the group name. E.g. 'group_1;group_2' is valid, but 'group_1;  group_2' is unlikely to be valid.

Names are case-independent.

Use {instance} to include the PhixFlow instance name if required.